Add doc for --initial-election-tick-advance flag (etcd-io#435)

* Add doc for --initial-election-tick-advance flag

Signed-off-by: Aman Dwivedi <[email protected]>

* Drop v3.5 change

Co-authored-by: Patrice Chalin <[email protected]>

content/en/docs/v3.1/op-guide/configuration.md

@@ -43,6 +43,11 @@ To start etcd automatically using custom settings at startup in Linux, using a [
 + default: "1000"
 + env variable: ETCD_ELECTION_TIMEOUT
 
+### --initial-election-tick-advance
++ Whether to fast-forward initial election ticks on boot for faster election. When it is true, then local member fast-forwards election ticks to speed up "initial" leader election trigger. This benefits the case of larger election ticks. Disabling this would slow down initial bootstrap process for cross datacenter deployments. Make your own tradeoffs by configuring this flag at the cost of slow initial bootstrap.
++ default: true
++ env variable: ETCD_INITIAL_ELECTION_TICK_ADVANCE
+
 ### --listen-peer-urls
 + List of URLs to listen on for peer traffic. This flag tells the etcd to accept incoming requests from its peers on the specified scheme://IP:port combinations. Scheme can be either http or https.If 0.0.0.0 is specified as the IP, etcd listens to the given port on all interfaces. If an IP address is given as well as a port, etcd will listen on the given port and interface. Multiple URLs may be used to specify a number of addresses and ports to listen on. The etcd will respond to requests from any of the listed addresses and ports.
 + default: "http://localhost:2380"

content/en/docs/v3.2/op-guide/configuration.md

@@ -43,6 +43,11 @@ To start etcd automatically using custom settings at startup in Linux, using a [
 + default: "1000"
 + env variable: ETCD_ELECTION_TIMEOUT
 
+### --initial-election-tick-advance
++ Whether to fast-forward initial election ticks on boot for faster election. When it is true, then local member fast-forwards election ticks to speed up "initial" leader election trigger. This benefits the case of larger election ticks. Disabling this would slow down initial bootstrap process for cross datacenter deployments. Make your own tradeoffs by configuring this flag at the cost of slow initial bootstrap.
++ default: true
++ env variable: ETCD_INITIAL_ELECTION_TICK_ADVANCE
+
 ### --listen-peer-urls
 + List of URLs to listen on for peer traffic. This flag tells the etcd to accept incoming requests from its peers on the specified scheme://IP:port combinations. Scheme can be either http or https.If 0.0.0.0 is specified as the IP, etcd listens to the given port on all interfaces. If an IP address is given as well as a port, etcd will listen on the given port and interface. Multiple URLs may be used to specify a number of addresses and ports to listen on. The etcd will respond to requests from any of the listed addresses and ports.
 + default: "http://localhost:2380"

content/en/docs/v3.3/op-guide/configuration.md

@@ -48,6 +48,11 @@ To start etcd automatically using custom settings at startup in Linux, using a [
 + default: "1000"
 + env variable: ETCD_ELECTION_TIMEOUT
 
+### --initial-election-tick-advance
++ Whether to fast-forward initial election ticks on boot for faster election. When it is true, then local member fast-forwards election ticks to speed up "initial" leader election trigger. This benefits the case of larger election ticks. Disabling this would slow down initial bootstrap process for cross datacenter deployments. Make your own tradeoffs by configuring this flag at the cost of slow initial bootstrap.
++ default: true
++ env variable: ETCD_INITIAL_ELECTION_TICK_ADVANCE
+
 ### --listen-peer-urls
 + List of URLs to listen on for peer traffic. This flag tells the etcd to accept incoming requests from its peers on the specified scheme://IP:port combinations. Scheme can be http or https. Alternatively, use `unix://<file-path>` or `unixs://<file-path>` for unix sockets. If 0.0.0.0 is specified as the IP, etcd listens to the given port on all interfaces. If an IP address is given as well as a port, etcd will listen on the given port and interface. Multiple URLs may be used to specify a number of addresses and ports to listen on. The etcd will respond to requests from any of the listed addresses and ports.
 + default: "http://localhost:2380"

content/en/docs/v3.4/op-guide/configuration.md

@@ -50,6 +50,11 @@ To start etcd automatically using custom settings at startup in Linux, using a [
 + default: "1000"
 + env variable: ETCD_ELECTION_TIMEOUT
 
+### --initial-election-tick-advance
++ Whether to fast-forward initial election ticks on boot for faster election. When it is true, then local member fast-forwards election ticks to speed up "initial" leader election trigger. This benefits the case of larger election ticks. Disabling this would slow down initial bootstrap process for cross datacenter deployments. Make your own tradeoffs by configuring this flag at the cost of slow initial bootstrap.
++ default: true
++ env variable: ETCD_INITIAL_ELECTION_TICK_ADVANCE
+
 ### --listen-peer-urls
 + List of URLs to listen on for peer traffic. This flag tells the etcd to accept incoming requests from its peers on the specified scheme://IP:port combinations. Scheme can be http or https. Alternatively, use `unix://<file-path>` or `unixs://<file-path>` for unix sockets. If 0.0.0.0 is specified as the IP, etcd listens to the given port on all interfaces. If an IP address is given as well as a port, etcd will listen on the given port and interface. Multiple URLs may be used to specify a number of addresses and ports to listen on. The etcd will respond to requests from any of the listed addresses and ports.
 + default: "http://localhost:2380"