queueflush
Use the queueflush
program to gracefully shut down all Bravura Security Fabric services, with the exception of Database Service (iddb
) and Logging Service (idmlogsvc
), on every replication node (or a set list of servers). The command initiates the DB_COMMIT_SUSPEND state; in which database commits are suspended. This is followed by a flushing of all data in replication queues. The program will display the progress of the flushing process.
The standard way to reverse the DB_COMMIT_SUSPEND state is stop the Database Service on all nodes after queueflush has done its work. If this is not done, you will encounter problems when starting the other services while still in DB_COMMIT_SUSPEND state.
Usage
queueflush.exe [ -cancel | -list | -servers --servers <serverlist> ]
Argument | Description |
---|---|
-cancel | Cancel a flush and lift DB_COMMIT_SUSPEND. See notes below. |
-list | List servers in a replication environment. |
-servers, --servers <serverlist> | List of servers to flush queues on. If this argument is not specified, queues from all servers will be flushed. WarningThis option is not recommended, as servers that are in a flush state may still be receiving data from other servers that are not in a flush state. Use at your own risk. |
Examples
To flush queues from all replication nodes:
queueflush.exe
This command shuts down the services (except the Database Service and Logging Service) and initiates the DB_COMMIT_SUSPEND state. No arguments are needed.
To cancel an in-progress queueflush initiated flush and DB_COMMIT_SUSPEND state:
queueflush.exe -cancel
To list all servers in a replication environment:
queueflush.exe -list
Notes on -cancel argument
The queueflush.exe -cancel
command can be used to cancel the process initiated by queueflush
; for example, if there is much more data in the replication queues than expected and the queues will not be flushed in reasonable time for a change window, and there is a need to abort.
For queueflush.exe -cancel
to work, the Database Service and Logging Service should be running. If the Database Service is not running, it will not work.
When queueflush.exe -cancel
is executed (from a single node) it lifts the DB_COMMIT_SUSPEND state and gracefully starts all the Bravura Security Fabric services on all replicated nodes in the instance.