ID | IEP-7 |
Author | Anton Vinogradov |
Sponsor | Anton Vinogradov |
Created | Nov 14, 2017 |
Status | DRAFT |
Internal problems may cause unexpected cluster behaviour.
We should determine behavior in case any internal problems happened.
Internal problems can be split to
1) OOM or any other reason cause node crash
2) Situations required graceful node shutdown with custom notification
- IgniteOutOfMemoryException
- Persistence errors
- ExchangeWorker exits with error
3) Prefomance issues should be covered by metrics
- GC STW duration
- Timed out tasks and jobs
- TX deadlock
- Hanged Tx (waits for some service)
- Java Deadlocks
4) Situations required external monitoring implementation
- GC STW duration exceed maximum possible length (node should be stopped before STW finished)
// Describe project risks, such as API or binary compatibility issues, major protocol changes, etc.
// Links to discussions on the devlist, if applicable.
Deadlock Detection And Cluster Protection.