Re: Cassandra Exception

Carlos, Yes, I'm running multiple clients simultaneously. Each one of them tries to create table if it doesn't exists in the cassandra. Ali, I've cleared the data directory. Next time, If it reoccurs, I'll follow the steps listed and come here again. Thanks for the information. Regards, Kamal C

Re: Cassandra Exception

Ok cool, glad you found the issue. Carlos Alonso | Software Engineer | @calonso On 17 August 2016 at 09:48, Kamal C wrote: > Carlos, > Yes, I'm running multiple clients simultaneously. Each one of them tries > to create table if it doesn't exists in the cassandra.

Re: sstableloader

yes, you are correct. On Tue, Aug 16, 2016 at 2:37 PM, Jean Tremblay < jean.tremb...@zen-innovations.com> wrote: > Hi, > > I’m using Cassandra 3.7. > > In the documentation for sstableloader I read the following: > > << Note: To get the best throughput from SSTable loading, you can use > multiple

Re: Corrupt SSTABLE over and over

This might not be good news to you. But my experience is that C* 2.X/Windows is not ready for production yet. I've seen various file system related errors. And in one of the JIRAs I was told major work (or rework) is done in 3.X to improve C* stability on Windows. On Tue, Aug 16, 2016 at 3:44 AM,

Hintedhandoff mutation

Hi All, I want to differ hintedhandoff mutation and normal write mutation when i receive a mutation. how to get this in cassandra source code.have not found any attribute about this in Mutation class. or there is no way to get this. thanks stone

Re: sstableloader

Thank you for your answer Kai. On 17 Aug 2016, at 11:34 , Kai Wang mailto:dep...@gmail.com>> wrote: yes, you are correct. On Tue, Aug 16, 2016 at 2:37 PM, Jean Tremblay mailto:jean.tremb...@zen-innovations.com>> wrote: Hi, I’m using Cassandra 3.7. In the documentation for sstableloader I re

Re: migrating from 2.1.2 to 3.0.8 log errors

just to share with you, by running rebuild_index the problem is solved. 2016-08-11 22:05 GMT+02:00 Adil : > After migrating C* from 2.1.2 to 3.0.8, all queries with the where > condition involved ad indexed column return zero rows for the old data, > instead news inserted data are returned from t

large number of pending compactions, sstables steadily increasing

I have one node in my cluster 2.2.7 (just upgraded from 2.2.6 hoping to fix issue) which seems to be stuck in a weird state -- with a large number of pending compactions and sstables. The node is compacting about 500gb/day, number of pending compactions is going up at about 50/day. It is at about 2

Re: large number of pending compactions, sstables steadily increasing

What compaction strategy? Looks like leveled – is that what you expect? Any exceptions in the logs? Are you throttling compaction? SSD or spinning disks? How many cores? How many concurrent compactors? From: Ezra Stuetzel Reply-To: "user@cassandra.apache.org" Date

Re: large number of pending compactions, sstables steadily increasing

Yes, leveled compaction strategy. Concurrent compactors were 2, I changed to 8 recently and no change. Also at same time changed compaction throughput from 64 to to 384 mb/s. The number of pending was still increasing after the change. Other nodes are handling the same throughput with the previous

Re: Hintedhandoff mutation

Probably question better suited for the dev@ list. But I afaik the answer is there is no way to tell the difference, but probably safe to look at the created time, HHs tend to be older. Chris On Wed, Aug 17, 2016 at 5:02 AM, Stone Fang wrote: > Hi All, > > I want to differ hintedhandoff mutatio