case classNoLongerLeaderException(nodeId: Int, msgId: Long) extends RuntimeException with PaxosMessage with Product with Serializable
Response to a client when the nodes has lost its leadership whilst servicing a request during a fail-over due to
either a network partition or a long stall. The outcome of the client operation indicated by msgId is unknown as the
operation may or may not be committed by the new leader. The application will have to query data to learn whether the
operation did actually work. Note that semantically this is no different from sending a tcp request to an open socket
and not getting back a response; its not known whether the request was processed as there has been neither positive
nor negative acknowledgement. Since we don't know if it is safe to retry the operation nor how to query to check it
the host application will have to decided what to do next. Note that this may be thrown for read only work if the
application used strong or single reads as those avoid returning stale data which may occur doing a leader failover.
nodeId
The node replying that it is has lost the leader.
msgId
The client message which the node is responding to.
Linear Supertypes
Serializable, Product, Equals, PaxosMessage, RuntimeException, Exception, Throwable, Serializable, AnyRef, Any
Response to a client when the nodes has lost its leadership whilst servicing a request during a fail-over due to either a network partition or a long stall. The outcome of the client operation indicated by msgId is unknown as the operation may or may not be committed by the new leader. The application will have to query data to learn whether the operation did actually work. Note that semantically this is no different from sending a tcp request to an open socket and not getting back a response; its not known whether the request was processed as there has been neither positive nor negative acknowledgement. Since we don't know if it is safe to retry the operation nor how to query to check it the host application will have to decided what to do next. Note that this may be thrown for read only work if the application used strong or single reads as those avoid returning stale data which may occur doing a leader failover.
The node replying that it is has lost the leader.
The client message which the node is responding to.