372046933 commented on issue #2265:
URL: https://github.com/apache/brpc/issues/2265#issuecomment-1581831377
很随机，有时十几分钟出现，有时要几个小时才能出现。用RPC example模拟是个办法，完全实现相同逻辑成本有点高。
时序上是
## Server端
先出现 Close Socket
```
Close Socket{id=8589934931 fd=1341 addr=10.156.1.11:61768:25823}
(0x55f2f6f6c000) due to unknown message:
\B6\80\F5#8\D1$\A3\B6\0C\E7\CE6\DA;\018J\E3\B1\B7Q\EE\FD\B7\F8\01\0B8U\1Bn\B8\11,\t\B8d\18W\B6~+\04\B8
\B9\E16k\E0$\B7\C1\13\E1\B7~"\91\B4\E5\8BS...<skipping 200964 bytes>
```
然后 Fail to write into Socket
```
Fail to write into Socket{id=8589934931 fd=1341
addr=10.156.1.11:61768:25823} (0x55f2f6f6c000): Invalid argument
```
然后 Fail to read Hello message
```
Fail to read Hello Message from client:Socket{id=3842 fd=1341
addr=10.156.1.11:18802:25823} (0x0x55fb763c8000) 10.156.1.11:18802: Got EOF
```
## 客户端
成片RPC失败
```
[E1014]Got EOF of Socket{id=4 fd=1336 addr=10.156.8.29:25823:61768}
(0x0x55aa6dfb8900) [R1][E112]Not connected to 10.156.8.29:25823 yet,
server_id=4 [R2][E112]Not connected to 10.156.8.29:25823 yet, server_id=4
[R3][E112]Not connected to 10.156.8.29:25823 yet, server_id=4 [R4][E112]Not
connected to 10.156.8.29:25823 yet, server_id=4 [R5][E112]Not connected to
10.156.8.29:25823 yet, server_id=4 [R6][E112]Not connected to 10.156.8.29:25823
yet, server_id=4 [R7][E112]Not connected to 10.156.8.29:25823 yet, server_id=4
[R8][E112]Not connected to 10.156.8.29:25823 yet, server_id=4 [R9][E112]Not
connected to 10.156.8.29:25823 yet, server_id=4 [R10][E112]Not connected to
10.156.8.29:25823 yet, server_id=4
```
还有个思路是接受目前的Socket异常，应用层做好重试，由于每次RPC都是有Side effect. 这样的话需要Server端做好重复请求的去重
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
