Обсуждение: Db nodes are getting deregistering from consul

Поиск
Список
Период
Сортировка

Db nodes are getting deregistering from consul

От
Rambabu V
Дата:
Hi Team,

Db replication running with patroni and patronictl showing 3 nodes running without any issue. But db notes are getting deregistering from consul within few seconds.

Earlier this was working fine, started facing issue after we have replaced old consul cluster with new consul cluster .

Deregistercriticalserviceafter value is 150s.

Db nodes are getting deregistering from consul

От
"Wetmore, Matthew (CTR)"
Дата:

Are these logical nodes?  If they are not physical nodes, you will have to script something to keep the logical nodes persistent during a restart or failover.

 

From: Rambabu V <ram.wissen@gmail.com>
Sent: Saturday, January 6, 2024 11:29 PM
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: [EXTERNAL] Db nodes are getting deregistering from consul

 

Hi Team,

 

Db replication running with patroni and patronictl showing 3 nodes running without any issue. But db notes are getting deregistering from consul within few seconds.

 

Earlier this was working fine, started facing issue after we have replaced old consul cluster with new consul cluster .

 

Deregistercriticalserviceafter value is 150s.

Re: Db nodes are getting deregistering from consul

От
Rambabu V
Дата:
Thanks Matthew for the quick response. Issue resolved, it's due to port issue.

On Mon, Jan 8, 2024, 22:31 Wetmore, Matthew (CTR) <Matthew.Wetmore@express-scripts.com> wrote:

Are these logical nodes?  If they are not physical nodes, you will have to script something to keep the logical nodes persistent during a restart or failover.

 

From: Rambabu V <ram.wissen@gmail.com>
Sent: Saturday, January 6, 2024 11:29 PM
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: [EXTERNAL] Db nodes are getting deregistering from consul

 

Hi Team,

 

Db replication running with patroni and patronictl showing 3 nodes running without any issue. But db notes are getting deregistering from consul within few seconds.

 

Earlier this was working fine, started facing issue after we have replaced old consul cluster with new consul cluster .

 

Deregistercriticalserviceafter value is 150s.