Schema Disagreement vs Nodetool resetlocalschema

[Michael Fong <mi...@ruckuswireless.com>]

Hi,

We have recently encountered several schema disagreement issue while upgrading Cassandra. In one of the cases, the 2-node cluster idled for over 30 minutes and their schema remain unsynced. Due to other logic flows, Cassandra cannot be restarted, and hence we need to come up an alternative on-the-fly. We are thinking to do a nodetool resetlocalschema to force the schema synchronization. How safe is this method? Do we need to disable thrift/gossip protocol before performing this function, and enable them back after resync completes?

Thanks in advance!

Sincerely,

Michael Fong

Re: Schema Disagreement vs Nodetool resetlocalschema

[Jens Rantil <je...@tink.se>]

Hi Michael,

Did you ever get an answer on this? I'm curious to hear for future
reference.

Thanks,
Jens

On Monday, June 20, 2016, Michael Fong <mi...@ruckuswireless.com>
wrote:

> Hi,
>
>
>
> We have recently encountered several schema disagreement issue while
> upgrading Cassandra. In one of the cases, the 2-node cluster idled for over
> 30 minutes and their schema remain unsynced. Due to other logic flows,
> Cassandra cannot be restarted, and hence we need to come up an alternative
> on-the-fly. We are thinking to do a nodetool resetlocalschema to force the
> schema synchronization. How safe is this method? Do we need to disable
> thrift/gossip protocol before performing this function, and enable them
> back after resync completes?
>
>
>
> Thanks in advance!
>
>
>
> Sincerely,
>
>
>
> Michael Fong
>


-- 
Jens Rantil
Backend engineer
Tink AB

Email: jens.rantil@tink.se
Phone: +46 708 84 18 32
Web: www.tink.se

Facebook <https://www.facebook.com/#!/tink.se> Linkedin
<http://www.linkedin.com/company/2735919?trk=vsrp_companies_res_photo&trkInfo=VSRPsearchId%3A1057023381369207406670%2CVSRPtargetId%3A2735919%2CVSRPcmpt%3Aprimary>
 Twitter <https://twitter.com/tink>

Re: Schema Disagreement vs Nodetool resetlocalschema

[Aleksey Yeschenko <al...@apache.org>]

Schema will disagree during the upgrade itself, you can’t really work around it. It will converge once you finish the upgrade, however.

-- 
AY

On 20 June 2016 at 04:21:02, Michael Fong (michael.fong@ruckuswireless.com) wrote:

Hi,  

We have recently encountered several schema disagreement issue while upgrading Cassandra. In one of the cases, the 2-node cluster idled for over 30 minutes and their schema remain unsynced. Due to other logic flows, Cassandra cannot be restarted, and hence we need to come up an alternative on-the-fly. We are thinking to do a nodetool resetlocalschema to force the schema synchronization. How safe is this method? Do we need to disable thrift/gossip protocol before performing this function, and enable them back after resync completes?  

Thanks in advance!  

Sincerely,  

Michael Fong