#[non_exhaustive]
pub enum TestFailoverErrorKind {
ApiCallRateForCustomerExceededFault(ApiCallRateForCustomerExceededFault),
InvalidCacheClusterStateFault(InvalidCacheClusterStateFault),
InvalidKmsKeyFault(InvalidKmsKeyFault),
InvalidParameterCombinationException(InvalidParameterCombinationException),
InvalidParameterValueException(InvalidParameterValueException),
InvalidReplicationGroupStateFault(InvalidReplicationGroupStateFault),
NodeGroupNotFoundFault(NodeGroupNotFoundFault),
ReplicationGroupNotFoundFault(ReplicationGroupNotFoundFault),
TestFailoverNotAvailableFault(TestFailoverNotAvailableFault),
Unhandled(Unhandled),
}Expand description
Types of errors that can occur for the TestFailover operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
ApiCallRateForCustomerExceededFault(ApiCallRateForCustomerExceededFault)
The customer has exceeded the allowed rate of API calls.
InvalidCacheClusterStateFault(InvalidCacheClusterStateFault)
The requested cluster is not in the available state.
InvalidKmsKeyFault(InvalidKmsKeyFault)
The KMS key supplied is not valid.
InvalidParameterCombinationException(InvalidParameterCombinationException)
Two or more incompatible parameters were specified.
InvalidParameterValueException(InvalidParameterValueException)
The value for a parameter is invalid.
InvalidReplicationGroupStateFault(InvalidReplicationGroupStateFault)
The requested replication group is not in the available state.
NodeGroupNotFoundFault(NodeGroupNotFoundFault)
The node group specified by the NodeGroupId parameter could not be found. Please verify that the node group exists and that you spelled the NodeGroupId value correctly.
ReplicationGroupNotFoundFault(ReplicationGroupNotFoundFault)
The specified replication group does not exist.
TestFailoverNotAvailableFault(TestFailoverNotAvailableFault)
The TestFailover action is not available.
Unhandled(Unhandled)
An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).
When logging an error from the SDK, it is recommended that you either wrap the error in
DisplayErrorContext, use another
error reporter library that visits the error’s cause/source chain, or call
Error::source for more details about the underlying cause.