From: Christian Kauhaus <kc@flyingcircus.io>
To: Robert LeBlanc <robert@leblancnet.us>
Cc: Ceph-User <ceph-users@ceph.com>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: [ceph-users] Blocked requests after "osd in"
Date: Fri, 11 Dec 2015 15:14:48 +0100 [thread overview]
Message-ID: <566ADA58.3070905@flyingcircus.io> (raw)
In-Reply-To: <CAANLjFqUoGTFSYrdwCwRw0apfXJN61SeS7FiXb0A_Bxtu4PJJg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
Am 10.12.2015 um 06:38 schrieb Robert LeBlanc:
> Since I'm very interested in
> reducing this problem, I'm willing to try and submit a fix after I'm
> done with the new OP queue I'm working on. I don't know the best
> course of action at the moment, but I hope I can get some input for
> when I do try and tackle the problem next year.
Is there already a ticket present for this issue in the bug tracker? I think
this is an import issue.
Regards
Christian
--
Dipl-Inf. Christian Kauhaus <>< · kc@flyingcircus.io · +49 345 219401-0
Flying Circus Internet Operations GmbH · http://flyingcircus.io
Forsterstraße 29 · 06112 Halle (Saale) · Deutschland
HR Stendal 21169 · Geschäftsführer: Christian Theune, Christian Zagrodnick
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-12-11 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5667FC6E.5080600@flyingcircus.io>
[not found] ` <B0751415-538E-471E-B310-76812C3C374C@schermer.cz>
[not found] ` <56683B9E.8070201@flyingcircus.io>
2015-12-10 5:38 ` [ceph-users] Blocked requests after "osd in" Robert LeBlanc
[not found] ` <CAANLjFqUoGTFSYrdwCwRw0apfXJN61SeS7FiXb0A_Bxtu4PJJg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-12-10 9:03 ` Christian Kauhaus
2015-12-10 9:58 ` [ceph-users] " Jan Schermer
2015-12-11 14:14 ` Christian Kauhaus [this message]
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=566ADA58.3070905@flyingcircus.io \
--to=kc@flyingcircus.io \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@ceph.com \
--cc=robert@leblancnet.us \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox