Comments (4)
Hello,
we have tried to test this bug on different servers and unfortunately it also appears in PostgreSQL version 14.
For now it seems to us that it is a combination with the version of the operating system - Specifically on RHEL v7. On RHEL v8, the 'pg_autoctl: node active' process takes about 70M of memory.
Please does anyone have a solution to this?
from pg_auto_failover.
Hello @MiroslavDanek
I believe your bug requires careful investigation, and time. Having access to a test server or a gdb output will definitively help...
from pg_auto_failover.
There is a way to use make valgrind-session
and then do a couple interactive failovers/switchovers and then look at the valgrind reports etc.
from pg_auto_failover.
We didn't observe this leak on Ubuntu 20.04 and Ubuntu 22.04 over the past 3 years with multiple clusters running.
@MiroslavDanek
Have you checked if you maybe have some HardwareCorrupted bytes of memory on your systems? Are there any CE/UE ECC errors logged? I've had some processes experiencing memory leaks in the past due to corruption.
As it seems that only the older systems experience this (RHEL7), this may be plausible that you have some hardware failure in there.
from pg_auto_failover.
Related Issues (20)
- Initialize an already existing primary server
- Deadlocks during pg_auto_failover operations HOT 1
- PostgreSQL 16 support HOT 13
- Error when building image using docs/citus/Dockerfile HOT 1
- ERROR candidate-priority value 10 is not valid. Valid values are integers from 0 to 100 🧐 HOT 1
- Switchover and failover get stuck in the report_lst status in certain configurations HOT 5
- Release 2.1 HOT 5
- Upgrade to 2.1 fails: extension "pgautofailover" has no update path from version "2.0" to version "2.1" HOT 4
- Citus formation upgrade path
- Error when creating Citus worker to a formation HOT 2
- When a secondary node is dropped, the FSM is promoted from secondary to single.
- Configuration parameter in pg_autoctl.cfg for the ability to clear PGDATA before running pg_basebackup HOT 1
- Possible FAILURE STATE in State Machine HOT 1
- How can I configure the maximum number of WAL segments a standby can lag behind the primary in pg_auto_failover? HOT 1
- Hung (unclosed) old connections in idle status on the monitor from datanodes HOT 7
- Question: Running with wal_level = logical?
- Both the data nodes left in read/write mode
- Monitor ERROR: invalid input syntax for type integer: "" HOT 1
- Minimal supported postgresql version
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pg_auto_failover.