[
https://issues.apache.org/jira/browse/CASSANDRA-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Klages resolved CASSANDRA-2969.
------------------------------------
Resolution: Not A Problem
I specified the replication factor in the cassandra-cli incorrectly. The
Keyspace was set to NetworkTopologyStrategy and I didn't use the correct format
for specifying RF. I did
update keyspace xyz with strategy_options=[{replication_factor:2}]
instead of
update ... strategy_options=[{datacenter1:2}]
> Queries and inserts fail on 2 node cluster when replication factor is
> specified.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-2969
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2969
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.2
> Environment: 2 node Cassandra cluster with both nodes up and running.
> The replication factor is specified and can be 1 or 2. Client is using
> Hector. For production, I want to use a RF of 2 so the data is stored on both
> nodes and use a CL of ONE for reads and writes.
> Reporter: Andy Klages
> Labels: 2-node, replica
>
> When a query or insert is performed, I get the following exception:
> me.prettyprint.hector.api.exceptions.HUnavailableException: : May not be
> enough replicas present to handle consistency level.
> I've tried consistency levels ANY, ONE, and QUORUM, but to no avail. I'm
> assuming it would do this for the other levels too.
> Running the "get" and "set" commands on cassandra-cli always return "null" so
> it's encountering the same problem.
> Note that I don't get this problem when the keyspace doesn't have
> replication_factor specified. But I need the data replicated on both nodes
> which is why I'm specifying the RF.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
