Tim Quinn wrote on 04/30/10 01:24 PM:
> Hi, Vijay.
>
> On Apr 30, 2010, at 2:11 PM, Vijay Ramachandran wrote:
>
>> We are not assuming that the server is going to be up and that the
>> communication is reliable. We will try to send the command to the
>> instance and get back results. If sending the command itself failed,
>> we will flag it as one type of error that indicates something wrong
>> with network or the server. If the command went through to the server
>> but the command execution fails, we will get a detailed error (just as
>> it happens now between CLI-DAS), and we will display this error. In
>> either of the failure cases, we indicate to the caller (the CLI or
>> GUI), that the server(s) where the replication failed need to be
>> restarted.
>
> If the server was up but the remote deploy command failed, why do we
> expect restarting the server to fix the problem? We need to ask the
> administrator to look at the problem and, perhaps, fix something with
> the instance or the app. That's different from a remote deployment
> failing because the DAS could not talk to the instance.
Yes, the administrator may have to do something else to get the
instance working again, but restarting it and synchronizing from
scratch is the only way to get it back in sync if it fails.