Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: 1.2.1
    • Component/s: None
    • Labels:
      None

      Description

      There are many cases where getRangeSlice creates more
      RangeSliceCommand than it should, because it always creates one for each range
      returned by getRestrictedRange. Especially for CL.ONE this does not take
      the replication factor into account and is potentially pretty wasteful.
      A range slice at CL.ONE on a 3 node cluster with RF=3 should only
      ever create one RangeSliceCommand.

        Attachments

        1. 4858-v4.txt
          72 kB
          Sylvain Lebresne
        2. 4858-cleanup.txt
          32 kB
          Jonathan Ellis
        3. 4858-v3-2.txt
          3 kB
          Sylvain Lebresne
        4. 4858-v3-1.txt
          34 kB
          Sylvain Lebresne
        5. 0001-CASSANDRA-4858-v2.patch
          7 kB
          Vijay
        6. 0001-CASSANDRA-4858.patch
          7 kB
          Vijay

          Issue Links

            Activity

              People

              • Assignee:
                slebresne Sylvain Lebresne
                Reporter:
                jbellis Jonathan Ellis
                Reviewer:
                Vijay
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: