Skip to content
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

kraken: osd: FAILED assert(object_contexts.empty()) (live on master only from Jan-Feb 2017, all other instances are different) #16132

Merged
merged 2 commits into from Jul 6, 2017

Conversation

smithfarm
Copy link
Contributor

@smithfarm smithfarm commented Jul 5, 2017

This has always been a bug, but until
68defc2, nothing deleted those contexts
without calling complete().

Fixes: http://tracker.ceph.com/issues/18809
Bug shadowed until: 68defc2
Signed-off-by: Samuel Just <sjust@redhat.com>
(cherry picked from commit 91b7423)
We only flush the ObjectStore callbacks, not everything else.  Thus,
there isn't a guarrantee that the obc held by pull_complete_info will
be cleaned up before the Flush callback is triggered.  Instead, just
defer clearing the pull state until the callback (it'll be cleaned up
during the interval change) and remove the ObjectContext from
pull_complete_info.

Introduced: 68defc2
Fixes: http://tracker.ceph.com/issues/18927
Signed-off-by: Samuel Just <sjust@redhat.com>
(cherry picked from commit 51eee55)
@smithfarm smithfarm requested a review from jdurgin July 5, 2017 20:32
@smithfarm smithfarm merged commit 08b8a73 into ceph:kraken Jul 6, 2017
@smithfarm smithfarm deleted the wip-20522-kraken branch July 6, 2017 07:28
@smithfarm smithfarm changed the title kraken: FAILED assert(object_contexts.empty()) (live on master only from Jan-Feb 2017, all other instances are different) kraken: osd: FAILED assert(object_contexts.empty()) (live on master only from Jan-Feb 2017, all other instances are different) Aug 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants