Just so everyone's clear...
restart-instance will restart the instance using all the same options
that were supplied when the instance was originally started. If the
instance was started with --nosync, then every use of restart-instance
will use --nosync as well, and there's no way to override that.
Personally, I'm not convinced that's the right choice, but that's what
falls out of the current implementation. If we want something different,
we have to do some work.
Comerford, Sean wrote on 07/20/2010 07:40 PM:
> Sorry to be dense / have not been following along closely enough lately...
>
> But —nosync will be supported as an option on start-instance in 3.1?
>
> If so, that’s probably good enough... Would be nice to have on
> restart-instance as well but (while I’ll have to double check with our
> operations team) I believe our automated deployment scripts are all
> calling stop-instance and then start-instance
>
> On 7/20/10 10:23 PM, "Paul M Davies (Oracle)" <paul.m.davies_at_oracle.com>
> wrote:
>
> Hi,
>
> I know that in the meeting we decided not to include --nosync and
> --fullsync (not syncfull as you have) in restart-instance, instead
> relying on the settings of these options in the start-instance
> command that initially started the instance. Should we reconsider
> this decision in the light of Sean's request that restart-instance
> accept an optional flag to not attempt to sync with the DAS?
>
> Regards,
> -Paul