Timeout while waiting for workers when flushing pool

2016-06-01 Thread Zhang, Charles
We have a 4 nodes, two dc's test cluster. All of them have datastax enterprise installed and running. One dc is the Cassandra dc, and the other is the Solr dc. We first used sstableloader to stream 1 billion rows into the cluster. After that was done, we created a Solr core using resource auto-g

RE: Decommissioned node shows up in the gossip log

2016-05-03 Thread Zhang, Charles
, Zhang, Charles mailto:cong.zh...@fmr.com>> wrote: I decommissioned a seed node from the cluster but now it still shows up in the log files but does not show up in “nodetool status”. The steps I took to decommission this seed node was first I added another node to the seed node list and

MigrationManager.java:164 - Migration task failed to complete

2016-05-03 Thread Zhang, Charles
I have seen a bunch of them in the log files of some newly joined nodes. I did a search in google and it seems increasing the countdown latch timeout can solve this problem. But I assume it only resolves it for future nodes when joining happens? For the existing nodes, anything needs to be done?

Decommissioned node shows up in the gossip log

2016-05-03 Thread Zhang, Charles
I decommissioned a seed node from the cluster but now it still shows up in the log files but does not show up in "nodetool status". The steps I took to decommission this seed node was first I added another node to the seed node list and remove this node from the seed node list and then restarted