Skip to main content

JMX Maintenance Operations (Legacy)

Note

High Availability Clustering is a legacy feature that only works on the Orient database.

All new deployments should use one of our new high availability or resilient deployment options described in Resiliency and High Availability.

DatabaseMaintenanceBean

Java Monitoring and Management Console

This JMX bean provides a set of attributes and operations to allow the user to inspect and manipulate the state of a node in Orient database cluster. The expectation is that these will be used mainly for troubleshooting and recovery operations.

Attributes

DatabaseRole

Note

Only available in HA-C

Note

Applies to all databases on the current node

Java Monitoring and Management Console

Possible Values: MASTER, REPLICA

This attribute represents the role of the node in an Orient cluster. The role of MASTER represents a fully writable node in an Orient cluster which participates in the writeQuorum. The role of REPLICA represents a node in read-only mode which is accepting only idempotent commands, e.g. read and queries.

When setting a node's role to REPLICA an override is added to Orient's configuration so that node will always be a REPLICA, regardless of the cluster's default role. When the node is set back to MASTER that override is removed, so it will defer to the cluster's default role - which is MASTER unless it's been frozen.

References
DatabaseStatus

Note

Only available in HA-C

Note

Applies to all databases on the current node

Java Monitoring and Management Console

Possible Values: ONLINE, OFFLINE, NOT_AVAILABLE

This attribute represents the status of the node in an Orient cluster. The status of ONLINE represents a node in a normal state which is fully participating in the cluster. The status of OFFLINE represents a node that is not currently participating in the cluster. The status of NOT_AVAILABLE represents a node that is not currently available for some reason.

Note

Setting the database status to NOT_AVAILABLE triggers an automatic delta-sync with the rest of the cluster. If this is successful, it will move back to ONLINE.

Operations

checkDatabase
Java Monitoring and Management Console

Possible Database Names: accesslog, component, config, security

Checks database pages for corruption and checks that indices cover all records (i.e. no duplicates).

repairDatabase
Java Monitoring and Management Console

Possible Database Names: accesslog, component, config, security

Attempts to repair any corrupt database pages and rebuilds indices.

reinstallDatabase

Note

Only available in HA-C

Java Monitoring and Management Console

Possible Database Names: accesslog, component, config, security

Attempts to reinstall the full database from the rest of the cluster.

Note

The user can't force a reinstall from a specific node, but typically Orient will choose the node that most recently took a backup or the oldest member (assuming that's not the node requesting the reinstall)