[KUDU-2034] For kudu-jepsen scenario, add parameters to induce more frequent fail-over events on the server side

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.0
• Labels: consistency kudu-jepsen newbie
• Assignee: Unassigned
• Reporter: Alexey Serbin
• Created: 07/Jun/17 03:07
• Updated: 14/Aug/18 15:13

Description

Currently, the set of parameters for the back-end components is almost standard – everything is set to defaults, but the experimental flags are enabled and only the following tserver flags are set to something 'special' to speed up the test:

--heartbeat_interval_ms
--raft_heartbeat_interval_ms
--heartbeat_max_failures_before_backoff

Let's set parameters to induce frequent re-election/fail-over events at the server side. The idea is to bring in set of parameters used by certain tests in src/kudu/integration-tests. E.g., catalog_manager_tsk-itest.cc contains an example of parameters to enable frequent re-elections among masters; the raft-related part can be used as a starting point to update tserver's parameters for kudu-jepsen.

An additional step might be injecting latency into tservers' operations.