Anissa,
I suspect the problem is not that the instance isn't in the
restart-required state, but rather than there isn't any way to find out
that it is in the restart-required state.
The list-instances command only reports the instance state according to
what the DAS thinks the state is. And the only reason the DAS thinks an
instance should be restarted is if it knows that it has missed a
configuration update. So to produce this, you can do something like stop
the instance and apply a configuration update, or if you want to just
simulate a hung instance, you could do kill -STOP to the instance, apply
a configuration update, and then do kill -START. At this point, the
instance will be up and the DAS will think it needs to be restarted.
We should probably modify the list-instances command so that when it
calls __locations on the instance, it also gets back the state
(restart-required or not) too, so that it can update the DAS's view of
what the state is. Do you want to file an issue on this?
Tom
On 11/16/2010 12:07 AM, Anissa Lam wrote:
>
> I want to know, as a user, what do i need to do to trigger an
> instance into a restart-required state ?
> For DAS, if i change debug-enabled to true, DAS will be in
> restart-required state.
> <java-config debug-options="-Xdebug
> -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009"
> *debug-enabled="true"* system-classpath="" bytecode-preprocessors=""
> classpath-suffix="">
> However, if i do that to any standalone instance or clustered
> instance, the instance will still be in the running state. It
> doesn't say restart-required. Is this a bug ?
> Can someone tell me what changes will trigger the instance to go to
> restart-required state ? I need this to do some testing.
>
> thanks
> Anissa.
>