One question from an end user perspective (I think I may have mentioned this
before but don't remember outcome):
Can restart-instance and start-instance be made to accept an optional flag
to NOT attempt to sync with the DAS?
I.e. asadmin restart-instance --syncWithDAS=false myClusteredInstance
Here at ESPN, we've run into problems on occasion that (for whatever reason)
the DAS is unavailable therefore we can't start a clustered instance with
the normal asadmin command b/c DAS sync fails.
We'd also like to be able to use this flag to better control when the DAS
pushses changes staged to the DAS to each target instance (i.e. We may want
to test a fix long term on just a single instance before rolling to others
but currently restart ALWAYS sync so the change may inadvertently bleed out
to all targets).
I understand there's another script in the bin directory you can use to
start w/o the DAS but that's one extra step we'd like to avoid if possible
(maybe the asadmin command just invokes that under the covers?)
On 7/20/10 7:51 PM, "Byron Nevins" <byron.nevins_at_oracle.com> wrote:
> restart-local-instance takes an instance name. It uses that info to get
> a host:port Then it calls restart-instance on the instance itself
>
> restart-instance takes no name param. It restarts itself.
>
> If you call restart-instance on DAS it restarts itself!
>
> --
> Byron Nevins - Oracle Corporation
> Home: 650-359-1290
> Cell: 650-784-4123
> Sierra: 209-295-2188
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
>
> Please consider the environment before printing this e-mail.
--
Sean Comerford, Software Engineer
ESPN.com Site Architecture Group
Office: 860.766.6454 Cell: 860.329.5842