From c3317f748e1562f7d7029f7f2075605681d659a5 Mon Sep 17 00:00:00 2001 From: Feike Steenbergen Date: Fri, 13 May 2016 09:17:23 +0200 Subject: [PATCH] Spelling only --- specs/dynamic_configuration.rst | 17 +++++------------ 1 file changed, 5 insertions(+), 12 deletions(-) diff --git a/specs/dynamic_configuration.rst b/specs/dynamic_configuration.rst index a65012ab..6bdd714b 100644 --- a/specs/dynamic_configuration.rst +++ b/specs/dynamic_configuration.rst @@ -3,7 +3,7 @@ Patroni configuration reload Patroni configuration should be stored in the DCS. There will be 3 types of configuration: -- bootstrap configuraton set in Patroni +- bootstrap configuration set in Patroni That should be applied during the initialization time and written to etcd. - startup configuration (also in patroni.yml). @@ -14,9 +14,9 @@ Patroni configuration should be stored in the DCS. There will be 3 types of conf Those options can be set in etcd at any time. If the options changed are not part of the startup configuration, they are applied asynchronously (upon the next wake up cycle) to every node, which gets subsequently reloaded. If the node requires a restart to apply the configuration (for options with context postmaster or internal, if - their values have changed), a special flag indiciating this should be set in the members.data JSON. A new API - endpoint should return whether the given node requires a restart. Additionally, the node status shoudl also - idincate this. + their values have changed), a special flag indicating this should be set in the members.data JSON. A new API + endpoint should return whether the given node requires a restart. Additionally, the node status should also + indicate this. Some options may not be increased on the master independently of the replicas (master-dependent options): @@ -46,16 +46,9 @@ Also, the following patroni configuration options can be changed dynamically: - loop_wait - retry_timeouts (to be defined first in patroni.yaml) -Upon changing those options, Patroni should read the relevant section of the configuration storedi in DCS and change their +Upon changing those options, Patroni should read the relevant section of the configuration stored in DCS and change their run-time values. Patroni nodes should dump the state of the DCS options to disk on startup and upon every change of the configuration. Only master is allowed to restore those options from the on-disk dump if those are completely absent from the DCS or invalid. - - - - - - -