Re: endless full gc on one node

DuyHai, In this case I didn't use batch, just bind a single PreparedStatement and execute. Nor did I see any warning/error about batch being too large in the log. Thanks. On Sat, Jan 16, 2016 at 6:27 PM, DuyHai Doan wrote: > "As soon as inserting started, one node

Re: In UJ status for over a week trying to rejoin cluster in Cassandra 3.0.1

Carlos, so you essentially replace the 33 node. Did you follow this https://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_replace_node_t.html? The link is for 2.x not sure about 3.x. What if you change the new node to .34? On Mon, Jan 11, 2016 at 12:57 AM, Carlos A

Re: In UJ status for over a week trying to rejoin cluster in Cassandra 3.0.1

What do the logs say on the seed node (and on the UJ node)? Look for timeout messages. This problem has occurred for me when there was high network utilization between the seed and the joining node, also routing issues. *...* *“Life should not be a journey to the grave with the

broadcast_address in multi data center setups

Setting up my first Cassandra cluster. Does one need to setup broadcast_address to public in all the nodes like this? node 1 - colo 1 - broadcast points to public IP node 2 - colo 1 - broadcast points to public IP . node n - colo 1 - broadcast points to public IP node 4 - colo 2 -

Re: New node has high network and disk usage.

James, Thanks for sharing. Anyway, good to know there's one more thing to add to the checklist. On Sun, Jan 17, 2016 at 12:23 PM, James Griffin < james.grif...@idioplatform.com> wrote: > Hi all, > > Just to let you know, we finally figured this out on Friday. It turns out > the new nodes had an

Re:Re: endless full gc on one node

Hi Kai Wang, I also encounter such issue a few days ago. I have 6 nodes, and I found 2 nodes do endless full gc when I export ALL datas from C* using "Select * from table". I remove all datas of the 2 nodes and install Cassandra again, and the problem gone away. At 2016-01-18 06:18:46,

Re: Too many compactions, maybe keyspace system?

I documented this on JIRA. Please see CASSANDRA-11025 On Sun, Jan 17, 2016 at 11:48 PM, Sebastian Estevez < sebastian.este...@datastax.com> wrote: > I agree that this may be worth a jira. > > Can you clarify this statement? > > >>5

Re: Basic query in setting up secure inter-dc cluster

Hi All. A gentle query-reminder. I will be grateful if I could be given a brief technical overview, as to how secure-communication occurs between two nodes in a cluster. Please note that I wish for some information on the "how it works below the hood", and NOT "how to set it up". Thanks and

Re: Too many compactions, maybe keyspace system?

I agree that this may be worth a jira. Can you clarify this statement? >>5 keyspaces and about 100 cfs months How many total empty tables did you create? Creating hundreds of tables is a bad practice in Cassandra but I was not aware of a compaction impact like what you're describing. all the

Re: New node has high network and disk usage.

Hi all, Just to let you know, we finally figured this out on Friday. It turns out the new nodes had an older version of the kernel installed. Upgrading the kernel solved our issues. For reference, the "bad" kernel was 3.2.0-75-virtual, upgrading to 3.2.0-86-virtual resolved the issue. We still