Is your ReplicationFactor (RF) really set to 0? Don't do that, it needs to be at least 1 and probably needs to be 3 in production if you care about your data. It must be greater than 0 and less than the number of nodes in your ring. It represents the number of nodes to copy/replicate data to. Another way to look at it is I'm willing to tolerate this many failures before I lose data.
On Mon, Feb 14, 2011 at 5:55 PM, mcasandra <mohitanch...@gmail.com> wrote: > > I am following example posted on > > http://www.datastax.com/dev/tutorials/getting_started_0.7/using_cli#cassandra-cli > cli > > I am seeing: > > $ set users['jsmith']['password']='ch@ngem3'; > Internal error processing insert > > In the logs I see: > > java.lang.AssertionError: invalid response count 1 for replication factor 0 > at > > org.apache.cassandra.service.WriteResponseHandler.determineBlockFor(WriteResponseHandler.java:98) > at > > org.apache.cassandra.service.WriteResponseHandler.<init>(WriteResponseHandler.java:48) > at > > org.apache.cassandra.service.WriteResponseHandler.create(WriteResponseHandler.java:61) > at > > org.apache.cassandra.locator.AbstractReplicationStrategy.getWriteResponseHandler(AbstractReplicationStrategy.java:125) > at > > org.apache.cassandra.locator.NetworkTopologyStrategy.getWriteResponseHandler(NetworkTopologyStrategy.java:165) > > -- > > My guess is because I am using network topology as specified in the > example. > Is that correct? > > What's the best way to fix the problem? > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Internal-error-processing-insert-tp6025740p6025740.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com. >
