PHP Swoole长连接常见问题
|
连接失效问题 配置项:timeout MySQL常见的报错: 配置项:wait_timeout & interactive_timeout 如何解决 2、定时发送心跳维持连接 用的时候进行重连 定时发送心跳维持连接 如何维持长连接 tcp协议中实现的tcp_keepalive 操作系统底层提供了一组tcp的keepalive配置: 1 tcp_keepalive_time (integer; default: 7200; since Linux 2.2) 2 The number of seconds a connection needs to be idle before TCP 3 begins sending out keep-alive probes. Keep-alives are sent only 4 when the SO_KEEPALIVE socket option is enabled. The default 5 value is 7200 seconds (2 hours). An idle connection is 6 terminated after approximately an additional 11 minutes (9 7 probes an interval of 75 seconds apart) when keep-alive is 8 enabled. 9 10 Note that underlying connection tracking mechanisms and 11 application timeouts may be much shorter. 12 13 tcp_keepalive_intvl (integer; default: 75; since Linux 2.4) 14 The number of seconds between TCP keep-alive probes. 15 16 tcp_keepalive_probes (integer; default: 9; since Linux 2.2) 17 The maximum number of TCP keep-alive probes to send before 18 giving up and killing the connection if no response is obtained 19 from the other end. 20 8
1 ?php
2
3 $server = new SwooleServer('127.0.0.1',6666, SWOOLE_PROCESS);
4
5 $server->set([
6 'worker_num' => 1, 7 'open_tcp_keepalive' => 1, 8 'tcp_keepidle' => 4,// 对应tcp_keepalive_time
9 'tcp_keepinterval' => 1,// 对应tcp_keepalive_intvl
10 'tcp_keepcount' => 5,// 对应tcp_keepalive_probes
11 ]);
其中: 1 'open_tcp_keepalive' => 1,// 总开关,用来开启tcp_keepalive 2 'tcp_keepidle' => 4,// 4s没有数据传输就进行检测 3 // 检测的策略如下: 4 'tcp_keepinterval' => 1,// 1s探测一次,即每隔1s给客户端发一个包(然后客户端可能会回一个ack的包,如果服务端收到了这个ack包,那么说明这个连接是活着的) 5 'tcp_keepcount' => 5,// 探测的次数,超过5次后客户端还没有回ack包,那么close此连接 我们来实战测试体验一下,服务端脚本如下: 1 <?php
2
3 $server = new SwooleServer('127.0.0.1',// 开启tcp_keepalive
8 'tcp_keepidle' => 4,// 4s没有数据传输就进行检测
9 'tcp_keepinterval' => 1,// 1s探测一次
10 'tcp_keepcount' => 5,// 探测的次数,超过5次后还没有回包close此连接
11 ]);
12
13 $server->on('connect',function ($server,$fd) {
14 var_dump("Client: Connect $fd");
15 });
16
17 $server->on('receive',$fd,$reactor_id,$data) {
18 var_dump($data);
19 });
20
21 $server->on('close',$fd) {
22 var_dump("close fd $fd");
23 });
24
25 $server->start();
我们启动这个服务器: 1 ~/codeDir/phpCode/hyperf-skeleton # php server.php 然后通过 ~/codeDir/phpCode/hyperf-skeleton # tcpdump -i lo port 6666 tcpdump: verbose output suppressed,use -v or -vv for full protocol decode listening on lo,link-type EN10MB (Ethernet),capture size 262144 bytes 我们此时正在监听 然后我们用客户端去连接它: 1 ~/codeDir/phpCode/hyperf-skeleton # nc 127.0.0.1 6666 此时服务端会打印出消息: ~/codeDir/phpCode/hyperf-skeleton # php server.php string(17) "Client: Connect 1"
1 01:48:40.178439 IP localhost.33933 > localhost.6666: Flags [S],seq 43162537,win 43690,options [mss 65495,sackOK,TS val 9833698 ecr 0,nop,wscale 7],length 0 2 01:48:40.178484 IP localhost.6666 > localhost.33933: Flags [S.],seq 1327460565,ack 43162538,TS val 9833698 ecr 9833698,length 0 3 01:48:40.178519 IP localhost.33933 > localhost.6666: Flags [.],ack 1,win 342,options [nop,TS val 9833698 ecr 9833698],length 0 4 01:48:44.229926 IP localhost.6666 > localhost.33933: Flags [.],TS val 9834104 ecr 9833698],length 0 5 01:48:44.229951 IP localhost.33933 > localhost.6666: Flags [.],length 0 6 01:48:44.229926 IP localhost.6666 > localhost.33933: Flags [.],length 0 7 01:48:44.229951 IP localhost.33933 > localhost.6666: Flags [.],length 0 8 01:48:44.229926 IP localhost.6666 > localhost.33933: Flags [.],length 0 9 // 省略了其他的输出 我们会发现最开始的时候,会打印三次握手的包: 01:48:40.178439 IP localhost.33933 > localhost.6666: Flags [S],length 0 01:48:40.178484 IP localhost.6666 > localhost.33933: Flags [S.],length 0 01:48:40.178519 IP localhost.33933 > localhost.6666: Flags [.],length 0 然后,停留了 之后,每隔 1 01:52:54.359341 IP localhost.6666 > localhost.43101: Flags [.],TS val 9859144 ecr 9858736],length 0 2 01:52:54.359377 IP localhost.43101 > localhost.6666: Flags [.],TS val 9859144 ecr 9855887],length 0 其实这就是我们配置的策略: 1 'tcp_keepinterval' => 1,// 1s探测一次 2 'tcp_keepcount' => 5,// 探测的次数,超过5次后还没有回包close此连接 因为我们操作系统底层会自动的给客户端回 1 01:52:54.359341 IP localhost.6666 > localhost.43101: Flags [.],length 0 如果我们要测试 1 ~/codeDir/phpCode/hyperf-skeleton # iptables -A INPUT -p tcp --dport 6666 -j DROP 这样会把所有从 然后服务器过 1 ~/codeDir/phpCode/hyperf-skeleton # php server.php 2 string(17) "Client: Connect 1" 3 string(10) "close fd 1" 我们恢复一下 1 ~/codeDir/phpCode # iptables -D INPUT -p tcp -m tcp --dport 6666 -j DROP 即把我们设置的规则给删除了。 通过tcp_keepalive的方式实现心跳的功能,优点是简单,不要写代码就可以完成这个功能,并且发送的心跳包小。缺点是依赖于系统的网络环境,必须保证服务器和客户端都实现了这样的功能,需要客户端配合发心跳包。还有一个更为严重的缺点是如果客户端和服务器不是直连的,而是通过代理来进行连接的,例如socks5代理,它只会转发应用层的包,不会转发更为底层的tcp探测包,那这个心跳功能就失效了。 所以,Swoole就提供了其他的解决方案,一组检测死连接的配置。 1 'heartbeat_check_interval' => 1,// 1s探测一次 2 'heartbeat_idle_time' => 5,// 5s未发送数据包就close此连接 swoole实现的heartbeat 我们来测试一下: 1 <?php
2
3 $server = new SwooleServer('127.0.0.1', 7 'heartbeat_check_interval' => 1,// 1s探测一次
8 'heartbeat_idle_time' => 5,// 5s未发送数据包就close此连接
9 ]);
10
11 $server->on('connect',$fd) {
12 var_dump("Client: Connect $fd");
13 });
14
15 $server->on('receive',$data) {
16 var_dump($data);
17 });
18
19 $server->on('close',$fd) {
20 var_dump("close fd $fd");
21 });
22
23 $server->start();
然后启动服务器: 1 ~/codeDir/phpCode/hyperf-skeleton # php server.php 然后启动 1 ~/codeDir/phpCode # tcpdump -i lo port 6666 2 tcpdump: verbose output suppressed,use -v or -vv for full protocol decode 3 listening on lo,capture size 262144 bytes
1 ~/codeDir/phpCode/hyperf-skeleton # nc 127.0.0.1 6666
1 ~/codeDir/phpCode/hyperf-skeleton # php server.php 2 string(17) "Client: Connect 1" 然后tcpdump打印: 1 02:48:32.516093 IP localhost.42123 > localhost.6666: Flags [S],seq 1088388248,TS val 10193342 ecr 0,length 0 2 02:48:32.516133 IP localhost.6666 > localhost.42123: Flags [S.],seq 80508236,ack 1088388249,TS val 10193342 ecr 10193342,length 0 3 02:48:32.516156 IP localhost.42123 > localhost.6666: Flags [.],TS val 10193342 ecr 10193342],length 0 这是三次握手信息。 (编辑:安卓应用网) 【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容! |
