Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-9347

Attempt to start a dynamic cache with invalid configuration leads to exchange worker death

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.5, 2.6
    • Fix Version/s: 2.8
    • Component/s: cache
    • Labels:
      None

      Description

      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:

      [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)

      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)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                garus.d.g Denis Garus
                Reporter:
                vozerov Vladimir Ozerov
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: