summaryrefslogtreecommitdiffstats
path: root/drivers/block/drbd/drbd_req.h
diff options
context:
space:
mode:
authorLars Ellenberg <lars.ellenberg@linbit.com>2018-12-20 17:23:41 +0100
committerJens Axboe <axboe@kernel.dk>2018-12-20 09:51:31 -0700
commit9848b6ddd8c92305252f94592c5e278574e7a6ac (patch)
treeaf4222f659d1bb396e8fd127b19f5beb10c0d949 /drivers/block/drbd/drbd_req.h
parent9049ccd46f1f39166c99861c2c59d01ce3e20fd6 (diff)
downloadlinux-9848b6ddd8c92305252f94592c5e278574e7a6ac.tar.gz
linux-9848b6ddd8c92305252f94592c5e278574e7a6ac.tar.bz2
linux-9848b6ddd8c92305252f94592c5e278574e7a6ac.zip
drbd: skip spurious timeout (ping-timeo) when failing promote
If you try to promote a Secondary while connected to a Primary and allow-two-primaries is NOT set, we will wait for "ping-timeout" to give this node a chance to detect a dead primary, in case the cluster manager noticed faster than we did. But if we then are *still* connected to a Primary, we fail (after an additional timeout of ping-timout). This change skips the spurious second timeout. Most people won't notice really, since "ping-timeout" by default is half a second. But in some installations, ping-timeout may be 10 or 20 seconds or more, and spuriously delaying the error return becomes annoying. Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/block/drbd/drbd_req.h')
0 files changed, 0 insertions, 0 deletions