Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-13738

Load is over calculated after each IndexSummaryRedistribution

    XMLWordPrintableJSON

Details

    • Normal

    Description

      For example, here is one of our cluster with about 500GB per node, but nodetool status shows far more load than it actually is and keeps increasing, restarting the process will reset the load, but keeps increasing afterwards:

      Status=Up/Down
      |/ State=Normal/Leaving/Joining/Moving
      --  Address        Load       Tokens       Owns (effective)  Host ID                               Rack
      UN  IP1*****       13.52 TB   256          100.0%            c4c31e0a-3f01-49f7-8a22-33043737975d  rac1
      UN  IP2*****       14.25 TB   256          100.0%            efec4980-ec9e-4424-8a21-ce7ddaf80aa0  rac1
      UN  IP3*****       13.52 TB   256          100.0%            7dbcfdfc-9c07-4b1a-a4b9-970b715ebed8  rac1
      UN  IP4*****       22.13 TB   256          100.0%            8879e6c4-93e3-4cc5-b957-f999c6b9b563  rac1
      UN  IP5*****       18.02 TB   256          100.0%            4a1eaf22-4a83-4736-9e1c-12f898d685fa  rac1
      UN  IP6*****       11.68 TB   256          100.0%            d633c591-28af-42cc-bc5e-47d1c8bcf50f  rac1
      

      The root cause is if the SSTable index summary is redistributed (typically executes hourly), the updated SSTable size is added again.

      Attachments

        1. sizeIssue.png
          400 kB
          Jay Zhuang

        Issue Links

          Activity

            People

              jay.zhuang Jay Zhuang
              jay.zhuang Jay Zhuang
              Jay Zhuang
              Marcus Eriksson
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: