gitops/patroni
1
0
Fork 0
mirror of https://github.com/outbackdingo/patroni.git synced 2026-08-25 14:53:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

Spelling only

Browse Source
This commit is contained in:
Feike Steenbergen
2016-05-13 09:17:23 +02:00
parent 622e110f0a
commit c3317f748e
1 changed files with 5 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
specs/dynamic_configuration.rst
+5 -12
View File
@@ -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.