Open topic with navigation
This is a NuoDB Manager command. See NuoDB Manager.
Instructs all transaction engines in the domain to hang up any sockets that are open with the transaction engine connected to the specified database on the specified host. NuoDB terminates the transaction engine that is connected to the specified database on the specifed host and removes that process from the durable domain configuration.
The broker on the host on which the evicted process was running continues to be a peer in the domain. If enforcement is enabled and the termination of the evicted process causes the database's template requirements to be unmet, then the enforcer starts a new process to replace the evicted process. If you do not want the terminated process to be replaced then you can stop the database or disable enforcement before issuing the
remove host command. See Disable Enforcer.
remove host address
The address of the host for which to hang up sockets.
The name of the database whose connections should be closed.
Database: mydb1, template [Minimally Redundant] MET, processes [2 TE, 2 SM], ACTIVE [TE] nuodb1/172.17.0.1:48006 (DEFAULT_REGION) [ pid = 165 ] [ nodeId = 4 ] RUNNING [SM] nuodb2/172.17.0.2:48010 (DEFAULT_REGION) [ pid = 413 ] [ nodeId = 1 ] RUNNING [TE] nuodb2/172.17.0.2:48011 (DEFAULT_REGION) [ pid = 429 ] [ nodeId = 2 ] RUNNING [SM] nuodb3/172.17.0.3:48013 (DEFAULT_REGION) [ pid = 276 ] [ nodeId = 3 ] RUNNING nuodb [domain] >
remove host address 172.17.0.1 database mydb1Evicted nodes: [TE] nuodb1/172.17.0.1:48006 (DEFAULT_REGION) [ pid = 165 ] [ nodeId = 4 ] RUNNING
remove host command can be executed with
--command as follows:
password\ --command "remove host address 172.17.0.1 database mydb1"