-
Enhancement
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
There are 2 mechanisms which seems to do the same but are totally different:
- Kubernetes Rolling Update - replaces Pods in controllable fashon
- Infinispan Rolling Updgrate - a procedure for upgrading Infinispan or changing the configuration
Kubernetes Rolling Updates can be used very easily for changing the configuration however if changes are not runtime-compatible, one might loss data. Potential way to avoid this is to use a Cache Store. All other changes must be propagated using Infinispan Rolling Upgrade procedure.
- is blocked by
-
ISPN-7487 Fix NPE in ClusterCacheStatus.java:147
- Closed
-
ISPN-7488 Node tries to register component after stopping
- Closed
-
ISPN-7491 When a node leaves the cluster it emits unsolicited state
- Closed
-
ISPN-7489 org.jgroups.protocols.TCP emits errors when node leaves the cluster
- Closed
-
ISPN-6883 Remote Cache Store does does't work properly in compatibility mode
- Closed
-
ISPN-6884 NullPointerException when performing Rolling Upgrade Procedure using Kubernetes
- Closed
-
ISPN-7493 Cannot remove cache configuration while performing Rolling Update
- Closed
-
ISPN-7490 "cancelled task by interrupting thread Thread" is emitted without any reason
- Closed
- relates to
-
ISPN-7537 Test Rolling Updates with persistent cache store and node failures
- Closed
- links to