Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-3522

Idle replication change log consumes CPU and disk IO

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 4.0.0, 3.5.1
    • Fix Version/s: Not applicable
    • Component/s: replication
    • Labels:
      None
    • Support Ticket IDs:

      Description

      On an idle server the change number indexer thread wakes up regularly to check the changelog head.

      This can be observed with strace -p <change number indexer thread>

      Attaching a debugger it seems that it's being woken up when heartbeat messages are received. In a large topology this could be noticeable number of times per second and leads to a small constant usage of resources.

      This is not a significant concern, since I believe as load increases, wake-ups due to heartbeat messages should become irrelevant; the indexer will be active anyway due to real changes coming in.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                matthew Matthew Swift
                Reporter:
                ian.packer Ian Packer [X] (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: