Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-1572

Explore memory leaks when a primary on one of backup instances is stopped

    XMLWordPrintable

Details

    • Task
    • Status: Complete
    • Medium
    • Resolution: Done
    • None
    • 1.6.78
    • None
    • None

    Description

      There is a high chance of memory leaks if one of the (non-master) primaries is stopped.

      The corresponding instance will not be able to order, and requests will not be cleared till the next view change.

      Acceptance criteria:

      Perform the following tests and report results about memory consumption with memory checks enabled (in particular, the checks for memory usage of our internal queues and structures).

      • Disable view change. Stop a primary on 1 backup instance. Run load of 10 writes per second.
      • Disable view change. Stop a primary on multiple backup instances. Run load of 10 writes per second.

      Attachments

        1. ALL_UP.png
          ALL_UP.png
          249 kB
        2. BACKUP_DOWN_UNDER_LOAD.png
          BACKUP_DOWN_UNDER_LOAD.png
          265 kB
        3. BACKUP_DOWN.png
          BACKUP_DOWN.png
          283 kB

        Issue Links

          Activity

            People

              VladimirWork Vladimir Shishkin
              ashcherbakov Alexander Shcherbakov
              Alexander Shcherbakov, Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: