-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default Consistency needs mandatory override? #74
Comments
A Cassandra cluster can respond with "Can not achieve consistency quorum" when some of the nodes are down, this is an expected behaviour. For example, you have a keyspace with replication factor 2 and one of the nodes it is not responding. If this is what is happening, then is an expected behaviour. You should tune the consistency level per query, the default values are just that... |
Thanks for the inputs, Here are my values
Should i look for anything else? |
Using quorum on one node cluster should not be a problem. |
Its a PoolConnectionError, it means that the connection could not be established to any of the nodes (in your case 1). You should check if your node... |
Does a PoolConnectionError go away if i introduce consistency override ? |
Should the consistency level not default to ONE? http://www.datastax.com/docs/1.0/references/cql/index#specifying-consistency-level |
Changing that default would be very bad. Rely on a wrapper to provide YOUR default consistency, like priam: https://github.com/godaddy/node-priam |
Agreed. Too bad it wasn't the expected default from the beginning. |
As wiki and NPM description says default consistency is QUORUM and it is optional for as shown client.execute(query, [params], [consistency], callback).
How come for default consistency Simple Select queries not working throwing consistency issues. I had to use var consistency = cql.types.consistencies.one; to help get my simple select query working.
Even client.execute examples shown in wiki/npm uses default consistency, am i missing something ?
Please advice.
The text was updated successfully, but these errors were encountered: