Skip to content

DAOS-18361 chk: handle CHK engine side inconsistency in parallel#17556

Draft
Nasf-Fan wants to merge 1 commit intoNasf-Fan/DAOS-18587from
Nasf-Fan/DAOS-18361_1
Draft

DAOS-18361 chk: handle CHK engine side inconsistency in parallel#17556
Nasf-Fan wants to merge 1 commit intoNasf-Fan/DAOS-18587from
Nasf-Fan/DAOS-18361_1

Conversation

@Nasf-Fan
Copy link
Contributor

On CHK engine side, most of inconsistencies can be handled in parallel. For each of them, create dedicated ULT to handle the inconsistency and report (including interaction) to CHK leader independently. So even if some ULT was blocked for some reason, such as waiting for interaction, it will not affect the other inconsistencies to be handled in parallel.

Test-tag: recovery

Steps for the author:

  • Commit message follows the guidelines.
  • Appropriate Features or Test-tag pragmas were used.
  • Appropriate Functional Test Stages were run.
  • At least two positive code reviews including at least one code owner from each category referenced in the PR.
  • Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

  • Gatekeeper requested (daos-gatekeeper added as a reviewer).

On CHK engine side, most of inconsistencies can be handled in parallel.
For each of them, create dedicated ULT to handle the inconsistency and
report (including interaction) to CHK leader independently. So even if
some ULT was blocked for some reason, such as waiting for interaction,
it will not affect the other inconsistencies to be handled in parallel.

Test-tag: recovery

Signed-off-by: Fan Yong <fan.yong@hpe.com>
@github-actions
Copy link

Ticket title is 'CR did not detect orphan container shards on Aurora'
Status is 'In Review'
https://daosio.atlassian.net/browse/DAOS-18361

@daosbuild3
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments