After check the log and configuration, I found it caused by two reason.
1. GC grace seconds
I using hector client to connect cassandra, and the default value of GC
grace seconds for each column family is **Zero** ! So when hinted handoff
replay the temporary value, the tombstone on other two
On Monday, October 14, 2013 10:49:22 AM Romain HARDOUIN wrote:
> > Polites, isn't a rest API wrapper for Cassandra really, it does more
> > configuration and management of a Cassandra Node. Though it does have a
> > REST API
>
> Hi,
>
> Nice project Sean!
> Can't help but thinking about Trove...
Hi guys,
Thanks for your reply. It's very helpful.
I agree with Plotnik on the scaling part.
For the business logic, it sounds obvious that "it make sense to divide, i.e.
metadata and really BIG data into different clusters, of course." as you
mentioned. But after I think about it a bit more,
Those links are for Cassandra 0.8 and the OP is on 2.0.1.
http://www.datastax.com/documentation/cql/3.1/webhelp/index.html
Blair
On 10/14/2013 02:17 AM, Santosh Shet wrote:
Hope these links would help you.
--Getting started with CQL
http://www.datastax.com/docs/0.8/dml/using_cql
--Getting s
By clusters do you mean data centers? If so, I think it depends on your use
case and application requirements.
For instance, if you have a web application and and analytics application
(hadoop), you would want to separate your cluster in 2 different data
centers (even if they're located in the sam
> Polites, isn't a rest API wrapper for Cassandra really, it does more
> configuration and management of a Cassandra Node. Though it does have a
REST
> API
Hi,
Nice project Sean!
Can't help but thinking about Trove...
