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

[shakedown] Need to limit the transaction size.

    Details

    • Type: Task
    • Status: Complete
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Sprint:
      10, M1 Prelude

      Description

      Send extremely large request (attempt to fill memory).
      Not sure what size the nodes have but several GB.
      Should be tried with both ledger data and not ledger data.
      By that, I mean really large ledger entry
      and non-ledger data like whitespace in the message.

        Attachments

        1. LargeJson248
          245 kB
        2. Screenshot.PNG
          Screenshot.PNG
          55 kB
        3. shakedown.py
          6 kB
        4. SmallJson100
          86 kB

          Issue Links

          relates to

          Task - A task that needs to be done. INDY-698 Make max transaction size configurable via config ledger

          • Medium - Has the potential to affect progress.
          • Complete

          Task - A task that needs to be done. INDY-805 Client and node config parameter MSG_LEN_LIMIT mismatch

          • Medium - Has the potential to affect progress.
          • New

          Bug - A problem which impairs or prevents the functions of the product. INDY-765 Message length limitation affects parallel sending of transactions from different machines

          • High - Serious problem that could block progress.
          • Complete

            Activity

              People

              • Assignee:
                danielhardman Daniel Hardman
                Reporter:
                devin-fisher Devin Fisher
                Watchers:
                Alexander Shcherbakov, Daniel Hardman, Devin Fisher, Dmitry Surnin, Kelly Wilson, Lovesh Harchandani, Steve Tolman, Vladimir Shishkin
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3 hours
                  3h
                  Remaining:
                  Remaining Estimate - 3 hours
                  3h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified