forked from apache/ozone
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Implementation #3
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ivanzlenko
force-pushed
the
HDDS-fscheck
branch
from
September 9, 2024 09:08
79f8a6a
to
04de724
Compare
ivanzlenko
force-pushed
the
HDDS-fscheck-part2
branch
from
September 9, 2024 09:11
84ff2fb
to
352e269
Compare
ivanzlenko
force-pushed
the
HDDS-fscheck
branch
from
September 10, 2024 06:34
04de724
to
e067c4f
Compare
ivanzlenko
force-pushed
the
HDDS-fscheck-part2
branch
from
September 10, 2024 06:34
352e269
to
b06be25
Compare
ivanzlenko
force-pushed
the
HDDS-fscheck
branch
from
September 11, 2024 06:38
e067c4f
to
cdd0ee2
Compare
ivanzlenko
force-pushed
the
HDDS-fscheck-part2
branch
from
September 11, 2024 06:38
b06be25
to
22f60f7
Compare
ivanzlenko
force-pushed
the
HDDS-fscheck
branch
2 times, most recently
from
September 11, 2024 08:28
83911de
to
9740df9
Compare
…s was not equal to checksumBlockDataChunks. (apache#7009)
Co-authored-by: ashishk <ashishk@cloudera.com>
ivanzlenko
force-pushed
the
HDDS-fscheck-part2
branch
from
September 12, 2024 04:40
22f60f7
to
026faac
Compare
…for transactions in flight on the snapshot (apache#7179)
…uble buffer batch (apache#7188)
…ce/compile/kubernetes (apache#7192)
…acceptance/compile/kubernetes (apache#7192)" This reverts commit a7d7e37.
This reverts commit 008602b.
…r#testMarkContainerUnhealthyInFailedVolume (apache#7219)
…on snapshot deletes (apache#7200)
ivanzlenko
force-pushed
the
HDDS-fscheck-part2
branch
from
September 23, 2024 03:09
026faac
to
9cb6aa5
Compare
ivanzlenko
force-pushed
the
HDDS-fscheck-part2
branch
from
September 25, 2024 13:27
9cb6aa5
to
11c90d1
Compare
ivanzlenko
force-pushed
the
HDDS-fscheck-part2
branch
from
September 26, 2024 06:44
11c90d1
to
89ae571
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.)