diff options
author | Gang He <ghe@suse.com> | 2018-05-02 10:28:35 -0500 |
---|---|---|
committer | David Teigland <teigland@redhat.com> | 2018-05-02 10:28:35 -0500 |
commit | f706d830154b6c8405c6b77595a60d135182c97e (patch) | |
tree | b09e5fa8f6c7df5b9da46888053358dba1f83c9e /fs/dlm/recoverd.c | |
parent | b09c603ca40fc6980188f9c7f419c0918a3f461e (diff) | |
download | linux-f706d830154b6c8405c6b77595a60d135182c97e.tar.bz2 |
dlm: make sctp_connect_to_sock() return in specified time
When the user setup a two-ring cluster, DLM kernel module
will automatically selects to use SCTP protocol to communicate
between each node. There will be about 5 minute hang in DLM
kernel module, in case one ring is broken before switching to
another ring, this will potentially affect the dependent upper
applications, e.g. ocfs2, gfs2, clvm and clustered-MD, etc.
Unfortunately, if the user setup a two-ring cluster, we can not
specify DLM communication protocol with TCP explicitly, since
DLM kernel module only supports SCTP protocol for multiple
ring cluster.
Base on my investigation, the time is spent in sock->ops->connect()
function before returns ETIMEDOUT(-110) error, since O_NONBLOCK
argument in connect() function does not work here, then we should
make sock->ops->connect() function return in specified time via
setting socket SO_SNDTIMEO atrribute.
Signed-off-by: Gang He <ghe@suse.com>
Signed-off-by: David Teigland <teigland@redhat.com>
Diffstat (limited to 'fs/dlm/recoverd.c')
0 files changed, 0 insertions, 0 deletions