[Ocfs2-users] Ocfs2-devel Digest, Vol 127, Issue 25

[Guozhonghua]

Hi Joseph and Srinivas,

We had merged and test the two patches:
1.    ocfs2: o2net: set tcp user timeout to max value
         8e9801dfe37c9e68cdbfcd15988df2187191864e
2.    ocfs2: o2net: don't shutdown connection when idle timeout
         c43c363def04cdaed0d9e26dae846081f55714e7

They are works well as we shut down and up the Ethernet interface manually and intervals to create the scenarios with shell scripts, the issues cat not be recreated.
Thanks you for reviews and better advices.

There is another question.
As the node number rises to 32 or 128 in one cluster, we think the TCP keep alive MSG interval should be make longer from 2 seconds to 10 seconds and the idle timeout value should be 60000ms or 90000ms.
We think it can reduce the non-useful keep alive messages and improve the performance of the TCP connection.
O2CB_IDLE_TIMEOUT_MS=30000  to  90000
O2CB_KEEPALIVE_DELAY_MS=2000  to  10000

We test the values and the changes works well.
Is there any side effect? We are forward your better thoughts about that.
Thanks.

-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!