Cassandra
  1. Cassandra
  2. CASSANDRA-5161

Slow secondary index performance when using VNodes

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Duplicate
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      When having a big number of vnodes (such as 256/node advised by http://www.datastax.com/dev/blog/upgrading-an-existing-cluster-to-vnodes), using secondary indices becomes really slow because Cassandra has to search for the index in all the nodes.

      This results in very slow queries (in the order of 1-2s).

      For an exemple, see this tracing with a 3 physical nodes cluster with 256 vnodes on each.
      The keyspace has a RF=3.

      https://gist.github.com/16f510fc349584966a56

        Activity

        Steeve Morin created issue -
        Hide
        Jonathan Ellis added a comment -

        Fixed in CASSANDRA-4858

        Show
        Jonathan Ellis added a comment - Fixed in CASSANDRA-4858
        Jonathan Ellis made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Duplicate [ 3 ]
        Gavin made changes -
        Workflow no-reopen-closed, patch-avail [ 12746103 ] patch-available, re-open possible [ 12753800 ]
        Gavin made changes -
        Workflow patch-available, re-open possible [ 12753800 ] reopen-resolved, no closed status, patch-avail, testing [ 12758984 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Steeve Morin
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development