Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mypy: Add type hints to pglookout [BF-1560] #106

Open
wants to merge 24 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 20 commits
Commits
Show all changes
24 commits
Select commit Hold shift + click to select a range
0d4ea2c
mypy: `pglookout/logutil.py` [BF-1560]
Mar 16, 2023
238eb76
mypy: `pglookout/pgutil.py` [BF-1560]
Mar 16, 2023
3db5684
mypy: `pglookout/current-master.py` [BF-1560]
Mar 17, 2023
2ce13ab
mypy: `pglookout/statsd.py` [BF-1560]
Mar 17, 2023
25617d1
mypy: `pglookout/common.py` [BF-1560]
Mar 16, 2023
016d14d
mypy: `pglookout/config.py` [BF-1560]
Mar 17, 2023
bf067b3
mypy: `pglookout/common_types.py` [BF-1560]
Mar 23, 2023
a462bf9
mypy: `pglookout/webserver.py` [BF-1560]
Mar 17, 2023
9b4e13f
mypy: `pglookout/cluster_monitor.py` [BF-1560]
Mar 17, 2023
45d413b
mypy: `pglookout/pglookout.py` [BF-1560]
Mar 23, 2023
6ce993e
mypy: Refactor `check_cluster_state` [BF-1560]
Mar 24, 2023
0d438e9
mypy: `test/test_pglookout.py` [BF-1560]
Mar 27, 2023
1f47155
mypy: New method to normalize config [BF-1560]
Mar 27, 2023
5d4ac6e
mypy: `version.py` [BF-1560]
Mar 27, 2023
51bb85e
mypy: `setup.py` [BF-1560]
Mar 27, 2023
e9834d4
mypy: Remove python2 dependency [BF-1560]
Mar 27, 2023
a3ad6f8
mypy: `conftest.py` [BF-1560]
Mar 27, 2023
7434873
Bump `Makefile` version to `2.1.0` [BF-1560]
Mar 27, 2023
30bcd0d
mypy: Compatible with Python 3.9 logging [BF-1560]
Mar 27, 2023
e4e771a
pylint: Enable more messages [BF-1560]
Mar 27, 2023
56c01a8
pylint: Fix broad exception raised [BF-1560]
Mar 28, 2023
09a15b1
pylint: Dev requirements are now pinned [BF-1560]
Mar 28, 2023
9a0abae
make: Dev reqs are now in isolation [BF-1560]
Apr 4, 2023
dac0aad
Merge remote-tracking branch 'origin/main' into sgiffard/BF-1560_add_…
Apr 5, 2023
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions Makefile
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
short_ver = 2.0.3
short_ver = 2.1.0
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bump. Open to other types of bump.

long_ver = $(shell git describe --long 2>/dev/null || echo $(short_ver)-0-unknown-g`git describe --always`)
generated = pglookout/version.py

PYTHON ?= python3
PYTHON_SOURCE_DIRS = pglookout/ test/
PYTHON_SOURCE_DIRS = pglookout/ test/ stubs/ version.py setup.py

all: $(generated)
: 'try "make rpm" or "make deb" or "make test"'
Expand All @@ -17,7 +17,7 @@ unittest: $(generated)
$(PYTHON) -m pytest

mypy: $(generated)
$(PYTHON) -m mypy
MYPYPATH=stubs $(PYTHON) -m mypy

flake8: $(generated)
$(PYTHON) -m flake8 $(PYTHON_SOURCE_DIRS)
Expand Down
153 changes: 79 additions & 74 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -201,6 +201,11 @@ description of the current state of the cluster which is under monitoring.
Configuration keys
==================

``alert_file_dir`` (default ``os.getcwd()``)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I alphabetically sorted configuration keys in the README. This has the effect of grouping related keys closer.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe a different PR? This one is already big enough:)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sort could have been in a different PR or a different commit (just the sort operation, no change). My bad 🙇.
Having them in 016d14d might not be the best. That's why I added the GitHub comments to guide reviewers (there's a sort and there's one key that was missing). If that's not good enough, sure it would be possible to split, rebase interactively (pray), force push, modify the test in aiven-core to target the new hash. Tell me if you want this.


Directory in which alert files for replication warning and failover
are created.

``autofollow`` (default ``false``)

Do you want pglookout to try to start following the new primary. Useful
Expand All @@ -210,38 +215,24 @@ to start following the new primary.
Requires ``pg_data_directory``, ``pg_start_command``
and ``pg_stop_command`` configuration keys to be set.

``cluster_monitor_health_timeout_seconds`` (default: ``2 * replication_state_check_interval``)

If set, it will increase the statsd counter `cluster_monitor_health_timeout` if the
`cluster_monitor` thread has not successfully completed a check since
`cluster_monitor_health_timeout_seconds`.

``db_poll_interval`` (default ``5.0``)

Interval on how often should the connections defined in remote_conns
be polled for information on DB replication state.

``remote_conns`` (default ``{}``)

PG database connection strings that the pglookout process should monitor.
Keys of the object should be names of the remotes and values must be valid
PostgreSQL connection strings or connection info objects.

``primary_conninfo_template``

Connection string or connection info object template to use when setting a new
primary_conninfo value for recovery.conf after a failover has happened. Any
provided hostname and database name in the template is ignored and they are
replaced with a replication connection to the new primary node.

Required when ``autofollow`` is true.

``observers`` (default ``{}``)
``failover_command`` (default ``""``)

This object contains key value pairs like ``{"1.2.3.4":
"http://2.3.4.5:15000"}``. They are used to determine the location of
pglookout observer processes. Observers are processes that don't take any
actions, but simply give a third party viewpoint on the state of the
cluster. Useful especially during net splits.
Shell command to execute in case the node has deemed itself in need of promotion

``poll_observers_on_warning_only`` (default ``False``)
``failover_sleep_time`` (default ``0.0``)

this allows observers to be polled only when replication lag is over
``warning_replication_time_lag``
Time to sleep after a failover command has been issued.

``http_address`` (default ``""``)

Expand All @@ -251,55 +242,36 @@ HTTP webserver address, by default pglookout binds to all interfaces.

HTTP webserver port.

``replication_state_check_interval`` (default ``10.0``)
``json_state_file_path`` (default ``"/tmp/pglookout_state.json"``)

How often should pglookout check the replication state in order to
make decisions on should the node be promoted.
Location of a JSON state file which describes the state of the
pglookout process.

``failover_sleep_time`` (default ``0.0``)
``known_gone_nodes`` (default ``[]``)

Time to sleep after a failover command has been issued.
Lists nodes that are explicitly known to have left the cluster. If the old
primary is removed in a controlled manner it should be added to this list to
ensure there's no extra delay when making promotion decision.

``log_level`` (default ``"INFO"``)

Determines log level of pglookout.

``maintenance_mode_file`` (default ``"/tmp/pglookout_maintenance_mode_file"``)

If a file exists in this location, this node will not be considered
for promotion to primary.

``missing_master_from_config_timeout`` (default ``15``)

In seconds the amount of time before we do a failover decision if a
previously existing primary has been removed from the config file and
we have gotten a SIGHUP.

``alert_file_dir`` (default ``os.getcwd()``)

Directory in which alert files for replication warning and failover
are created.

``json_state_file_path`` (default ``"/tmp/pglookout_state.json"``)

Location of a JSON state file which describes the state of the
pglookout process.

``max_failover_replication_time_lag`` (default ``120.0``)

Replication time lag after which failover_command will be executed and a
failover_has_happened file will be created.

``warning_replication_time_lag`` (default ``30.0``)

Replication time lag at which point to execute
over_warning_limit_command and to create a warning file.

``failover_command`` (default ``""``)

Shell command to execute in case the node has deemed itself in need of promotion

``known_gone_nodes`` (default ``[]``)
``missing_master_from_config_timeout`` (default ``15``)

Lists nodes that are explicitly known to have left the cluster. If the old
primary is removed in a controlled manner it should be added to this list to
ensure there's no extra delay when making promotion decision.
In seconds the amount of time before we do a failover decision if a
previously existing primary has been removed from the config file and
we have gotten a SIGHUP.

``never_promote_these_nodes`` (default ``[]``)

Expand All @@ -308,6 +280,14 @@ you have primary ``p`` which fails and replicas ``a`` and ```b``, even if
``b`` is ahead but is listed in ``never_promote_these_nodes``, ``a`` will be
promoted.

``observers`` (default ``{}``)

This object contains key value pairs like ``{"1.2.3.4":
"http://2.3.4.5:15000"}``. They are used to determine the location of
pglookout observer processes. Observers are processes that don't take any
actions, but simply give a third party viewpoint on the state of the
cluster. Useful especially during net splits.

``over_warning_limit_command`` (default ``null``)

Shell command to be executed once replication lag is warning_replication_time_lag
Expand All @@ -316,10 +296,6 @@ Shell command to be executed once replication lag is warning_replication_time_la

The key of the entry in ``remote_conns`` that matches this node.

``log_level`` (default ``"INFO"``)

Determines log level of pglookout.

``pg_data_directory`` (default ``"/var/lib/pgsql/data"``)

PG data directory that needs to be set when autofollow has been turned on.
Expand All @@ -336,18 +312,35 @@ true. Usually something like "sudo systemctl start postgresql".
Command to stop a PostgreSQL process on a node which has autofollow set to
true. Usually something like "sudo systemctl start postgresql".

``syslog`` (default ``false``)
``poll_observers_on_warning_only`` (default ``False``)

Determines whether syslog logging should be turned on or not.
this allows observers to be polled only when replication lag is over
``warning_replication_time_lag``

``syslog_address`` (default ``"/dev/log"``)
``primary_conninfo_template``

Determines syslog address to use in logging (requires syslog to be
true as well)
Connection string or connection info object template to use when setting a new
primary_conninfo value for recovery.conf after a failover has happened. Any
provided hostname and database name in the template is ignored and they are
replaced with a replication connection to the new primary node.

``syslog_facility`` (default ``"local2"``)
Required when ``autofollow`` is true.

Determines syslog log facility. (requires syslog to be true as well)
``remote_conns`` (default ``{}``)

PG database connection strings that the pglookout process should monitor.
Keys of the object should be names of the remotes and values must be valid
PostgreSQL connection strings or connection info objects.

``replication_catchup_timeout`` (default ``300.0``)

How long should pglookout wait for a node to catch up with the primary
before it decides to promote itself.
Comment on lines +335 to +338
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added missing key: replication_catchup_timeout


``replication_state_check_interval`` (default ``10.0``)

How often should pglookout check the replication state in order to
make decisions on should the node be promoted.

``statsd`` (default: disabled)

Expand All @@ -368,13 +361,25 @@ The ``tags`` setting can be used to enter optional tag values for the metrics.

Metrics sending follows the `Telegraf spec`_.

.. _`Telegraf spec`: https://github.com/influxdata/telegraf/tree/master/plugins/inputs/statsd
``syslog`` (default ``false``)

``cluster_monitor_health_timeout_seconds`` (default: ``2 * replication_state_check_interval``)
Determines whether syslog logging should be turned on or not.

If set, it will increase the statsd counter `cluster_monitor_health_timeout` if the
`cluster_monitor` thread has not successfully completed a check since
`cluster_monitor_health_timeout_seconds`.
``syslog_address`` (default ``"/dev/log"``)

Determines syslog address to use in logging (requires syslog to be
true as well)

``syslog_facility`` (default ``"local2"``)

Determines syslog log facility. (requires syslog to be true as well)

``warning_replication_time_lag`` (default ``30.0``)

Replication time lag at which point to execute
over_warning_limit_command and to create a warning file.

.. _`Telegraf spec`: https://github.com/influxdata/telegraf/tree/master/plugins/inputs/statsd

License
=======
Expand Down
2 changes: 1 addition & 1 deletion debian/rules
Original file line number Diff line number Diff line change
Expand Up @@ -3,4 +3,4 @@
export PYBUILD_NAME=pglookout

%:
dh $@ --with python2 --with systemd --buildsystem=pybuild
dh $@ --with python3 --with systemd --buildsystem=pybuild
Loading