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

CqlRecordReader creates wrong cluster if the first replica of a split is down

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 2.0.10, 2.1.1
    • None
    • None
    • Normal

    Description

      For a given split, CqlRecordReader gets a list of replicas of that split. Then, it tries to create a Cluster object with a ClusterBuilder for each replica separately in a loop, so that if the cluster creation fails for a certain replica, the next replica is tried. Unfortunately it does not work, because the cluster creation does not fail if the provided contact point is down. So, it always selects the first replica regardless of its state.

      The solution is quite simple - ClusterBuilder accepts a collection of contact points - at least one of them must be up. So instead of iterating over the replicas we can pass the whole set of them and the driver will select the working one. It will follow some changes in the load balancing policy - I'm going to switch to use the same similar balancing policy as to the one we use in OSS Spark Connector.

      Attachments

        1. 0001-CASSANDRA-7774-Fixed-cluster-initialisation-for-a-sp.patch
          13 kB
          Jacek Lewandowski
        2. CASSANDRA-7774-patch-v2.patch
          13 kB
          Jacek Lewandowski

        Activity

          People

            jlewandowski Jacek Lewandowski
            jlewandowski Jacek Lewandowski
            Jacek Lewandowski
            Alex Liu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: