[ https://issues.apache.org/jira/browse/IGNITE-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-9347: ------------------------------------ Fix Version/s: (was: 2.7) > Attempt to start a dynamic cache with invalid configuration leads to exchange > worker death > ------------------------------------------------------------------------------------------ > > Key: IGNITE-9347 > URL: https://issues.apache.org/jira/browse/IGNITE-9347 > Project: Ignite > Issue Type: Bug > Components: cache > Affects Versions: 2.5, 2.6 > Reporter: Vladimir Ozerov > Priority: Blocker > Fix For: 2.7 > > > Reproducer - {{SqlIllegalSchemaSelfTest}}. Technically, this test pass. But > note the following: > 1) See logs of {{*Dynamic}} tests - instead of normal stop, node gets killed > by failure detector: > {code:java} > [2018-08-22 > 14:20:39,777][ERROR][exchange-worker-#77%query.SqlIllegalSchemaSelfTest%][IgniteTestResources] > Critical system error detected. Will be handled accordingly to configured > handler [hnd=class o.a.i.failure.NoOpFailureHandler, > failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, > err=java.lang.AssertionError: stopping=true, groupName=null, caches=[]]] > java.lang.AssertionError: stopping=true, groupName=null, caches=[] > at > org.apache.ignite.internal.processors.cache.CacheGroupContext.singleCacheContext(CacheGroupContext.java:371){code} > 2) Similar behavior is observed if one tries to start caches with invalid > configuration twice. Pick any {{*Dynamic}} test and just copy/paste > {{GridTestUtils.assertThrows}} logic one after another. Expected - two > expected exceptions, actual - node is killed. > > Possibly duplicate of IGNITE-8640 (need to double-check) -- This message was sent by Atlassian JIRA (v7.6.3#76005)