Reduce shard started failure logging (#43330)
If the master is stepping or shutting down, the error-level logging can cause quite a bit of noise.
This commit is contained in:
parent
7f8e1454ab
commit
a76c034866
|
@ -589,9 +589,13 @@ public class ShardStateAction {
|
|||
|
||||
@Override
|
||||
public void onFailure(String source, Exception e) {
|
||||
if (e instanceof FailedToCommitClusterStateException || e instanceof NotMasterException) {
|
||||
logger.debug(() -> new ParameterizedMessage("failure during [{}]", source), e);
|
||||
} else {
|
||||
logger.error(() -> new ParameterizedMessage("unexpected failure during [{}]", source), e);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
public static class StartedShardEntry extends TransportRequest {
|
||||
final ShardId shardId;
|
||||
|
|
Loading…
Reference in New Issue