Be really cautious here, this can be deceptive
There are races in some versions of cassandra that can leave you with different
combinations of cfid
The cfid is on disk for schema
It’s in memory for schema
It’s used for the table path on disk
Those three have to match for things to work properly
>
> Another suggestion before resetlocalschema. Try rolling restart all the
> nodes in the cluster and see if it fix the problem. After the restart all
> the nodes will use the same schema for the table.
>
That's a little bit heavy-handed. 🙂 Resetting a node's schema is a simple,
online operation
Another suggestion before resetlocalschema. Try rolling restart all the
nodes in the cluster and see if it fix the problem. After the restart all
the nodes will use the same schema for the table.
On Sunday, April 5, 2020, David Ni wrote:
> Hi Erick
> Thank you very much for your friendly note.
>
Hi Erick
Thank you very much for your friendly note.
ERROR [AntiEntropyStage:1] 2020-04-04 13:57:09,614
RepairMessageVerbHandler.java:177 - Table with id
21a3fa90-74c7-11ea-978a-b556b0c3a5ea was dropped during prepare phase of repair
cassandra@cqlsh:system_schema> select keyspace_name,table_name
This is confirmation that you have a schema disagreement in your cluster:
- 21a3fa90-74c7-11ea-978a-b556b0c3a5ea = Friday, April 3 05:07:44 PT
- 830028a0-7584-11ea-a277-bdf3d1289bdd = Friday, April 3 01:24:18 PT
The schema on the node where you ran that query has an older version of the
tab
Thank you very much for your friendly note.
ERROR [AntiEntropyStage:1] 2020-04-04 13:57:09,614
RepairMessageVerbHandler.java:177 - Table with id
21a3fa90-74c7-11ea-978a-b556b0c3a5ea was dropped during prepare phase of repair
cassandra@cqlsh:system_schema> select keyspace_name,table_name,id f
Is it possible someone else dropped then recreated the logtabl table? Also,
did you confirm that the missing table ID matches the ID of logtabl?
On a friendly note, there are a number of users here like me who respond to
questions on the go. I personally find it difficult to read screenshots on
my
Hi Erick
here is the log from system.log
but when I desc keyspace the table is still there
At 2020-04-04 11:56:15, "Erick Ramirez" wrote:
And from your review of the logs, what was the cause of the repair failures?
Because that's likely to yield clues on the root cause. Cheers
And from your review of the logs, what was the cause of the repair
failures? Because that's likely to yield clues on the root cause. Cheers!
Thanks Erick I think there is no problem with schema version:
At 2020-04-04 10:35:06, "Erick Ramirez" wrote:
The symptoms in your post indicate that you have a schema disagreement in your
cluster which you need to resolve. These 2 nodes in particular are the ones you
ne
The symptoms in your post indicate that you have a schema disagreement in
your cluster which you need to resolve. These 2 nodes in particular are the
ones you need to investigate in the first place:
[2020-04-03 20:07:44,242] Got negative replies from endpoints
> [10.17.140.69, 10.17.140.59]
>
If
Hello experts:
I am using cassandra 3.11.2 and having below problem:
cassandra@cqlsh> select * from oapi_dev.logtabl;
InvalidRequest: Error from server: code=2200 [Invalid query]
message="unconfigured table logtabl"
but when I descrbibe keyspace，it shows
12 matches
Mail list logo
