Oops. Looks like you are already on "next".
Greg,
Perhaps the issue still exists?
- Mike
On 4/26/2013 3:55 PM, Mike Dawson wrote:
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
