Only do rolling restart can't solve problem. But I thought I found a way.
There are two same name folder with different suffix in data dictionary. e.g.
dayu_123 and dayu_234, the dayu_123 folder is empty and dayu_234 folder is not.
then I use cql to query system_schema.tables，the id of table
Yeah, but you only really need to drain, restart Cassandra one by one. Not
that the others will hurt, but they aren't strictly necessary.
On 28 June 2018 at 05:38, dayu wrote:
> Hi kurt, a rolling restart means run disablebinary, disablethrift,
> disablegossip, drain,
> stop cassandra and
Hi kurt, a rolling restart means run disablebinary, disablethrift,
disablegossip, drain, stop cassandra and start cassandra command one by one,
right?
Only one node is executed at a time
Dayu
At 2018-06-28 11:37:43, "kurt greaves" wrote:
Best off trying a rolling restart.
On 28 June
Best off trying a rolling restart.
On 28 June 2018 at 03:18, dayu wrote:
> the output of nodetool describecluster
> Cluster Information:
> Name: online-xxx
> Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
You can sometimes bounce your way through it (or use nodetool resetlocalschema
if it’s a single node that’s wrong), but there are some edge cases from which
it’s very hard to recover
What’s the output of nodetool describecluster?
If you select from the schema tables, do you see that CFID on
That log message says you did:
CF 53f6d520-2dc6-11e8-948d-ab7caa3c8c36 was dropped during streaming
If you’re absolutely sure you didn’t, you should look for schema mismatches in
your cluster
--
Jeff Jirsa
> On Jun 27, 2018, at 7:49 PM, dayu wrote:
>
> CF
Try again and this time don’t remove tables during bootstrap (the streaming
code doesn’t handle removing tables very well).
--
Jeff Jirsa
> On Jun 27, 2018, at 7:30 PM, dayu wrote:
>
> Hi everyone
> I am joining a new node to a cluster. but it failed even if I use
> nodetool bootstrap
