On Mon, 17 Sep 2012 08:36:09 +0200, Sławomir Skowron <szibis@xxxxxxxxx> wrote: > Ok, i will try, but i have all day meeting today, and tomorrow. > > One more question, is there any way to check configuration not from > ceph.conf, but from running daemon in cluster ?? You can do this with the admin socket: ceph --admin-daemon /path/to/admin/socket show config Josh > > On Fri, Sep 14, 2012 at 9:12 PM, Sage Weil <sage@xxxxxxxxxxx> wrote: >> Hi, >> >> <On Wed, 5 Sep 2012, Skowron S?awomir wrote: >>> Dnia 5 wrz 2012 o godz. 17:53 "Sage Weil" <sage@xxxxxxxxxxx> napisa?(a): >>> >>> > On Wed, 5 Sep 2012, S?awomir Skowron wrote: >>> >> Ok, but in global case, when i use, a chef/puppet or any other, i wish >>> >> to change configuration in ceph.conf, and reload daemon to get new >>> >> configuration changes from ceph.conf, this feature would be very >>> >> helpful in ceph administration. >>> >> >>> >> Inject is ok, for testing, or debuging. >>> > >>> > Opened http://tracker.newdream.net/issues/3086. There is already an issue >>> > open for reloading the config file, >>> > http://tracker.newdream.net/issues/2459. >>> > >>> >>> Thanks. This is what i mean. >>> Is this feature have a chance, to be implemented in next months ?? >> >> I pushed a branch, wip-tp, that implements this. Want to give it a spin? >> Just inject the config option change (via the admin socket or injectargs) >> and it'll resize the thread pool. >> >> sage >> >>> >>> > sage >>> > >>> >> >>> >> On Tue, Sep 4, 2012 at 5:34 PM, Sage Weil <sage@xxxxxxxxxxx> wrote: >>> >>> On Tue, 4 Sep 2012, Wido den Hollander wrote: >>> >>>> On 09/04/2012 10:30 AM, Skowron S?awomir wrote: >>> >>>>> Ok, thanks. >>> >>>>> >>> >>>>> Number of workers used for recover, or numer of disk threads. >>> >>>>> >>> >>>> >>> >>>> I think those can be changed while the OSD is running. You could always give >>> >>>> it a try. >>> >>> >>> >>> The thread pool sizes can't currently be adjusted, unfortunately. It >>> >>> wouldn't be too difficult to change that... >>> >>> >>> >>> sage >>> >>> >>> >>>> >>> >>>> Wido >>> >>>> >>> >>>>> -----Original Message----- >>> >>>>> From: Wido den Hollander [mailto:wido@xxxxxxxxx] >>> >>>>> Sent: Tuesday, September 04, 2012 10:18 AM >>> >>>>> To: Skowron S?awomir >>> >>>>> Cc: ceph-devel@xxxxxxxxxxxxxxx >>> >>>>> Subject: Re: Inject configuration change into cluster >>> >>>>> >>> >>>>> On 09/04/2012 07:04 AM, Skowron S?awomir wrote: >>> >>>>>> Is there any way now, to inject new configuration change, without >>> >>>>>> restarting daemons ?? >>> >>>>>> >>> >>>>> >>> >>>>> Yes, you can use the injectargs command. >>> >>>>> >>> >>>>> $ ceph osd tell 0 injectargs '--debug-osd 20' >>> >>>>> >>> >>>>> What do you want to change? Not everything can be changed while the OSD is >>> >>>>> running. >>> >>>>> >>> >>>>> Wido >>> >>>>> >>> >>>>>> Regards >>> >>>>>> >>> >>>>>> Slawomir Skowron-- >>> >>>>>> 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 >>> >>>>>> >>> >>>>> >>> >>>>> N???????????????r??????y?????????b???X???????v???^???)?{.n???+?????????z???]z???{ay??? ?????,j ??????f?????????h?????????z??? ???w????????? >>> >>>>> ?????????j:+v?????????w???j???m???????????? ????????????zZ+???????j"??????!tml= >>> >>>>> >>> >>>> >>> >>>> -- >>> >>>> 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 >>> >> >>> >> >>> >> >>> >> -- >>> >> ----- >>> >> Pozdrawiam >>> >> >>> >> S?awek "sZiBis" Skowron >>> >> >>> >> >>> -- 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
