Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-45630

Ignite configure MessageQueueLimit, CollisionSpi, CheckpointSpi

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 21.0
    • Fix Version/s: 21.1, 22.0 [Tentative]
    • Component/s: Kernel
    • Labels:
      None
    • 21 Status:
      Merged
    • Test Plan:
      Hide

      Look in logs for these messages

      Show
      Look in logs for these messages

      Description

      Ignite emits a number of warning in the logs:

      • Work Directory
      WARN [main] org.apache.ignite.internal.util.typedef.G.warn Ignite work directory is not provided, automatically resolved to: 
      • Message Queue Limit
      WARN [main] org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.warn Message queue limit is set to 0 which may lead to potential OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to message queues growth on sender and receiver sides.
      • Checkpoints
      WARN [main] org.apache.ignite.spi.checkpoint.noop.NoopCheckpointSpi.warn Checkpoints are disabled (to enable configure any GridCheckpointSpi implementation)
      • Collisions
      WARN [main] org.apache.ignite.internal.managers.collision.GridCollisionManager.warn Collision resolution is disabled (all jobs will be activated upon arrival).

        Gliffy Diagrams

          Zeplin

            Attachments

              Activity

                People

                Assignee:
                ern Earle R Nietzel
                Reporter:
                ern Earle R Nietzel
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Git Integration