Identify the operation type in rejected exception (#60138)

Currently, we do not categorize the operation type in the rejection
exception messsage when we reject an indexing operation for indexing
memory limits. This commit fixes this to ensure that it is identified as
coordinating, primary, or replica.
This commit is contained in:
Tim Brooks 2020-07-27 09:34:16 -06:00
parent dbd7e7793a
commit df0f68da23
No known key found for this signature in database
GPG Key ID: C2AA3BB91A889E77

View File

@ -68,7 +68,7 @@ public class IndexingPressure {
"coordinating_and_primary_bytes=" + bytesWithoutOperation + ", " + "coordinating_and_primary_bytes=" + bytesWithoutOperation + ", " +
"replica_bytes=" + replicaWriteBytes + ", " + "replica_bytes=" + replicaWriteBytes + ", " +
"all_bytes=" + totalBytesWithoutOperation + ", " + "all_bytes=" + totalBytesWithoutOperation + ", " +
"operation_bytes=" + bytes + ", " + "coordinating_operation_bytes=" + bytes + ", " +
"max_coordinating_and_primary_bytes=" + primaryAndCoordinatingLimits + "]", false); "max_coordinating_and_primary_bytes=" + primaryAndCoordinatingLimits + "]", false);
} }
currentCoordinatingBytes.getAndAdd(bytes); currentCoordinatingBytes.getAndAdd(bytes);
@ -99,7 +99,7 @@ public class IndexingPressure {
"coordinating_and_primary_bytes=" + bytesWithoutOperation + ", " + "coordinating_and_primary_bytes=" + bytesWithoutOperation + ", " +
"replica_bytes=" + replicaWriteBytes + ", " + "replica_bytes=" + replicaWriteBytes + ", " +
"all_bytes=" + totalBytesWithoutOperation + ", " + "all_bytes=" + totalBytesWithoutOperation + ", " +
"operation_bytes=" + bytes + ", " + "primary_operation_bytes=" + bytes + ", " +
"max_coordinating_and_primary_bytes=" + primaryAndCoordinatingLimits + "]", false); "max_coordinating_and_primary_bytes=" + primaryAndCoordinatingLimits + "]", false);
} }
currentPrimaryBytes.getAndAdd(bytes); currentPrimaryBytes.getAndAdd(bytes);