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 any real tables? -- Jeff Jirsa > On Jun 27, 2018, at 7:58 PM, dayu <sdycre...@163.com> wrote: > > That sound reasonable, I have seen schema mismatch error before. > So any advise to deal with schema mismatches? > Dayu > > At 2018-06-28 09:50:37, "Jeff Jirsa" <jji...@gmail.com> wrote: > >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 <sdycre...@163.com> wrote: > >> > >> CF 53f6d520-2dc6-11e8-948d-ab7caa3c8c36 was dropped during streaming > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > >For additional commands, e-mail: user-h...@cassandra.apache.org > > >
