Officially, it is said that all worker and tasker processes can be smoothly restarted through
$swoole->reload(), or \swoole_process::kill($ master_pid, SIGUSR1), or directly kill -USR1 master_pid, etc.
Recommended learning:swoole video tutorial
Simple test
Open a swoole_http_server, both the worker process and tasker process are 1 Then the browser initiates an http request, and the content of the request is just a simple sleep. Through the sleep function, it should be able to indicate that the worker processing this request is in working status, and then perform a reload operation during the sleep period.
When a request is initiated to the swoole server for the first time, the manager process will schedule the request to the worker for processing. Then during the sleep period of the worker processing, if another request comes in, the manager will not send the subsequent request. The request is scheduled to the only worker process, because the worker process is still busy processing the first request. This can be confirmed with a simple test.
http requests are simply routed to the following. Because the easyswoole framework is used, executing the php easyswoole reload all command is actually kill -USR1 master_pid.
Server configuration
$swoole_server->set([ 'worker_num' => 1, 'task_worker_num' => 1, 'reload_async' => true, 'max
Start testing
1. The task logic is written in the worker process
http method
public function test() { $start = microtime(true); echo '请求开始时间:' . $start . PHP_EOL; echo 'pid: ' . getmypid() . PHP_EOL; sleep(30); # 这里睡眠脚本作测试 echo 'finish sleep' . PHP_EOL; $end = microtime(true); echo '请求结束时间:' . $end . PHP_EOL; $this->writeJson(0, round(($end - $start), 3)); }
Monitor onWorkerStart () method
EventHelper::registerWithAdd(ServerManager::getInstance()->getMainEventRegister(),EventRegister::onWorkerStart,function (\swoole_server $server,$workerId){ if(PHP_OS != 'Darwin'){ $name = Config::getInstance()->getConf('SERVER_NAME'); if( ($workerId < Config::getInstance()->getConf('MAIN_SERVER.SETTING.worker_num')) && $workerId >= 0){ $type = 'Worker'; }else{ $type = 'TaskWorker'; } cli_set_process_title("{$name}.{$type}.{$workerId}"); } # 下面是打印测试的 if ($type == 'Worker') { echo "这个是reload worker的时间:" . microtime(true) . "\n"; } if ($type == 'TaskWorker') { echo "这个是reload TaskWorker的时间:" . microtime(true) . "\n"; } });
Test result:
Request start time: 1566880257.9533 # The http interface is requested here, which is test()
pid: 42108
This This is the time to reload TaskWorker: 1566880265.1501 # This is the time to execute php easyswoole reload all. Because the tasker is idle and has no tasks, it can be reloaded immediately.
This is the reload worker time: 1566880275.1524 # This is the worker's reload time, because sleep(30) is in test(), and it exceeds max_wait_time, the bottom layer will not continue to wait for the worker's task to be completed, and directly The old worker was terminated, but 'finish sleep' was not printed, and a new worker was created.
# But why does it take 10 seconds to re-create the worker? Max_wait_time is set to 5s? ? This is something I've never been able to figure out.
The above is the detailed content of How to restart swoole. For more information, please follow other related articles on the PHP Chinese website!