in a 5 node cluster, i noticed in our client error log that one of the
nodes was consistently throwing cassandra_UnavailableException during
a read operation.
looking into jmx, it was obvious that one of the node's view of the
ring was out of sync.
$ nodetool -host 192.168.20.150 ring
Address
check out https://issues.apache.org/jira/browse/CASSANDRA-699
-keith
On Thu, May 13, 2010 at 6:46 PM, Sagar Naik sn...@attributor.com wrote:
Hi
Is there any auto-purging of keys mechanism (or time to live on key )in
cassandra.
Something, like after so many days, the key and its associated
i also noticed unknown result errors when my php thrift code was
generated using a different version of thrift than cassandra uses.
after regenerating my php code from thrift-r917130 (for
cassandra-0.6.0-rc1), the errors stopped.
-keith
On Mon, Apr 12, 2010 at 9:40 AM, vineet daniel
you mention never deleting from the queue, so what purpose is this
serving? (if you don't pop off the front, is it really a queue?)
seems if guaranteed order of messages is required, there are many
other projects which are focused towards that problem (rabbitmq,
kestrel, activemq, etc)
or am i
