Merge release/2.6 into google/2.6 #15759
Open
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
Contributor
mjmac
commented
Jan 22, 2025
mjmac
commented
- DAOS-16477 pool: Rename Suspect state to Dead (DAOS-16477 pool: Rename Suspect state to Dead #15716)
- DAOS-16469 dtx: properly handle DTX partial commit - b26 (DAOS-16469 dtx: properly handle DTX partial commit - b26 #15399)
- DAOS-16868 bio: Skip LED reset on absent bdev (DAOS-16868 bio: Skip LED reset on absent bdev #15718) (DAOS-16868 bio: Skip LED reset on absent bdev (#15718) #15733)
- DAOS-16897 object: add N+3 EC object class (DAOS-16897 object: add N+3 EC object class #15649) (DAOS-16897 object: add N+3 EC object class (#15649) #15730)
- DAOS-16374 vos: integer overflow on evt recx trace (DAOS-16374 vos: integer overflow on evt recx trace #15439) (DAOS-16374 vos: integer overflow on evt recx trace (#15439) #15533)
Change the name to more closely reflect the underlying SWIM status, and reduce user confusion. An engine that has been marked DEAD by SWIM cannot participate in pool services, and has most likely already SIGKILL-ed itself. Update "engines become unavailable" in admin/troubleshooting.md to link to the new "suspect ranks" description. Signed-off-by: Li Wei <[email protected]> Signed-off-by: Michael MacDonald <[email protected]> Signed-off-by: Wang Shilong <[email protected]> Co-authored-by: Michael MacDonald <[email protected]> Co-authored-by: Li Wei <[email protected]>
When a DTX leader globally commit the DTX, it is possible that some DTX participant(s) cannot commit such DTX entry because of kinds of issues, such as network or space trouble. Under such case, the DTX leader needs to keep the active DTX entry persistently for further commit/resync. But it does not means related modification attched to such DTX entry on the leader target cannot be committed, instead, we can commit related modification with only keeping the DTX header. That is enough for the DTX leader to do further DTX commit/resync to handle related former failed DTX participant(s). The benefit is that VOS aggregation on the leader target will not be affected by remote DTX commit failure. Signed-off-by: Fan Yong <[email protected]>
Signed-off-by: Tom Nabarro <[email protected]>
Currently, DAOS supports EC (Erasure Coding) object classes with redundancy levels of N+1 and N+2. In certain scenarios, users may wish to use N+3 for enhanced redundancy and safety. Generally, DAOS’s EC and rebuild mechanisms are designed to handle various parity levels effectively. With the introduction of new object classes, comprehensive testing should be conducted to ensure that these changes do not introduce any unexpected issues or disrupt existing functionalities. Extend test cases to cover EC_4P3X object classes as a min test coverage. Signed-off-by: Wang Shilong <[email protected]>
The evt recx trace is used for vos aggregation debugging, and it's currently reset on akey iteration callback, but the akey iteration callback could be skipped in some cases, for example, when evt aggregation hit an aborted recx, it'll start over in evtree level without the recx trace reset, that could lead to integer overflow on the 'int ap_trace_count'. This patch moved the ap_trace_count reset to merge window open/close to ensure the evt recx trace always being reset properly. Signed-off-by: Niu Yawei <[email protected]> Co-authored-by: Niu Yawei <[email protected]>
Features: pool Change-Id: I9e7d49d5c31dc048546de2010a88fcca5ff4a9d2 Signed-off-by: Michael MacDonald <[email protected]>
|
Errors are component not formatted correctly,Ticket number prefix incorrect,PR title is malformatted. See https://daosio.atlassian.net/wiki/spaces/DC/pages/11133911069/Commit+Comments,Unable to load ticket data |
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.