Bug 1831755

Summary: [RFE] Initialize Raft cluster with user specified election-timer
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Anil Vishnoi <avishnoi>
Component: openvswitchAssignee: Timothy Redaelli <tredaelli>
openvswitch sub component: daemons and tools QA Contact: Jianlin Shi <jishi>
Status: CLOSED EOL Docs Contact:
Severity: medium    
Priority: unspecified CC: avishnoi, ctrautma, jhsiao, jishi
Version: RHEL 7.7   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: openvswitch2.16-2.16.0-1.el8fdp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-10-08 17:49:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1831778    

Description Anil Vishnoi 2020-05-05 15:04:20 UTC
Description of problem:

Currently OVS Raft cluster initialize with the default election-timer (1000ms). If user wants to change the election-timer value to initialize the cluster with specific value, they need to manually find the raft leader and increase the value by 2*default_value using ovs-appctl till they reach the timer value they want to set.
This requires consumers to write some operational code around it to set this value (for example, see pathc [1]). This can get tricky specifially if your cluster start partitioning during the start-up because of the heavy load to start with.

By allowing this value to be set at start-up of the raft cluster, would simplify the start-up process for the consumers (CNO, OVN, OVN-Kubernetes).


Expected results:
User should be able to pass election-timer value using a start-up time config knob (e.g --election-timer <value>), and raft cluster will override that value as a default election-timer.

[1] https://github.com/openshift/cluster-network-operator/pull/615/commits/bd5f5e6ebd594d1d510b9002f02163844c94ed1d#diff-54b09156f80dfb820afa115de13b8f32R166

Comment 4 ovs-bot 2024-10-08 17:49:14 UTC
This bug did not meet the criteria for automatic migration and is being closed.
If the issue remains, please open a new ticket in https://issues.redhat.com/browse/FDP