-
Notifications
You must be signed in to change notification settings - Fork 0
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
Hdds 11784 #1
base: master
Are you sure you want to change the base?
Hdds 11784 #1
Conversation
…n the DB or Snapshot Chain. (apache#7557)
@sokui I think this PR in your fork was opened accidentally. |
I intentionally opened this to check how CI works. Will close afterwards. |
expired abort request
…ocateBlock latency (apache#7160)" This reverts commit bf6f323.
It's great that you check CI status. But opening a PR is not necessary to get CI feedback. CI checks are run for both push: https://github.com/sokui/ozone/actions/runs/12309831979 |
… prefix presence (apache#7567)
…g SST file reader (apache#7563)
…tatisticsWhileBalancingInProgress (apache#7579)
…apache#7581) Co-authored-by: Jyotirmoy Sinha <jsinha@cloudera.com>
…eived per datanode (apache#7522)
…, hdds-crypto-default, hdds-docs (apache#7638)
…, hdds-hadoop-dependency-client. (apache#7644)
…age is unavailable (apache#6339)
What changes were proposed in this pull request?
Provide a one-liner summary of the changes in the PR Title field above.
It should be in the form of
HDDS-1234. Short summary of the change
.Please describe your PR in detail:
perspective not just for the reviewer.
the Jira's description if the jira is well defined.
issue investigation, github discussion, etc.
Examples of well-written pull requests:
What is the link to the Apache JIRA
Please create an issue in ASF JIRA before opening a pull request, and you need to set the title of the pull
request which starts with the corresponding JIRA issue number. (e.g. HDDS-XXXX. Fix a typo in YYY.)
(Please replace this section with the link to the Apache JIRA)
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests, workflow run on the fork git repo.)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this.)