-
Enhancement
-
Resolution: Done
-
Critical
-
5.0.0.FINAL
-
None
-
None
-
High
This is an umbrella issue for several pieces need to make sure people will be able to perform a rolling upgrade.
After the depending issues are solved we should add specific tests to perform this.
- is blocked by
-
ISPN-2290 MBeans should be registered even if JMX statistics gathering is disabled
- Closed
-
ISPN-1409 Introduce a binary-stream upgrading CacheLoader
- Resolved
-
ISPN-2345 Add the ability to dump the entire key set of a node under a well-known key, via JMX
- Closed
-
ISPN-2346 Create a RollingUpgradeSynchronizer to move data from an old cluster to a new one
- Closed
-
ISPN-2488 Drop-in migrator to dump keys and metadata to a known entry for rolling upgrade
- Closed
-
ISPN-2606 RollingUpgradeSynchronizer should be accessible as an MBean
- Closed
-
ISPN-2621 Introduce a wrapper for entries received via a RemoteCacheStore
- Closed
-
ISPN-1405 Make it possible to disable a CacheStore via JMX
- Closed
-
ISPN-1407 Server-initiated cluster switch
- Closed
-
ISPN-2289 Server endpoints should report number of active connections as a JMX operation
- Closed
- relates to
-
ISPN-2323 RemoteCacheStore should optionally put/get raw values (instead of InternalCacheEntries)
- Closed