ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@gridgain.com>
Subject Re: Exception on Ignite cluster shutdown
Date Sun, 21 Feb 2016 19:44:40 GMT
Hi Steve,

In general this is exception is harmless and it won't affect consistency of
caches or stability of the cluster.

However it's interesting why it happens. Do you process SIGTERM using a
shutdown hook in your? Do you call Ignite.stop() for every node or how do
you stop Ignite cluster?

Regards,
Denis


On Sun, Feb 21, 2016 at 9:30 PM, Steve S. <sscheck@silverspringnet.com>
wrote:

>
> I observe this exception when my application hosting an Ignite cluster is
> shutdown (normal JVM termination, via SIGTERM):
>
> 2016-02-20T21:55:49.266+0000 [Thread-5] ERROR IgniteKernal%SOMOS_EN_FUEGO
> []
> - Failed to pre-stop processor: GridProcessorAdapter []
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to execute dynamic cache change request, node is stopping.
>         at
>
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1618)
> ~[ignite-core-1.5.6.jar!/:1.5.6]
>         at
>
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1876)
> ~[ignite-core-1.5.6.jar!/:1.5.6]
>         at
>
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.close(IgniteCacheProxy.java:1663)
> ~[ignite-core-1.5.6.jar!/:1.5.6]
>         at app.AppService.cancel(AppService.java:100) ~[classes!/:na]
>         at
>
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStop(GridServiceProcessor.java:222)
> ~[ignite-core-1.5.6.jar!/:1.5.6]
>         at
> org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1811)
> [ignite-core-1.5.6.jar!/:1.5.6]
>         at
> org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1757)
> [ignite-core-1.5.6.jar!/:1.5.6]
>         at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2207)
> [ignite-core-1.5.6.jar!/:1.5.6]
>         at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2170)
> [ignite-core-1.5.6.jar!/:1.5.6]
>         at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1731)
> [ignite-core-1.5.6.jar!/:1.5.6]
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to execute
> dynamic cache change request, node is stopping.
>         at
>
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.initiateCacheChanges(GridCacheProcessor.java:2382)
> ~[ignite-core-1.5.6.jar!/:1.5.6]
>         at
>
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicCloseCache(GridCacheProcessor.java:2287)
> ~[ignite-core-1.5.6.jar!/:1.5.6]
>         at
>
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.close(IgniteCacheProxy.java:1653)
> ~[ignite-core-1.5.6.jar!/:1.5.6]
>         ... 7 common frames omitted
>
> What does this mean? Is it something to be concerned with?
>
> Thanks.
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Exception-on-Ignite-cluster-shutdown-tp3129.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Mime
View raw message