Generally shouldn't happen in most modern versions of cassandra. Could be simultaneous conflicting statements (two "CREATE TABLE" statements at the same time, which can happen with programatic schema changes), or unhealthy schema tables (lots and lots of changes create tombstones in the schema tables, which can cause reading/calculating schema versions to be inefficient).
In the future, you can work around this with 'nodetool resetlocalschema' On Fri, May 5, 2017 at 3:45 PM, Nitan Kainth <ni...@bamlabs.com> wrote: > No, just two nodes have mismatch out of 18 nodes. We upgraded long back. > > Sent from my iPhone > > > On May 5, 2017, at 5:17 PM, Jeff Jirsa <jji...@apache.org> wrote: > > > > > > > >> On 2017-05-05 11:00 (-0700), Nitan Kainth <ni...@bamlabs.com> wrote: > >> Hi Experts, > >> > >> We found schema version mismatch in our cluster. We fixed it by > bouncing C* on nodes where version was mismatched. Can someone suggest, > what are the possible reasons for this? We are trying to figure out the > root cause. > >> > > > > Do all of your versions match? You didn't accidentally upgrade half the > cluster did you? > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: user-h...@cassandra.apache.org > > >
