[CELEBORN-1662] Handle PUSH_DATA_FAIL_PARTITION_NOT_FOUND in getPushDataFailCause

### What changes were proposed in this pull request?
Add a condition at the start of the failure cause logic to check for PUSH_DATA_FAIL_PARTITION_NOT_FOUND.

### Why are the changes needed?
Currently, the getPushDataFailCause method does not identify and handle the PUSH_DATA_FAIL_PARTITION_NOT_FOUND error type. All other failure causes are explicitly checked and managed, but this specific error type is overlooked.

### Does this PR introduce _any_ user-facing change?
No

### How was this patch tested?
Manual test

Closes #2833 from jiang13021/celeborn-1662.

Authored-by: jiang13021 <jiangyanze.jyz@antgroup.com>
Signed-off-by: SteNicholas <programgeek@163.com>
This commit is contained in:
jiang13021 2024-10-21 21:06:06 +08:00 committed by SteNicholas
parent df01fadc9f
commit dc5f3fb96b
No known key found for this signature in database
GPG Key ID: 1FC79E01BA3B84D5

View File

@ -1888,6 +1888,8 @@ public class ShuffleClientImpl extends ShuffleClient {
cause = StatusCode.PUSH_DATA_PRIMARY_WORKER_EXCLUDED;
} else if (message.startsWith(StatusCode.PUSH_DATA_REPLICA_WORKER_EXCLUDED.name())) {
cause = StatusCode.PUSH_DATA_REPLICA_WORKER_EXCLUDED;
} else if (message.startsWith(StatusCode.PUSH_DATA_FAIL_PARTITION_NOT_FOUND.name())) {
cause = StatusCode.PUSH_DATA_FAIL_PARTITION_NOT_FOUND;
} else if (ExceptionUtils.connectFail(message)) {
// Throw when push to primary worker connection causeException.
cause = StatusCode.PUSH_DATA_CONNECTION_EXCEPTION_PRIMARY;