It’s probably worth trying to put this type of info in the message for the root cause socket read timeout exceptions that get thrown.
It’s the same for all updates really - if you don’t get success or failure, you don’t know what happened. You don't necessarily just want to try again without trying to determine what happened. - Mark http://about.me/markrmiller On Feb 25, 2014, at 1:04 PM, Shalin Shekhar Mangar (JIRA) <[email protected]> wrote: > This is a synchronous operation and therefore keeping a large read timeout on > the invocation is advised. The request may still timeout due to inherent > limitations of the Collection APIs but that doesn’t necessarily mean that the > operation has failed. Users should check logs, cluster state, source and > target collections before invoking the operation again. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
