https://pgpool.net/mediawiki/index.php?action=history&feed=atom&title=pgpool-II-3.5-watchdog-testpgpool-II-3.5-watchdog-test - Revision history2026-05-05T08:12:09ZRevision history for this page on the wikiMediaWiki 1.43.3https://pgpool.net/mediawiki/index.php?title=pgpool-II-3.5-watchdog-test&diff=1075&oldid=prevIshii: Blanked the page2015-10-29T07:54:24Z<p>Blanked the page</p>
<a href="https://pgpool.net/mediawiki/index.php?title=pgpool-II-3.5-watchdog-test&diff=1075&oldid=1072">Show changes</a>Ishiihttps://pgpool.net/mediawiki/index.php?title=pgpool-II-3.5-watchdog-test&diff=1072&oldid=prevIshii: Created page with "{| |Test Num |Category |Test Description |Expected Output |How to test |Assigned-to |---- | | | | | | |---- |1 |Installation |Make sure that the new watchdog is installed and con..."2015-10-29T07:50:37Z<p>Created page with "{| |Test Num |Category |Test Description |Expected Output |How to test |Assigned-to |---- | | | | | | |---- |1 |Installation |Make sure that the new watchdog is installed and con..."</p>
<p><b>New page</b></p><div>{|<br />
|Test Num<br />
|Category<br />
|Test Description<br />
|Expected Output<br />
|How to test<br />
|Assigned-to<br />
|----<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|1<br />
|Installation<br />
|Make sure that the new watchdog is installed and configured successfully <br />
|<br />
|<br />
|<br />
|----<br />
|2<br />
|Upgrade<br />
|Make sure that pgpool II with new watchdog can be installed on a system running pgpool II with the old watchdog<br />
|<br />
|<br />
|<br />
|----<br />
|3<br />
|Configuration<br />
|Make sure that pgpool II can be configured successfully with one primary and one stand-by configuration<br />
|<br />
|<br />
|<br />
|----<br />
|4<br />
|Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a sample query <br />
|Configruation<br />
|<br />
|<br />
|----<br />
|4.1<br />
|Functional testing<br />
|Shutdown Host-1's pgpool instanse and execute query again<br />
|Host-2 should take and respond to query<br />
|<br />
|<br />
|----<br />
|4.2<br />
|Functional testing<br />
|Shutdown Host-2's pgpool instanse and execute query again<br />
|Host-3 should take and respond to query<br />
|<br />
|<br />
|----<br />
|4.3<br />
|Functional testing<br />
|Start Host-1's pgpool instanse and execute query again<br />
|Need to see which host will respond to query<br />
|<br />
|<br />
|----<br />
|5<br />
|Failover scenarions / Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a sample query <br />
|Configruation<br />
|<br />
|<br />
|----<br />
|5.1<br />
|Failover scenarios<br />
|Un-Plug Host-1's network cable and execute query again<br />
|Host-2 should take and respond to query<br />
|<br />
|<br />
|----<br />
|5.2<br />
|Failover scenarios<br />
|Un-Plug Host-2's network cable and execute query again<br />
|Host-3 should take and respond to query<br />
|<br />
|<br />
|----<br />
|5.3<br />
|Failover scenarios<br />
|Plug Host-1's network cable execute query again<br />
|Need to see which host will respond to query<br />
|<br />
|<br />
|----<br />
|6<br />
|Functional testing / Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a long query <br />
|<br />
|<br />
|<br />
|----<br />
|6.1<br />
|Functional testing<br />
|Shutdown / Power Off Host-1's instanse and execute query again<br />
|Host-2 should take over and start responding, need to see the already running query response. <br />
|<br />
|<br />
|----<br />
|6.2<br />
|Functional testing<br />
|Shutdown / Power Off Host-2's instanse and execute query again<br />
|Host-3 should take over and start responding, need to see the already running query response. <br />
|<br />
|<br />
|----<br />
|6.3<br />
|Functional testing<br />
|Start Host-1's pgpool instanse and execute query again<br />
|Need to see which host will respond to query<br />
|<br />
|<br />
|----<br />
|7.1<br />
|Cheking other functionality of watchdog <br />
|Changing active/standby state in case of certain faults detected<br />
|<br />
|<br />
|<br />
|----<br />
|7.2<br />
|Cheking other functionality of watchdog <br />
|Automatic virtual IP address assigning synchronous to server switching<br />
|<br />
|<br />
|<br />
|----<br />
|7.3<br />
|Cheking other functionality of watchdog <br />
|Automatic registration of a server as standby in recovery<br />
|<br />
|<br />
|<br />
|----<br />
|8<br />
|Isolated master scenario / Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a query<br />
|<br />
|<br />
|<br />
|----<br />
|8.1<br />
|Isolated master scenario<br />
|Break the connectivity between pgpool watchdog primary and stand node by bringing down connectivity on the stand-by.<br />
|Split brain testing ensures that their is only one master at a time that the clients can connect to. The stand-by should be promoted as the primary and the clients shouldn't be able to connect to the old master.<br />
|<br />
|<br />
|----<br />
|9<br />
|Networking Isolation scenarion<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|9.1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|10<br />
|Database Failure<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|10.1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|10.2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|11<br />
|Watchdog agent failure<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|11.1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|11.2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|}</div>Ishii