From: Mike Dawson <mike.dawson@scholarstack.com>
To: Wido den Hollander <wido@42on.com>
Cc: Sage Weil <sage@inktank.com>,
greg@inktank.com, ceph-devel@vger.kernel.org
Subject: Re: final mon issues
Date: Fri, 26 Apr 2013 15:55:28 -0400 [thread overview]
Message-ID: <517ADBB0.904@scholarstack.com> (raw)
In-Reply-To: <517ADB34.1020105@42on.com>
Wido,
I think you saw the same issue I did
(http://tracker.ceph.com/issues/4793). If so, I believe there is a fix
in "next".
- Mike
On 4/26/2013 3:53 PM, Wido den Hollander wrote:
> On 04/26/2013 09:43 PM, Sage Weil wrote:
>> I've merged the double-forward fix. I still have one remaining problem
>> that I can reproduce with my tests which looks like an overlap of mon
>> overload forwarded message priorities; I'm testing two possible fixes to
>> see which are necessary to resolve it.
>>
>> The memory issues with people using the gitbuilder appear to be because
>> our gitbuilders weren't linking in tcmalloc. The latest 'next' build
>> *does* link it now, so if you are one of those people, please re-test!
>>
>> I don't think either of those problems is related to the sync issues Mike
>> is seeing, though. I believe that is the final outstanding issue...?
>>
>
> I think I also just noticed a sync issue, reported it as:
> http://tracker.ceph.com/issues/4837
>
> This e-mail and my report just crossed each other I think.
>
>> sage
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
next prev parent reply other threads:[~2013-04-26 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 19:43 final mon issues Sage Weil
2013-04-26 19:53 ` Wido den Hollander
2013-04-26 19:55 ` Mike Dawson [this message]
2013-04-26 19:57 ` Mike Dawson
2013-04-26 19:58 ` Gregory Farnum
2013-04-26 20:13 ` Mark Nelson
2013-04-26 20:18 ` Mike Dawson
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=517ADBB0.904@scholarstack.com \
--to=mike.dawson@scholarstack.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=sage@inktank.com \
--cc=wido@42on.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.