[pgpool-general: 9028] force a pgpool re-scan?

[Sbob]

All;


we are setting up pgpool instances for a primary site and for a DR site. 
To start with the DR site pgpool instance will have no writable nodes 
but onle a set of hot standby's

if we failover to the DR site then we will promote one of the postgres 
nodes in DR but we will not have an actual db failure so the DR pgpool 
instance will not execute it's failover script.


Is there a method to force pgpool to re-scan the db nodes and identify 
the writable node?


Thanks in advance