cassandra version: 0.7 client library: scale7-pelops / 1.0-RC1-0.7.0-SNAPSHOT
cluster: 3 machines (A, B, C) details: it works perfectly when all 3 machines are up and running but if the seed machine is down, the problems happen: 1) new client connection cannot be established 2) if a client keeps connecting to and operating at (issue get and update) the cluster, when the seed is down, the working client will throw exception upon the next operation 3) using cassandra-cli to connect the remaining nodes in the cluster, "Internal error processing get_range_slices" will happen when querying column family > list <cf>; so i would like to know if the situation described above is normal or not? if yes, does that mean the seed node is the single point of failure? wing
