-
Notifications
You must be signed in to change notification settings - Fork 10
AutoFailover Testing
This is pretty straightforward, just stop one of the servers (or do something even more aggressive, like unplugging the power cable ¯\(ツ)/¯ ) and then do whatever tests you feel like.
The first test mentioned in the PgPool's Testing section is pretty quick and will show you the resulting cluster organization:
psql -U postgres -h 192.168.1.111 -c "show pool_nodes"
If what you tested was bringing down the main PgPool machine this test is still useful since getting an answer on the virtual IP means the backup server successfully took over.
You can take down all but 2 of the PostgreSQL machines and 1 PgPool machine and the behaviour will remain the same (If you're left with just a PostgreSQL Master the database will be read-only, to prevent changes with no backup)
- Home
- Overview
- Requirements
- Setup
- Summary and Quick Start
- Database (PostgreSQL) 1. PostgreSQL Installation 2. Configuring the Master 3. Configuring the Slaves 4. Testing Replication 5. Manual Failover
- Load Balancing (PgPool II) 1. PgPool II Installation 2. Configuration 3. Managing and Testing
- Automatic Failover 1. Setting it up 2. Testing
- Troubleshooting
- References
