AmandeepSingh285 opened a new pull request, #3695:
URL: https://github.com/apache/celeborn/pull/3695
<!--
Thanks for sending a pull request! Here are some tips for you:
- Make sure the PR title start w/ a JIRA ticket, e.g. '[CELEBORN-XXXX]
Your PR title ...'.
- Be sure to keep the PR description updated to reflect all changes.
- Please write your PR title to summarize what this PR proposes.
- If possible, provide a concise example to reproduce the issue for a
faster review.
-->
### What changes were proposed in this pull request?
The patch re-instantiates RocksDB in case of failures. In the current
implementation, when RocksDB enters a read-only mode due to failures, Celeborn
metadata operations fail and remain blocked until manual intervention or
restart.
This PR adds logic to detect such RocksDB failures and re-instantiate the
RocksDB instance so that metadata operations can recover automatically and
continue functioning without prolonged disruption.
RocksDB can enter a read-only or unusable state under scenarios such as:
corruption in files, errors from underlying file system
In such cases, RocksDB prevents further writes to protect data consistency,
which causes Celeborn metadata operations to fail.
### Why are the changes needed?
Currently, once RocksDB enters a read-only or error state, Celeborn metadata
operations become unavailable because the existing RocksDB instance remains
unusable. This can lead to failures in metadata updates
### Does this PR resolve a correctness bug?
No
<!-- Yes/No. (Note: If yes, committer will add `correctness` label to
current pull request). -->
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
