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

Replica.lastPrePrepareSeqNo may not be reset on view change



    • Bug
    • Status: Complete
    • Medium
    • Resolution: Done
    • None
    • None
    • None
    • STN network, running 1.1.43.

    • INDY 18.01: Stability+, Sprint 18.02 Stability


      During investigation of the bug INDY-959, on the master replica of the node "korea" a 3PC-batch was observed with a key with ppSeqNo generated using Replica.lastPrePrepareSeqNo counter that was not reset after the previous view, while it must be reset. The corresponding 3PC-batches on the backup replicas of this node had keys with expected ppSeqNo (generated using the counter reset after the previous view). The PrePrepare (initial message for 3PC-batch) on the master replica was postponed to Replica.prePreparesPendingPrevPP due to unavailability of previous PrePrepares while the 3PC-batches on all the backup replicas were successfully ordered by them.

      This 3PC-batch on the master replica and the corresponding 3PC-batches on the backup replicas were the 3PC-batches with viewNo 2 containing the single request with reqId 1509109895321705 from identifier Fvy1AsYgrpkjmTE7KsD4CY. On the master replica ppSeqNo was 76 and on the backup replicas ppSeqNo was 1.

      Also it's worth to note that later on the master replica there was a 3PC-batch with the same single request and with viewNo 3. It had ppSeqNo 1 and was successfully ordered by the replica and eventually by the node.

      The node log has been attached. Also this log and other logs from the pool can be found in INDY-959.


        Issue Links



              Unassigned Unassigned
              spivachuk Nikita Spivachuk
              Dmitry Surnin, Nikita Spivachuk, Olga Zheregelya
              0 Vote for this issue
              3 Start watching this issue