|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
See:
Description
| Interface Summary | |
|---|---|
| FailureDetector | The FailureDetector API is used to determine a cluster's node availability. |
| FailureDetectorListener | FailureDetectorListener is a simple means by which interested parties can listen for changes to the availability of nodes. |
| StoreVerifier | A StoreVerifier is used to test a Store given a Node. |
| Class Summary | |
|---|---|
| AbstractFailureDetector | AbstractFailureDetector serves as a building block for FailureDetector implementations. |
| AsyncRecoveryFailureDetector | AsyncRecoveryFailureDetector detects failures and then attempts to contact the failing node's Store to determine availability. |
| BannagePeriodFailureDetector | Deprecated. |
| BasicStoreVerifier<K,V,T> | BasicStoreVerifier is used to test Node->Store mappings when the mappings are already present at the time of FailureDetector implementation creation. |
| ClientStoreVerifier | ClientStoreVerifier is used to test stores in a client environment. |
| FailureDetectorConfig | FailureDetectorConfig simply holds all the data that was available to it upon construction. |
| FailureDetectorUtils | FailureDetectorUtils serves as a factory for creating a FailureDetector implementation. |
| NoopFailureDetector | NoopFailureDetector is used for testing classes which don't actually need a working FailureDetector ;) |
| ServerStoreVerifier | ServerStoreVerifier is used to verify store connectivity for a server environment. |
| ThresholdFailureDetector | ThresholdFailureDetector builds upon the AsyncRecoveryFailureDetector and provides a more lenient for marking nodes as unavailable. |
Classes associated with client side failure detectors.
We currently support two types of failure detectors - BannagePeriodFailureDetector and ThresholdFailureDetector
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||