All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Samuel Just <sam.just@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: FAILED assert(peer_missing.count(fromshard))
Date: Fri, 16 Jan 2015 17:39:09 +0100	[thread overview]
Message-ID: <54B93EAD.2040200@dachary.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 572 bytes --]

Hi Sam,

In the context of http://tracker.ceph.com/issues/10524 FAILED assert(peer_missing.count(fromshard)) I propose to add some information for when it happens:

https://github.com/ceph/ceph/pull/3389

If what happens really is that a bad peer ends up being added with in missing_loc.add_location, that will be a useful information. I tried a number of scenarios and could not find the right conditions to reproduce the problem locally. Hopefully this additional information will show me where to go :-)

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2015-01-16 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 16:39 Loic Dachary [this message]
2015-01-16 18:10 ` FAILED assert(peer_missing.count(fromshard)) Samuel Just
2015-01-16 18:16   ` Loic Dachary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54B93EAD.2040200@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sam.just@inktank.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.