Re: JMX metric to report number failed WCL ALL

2018-07-23 Thread onmstester onmstester
Thanks Jordan, Sent using Zoho Mail On Mon, 23 Jul 2018 21:28:54 +0430  Jordan West wrote https://issues.apache.org/jira/browse/CASSANDRA-13289 is a new feature, not yet available (its merged into trunk), that I believe will let you monitor what you want. On Sun, Jul 22, 2018 at 4:03

Re: Why and How is Cassandra using all my ram ?

2018-07-23 Thread Dennis Lovely
you define the max size of your heap (-Xmx), but you do not define the max size of your offheap (MaxMetaspaceSize for jdk 8, PermSize for jdk7), so you could occupy all of the memory on the instance. your system killed the process to preserve itself. you should also take into account that the mem

Re: Why and How is Cassandra using all my ram ?

2018-07-23 Thread Mark Rose
On 19 July 2018 at 10:43, Léo FERLIN SUTTON wrote: > Hello list ! > > I have a question about cassandra memory usage. > > My cassandra nodes are slowly using up all my ram until they get OOM-Killed. > > When I check the memory usage with nodetool info the memory > (off-heap+heap) doesn't match wha

Re: Timeout for only one keyspace in cluster

2018-07-23 Thread learner dba
Thanks Jonathan. this is device addition use case where we can't assign same value to more than one device, so we need isolation property. With regular UUID, we may end up assigning same value to two devices. I will talk to dev team and see if this can be changed and handled at application leve

Re: Timeout for only one keyspace in cluster

2018-07-23 Thread Jonathan Haddad
You don’t get this guarantee with counters. Do not use them for unique values. Use a UUID instead. On Mon, Jul 23, 2018 at 9:11 AM learner dba wrote: > James, > > Yes, counter is implemented due to valid reasons. We need this value > column to have unique values being used at the time of regis

Re: JMX metric to report number failed WCL ALL

2018-07-23 Thread Jordan West
https://issues.apache.org/jira/browse/CASSANDRA-13289 is a new feature, not yet available (its merged into trunk), that I believe will let you monitor what you want. On Sun, Jul 22, 2018 at 4:03 AM, onmstester onmstester wrote: > I'm using RF=2 and Write consistency = ONE, is there a counter in

Re: Timeout for only one keyspace in cluster

2018-07-23 Thread learner dba
James, Yes, counter is implemented due to valid reasons. We need this value column to  have unique values being used at the time of registering new devices.On Monday, July 23, 2018, 10:07:54 AM CDT, James Shaw wrote: does your application really need counter ?  just an option. Thanks,

Re: Timeout for only one keyspace in cluster

2018-07-23 Thread James Shaw
does your application really need counter ? just an option. Thanks, James On Mon, Jul 23, 2018 at 10:57 AM, learner dba wrote: > Thanks a lot Ben. This makes sense but feel bad that we don't have a > solution yet. We can try consistency level one but that will be against > general rule for ha

Re: Timeout for only one keyspace in cluster

2018-07-23 Thread learner dba
Thanks a lot Ben. This makes sense but feel bad that we don't have a solution yet. We can try consistency level one but that will be against general rule for having local_quorum for production. Also, consistency ONE will not guarantee 0 race condition. Is there any better solution? On Satur

Re: Timeout for only one keyspace in cluster

2018-07-23 Thread learner dba
Goutham, How will it make any difference? Could you please elaborate? On Saturday, July 21, 2018, 8:20:31 PM CDT, Goutham reddy wrote: Hi,As it is a single partition key, try to update the key with only partition key instead of passing other columns. And try to set consistency level ON