Module org.elasticsearch.server

Package org.elasticsearch.reservedstate.service

Class ReservedStateErrorTask

java.lang.Object

org.elasticsearch.reservedstate.service.ReservedStateErrorTask

All Implemented Interfaces:

ClusterStateTaskListener

public class ReservedStateErrorTask
extends Object
implements ClusterStateTaskListener

Cluster state update task that sets the error state of the reserved cluster state metadata.

This is used when a reserved cluster state update encounters error(s) while processing the ReservedStateChunk.

Constructor Summary

Constructors

Constructor	Description
ReservedStateErrorTask(org.elasticsearch.reservedstate.service.ErrorState errorState, ActionListener<ActionResponse.Empty> listener)

Method Summary

Modifier and Type	Method	Description
void	onFailure(Exception e)	A callback for when task execution fails.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

ReservedStateErrorTask

public ReservedStateErrorTask(org.elasticsearch.reservedstate.service.ErrorState errorState,
 ActionListener<ActionResponse.Empty> listener)

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