Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-23597

Idle Raft Replicator eats too much CPU

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      I noted that nodes of an idle cluster (taking no transactional load) which has 3 nodes and 1200 partitions (replication factor is 2 so there is a replicator per each partition, so 400 replicators per node) eat a considerable amount of CPU (approximately 12% of each of 8 CPU cores). According to the JFR, all work is done by replicators (sending side) and AppendEntries controllers (receiving side). Both spend most of the time in LogStorage#getTerm().

      We should try to optimize this method (probably caching terms for last N indices).

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-23642 Unable to start a node due to too many assignments recovered

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-16183 Raft heartbeat coalescing prototype

          • Major - Major loss of function.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-23781 Idle safe time propagation eats too much CPU

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-23631 Optimize NetworkMessageChunkedInput constructor

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              rpuch Roman Puchkovskiy
              rpuch Roman Puchkovskiy
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: