This page describes an older version of the product. The latest stable version is 16.4.

Quiesce Mode


This feature adds support for “Quiesce state” (or maintenance mode) for a Processing Unit. If a space is quiesced, it rejects all data-related operations with an exception, allowing the user to perform maintenance operations.

The XAP Polling Container and Notify Container are also aware of the Space’s quiesce state, and handle quiesce state changed events by implementing QuiesceStateChangedListener.

In addition to the XAP event containers mentioned above, a user-defined Bean can also handle quiesce state changed events by implementing QuiesceStateChangedListener.

Quiesce is usually triggered using the ProcessingUnit API, and is propagated to all Space instances and quiesce state changed listeners in the Processing Unit.

See also:

Quiesce mode can be also triggered using a CLI (see Quiesce CLI).

Uses for Quiesce State

There are several scenarios that can benefit from quiesce state. Some of these are described below.

Safe Shutdown

Use Quiesce state to shut down an application that contains a data grid and a mirror in a safe manner. This ensures that all operations completed on the grid are flushed to the mirror before undeploy.

To perform a safe shutdown:

  1. Enter quiesce mode.
  2. Wait for replication between the space and the mirror to complete (by monitoring the redolog).
  3. Undeploy the space and mirror.

Rolling System Upgrade

Use Quiesce mode to perform a rolling system upgrade on a live system (typically a Processing Unit code upgrade) and avoid inconsistencies related to processing of requests during the upgrade process.

To perform a rolling system upgrade with Quiesce mode:

  1. Enter Quiesce mode.
  2. Perform the hot-upgrade pattern:
    2.1. Update the Processing Unit in the GSM.
    2.2. Restart the backup instances.
    2.3. Restart the primary instances.
  3. Exit Quiesce mode and verify that the upgraded system resumes and works as expected,
See also:

Review additional use case examples here.

Space Behavior During Quiesce Mode

The Space behaves as follows when it is in Quiesce mode:

  • Rejects all user data-related new operations by throwing a QuiesceException back to the user (replication of previous ongoing operations continues).
  • Commit and abort are allowed for two-phase commit transactions.
  • Commit and prepare of single-phase transactions are rejected.
  • The Lease manager is paused, except for extend lease operations, in order to prevent losing notify listener templates.


In a secure system, Manage PU privileges are required to quiesce/unquiesce a Processing Unit.


The Quiesce feature can be disabled by setting to true.


The following limitations and open issues apply to Quiesce mode:

  • The Processing Unit should be intact before triggering a quiesce request.
  • Although Quiesce handles the Processing Unit restart, it is not resilient regarding sudden network disconnections (in XAP grid component machines). Therefore, under rare conditions the quiesce request must be repeated manually by the user.
  • Quiesce state changed events are propagated only to the components (beans) that are located within the Processing Unit context file (pu.xml), therefore custom components are not aware of quiesce state changed events (even if the component implements QuiesceStateChangedListener).
  • Replication of the Quiesce state between primary and backup GSM is not yet supported. GSM failover may result in losing the quiesce state of the system. If this happens, you must repeat the quiesce request in order to re-inform the GSM about the current quiesce state.

Processing Unit API

The following ProcessingUnit interface API is used to trigger and manage Quiesce Mode.

// Requests quiesce request from the GSM.
// All space instances and listeners will switch to quiesced mode.
// If the GSM rejects the request an exception with the rejection failure will be thrown.
QuiesceResult quiesce(QuiesceRequest request);
// Requests unquiesce request from the GSM.
// All space instances and listeners will switch to unquiesced mode.
// If the GSM rejects the request an exception with the rejection failure will be thrown.
void unquiesce(QuiesceRequest request);
// Return true if the processing unit reached to desired state as well as all instances in the requested timeout, false otherwise.
boolean waitFor(QuiesceState desiredState, long timeout, TimeUnit timeUnit);
boolean waitFor(QuiesceState desiredState);
// Return the quiesce details of the processing unit
QuiesceDetails getQuiesceDetails();

Quiesce State Changed Listener

A user-defined component (Spring Bean) in a Processing Unit can implement QuiesceStateChangedListener and be aware of quiesce state changed events.

public class CustomComponent implements ... ,QuiesceStateChangedListener {
    public void quiesceStateChanged(QuiesceStateChangedEvent event) {
        if (event.getQuiesceState() == QuiesceState.QUIESCED)
            // stop interacting with the space to prevent getting exceptions
            // resume interacting with the space

Sample Use Cases

Safely Undeploy a Stateful Processing Unit

QuiesceRequest request = new QuiesceRequest("Jacob: performing safe shutdown in 11:33 AM");
QuiesceResult result = pu.quiesce(request);
boolean quiesced = pu.waitFor(QuiesceState.QUIESCED, OPERATION_TIMEOUT, TimeUnit.MINUTES);
if (quiesced) {
    System.out.println("All instances are QUIESCED, shutting down...");
    // wait for redo log to drop to zero
    pu.undeployAndWait(OPERATION_TIMEOUT, TimeUnit.MILLISECONDS)
else {
    System.out.println("All instances were not QUIESCED within the given timeout");
    // Print QuiesceDetails to figure out which instances were not QUIESCED 
    System.out.println("Details: " + pu.getQuiesceDetails());
    // retry or do some logic 

Rolling Upgrade on a Live System

QuiesceRequest request = new QuiesceRequest("Jacob: performing hot deploy in 11:33 AM");
QuiesceResult result = pu.quiesce(request);
// wait for redo log to drop to zero
// upgrade the system, restart backups and then primaries
QuiesceRequest resumeRequest = new QuiesceRequest("Jacob: resumming the system in 12:14 AM");
System.out.println("the system was successfully upgraded");


The following are examples of entering and exiting Quiesce mode using the REST API.


curl -X POST --header 'Content-Type: application/json' --header 'Accept: text/plain' 'http://localhost:8090/v1/deployments/myApp/quiesce'


curl -X POST --header 'Content-Type: application/json' --header 'Accept: text/plain' 'http://localhost:8090/v1/deployments/myApp/unquiesce'