New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
msg/async/rdm: fix leak when existing failure in ip network #13435
Conversation
Signed-off-by: Haomai Wang <haomai@xsky.com>
@Adirl plz test this pr in your cluster to verify current qp number and see whether matching our assuption.. |
Great ! thanks |
@yuyuyu101 with 1 osds up out of 13 in, we got- with 6 osds up out of 13 in, we got - with 13 osds up out of 13 in, we got - |
@DanielBo @yuyuyu101 |
@yuyuyu101 Following the logs from the problematic node, this is what happens: The log is also attached. 2017-02-28 12:06:25.992135 7f9c3cc5f700 25 -- 11.0.0.4:6800/17441 >> 11.0.0.2:6800/5645 conn(0x7f9c4e324800 :-1 s=STATE_CONNECTING_WAIT_BANNER_AND_IDENTIFY pgs=0 cs=0 l=1).read_until read_bulk recv_end is 0 left is 281 got 281 |
Hey @yuyuyu101, any idea on why this is happening? |
@DanielBar-On see #13810 |
Signed-off-by: Haomai Wang haomai@xsky.com