In v2, start-instance first talks to the DAS, which then talks to the node
agent on the machine running the instance and asks the node agent to start
the instance. That's why it doesn't work if the DAS is down.
If the instance is already running, and it crashes or restarts for some
reason, the node agent should allow it to restart even if the DAS is
down.
Comerford, Sean wrote on 05/18/2010 01:16 PM:
> At least using 2.1 b60e, I don't know of any way to start an instance w/o
> the DAS running.
>
> Start-instance yields " Unable to connect to admin-server at given host:
> [vwtsas01] and port: [4848]. Please check if this server is up and running
> and that the host and port provided are correct. CLI137 Command
> start-instance failed."
>
> If there's an option to override, we'd love to know about it... or at least
> see it added in the future :-)
>
> On 5/18/10 2:22 PM, "Bill Shannon" <bill.shannon_at_oracle.com> wrote:
>
>> Comerford, Sean wrote on 05/18/10 05:49 AM:
>>> You guys have probably heard this RFE before but Iıll reiterate it just
>>> in case itıs something that can be fixed easily / hasnıt been already in v3:
>>>
>>> There should be an option to start a clustered instance WITHOUT synching
>>> with the DAS at all (i.e. Start and just use the last known configuration).
>>>
>>> Currently, if your DAS goes down, you canıt (re)start any instances
>>> until itıs back up which could be very problematic in case of a
>>> catastrophic failure to the DAS.
>> The intent is that, if the DAS is down when the instance starts up,
>> the startup will continue with a warning. My understanding is that
>> that's what v2 does, is that not the case?
>>
>> We haven't quite got to that point with v3, however...
>>
>> And, if the DAS later comes up, and it is discovered that the instance
>> is out of sync with the DAS, the instance will need to be restarted.
>> We'll probably need a policy flag to control whether the instance
>> restarts automatically in this case or whether the administrator is
>> informed that the instance needs to be restarted.
>>
>>
>> ---------------------------------------------------------------------
>> 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.
>