-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
Documentation (Ref Guide, User Guide, etc.)
-
Medium
There're are two primary reasons why Infinispan servers require predefined caches to be started up on startup, and do not allow invocations to undefined caches:
1. Concurrent cache startups were resulting in NPEs (ISPN-635) - This is already solved since the 4.2.x days.
2. Infinispan has issues dealing with asymmetric clusters (ISPN-658).
Once these two issues have been resolved, revisit the limitation.
- blocks
-
ISPN-3533 Design HotRod protocol version 2.0
- Closed
- is blocked by
-
ISPN-635 NPE on acquire lock LockManagerImpl.lockAndRecord
- Closed
-
ISPN-658 Asymmetric clusters should be supported
- Closed
- is duplicated by
-
ISPN-753 Verify the need for predefinition of Hot Rod and REST caches
- Closed
- is related to
-
ISPN-425 Stale data read when L1 invalidation happens while UnionConsistentHash is in use
- Closed
- relates to
-
ISPN-4212 Unable to get entries from newly started non-defined caches
- Closed
-
ISPN-4296 Restore predefined cache limitation for Hot Rod servers
- Closed