title: How to fix apache ignite error "ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]"?
body: <p>I'm setting up a in-memory cache store using apache ignite in my web application. Where I am starting the ignite node and storing some data in ignite cache store at the start of my application server. while doing so I m able to start ignite node but my app server got stuck in starting mode at the below line of code.</p>
  
  <p><code>igniteCache.getCache("some_string");</code></p>
  
  <ol>
  <li>Tried to increase failure timeout.</li>
  <li><p>Tried again after increase the memory.</p>
  
  <pre><code>IgniteConfiguration igniteConfig = new IgniteConfiguration();
      igniteConfig.setSystemWorkerBlockedTimeout(60 * 60 * 1000);
              StopNodeFailureHandler handler = new org.apache.ignite.failure.StopNodeFailureHandler();
              handler.setIgnoredFailureTypes(new HashSet());
              igniteConfig.setFailureHandler(handler);
              //implementing multiple cache stores
              List&lt;CacheConfiguration&gt; list = new ArrayList&lt;CacheConfiguration&gt;();
  CacheConfiguration&lt;String, Object&gt; cacheConfig0 = new CacheConfiguration&lt;String, Object&gt;(name);
  cacheConfig.setCacheMode(CacheMode.PARTITIONED);
  list.add(cacheConfig0);
  
  CacheConfiguration&lt;String, Object&gt; cacheConfig1 = new CacheConfiguration&lt;String, Object&gt;(name);
  cacheConfig.setCacheMode(CacheMode.PARTITIONED);
  list.add(cacheConfig1);
  //here starting the ignite node
  ignite = Ignition.start(igniteConfig);
  caches = ignite.getOrCreateCaches(list);
  </code></pre></li>
  </ol>
  
  <p>below are the exception i m getting while starting the server</p>
  
  <pre><code>*[15:08:12] Topology snapshot [ver=1, locNode=51a25b22, servers=1, clients=0, state=ACTIVE, CPUs=4, offheap=3.0GB, heap=2.5GB]
  &lt;Jul 27, 2019 3:08:35,634 PM IST&gt; &lt;Error&gt; &lt;org.apache.ignite.internal.util.typedef.G&gt; &lt;BEA-000000&gt; &lt;Blocked system-critical thread has been detected. This can lead to cluster-wide undefined behaviour [threadName=grid-timeout-worker, blockedFor=13s]&gt; 
  &lt;Jul 27, 2019 3:08:36,625 PM IST&gt; &lt;Warning&gt; &lt;org.apache.ignite.internal.util.typedef.G&gt; &lt;BEA-000000&gt; &lt;Thread [name="grid-timeout-worker-#23", id=219, state=RUNNABLE, blockCnt=1, waitCnt=43]
  &gt; 
  &lt;Jul 27, 2019 3:08:49,975 PM IST&gt; &lt;Error&gt; &lt;&gt; &lt;BEA-000000&gt; &lt;Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, super=AbstractFailureHandler [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker [name=grid-timeout-worker, igniteInstanceName=null, finished=false, heartbeatTs=1564220302360]]]
  class org.apache.ignite.IgniteException: GridWorker [name=grid-timeout-worker, igniteInstanceName=null, finished=false, heartbeatTs=1564220302360]
      at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1831)
      at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1826)
      at org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
      at org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297)
      at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.lambda$new$0(ServerImpl.java:2663)*
  </code></pre>