pg auto failover change candidate priority at monitor node fail with error " candidate-priority value xxx is not valid. Valid values are integers from 0 to 100"
search cancel

pg auto failover change candidate priority at monitor node fail with error " candidate-priority value xxx is not valid. Valid values are integers from 0 to 100"

book

Article ID: 406542

calendar_today

Updated On:

Products

VMware Tanzu for Postgres

Issue/Introduction

Some user may receive below error when change data node priority in pg_auto_failover.

pg_autoctl set node candidate-priority --name node_1 100 
candidate-priority value 100 is not valid. Valid values are integers from 0 to 100.

This error only show up when run this command from the monitor node. If run the same command at a data node, there is no error.

Environment

RHEL 9 

Tanzu postgresql 17.5

Cause

There is a reported issue at pg auto failover community. But from the community there is no fix yet. Tanzu R&D team decide to align with the community regarding the fix. Which means Tanzu R&D team will not provide a fix until the community decide to fix this issue. 

https://github.com/hapostgres/pg_auto_failover/issues/1011

 

Resolution

Since there is issue only show up when change node priority from monitor node when using RHEL 9. So the workaround would be :
1. use RHEL 8 or other platform.
2. change node priority from data node directly.