Re: How can I add blank values instead of null values in cassandra ?

2019-09-09 Thread Nitan Kainth
You can set default values in driver but that also little code change Regards, Nitan Cell: 510 449 9629 > On Sep 9, 2019, at 8:15 PM, buchi adddagada wrote: > > We are using DSE 5.1.0 & Spring boot Java. > > While we are trying to insert data into cassandra , java by default inserts > null

How can I add blank values instead of null values in cassandra ?

2019-09-09 Thread buchi adddagada
We are using DSE 5.1.0 & Spring boot Java. While we are trying to insert data into cassandra , java by default inserts null values in cassandra tables which is causing huge tombstones. Instead of changing code in java to insert null values, can you control anywhere at driver level ? Thanks,

Re: After restarting Cassandra , some of nodes are missing in nodetool status

2019-09-09 Thread Nandakishore Tokala
Ok, I will check. Can you please be more specific? like what to check about the token range and if we find any mismatch what to do next. On Mon, Sep 9, 2019 at 3:28 PM Dhanunjaya Tokala wrote: > I would suggest you to check the token ranges of all the nodes and see if > any of the nodes have

Re: After restarting Cassandra , some of nodes are missing in nodetool status

2019-09-09 Thread Dhanunjaya Tokala
I would suggest you to check the token ranges of all the nodes and see if any of the nodes have similar token ranges. Regard’s Dhanunjaya Tokala On Mon, Sep 9, 2019 at 6:25 PM Nandakishore Tokala < nandakishore.tok...@gmail.com> wrote: > @dhanunjayatok...@gmail.com NO, we did not > remove

Re: After restarting Cassandra , some of nodes are missing in nodetool status

2019-09-09 Thread Nandakishore Tokala
@dhanunjayatok...@gmail.com NO, we did not remove those nodes and it is not exactly same missing nodes for each restart (for each restart i am seeing different nodes). @jji...@gmail.com yeah it is typo 3.11.0 Thanks On Mon, Sep 9, 2019 at 12:38 PM Jeff Jirsa wrote: > Is 3.1.0 a typo? Is it

Re: After restarting Cassandra , some of nodes are missing in nodetool status

2019-09-09 Thread Jeff Jirsa
Is 3.1.0 a typo? Is it really 3.1 or 3.11.0 ? On Mon, Sep 9, 2019 at 10:51 AM Nandakishore Tokala < nandakishore.tok...@gmail.com> wrote: > Hi All, > > we are running apache Cassandra 3.1.0 on AWS in multi-region nearly around > 200 nodes. > after restarting each node I am seeing some of the

Re: Is this something to be concerned about? Compaction Error reported in the log every minute

2019-09-09 Thread Jeff Jirsa
It's unfortunate you dont have a better stack trace to know what's actually going on here. 3.7 is pretty old, I'd be inclined to upgrade to the latest 3.11 branch to hope that you either get a better stack or an outright fix, but that stack doesn't ring any bells for me. On Mon, Sep 9, 2019 at

Re: After restarting Cassandra , some of nodes are missing in nodetool status

2019-09-09 Thread Dhanunjaya Tokala
Did you replace any of the nodes which are missing in the nodetool status ? Regard’s Dhanunjaya Tokala On Mon, Sep 9, 2019 at 1:51 PM Nandakishore Tokala < nandakishore.tok...@gmail.com> wrote: > Hi All, > > we are running apache Cassandra 3.1.0 on AWS in multi-region nearly around > 200

After restarting Cassandra , some of nodes are missing in nodetool status

2019-09-09 Thread Nandakishore Tokala
Hi All, we are running apache Cassandra 3.1.0 on AWS in multi-region nearly around 200 nodes. after restarting each node I am seeing some of the nodes are missing from the nodetool status (not UN or DN they are completely missing). after couple of restarts, I am seeing them back. Please help me

Is this something to be concerned about? Compaction Error reported in the log every minute

2019-09-09 Thread Leena Ghatpande
We are on Cassandra 3.7 and have a 8 node cluster , 2DC, with 4 nodes in each DC. RF=3 The below Compaction Error message is being logged to the system.log exactly every Minute. ERROR [CompactionExecutor:5751] 2019-06-09 03:24:50,585 CassandraDaemon.java:217 - Exception in thread