From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Spray Subject: Re: adding "{mds,mon} metadata" asok command Date: Mon, 23 Mar 2015 10:35:22 +0000 Message-ID: <550FEC6A.1030208@redhat.com> References: <550FE53B.9050407@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com ([209.132.183.28]:47508 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752096AbbCWKf1 (ORCPT ); Mon, 23 Mar 2015 06:35:27 -0400 In-Reply-To: <550FE53B.9050407@gmail.com> Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Joao Eduardo Luis , Sage Weil , kefu chai Cc: "ceph-devel@vger.kernel.org" On 23/03/2015 10:04, Joao Eduardo Luis wrote: > I agree. And I don't think we need a new service for this, and I also > don't think we need to write stuff to the store. We can generate this > information when the monitor hits 'bootstrap()' and share it with the > rest of the quorum once an election finishes, and always keep it in > memory (unless there's some information that needs to be persisted, > but I was under the impression that was not the case). Just to clarify, you mean we don't need to write the mon metadata to the store, but we'd still want to persist the MDS/OSD metadata - right? John