From 24286f381b0d6b8e4969645aac6b3ba5550a5905 Mon Sep 17 00:00:00 2001 From: Vladimir Danilov Date: Thu, 5 Dec 2024 22:18:35 +0500 Subject: [PATCH] docs(priority-election): fix the property key (#4716) --- .../zeebe-deployment/configuration/priority-election.md | 8 ++++---- .../zeebe-deployment/configuration/priority-election.md | 8 ++++---- .../zeebe-deployment/configuration/priority-election.md | 8 ++++---- .../zeebe-deployment/configuration/priority-election.md | 8 ++++---- .../zeebe-deployment/configuration/priority-election.md | 8 ++++---- 5 files changed, 20 insertions(+), 20 deletions(-) diff --git a/docs/self-managed/zeebe-deployment/configuration/priority-election.md b/docs/self-managed/zeebe-deployment/configuration/priority-election.md index 4e466a0640..d7fc45c041 100644 --- a/docs/self-managed/zeebe-deployment/configuration/priority-election.md +++ b/docs/self-managed/zeebe-deployment/configuration/priority-election.md @@ -10,8 +10,8 @@ It aims to achieve a more uniform leader distribution by assigning each node a p ## Configuration -Enable priority election by setting `zeebe.broker.raft.enablePriorityElection = "true"` in your config or -by setting the equivalent environment variable `ZEEBE_BROKER_RAFT_ENABLEPRIORITYELECTION="true"`. +Enable priority election by setting `zeebe.broker.cluster.raft.enablePriorityElection=true` in your config or +by setting the equivalent environment variable `ZEEBE_BROKER_CLUSTER_RAFT_ENABLEPRIORITYELECTION=true`. If you are using the fixed partitioning scheme (experimental), you may need [additional configuration](fixed-partitioning.md#priority-election). @@ -19,7 +19,7 @@ If you are using the fixed partitioning scheme (experimental), you may need [add With priority election enabled, election latency and thus failover time increases. -The result of leader election is not deterministic and priority election can only increase the chance of having a +The result of a leader election is not deterministic, and priority election can only increase the chance of having a uniform leader distribution, not guarantee it. -Factors such as high load can prevent high priority nodes from becoming the leader. +Factors such as high load can prevent high-priority nodes from becoming the leader. diff --git a/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/priority-election.md b/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/priority-election.md index 4e466a0640..d7fc45c041 100644 --- a/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/priority-election.md +++ b/versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/priority-election.md @@ -10,8 +10,8 @@ It aims to achieve a more uniform leader distribution by assigning each node a p ## Configuration -Enable priority election by setting `zeebe.broker.raft.enablePriorityElection = "true"` in your config or -by setting the equivalent environment variable `ZEEBE_BROKER_RAFT_ENABLEPRIORITYELECTION="true"`. +Enable priority election by setting `zeebe.broker.cluster.raft.enablePriorityElection=true` in your config or +by setting the equivalent environment variable `ZEEBE_BROKER_CLUSTER_RAFT_ENABLEPRIORITYELECTION=true`. If you are using the fixed partitioning scheme (experimental), you may need [additional configuration](fixed-partitioning.md#priority-election). @@ -19,7 +19,7 @@ If you are using the fixed partitioning scheme (experimental), you may need [add With priority election enabled, election latency and thus failover time increases. -The result of leader election is not deterministic and priority election can only increase the chance of having a +The result of a leader election is not deterministic, and priority election can only increase the chance of having a uniform leader distribution, not guarantee it. -Factors such as high load can prevent high priority nodes from becoming the leader. +Factors such as high load can prevent high-priority nodes from becoming the leader. diff --git a/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/priority-election.md b/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/priority-election.md index 4e466a0640..d7fc45c041 100644 --- a/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/priority-election.md +++ b/versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/priority-election.md @@ -10,8 +10,8 @@ It aims to achieve a more uniform leader distribution by assigning each node a p ## Configuration -Enable priority election by setting `zeebe.broker.raft.enablePriorityElection = "true"` in your config or -by setting the equivalent environment variable `ZEEBE_BROKER_RAFT_ENABLEPRIORITYELECTION="true"`. +Enable priority election by setting `zeebe.broker.cluster.raft.enablePriorityElection=true` in your config or +by setting the equivalent environment variable `ZEEBE_BROKER_CLUSTER_RAFT_ENABLEPRIORITYELECTION=true`. If you are using the fixed partitioning scheme (experimental), you may need [additional configuration](fixed-partitioning.md#priority-election). @@ -19,7 +19,7 @@ If you are using the fixed partitioning scheme (experimental), you may need [add With priority election enabled, election latency and thus failover time increases. -The result of leader election is not deterministic and priority election can only increase the chance of having a +The result of a leader election is not deterministic, and priority election can only increase the chance of having a uniform leader distribution, not guarantee it. -Factors such as high load can prevent high priority nodes from becoming the leader. +Factors such as high load can prevent high-priority nodes from becoming the leader. diff --git a/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/priority-election.md b/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/priority-election.md index 4e466a0640..d7fc45c041 100644 --- a/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/priority-election.md +++ b/versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/priority-election.md @@ -10,8 +10,8 @@ It aims to achieve a more uniform leader distribution by assigning each node a p ## Configuration -Enable priority election by setting `zeebe.broker.raft.enablePriorityElection = "true"` in your config or -by setting the equivalent environment variable `ZEEBE_BROKER_RAFT_ENABLEPRIORITYELECTION="true"`. +Enable priority election by setting `zeebe.broker.cluster.raft.enablePriorityElection=true` in your config or +by setting the equivalent environment variable `ZEEBE_BROKER_CLUSTER_RAFT_ENABLEPRIORITYELECTION=true`. If you are using the fixed partitioning scheme (experimental), you may need [additional configuration](fixed-partitioning.md#priority-election). @@ -19,7 +19,7 @@ If you are using the fixed partitioning scheme (experimental), you may need [add With priority election enabled, election latency and thus failover time increases. -The result of leader election is not deterministic and priority election can only increase the chance of having a +The result of a leader election is not deterministic, and priority election can only increase the chance of having a uniform leader distribution, not guarantee it. -Factors such as high load can prevent high priority nodes from becoming the leader. +Factors such as high load can prevent high-priority nodes from becoming the leader. diff --git a/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/priority-election.md b/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/priority-election.md index 4e466a0640..d7fc45c041 100644 --- a/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/priority-election.md +++ b/versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/priority-election.md @@ -10,8 +10,8 @@ It aims to achieve a more uniform leader distribution by assigning each node a p ## Configuration -Enable priority election by setting `zeebe.broker.raft.enablePriorityElection = "true"` in your config or -by setting the equivalent environment variable `ZEEBE_BROKER_RAFT_ENABLEPRIORITYELECTION="true"`. +Enable priority election by setting `zeebe.broker.cluster.raft.enablePriorityElection=true` in your config or +by setting the equivalent environment variable `ZEEBE_BROKER_CLUSTER_RAFT_ENABLEPRIORITYELECTION=true`. If you are using the fixed partitioning scheme (experimental), you may need [additional configuration](fixed-partitioning.md#priority-election). @@ -19,7 +19,7 @@ If you are using the fixed partitioning scheme (experimental), you may need [add With priority election enabled, election latency and thus failover time increases. -The result of leader election is not deterministic and priority election can only increase the chance of having a +The result of a leader election is not deterministic, and priority election can only increase the chance of having a uniform leader distribution, not guarantee it. -Factors such as high load can prevent high priority nodes from becoming the leader. +Factors such as high load can prevent high-priority nodes from becoming the leader.