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

Validator unable to catch up until load generator client is stopped

    XMLWordPrintable

Details

    • Bug
    • Status: Complete
    • High
    • Resolution: Done
    • None
    • None
    • validator-info
    • ESN network, running indy-node 1.0.28

    • Sprint 18.03 Stability, DKMS

    Description

      While running a low-volume load test on the ESN, one node, play, did not maintain sync with the rest of the network.  It's transaction count remained at 15072, while the rest of the network was posting new transactions at a rate of one per minute.  At 20:51:23 UTC, when the ledger transaction count on the rest of the pool reached 15175, the load generator was killed.  Immediately at this time, play began to resync with the rest of the pool.  This resync was successfully completed at 20:53:01.

      The issue to investigate is why was play unable to obtain and maintain synchronization with the remainder of the pool while the load generator was running an a low rate?

      Attachments

        Issue Links

          Activity

            People

              VladimirWork Vladimir Shishkin
              mgbailey Mike Bailey
              Andrew Nikitin, Dmitry Surnin, Mike Bailey, Sean Bohan, Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: