Skip to content

HBASE-27781 Fix case of action counter assertion error in handling of batch operation timeout exceeded #7079

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: branch-2
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -448,30 +448,22 @@ void groupAndSendMultiAction(List<Action> currentActions, int numAttempt) {

boolean isReplica = false;
List<Action> unknownReplicaActions = null;
List<Action> locateRegionFailedActions = null;
for (Action action : currentActions) {
if (isOperationTimeoutExceeded()) {
String message = numAttempt == 1
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The logic here has been preserved exactly inside of failIncompleteActionsWithOpTimeout , I opted to move it into a new method because groupAndSendMultiAction is already quite long and complex and we need to add more logic to it to handle this bug, I believe its better to do this timeout handling inside a seperate method that is clearly named with docstring

? "Operation timeout exceeded during resolution of region locations, "
+ "prior to executing any actions."
: "Operation timeout exceeded during re-resolution of region locations on retry "
+ (numAttempt - 1) + ".";

message += " Meta may be slow or operation timeout too short for batch size or retries.";
OperationTimeoutExceededException exception =
new OperationTimeoutExceededException(message);

// Clear any actions we already resolved, because none will have been executed yet
// We are going to fail all passed actions because there's no way we can execute any
// if operation timeout is exceeded.
actionsByServer.clear();
for (Action actionToFail : currentActions) {
manageLocationError(actionToFail, exception);
}
failIncompleteActionsWithOpTimeout(currentActions, locateRegionFailedActions, numAttempt);
return;
}

RegionLocations locs = findAllLocationsOrFail(action, true);
if (locs == null) continue;
if (locs == null) {
if (locateRegionFailedActions == null) {
locateRegionFailedActions = new ArrayList<>(1);
}
Comment on lines +461 to +463
Copy link
Preview

Copilot AI Jun 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The null check and initialization for 'locateRegionFailedActions' is repeated in multiple places. Consider extracting this logic into a helper method to reduce duplication and improve maintainability.

Suggested change
if (locateRegionFailedActions == null) {
locateRegionFailedActions = new ArrayList<>(1);
}
locateRegionFailedActions = initializeIfNull(locateRegionFailedActions);

Copilot uses AI. Check for mistakes.

locateRegionFailedActions.add(action);
continue;
}
boolean isReplicaAction = !RegionReplicaUtil.isDefaultReplica(action.getReplicaId());
if (isReplica && !isReplicaAction) {
// This is the property of the current implementation, not a requirement.
Expand All @@ -488,6 +480,10 @@ void groupAndSendMultiAction(List<Action> currentActions, int numAttempt) {
} else {
// TODO: relies on primary location always being fetched
manageLocationError(action, null);
if (locateRegionFailedActions == null) {
locateRegionFailedActions = new ArrayList<>(1);
}
locateRegionFailedActions.add(action);
}
} else {
byte[] regionName = loc.getRegionInfo().getRegionName();
Expand Down Expand Up @@ -561,6 +557,39 @@ private RegionLocations findAllLocationsOrFail(Action action, boolean useCache)
return loc;
}

/**
* For failing all actions that were being grouped during a groupAndSendMultiAction when operation
* timeout was exceeded and there is no time remaining to continue grouping/sending any of the
* actions. We don't fail any actions which have already failed to completion during grouping due
* to location error (they already have an error set and had action counter decremented for)
* @param actions actions being processed by the groupAndSend when operation
* timeout occurred
* @param locateRegionFailedActions actions already failed to completion due to location error
* @param numAttempt the number of attempts so far
*/
private void failIncompleteActionsWithOpTimeout(List<Action> actions,
List<Action> locateRegionFailedActions, int numAttempt) {
String message = numAttempt == 1
? "Operation timeout exceeded during resolution of region locations, "
+ "prior to executing any actions."
: "Operation timeout exceeded during re-resolution of region locations on retry "
+ (numAttempt - 1) + ".";
message += " Meta may be slow or operation timeout too short for batch size or retries.";
OperationTimeoutExceededException exception = new OperationTimeoutExceededException(message);

for (Action actionToFail : actions) {
// Action equality is implemented as row equality so we check action index equality
// since we don't want two different actions for the same row to be considered equal here
boolean actionAlreadyFailed =
locateRegionFailedActions != null && locateRegionFailedActions.stream().anyMatch(
failedAction -> failedAction.getOriginalIndex() == actionToFail.getOriginalIndex()
&& failedAction.getReplicaId() == actionToFail.getReplicaId());
if (!actionAlreadyFailed) {
Comment on lines +583 to +587
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The logic for avoiding the assertion error is here, rest of the method is existing logic from groupAndSendMulti

manageLocationError(actionToFail, exception);
}
}
}

/**
* Send a multi action structure to the servers, after a delay depending on the attempt number.
* Asynchronous.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@
import java.io.IOException;
import java.net.SocketTimeoutException;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import org.apache.hadoop.conf.Configuration;
import org.apache.hadoop.hbase.HBaseClassTestRule;
Expand Down Expand Up @@ -321,6 +322,70 @@ public void testMultiGetRetryTimeout() {
}
}

/**
* Test that for a batch operation where region location resolution fails for the first action in
* the batch and consumes the entire operation timeout, that the location error is preserved for
* the first action and that the rest of the batch is failed fast with
* OperationTimeoutExceededException , this also (indirectly) tests that the action counter is
* decremented properly for all actions, see last catch block
*/
@Test
public void testMultiOperationTimoutWithLocationError() throws IOException, InterruptedException {
Copy link
Preview

Copilot AI Jun 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a typo in the test method name 'testMultiOperationTimoutWithLocationError'. Consider renaming it to 'testMultiOperationTimeoutWithLocationError' for clarity.

Suggested change
public void testMultiOperationTimoutWithLocationError() throws IOException, InterruptedException {
public void testMultiOperationTimeoutWithLocationError() throws IOException, InterruptedException {

Copilot uses AI. Check for mistakes.

// Need meta delay > meta scan timeout > operation timeout (with no retries) so that the
// meta scan for resolving region location for the first action times out after the operation
// timeout has been exceeded leaving no time to attempt region location resolution for any
// other actions remaining in the batch
int operationTimeout = 100;
int metaScanTimeout = 150;
DELAY_META_SCAN = 200;

Configuration conf = new Configuration(UTIL.getConfiguration());
conf.setLong(HConstants.HBASE_CLIENT_OPERATION_TIMEOUT, operationTimeout);
conf.setLong(ConnectionConfiguration.HBASE_CLIENT_META_SCANNER_TIMEOUT, metaScanTimeout);
conf.setLong(HConstants.HBASE_CLIENT_RETRIES_NUMBER, 0);

try (Connection specialConnection = ConnectionFactory.createConnection(conf);
Table specialTable = specialConnection.getTable(TABLE_NAME)) {

// Region location resolution for first action should fail due to meta scan timeout and cause
// the batch to exceed the operation timeout, second and third action should then be failed
// fast with OperationTimeoutExceededException
Get firstAction = new Get(Bytes.toBytes(0)).addColumn(FAMILY, QUALIFIER);
Get secondAction = firstAction;
Get thirdAction = new Get(Bytes.toBytes(1)).addColumn(FAMILY, QUALIFIER);
List<Get> gets = Arrays.asList(firstAction, secondAction, thirdAction);
try {
specialTable.batch(gets, new Object[3]);
Assert.fail("Should not reach here");
} catch (RetriesExhaustedWithDetailsException exception) {
byte[] firstExceptionRow = exception.getRow(0).getRow();
Assert.assertEquals(firstAction.getRow(), firstExceptionRow);

// CallTimeout comes from the scan timeout to meta table in locateRegionInMeta
Throwable firstActionCause = exception.getCause(0);
Assert.assertTrue(firstActionCause instanceof RetriesExhaustedException);
Assert.assertTrue(firstActionCause.getCause() instanceof CallTimeoutException);

byte[] secondExceptionRow = exception.getRow(1).getRow();
Assert.assertEquals(secondAction.getRow(), secondExceptionRow);

Throwable secondActionCause = exception.getCause(1);
Assert.assertTrue(secondActionCause instanceof OperationTimeoutExceededException);

byte[] thirdExceptionRow = exception.getRow(2).getRow();
Assert.assertEquals(thirdAction.getRow(), thirdExceptionRow);

Throwable thirdActionCause = exception.getCause(2);
Assert.assertTrue(thirdActionCause instanceof OperationTimeoutExceededException);
}
} catch (SocketTimeoutException ste) {
if (ste.getMessage().contains("time out before the actionsInProgress changed to zero")) {
Assert.fail("Not all actions had action counter decremented: " + ste);
}
throw ste;
}
}

/**
* Tests that scan on a table throws {@link RetriesExhaustedException} when the operation takes
* longer than 'hbase.client.scanner.timeout.period'.
Expand Down