That would accomplish what you are looking for, yes. Keep in mind that with norebalance that won't stop NEW data from landing there. It will only keep old data from migrating in. This shouldn't pose too much of an issue for most use cases. -- Paul Mezzanini Sr Systems Administrator / Engineer, Research Computing Information & Technology Services Finance & Administration Rochester Institute of Technology o:(585) 475-3245 | pfmeec@xxxxxxx CONFIDENTIALITY NOTE: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information. ------------------------ ________________________________________ From: Satish Patel <satish.txt@xxxxxxxxx> Sent: Tuesday, October 1, 2019 2:45 PM To: Paul Mezzanini Cc: ceph-users Subject: Re: how to set osd_crush_initial_weight 0 without restart any service You are saying set "ceph osd set norebalance" before running ceph-ansible playbook to add OSD once osd visible in "ceph osd tree" then i should do reweight to 0 and then do "ceph osd unset norebalance" On Tue, Oct 1, 2019 at 2:41 PM Paul Mezzanini <pfmeec@xxxxxxx> wrote: > > You could also: > ceph osd set norebalance > > > -- > Paul Mezzanini > Sr Systems Administrator / Engineer, Research Computing > Information & Technology Services > Finance & Administration > Rochester Institute of Technology > o:(585) 475-3245 | pfmeec@xxxxxxx > > CONFIDENTIALITY NOTE: The information transmitted, including attachments, is > intended only for the person(s) or entity to which it is addressed and may > contain confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon this > information by persons or entities other than the intended recipient is > prohibited. If you received this in error, please contact the sender and > destroy any copies of this information. > ------------------------ > > ________________________________________ > From: ceph-users <ceph-users-bounces@xxxxxxxxxxxxxx> on behalf of Satish Patel <satish.txt@xxxxxxxxx> > Sent: Tuesday, October 1, 2019 2:34 PM > To: ceph-users > Subject: how to set osd_crush_initial_weight 0 without restart any service > > Folks, > > Method: 1 > > In my lab i am playing with ceph and trying to understand how to add > new OSD without starting rebalancing. > > I want to add this option on fly so i don't need to restart any > services or anything. > > $ ceph tell mon.* injectargs '--osd_crush_initial_weight 0' > > $ ceph daemon /var/run/ceph/ceph-mon.*.asok config show | grep > osd_crush_initial_weight > "osd_crush_initial_weight": "0.000000", > > All looks good, now i am adding OSD with ceph-ansible and you know > what look like it don't honer that option and adding OSD with default > weight (In my case i have 1.9TB SSD so weight is 1.7) > > Can someone confirm injectargs work with osd_crush_initial_weight ? > > > Method: 2 > > Now i have added that option in ceph-ansible playbook like following > > ceph_conf_overrides: > osd: > osd_crush_initial_weight: 0 > > and i run playbook and it did magic and added OSD with weight zero (0) > but i have notice it restarted all OSD daemon on that node, i am > worried is it safe to restart osd daemon on ceph in production? > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |