From mboxrd@z Thu Jan 1 00:00:00 1970 From: Piotr =?utf-8?B?RGHFgmVr?= Subject: Re: Osd failure detection Date: Thu, 9 Nov 2017 13:25:30 +0100 Message-ID: <20171109122530.GA4634@mailware> References: <20171109120318.1946caf2@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from predictor.org.pl ([185.5.97.54]:49818 "EHLO predictor.org.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754211AbdKIMdN (ORCPT ); Thu, 9 Nov 2017 07:33:13 -0500 Content-Disposition: inline In-Reply-To: Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Wei Jin Cc: David Disseldorp , ceph-devel On Thu, Nov 09, 2017 at 08:13:57PM +0800, Wei Jin wrote: > On Thu, Nov 9, 2017 at 7:03 PM, David Disseldorp wrote: > > On Thu, 9 Nov 2017 17:43:04 +0800, Wei Jin wrote: > >> This is critical and we have no plan to upgrade to Luminous so far. > >> Is there any plan to back port it Jewel? Or anybody know the related pr or patches? Maybe I could do it by myself. > > > > It was backported to Jewel, alongside a bunch of other async messenger > > fixes, and submitted via https://github.com/ceph/ceph/pull/13212 . IIRC, > > there's still a small async messenger leak blocking the PR. > > > > Yeah. It is still open and marked as DNM. > And there are some issues with async messenger. As async is not the > default one, why not just make it available for simple messenger? Because the change is so vast that it would affect async messenger anyway. In fact I didn't bother backporting it myself because I was certain that maintainers/backporters wouldn't give it a green light anyway. -- Piotr Dałek branch@predictor.org.pl http://blog.predictor.org.pl