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

Message length limitation affects parallel sending of transactions from different machines

    Details

    • Type: Bug
    • Status: Complete
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Build Info:
        indy-node 1.0.111
        indy-anoncreds 1.0.25
        indy-plenum 1.0.97
        sovrin 1.0.23
      OS/Platform: Ubuntu 16.04.2 LTS
      Setup: performance pool (7 nodes, 2 clients)

    • Sprint:
      11, 12

      Description

      Case 1:

      Steps to Reproduce:
      1. Run load test with following parameters on one of the clients:

      python3 load_test.py --clients-list load_test_clients.list -t NYM -c 10 -r 100 --at-once

      2. After completion of load test check InvalidMessageExceedingSizeException messages in logs.

      ubuntu@californiaPerf1:/home/sovrin/.sovrin$ grep "InvalidMessageExceedingSizeException" /home/sovrin/.sovrin/Node1.log* | wc -l

       

      Actual Results:
      All 1000 transactions are written successfully, but there are 12 InvalidMessageExceedingSizeException messages appear in logs (there were no such exceptions before the test).

      Expected Results:
      If the massage from one client (running on one physical machine) exceeded limitation, transactions should not be written.

      Case 2:

      Steps to Reproduce:

      1. Run load test with following parameters on one of the clients:

      python3 load_test.py --clients-list load_test_clients.list -t NYM -c 5 -r 100 --at-once

      => All transactions are written, count of InvalidMessageExceedingSizeException messages was not increased.
      2. After completion of previous script run load test with the same parameters at the same time on all clients.

      Actual Results:
      All transactions were written on 3 clients, but on the 4th client all of transactions were not written. Count of InvalidMessageExceedingSizeException in logs become equal to 60 (before test there were 48 messages).

      Expected Results:
      Transactions which were send by different clients should not affect each other.

        Attachments

        1. length1.txt
          174 kB
        2. logs1.7z
          3.25 MB
        3. logs2.7z
          3.37 MB
        4. logs3.7z
          3.18 MB
        5. logs4.7z
          3.31 MB
        6. logs5.7z
          3.22 MB
        7. logs6.7z
          3.03 MB
        8. logs7.7z
          2.89 MB

          Issue Links

            Activity

              People

              • Assignee:
                danielhardman Daniel Hardman
                Reporter:
                ozheregelya Olga Zheregelya
                Watchers:
                Alexander Shcherbakov, Alexander Shekhovcov, Andrey Goncharov, Daniel Hardman, Dmitry Surnin, Kelly Wilson, Olga Zheregelya, Victor Muzychenko
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: