mirror of
https://github.com/scylladb/scylladb.git
synced 2026-04-23 01:50:35 +00:00
I am about to change resharding to block the start of the node. Being a somewhat slow operation, the timeout of 900 sec is guaranteed to trigger in large nodes with lots of data. This patch effectively disables the start timeout, while keeping the stop timeout unchanged. My preference would have been to use a timeout extension mechanism during resharding. Systemd actually has such mechanism, where we can send a message through sd_notify asking the timeout to be extended. However such mechanism is not present in SystemD v219, used by RHEL7. That means for RHEL7 we need a different way to deal with the timeout anyway. The second preference is also obviously to write "infinity" as the timeout value. But guess what? SystemD v219 also has a bug in which infinity is interepreted as zero (https://bugzilla.redhat.com/show_bug.cgi?id=1446015) Signed-off-by: Glauber Costa <glauber@scylladb.com> Message-Id: <20200407155754.10020-1-glauber@scylladb.com>