User can pass broken configuration, for example, store factory that throws exception from create() method. I created test to demonstrate the problem. See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094' branch
- causes
-
IGNITE-9347 Attempt to start a dynamic cache with invalid configuration leads to exchange worker death
-
- Resolved
-
-
IGNITE-9407 Node is hang when it was stopping from several client in one time
-
- Open
-
- incorporates
-
IGNITE-10723 Investigate failures related to enabling tests (IGNITE-1094)
-
- Open
-
- is duplicated by
-
IGNITE-7207 Exchange worker dies if index contains non existent field
-
- Resolved
-
-
IGNITE-5063 Dynamic cache start hangs if validation fails
-
- Closed
-
- is related to
-
IGNITE-5026 getOrCreateCaches() hangs if any exception in GridDhtPartitionsExchangeFuture.init()
-
- Resolved
-
-
IGNITE-7207 Exchange worker dies if index contains non existent field
-
- Resolved
-
- relates to
-
IGNITE-9955 Fail of cache creation on cluster activation
-
- Open
-
-
IGNITE-9347 Attempt to start a dynamic cache with invalid configuration leads to exchange worker death
-
- Resolved
-
-
IGNITE-8640 If first createCache fail - Ignite is freezing on next createCache
-
- Resolved
-
- links to