Log if recovery affected by disconnect (#62437)

Today we only emit `DEBUG` logs if the source disconnects from the
target during a recovery. This deserves to be noisier by default since
it should be rare and may help users identify other problems with their
network or with their shard movements.

This commit promotes this message to `INFO`. There's no need for `WARN`
since these days we will normally resume the recovery where it left off.
This commit is contained in:
David Turner 2020-09-17 08:09:17 +01:00
parent 26388fe22e
commit 14aec44cd8

View File

@ -633,8 +633,8 @@ public class PeerRecoveryTargetService implements IndexEventListener {
}
if (cause instanceof ConnectTransportException) {
logger.debug("delaying recovery of {} for [{}] due to networking error [{}]", request.shardId(),
recoverySettings.retryDelayNetwork(), cause.getMessage());
logger.info("recovery of {} from [{}] interrupted by network disconnect, will retry in [{}]; cause: [{}]",
request.shardId(), request.sourceNode(), recoverySettings.retryDelayNetwork(), cause.getMessage());
if (request.sourceNode().getVersion().onOrAfter(Version.V_7_9_0)) {
reestablishRecovery(request, cause.getMessage(), recoverySettings.retryDelayNetwork());
} else {