stop servers doesn't stop monitor

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

stop servers doesn't stop monitor

jcalcote
Hi Yaguang,

I've been testing start/stop servers. I have a system with four OSDs - osd.1, osd.3, osd.5, ods.6. The following is captured by the vsm-agent.log during a "stop server" followed by a "start server":

( ... stop server begins here ... )
2016-01-05 13:28:31     INFO [vsm.agent.driver] agent/driver.py stop_server
2016-01-05 13:28:31     INFO [vsm.agent.driver] Step 1. Scan the osds in db.
2016-01-05 13:28:31     INFO [vsm.agent.driver] Step 2. ceph osd set noout
2016-01-05 13:28:32     INFO [vsm.agent.driver] >> service ceph stop osd.6
2016-01-05 13:28:35     INFO [vsm.agent.driver] >> update status into db osd.6
2016-01-05 13:28:35     INFO [vsm.agent.driver] >> service ceph stop osd.5
2016-01-05 13:28:38     INFO [vsm.agent.driver] >> update status into db osd.5
2016-01-05 13:28:38     INFO [vsm.agent.driver] >> service ceph stop osd.3
2016-01-05 13:28:41     INFO [vsm.agent.driver] >> update status into db osd.3
2016-01-05 13:28:41     INFO [vsm.agent.driver] >> service ceph stop osd.1
2016-01-05 13:28:44     INFO [vsm.agent.driver] >> update status into db osd.1
2016-01-05 13:28:44     INFO [vsm.agent.driver] >> remove ceph mds on hostid(3) start
2016-01-05 13:28:45     INFO [vsm.agent.driver] Have not find mds on 3
( ... start server begins here ... )
2016-01-05 13:29:38     INFO [vsm.agent.driver] >> start the monitor id: 1
2016-01-05 13:29:38     INFO [vsm.agent.driver] Can not find pid file for osd.1
2016-01-05 13:29:39     INFO [vsm.agent.driver] begin to start osd = osd.6
2016-01-05 13:29:39     INFO [vsm.agent.driver] begin to start osd = osd.5
2016-01-05 13:29:39     INFO [vsm.agent.driver] begin to start osd = osd.3
2016-01-05 13:29:39     INFO [vsm.agent.driver] begin to start osd = osd.1
2016-01-05 13:30:14     INFO [vsm.agent.manager] No client io rate update for pool 0.
2016-01-05 13:34:20     INFO [vsm.agent.manager] No client io rate update for pool 0.
2016-01-05 13:36:24     INFO [vsm.agent.manager] No client io rate update for pool 0.
2016-01-05 13:42:36     INFO [vsm.agent.driver] osd_restart osd_id = 5
2016-01-05 13:42:40     INFO [vsm.agent.driver] begin to start osd = osd.6

I noticed that the "start server" command attempts to start the monitor ("start the monitor id: 1"), but the "stop server" command did not stop the monitor. Should "stop server" be stopping all OSDs and the monitor?

Thanks,
John