-
Notifications
You must be signed in to change notification settings - Fork 297
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
DAOS-15672 rebuild: Fix pool destroy hangs #14183
Conversation
Ticket title is 'Couldn't destroy a pool because of outstanding ds_pool_child references due to migrate_pool_tls leaks' |
See the Jira ticket for the long story. When releasing resources, for instance, for stopping a pool, we should attempt on all targets, because the latest version of the pool map may differ from the version used to acquire the resources. (And in some cases, we no longer have the original pool map version in the context.) Signed-off-by: Li Wei <wei.g.li@intel.com> Required-githooks: true
Removed the container change because it is already in #14108. |
Test stage Functional Hardware Medium Verbs Provider completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-14183/2/execution/node/1452/log |
daos_test/degraded: DAOS-15519 (the fix landed after this PR was created) |
See the Jira ticket for the long story. When releasing resources, for instance, for stopping a pool, we should attempt on all targets, because the latest version of the pool map may differ from the version used to acquire the resources. (And in some cases, we no longer have the original pool map version in the context.) Required-githooks: true Change-Id: I363fbfefae01dd75cc07ded31a2e5b7033f01610 Signed-off-by: Li Wei <wei.g.li@intel.com>
DAOS-14679 pool: Report on stopping sp_stopping (#14374) DAOS-15514 container: fix container destroy failure (#14108) DAOS-15672 rebuild: Fix pool destroy hangs (#14183) DAOS-15145 pool: add pool collective function (#13764) *DAOS-14105 object: collectively punch object (#13493) partial backport, just the bitmap function Signed-off-by: Jeff Olivier <jeffolivier@google.com> Signed-off-by: Li Wei <wei.g.li@intel.com> Signed-off-by: Wang Shilong <shilong.wang@intel.com>
See the Jira ticket for the long story. When releasing resources, for instance, for stopping a pool, we should attempt on all targets, because the latest version of the pool map may differ from the version used to acquire the resources. (And in some cases, we no longer have the original pool map version in the context.)
Before requesting gatekeeper:
Features:
(orTest-tag*
) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.Gatekeeper: