On Mon, Dec 19, 2016 at 12:31 PM, Ken Dreyer <kdreyer@xxxxxxxxxx> wrote:
> On Tue, Dec 13, 2016 at 4:42 AM, Francois Lafont
> <francois.lafont.1978@xxxxxxxxx> wrote:
>> So, now with 10.2.5 version, in my process, OSD daemons are stopped,
>> then automatically restarted by the upgrade and then stopped again
>> by the reboot. This is not an optimal process of course. ;)
>
> We do not intend for anything in the packaging to restart the daemons.
>
> The last time I looked into this issue, it behaved correctly (dpkg did
> not restart the daemons during the apt-get process - the PID files
> were the same before and after the upgrade).
I looked into this again on a Trusty VM today. I set up a single
mon+osd cluster on v10.2.3, with the following:
# status ceph-osd id=0
ceph-osd (ceph/0) start/running, process 1301
#ceph daemon osd.0 version
{"version":"10.2.3"}
I ran "apt-get upgrade" to get go 10.2.3 -> 10.2.5, and the OSD PID
(1301) and version from the admin socket (v10.2.3) remained the same.
Could something else be restarting the daemons in your case?
- Ken
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
