Thanks, but does this not work on Luminous maybe? I am on the mon hosts
trying this:
# ceph config set osd osd_recovery_max_active 4
Invalid command: unused arguments: [u'4']
config set <key> <value> : Set a configuration option at runtime (not
persistent)
Error EINVAL: invalid command
# ceph daemon osd.0 config diff|grep -A5 osd_recovery_max_active
admin_socket: exception getting command descriptions: [Errno 2] No such
file or directory
On Tue, Apr 16, 2019 at 4:04 PM Brad Hubbard <bhubb...@redhat.com> wrote:
> $ ceph config set osd osd_recovery_max_active 4
> $ ceph daemon osd.0 config diff|grep -A5 osd_recovery_max_active
> "osd_recovery_max_active": {
> "default": 3,
> "mon": 4,
> "override": 4,
> "final": 4
> },
>
> On Wed, Apr 17, 2019 at 5:29 AM solarflow99 <solarflo...@gmail.com> wrote:
> >
> > I wish there was a way to query the running settings from one of the MGR
> hosts, and it doesn't help that ansible doesn't even copy the keyring to
> the OSD nodes so commands there wouldn't work anyway.
> > I'm still puzzled why it doesn't show any change when I run this no
> matter what I set it to:
> >
> > # ceph -n osd.1 --show-config | grep osd_recovery_max_active
> > osd_recovery_max_active = 3
> >
> > in fact it doesn't matter if I use an OSD number that doesn't exist,
> same thing if I use ceph get
> >
> >
> >
> > On Tue, Apr 16, 2019 at 1:18 AM Brad Hubbard <bhubb...@redhat.com>
> wrote:
> >>
> >> On Tue, Apr 16, 2019 at 6:03 PM Paul Emmerich <paul.emmer...@croit.io>
> wrote:
> >> >
> >> > This works, it just says that it *might* require a restart, but this
> >> > particular option takes effect without a restart.
> >>
> >> We've already looked at changing the wording once to make it more
> palatable.
> >>
> >> http://tracker.ceph.com/issues/18424
> >>
> >> >
> >> > Implementation detail: this message shows up if there's no internal
> >> > function to be called when this option changes, so it can't be sure if
> >> > the change is actually doing anything because the option might be
> >> > cached or only read on startup. But in this case this option is read
> >> > in the relevant path every time and no notification is required. But
> >> > the injectargs command can't know that.
> >>
> >> Right on all counts. The functions are referred to as observers and
> >> register to be notified if the value changes, hence "not observed."
> >>
> >> >
> >> > Paul
> >> >
> >> > On Mon, Apr 15, 2019 at 11:38 PM solarflow99 <solarflo...@gmail.com>
> wrote:
> >> > >
> >> > > Then why doesn't this work?
> >> > >
> >> > > # ceph tell 'osd.*' injectargs '--osd-recovery-max-active 4'
> >> > > osd.0: osd_recovery_max_active = '4' (not observed, change may
> require restart)
> >> > > osd.1: osd_recovery_max_active = '4' (not observed, change may
> require restart)
> >> > > osd.2: osd_recovery_max_active = '4' (not observed, change may
> require restart)
> >> > > osd.3: osd_recovery_max_active = '4' (not observed, change may
> require restart)
> >> > > osd.4: osd_recovery_max_active = '4' (not observed, change may
> require restart)
> >> > >
> >> > > # ceph -n osd.1 --show-config | grep osd_recovery_max_active
> >> > > osd_recovery_max_active = 3
> >> > >
> >> > >
> >> > >
> >> > > On Wed, Apr 10, 2019 at 7:21 AM Eugen Block <ebl...@nde.ag> wrote:
> >> > >>
> >> > >> > I always end up using "ceph --admin-daemon
> >> > >> > /var/run/ceph/name-of-socket-here.asok config show | grep ..."
> to get what
> >> > >> > is in effect now for a certain daemon.
> >> > >> > Needs you to be on the host of the daemon of course.
> >> > >>
> >> > >> Me too, I just wanted to try what OP reported. And after trying
> that,
> >> > >> I'll keep it that way. ;-)
> >> > >>
> >> > >>
> >> > >> Zitat von Janne Johansson <icepic...@gmail.com>:
> >> > >>
> >> > >> > Den ons 10 apr. 2019 kl 13:37 skrev Eugen Block <ebl...@nde.ag>:
> >> > >> >
> >> > >> >> > If you don't specify which daemon to talk to, it tells you
> what the
> >> > >> >> > defaults would be for a random daemon started just now using
> the same
> >> > >> >> > config as you have in /etc/ceph/ceph.conf.
> >> > >> >>
> >> > >> >> I tried that, too, but the result is not correct:
> >> > >> >>
> >> > >> >> host1:~ # ceph -n osd.1 --show-config | grep
> osd_recovery_max_active
> >> > >> >> osd_recovery_max_active = 3
> >> > >> >>
> >> > >> >
> >> > >> > I always end up using "ceph --admin-daemon
> >> > >> > /var/run/ceph/name-of-socket-here.asok config show | grep ..."
> to get what
> >> > >> > is in effect now for a certain daemon.
> >> > >> > Needs you to be on the host of the daemon of course.
> >> > >> >
> >> > >> > --
> >> > >> > May the most significant bit of your life be positive.
> >> > >>
> >> > >>
> >> > >>
> >> > >> _______________________________________________
> >> > >> ceph-users mailing list
> >> > >> ceph-users@lists.ceph.com
> >> > >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> >> > >
> >> > > _______________________________________________
> >> > > ceph-users mailing list
> >> > > ceph-users@lists.ceph.com
> >> > > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> >> > _______________________________________________
> >> > ceph-users mailing list
> >> > ceph-users@lists.ceph.com
> >> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> >>
> >>
> >>
> >> --
> >> Cheers,
> >> Brad
>
>
>
> --
> Cheers,
> Brad
>
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
