RE: [Cassandra] nodetool compactionstats not showing pending task.

I just restart the cluster but still facing same issue. Please let me know where I can search on JIRA or will raise new ticket for the same? Thanks & Regards, Abhishek Kumar Maheshwari +91- 805591 (Mobile) Times Internet Ltd. | A Times of India Group Company FC - 6, Sector 16A, Film City,

Re: DTCS to TWCS

We (The Last Pickle) wrote a blog post on using TWCS pre-3.0: http://thelastpickle.com/blog/2017/01/10/twcs-part2.html Alex Dejanovski wrote a very comprehensive guide to TWCS I recommend reading before putting it in prod:

Re: DTCS to TWCS

Hi, Take a look to https://issues.apache.org/jira/browse/CASSANDRA-13038 Regards On 04-05-2017 18:22, vasu gunja wrote: > Hi All, > > We are currently on C* 2.1.13 version and we are using DTCS for our > tables. > We planning to move to TWCS. > > My questions > From which versions TWCS is

DTCS to TWCS

Hi All, We are currently on C* 2.1.13 version and we are using DTCS for our tables. We planning to move to TWCS. My questions >From which versions TWCS is available ? Do we need to perform upgrade of cassandra before changing DTCS to TWCS ? Thanks

Re: Totally unbalanced cluster

Adding nodes with NTS is easier, in my opinion. You don’t need to worry about replica placement, if you do it right. > On May 4, 2017, at 7:43 AM, Cogumelos Maravilha > wrote: > > Hi Alain thanks for your kick reply. > > > Regarding SimpleStrategy perhaps you

Re: Totally unbalanced cluster

Hi Alain thanks for your kick reply. Regarding SimpleStrategy perhaps you are right but it's so easy to add nodes. I'm *not* using vnodes and the default 256. The information that I've posted it a regular nodetool status keyspace. My partition key is a sequencial big int but nodetool cfstatus

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

Hi guys, Has anybody got fix for this issue? Recently we upgraded our c* cluster from 2.0.17 to 2.1.17. And we saw increase in read latency on few tables, read latency increased almost 2 to 3 times more than what it was in 2.0.17. Kindly let me know the fix for it if anybody knows it. Thanks

Re: cql3 - adding two numbers in insert statement

Thanks for the feedback Shreyas, it's good to keep a trace of solutions and workarounds in the archives of the mailing list :-). C*heers, --- Alain Rodriguez - @arodream - al...@thelastpickle.com France The Last Pickle - Apache Cassandra Consulting

Re: Totally unbalanced cluster

Hi, CREATE KEYSPACE mykeyspace WITH replication = {'class': > 'SimpleStrategy', 'replication_factor': '2'} AND durable_writes = false; The SimpleStrategy is never recommended for production clusters as it does not recognise racks or datacenter, inducing possible availability issues and

Totally unbalanced cluster

Hi all, I'm using C* 3.10. CREATE KEYSPACE mykeyspace WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '2'} AND durable_writes = false; CREATE TABLE mykeyspace.data ( id bigint PRIMARY KEY, kafka text ) WITH bloom_filter_fp_chance = 0.5 AND caching = {'keys':

Re: Fail to add a new node to a exist cluster

Hello Kevin, here are a few thoughts and things you could try: each node has stored about 4TB When I joined a new node, I found that the process has not been completed > for more than a week So first thought is that this is a lot of data per node. I think the sweet spot is around 1-2 TB /