Re: How long/how many days 'nodetool gossipinfo' will have decommissioned nodes info

Thank you @Jaoquin and @DuyHai On Mon, Sep 26, 2016 at 10:00 PM, DuyHai Doan wrote: > I've read from some that the gossip info will stay > around for 72h before being removed. > > On Mon, Sep 26, 2016 at 6:19 PM, Joaquin Casares < > joaq...@thelastpickle.com> wrote: > >>

Re: How long/how many days 'nodetool gossipinfo' will have decommissioned nodes info

Hello Techpyassa, Sometimes old gossip information tends to echo around for quite a bit longer than intended. I'm unsure how long the LEFT messages are supposed to be echoed for, but if you want to force the removal of a removed node from gossip, you can use the Assassinate Endpoint JMX command.

Re: How long/how many days 'nodetool gossipinfo' will have decommissioned nodes info

I've read from some that the gossip info will stay around for 72h before being removed. On Mon, Sep 26, 2016 at 6:19 PM, Joaquin Casares wrote: > Hello Techpyassa, > > Sometimes old gossip information tends to echo around for quite a bit > longer than intended. I'm

Exceptions whenever compaction happens

Hi, We are not exactly sure what is causing this problem. But after compaction happens (after 1 week ttl). We start getting this exception: WARN [SharedPool-Worker-1] 2016-09-26 04:07:19,849 AbstractLocalAwareExecutorService.java:169 - Uncaught exception on thread

Re: Exceptions whenever compaction happens

Hi Ben, Thanks for your help. We have created an issue here: https://issues.apache.org/jira/browse/CASSANDRA-12706 Let's see if we can get some comments there. Regards, Nikhil Sharma On Mon, Sep 26, 2016 at 1:12 PM, Ben Slater wrote: > Hi Nikhil, > > If you

Re: Exceptions whenever compaction happens

Hi Nikhil, If you haven’t already done so I would recommend logging Cassandra project JIRA for this issue - it looks like a defect to me and occurring during compaction will probably be hard to work around. If you can work out what table is being compacted when the issue occurs and include the

Repairs at scale in Cassandra 2.1.13

Hello, We run Cassandra 2.1.13 (don't have plans to upgrade yet). What is the best way to run repairs at scale (400 nodes, each holding ~600GB) that actually works ? I'm considering doing subrange repairs (https://github.com/BrianGallew/cassandra_range_repair/blob/master/src/range_repair.py)

Re: How to query '%' character using LIKE operator in Cassandra 3.7?

> LIKE '%%%escape' --> EQUALS TO '%%escape' ??? In the current implementation (‘%’ could be a wildcard only at the start/end of a term) I guess it should be ’ENDS with ‘%escape’ ‘. Moreover all terms that contains single ‘%’ somewhere in the middle should cause an exception. BUT may be it’s

Re: How to query '%' character using LIKE operator in Cassandra 3.7?

"In the current implementation (‘%’ could be a wildcard only at the start/end of a term) I guess it should be ’ENDS with ‘%escape’ ‘." --> Yes in the current impl, it means ENDS WITH '%escape' but we want SASI to understand the %% as an escape for % so the goal is that SASI understands LIKE

Using Spring Data Cassandra with Spring Boot Batch

Hi, I am wondering if anyone has used or tried using Spring data Cassandra with Spring Batch or Spring book batch. I understand that Spring batch today only supports RDBMS to store its metadata and only way I is to either provide a relational database as datasource for spring batch or use an