Uploaded image for project: 'Fabric'
  1. Fabric
  2. FAB-14350

RAFT test with large number of channels

    XMLWordPrintable

Details

    • Test Task
    • Status: Closed
    • Medium
    • Resolution: Done
    • v2.0.0
    • v2.0.0
    • fabric-quality
    • System Test
    • Manual
    • Pass
    • Hide
      Attachment observations.txt describes many confusing logs and potential issues; we will open bugs to track each unique one to capture investigation explanations (and fixes where needed).
      Marked as Executing because we are rerunning variations of this testcase with different numbers of channels and traffic volume in an effort to identify what we can support in our test environment without those problems:
      0: change logspec to WARNING in orderers
      1. Create 500 channels, and run traffic on 50.
      2. If that looks ok, then (still with 500 channels) run traffic on 100.
      3. If that looks ok, then increase by 50. Repeat until problems resurface, and then investigate.
      4. Repeat where we left off, but this time change the port used for step messages so that it is different than the one used for invokes. Maybe that will help. Refer to:
      Orderer_General_Cluster_ListenPort
      Orderer_General_Cluster_ListenAddress
      Orderer_General_Cluster_ServerCertificate
      Orderer_General_Cluster_ServerPrivateKey
      Show
      Attachment observations.txt describes many confusing logs and potential issues; we will open bugs to track each unique one to capture investigation explanations (and fixes where needed). Marked as Executing because we are rerunning variations of this testcase with different numbers of channels and traffic volume in an effort to identify what we can support in our test environment without those problems: 0: change logspec to WARNING in orderers 1. Create 500 channels, and run traffic on 50. 2. If that looks ok, then (still with 500 channels) run traffic on 100. 3. If that looks ok, then increase by 50. Repeat until problems resurface, and then investigate. 4. Repeat where we left off, but this time change the port used for step messages so that it is different than the one used for invokes. Maybe that will help. Refer to: Orderer_General_Cluster_ListenPort Orderer_General_Cluster_ListenAddress Orderer_General_Cluster_ServerCertificate Orderer_General_Cluster_ServerPrivateKey

    Description

      Summary

      This objective of this test is to evaluate the functional impact of a network with large number of channels under heavy traffic

      Setup

      Same setup as in FAB-13601, with the following differences:

      1. create 500 channels: channel1-channel500
      2. install/instantiate samplcc chaincode on all channels
      3. 3 peers with 1 peer/org
      4. 3 orderers in orderersystemchannel
      5. batchSize.maxMessageCount: 500
      6. logging level set to info (and if we see errors, then we can re-run test with debug-level logs in the orderer package per FAB-13597)

      Inputs

      1. Start 1 thread transaction to one org's peer for each channel, total 500 threads
      2. Each thread sends 10K invokes, using PTE constant mode, i.e. sending next transaction as soon as the previous one is sent to and ACK'd received by the ingress orderer. Total 5M transactions.
      3. All transactions from a single thread will target the same orderer.

      Expectations

      1. No errors in the logs of peers and orderers.
      2. No failures or errors reported by PTE.
      3. All transaction events are received by PTE.

      Attachments

        1. FAB-14350-orderer1st.log.gz
          1.62 MB
          Dongming Hwang
        2. FAB-14350-orderer2nd.log.gz
          1.94 MB
          Dongming Hwang
        3. FAB-14350-orderer3rd.log.gz
          185 kB
          Dongming Hwang
        4. leader.PNG
          34 kB
          Dongming Hwang
        5. observations.txt
          9 kB
          Dongming Hwang

        Issue Links

          Activity

            People

              dongming Dongming Hwang
              dongming Dongming Hwang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: