> > So the ‘strategy’ change may not be seen by all nodes when the ‘upgrade > keyspace …’ command returns and I can use ’describe cluster’ to check if > the change has taken effect on all nodes right?
Correct, the change may take time to propagate to all nodes. As Rahul said you can check describe cluster in cli to be sure. Mark On Tue, Aug 5, 2014 at 3:06 PM, Lu, Boying <boying...@emc.com> wrote: > Thanks a lot. > > > > So the ‘strategy’ change may not be seen by all nodes when the ‘upgrade > keyspace …’ command returns and I can use ’describe cluster’ to check if > > the change has taken effect on all nodes right? > > > > *From:* Rahul Neelakantan [mailto:ra...@rahul.be] > *Sent:* 2014年8月5日 18:46 > *To:* user@cassandra.apache.org > *Subject:* Re: A question about using 'update keyspace with > strategyoptions' command > > > > Try running "describe cluster" from Cassandra-CLI to see if all nodes have > the same schema version. > > Rahul Neelakantan > > > On Aug 5, 2014, at 6:13 AM, Sylvain Lebresne <sylv...@datastax.com> wrote: > > On Tue, Aug 5, 2014 at 11:40 AM, Lu, Boying <boying...@emc.com> wrote: > > What I want to know is “are the *strategy* changed ?’ after the ‘udpate > keyspace with strategy_options…’ command returns successfully > > > > Like all schema changes, not necessarily on all nodes. You will have to > check for schema agreement between nodes. > > > > > Not the *data* change. > > > > e.g. say I run the command ‘update keyspace with strategy_opitons [dc1: 3, > dc2:3]’ , when this command returns, > > are the *strategy* options already changed? Or I need to wait some time > for the strategy to be changed? > > > > > > *From:* Sylvain Lebresne [mailto:sylv...@datastax.com] > *Sent:* 2014年8月5日 16:59 > *To:* user@cassandra.apache.org > > > *Subject:* Re: A question about using 'update keyspace with > strategyoptions' command > > > > Changing the strategy options, and in particular the replication factor, > does not perform any data replication by itself. You need to run a repair > to ensure data is replicated following the new replication. > > > > On Tue, Aug 5, 2014 at 10:52 AM, Lu, Boying <boying...@emc.com> wrote: > > Thanks. yes. I can use the ‘show keyspace’ command to check and see the > strategy does changed. > > > > But what I want to know is if the ‘update keyspace with strategy_options > …’ command is > > a ‘sync’ operation or a ‘async’ operation. > > > > > > > > *From:* Rahul Menon [mailto:ra...@apigee.com] > *Sent:* 2014年8月5日 16:38 > *To:* user > *Subject:* Re: A question about using 'update keyspace with > strategyoptions' command > > > > Try the show keyspaces command and look for "Options" under each keyspace. > > > > Thanks > > Rahul > > > > On Tue, Aug 5, 2014 at 2:01 PM, Lu, Boying <boying...@emc.com> wrote: > > Hi, All, > > > > I want to run ‘update keyspace with strategy_options={dc1:3, dc2:3}’ from > cassandra-cli to update the strategy options of some keyspace > > in a multi-DC environment. > > > > When the command returns successfully, does it mean that the strategy > options have been updated successfully or I need to wait > > some time for the change to be propagated to all DCs? > > > > Thanks > > > > Boying > > > > > > > > > >
