Module org.elasticsearch.server
Package org.elasticsearch.action.admin.indices.delete

Class DeleteIndexClusterStateUpdateRequest

java.lang.Object
org.elasticsearch.cluster.ack.ClusterStateUpdateRequest<T>
org.elasticsearch.cluster.ack.IndicesClusterStateUpdateRequest<DeleteIndexClusterStateUpdateRequest>
org.elasticsearch.action.admin.indices.delete.DeleteIndexClusterStateUpdateRequest
All Implemented Interfaces:
AckedRequest, ClusterStateAckListener, ClusterStateTaskListener
public class DeleteIndexClusterStateUpdateRequest extends IndicesClusterStateUpdateRequest<DeleteIndexClusterStateUpdateRequest> implements ClusterStateAckListener, ClusterStateTaskListener
Cluster state update request that allows to close one or more indices

  • Constructor Details

  • Method Details

    • onFailure

      public void onFailure(Exception e)
      Description copied from interface: ClusterStateTaskListener
      A callback for when task execution fails. May receive a NotMasterException if this node stopped being the master before this task was executed or a ProcessClusterEventTimeoutException if the task timed out before it was executed. If the task fails during execution then this method receives the corresponding exception. If the task executes successfully but the resulting cluster state publication fails then this method receives a FailedToCommitClusterStateException. If publication fails then a new master is elected and the update might or might not take effect, depending on whether or not the newly-elected master accepted the published state that failed to be committed.

      Use MasterService.isPublishFailureException(java.lang.Exception) to detect the "expected" master failure cases if needed.

      Implementations of this callback must not throw exceptions: an exception thrown here is logged by the master service at ERROR level and otherwise ignored, except in tests where it raises an AssertionError. If log-and-ignore is the right behaviour then implementations must do so themselves, typically using a more specific logger and at a less dramatic log level.

      Specified by:
      onFailure in interface ClusterStateTaskListener

    • mustAck

      public boolean mustAck(DiscoveryNode discoveryNode)
      Description copied from interface: ClusterStateAckListener
      Called to determine which nodes the acknowledgement is expected from. As this method will be called multiple times to determine the set of acking nodes, it is crucial for it to return consistent results: Given the same listener instance and the same node parameter, the method implementation should return the same result.
      Specified by:
      mustAck in interface ClusterStateAckListener
      Parameters:
      discoveryNode - a node
      Returns:
      true if the node is expected to send ack back, false otherwise

    • onAllNodesAcked

      public void onAllNodesAcked()
      Description copied from interface: ClusterStateAckListener
      Called once all the nodes have acknowledged the cluster state update request. Must be very lightweight execution, since it gets executed on the cluster service thread.
      Specified by:
      onAllNodesAcked in interface ClusterStateAckListener

    • onAckFailure

      public void onAckFailure(Exception e)
      Description copied from interface: ClusterStateAckListener
      Called after all the nodes have acknowledged the cluster state update request but at least one of them failed. Must be very lightweight execution, since it gets executed on the cluster service thread.
      Specified by:
      onAckFailure in interface ClusterStateAckListener
      Parameters:
      e - optional error that might have been thrown

    • onAckTimeout

      public void onAckTimeout()
      Description copied from interface: ClusterStateAckListener
      Called once the acknowledgement timeout defined by AckedClusterStateUpdateTask.ackTimeout() has expired
      Specified by:
      onAckTimeout in interface ClusterStateAckListener