Ignite node crash: IndexOutOfBoundsException

[Mahesh Renduchintala]

Hi


We have an IndexOutOfBoundsException and ignite JVM stopped.

Can you please check if it is a known bug?


regards

mahesh
[12:42:43,456][SEVERE][exchange-worker-#63][CacheAffinitySharedManager] Failed to initialize cache. Will try to rollback cache start routine. [cacheName=SQL_PUBLIC_FSDZ]
class org.apache.ignite.IgniteCheckedException: Failed to find value class in the node classpath (use default marshaller to enable binary objects) : SQL_PUBLIC_FSDZ_1cff78c1_3fd3_4955_afe7_70a13c743bbc
	at org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:454)
	at org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:706)
	at org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:866)
	at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1330)
	at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:2165)
	at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:898)
	at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:798)
	at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1231)
	at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:738)
	at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667)
	at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539)
	at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
	at java.lang.Thread.run(Thread.java:745)
[12:42:43,622][SEVERE][exchange-worker-#63][GridDhtPartitionsExchangeFuture] Failed to reinitialize local partitions (rebalancing will be stopped): GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=6347, minorTopVer=2], discoEvt=DiscoveryCustomEvent [customMsg=DynamicCacheChangeBatch [id=6cbe2790c61-0a87ef9b-d326-4a61-944b-33378215c4b1, reqs=[DynamicCacheChangeRequest [cacheName=SQL_PUBLIC_FSDZ, hasCfg=true, nodeId=f48eb58b-381b-429a-9133-b6b4dfa41567, clientStartOnly=false, stop=false, destroy=false, disabledAfterStartfalse]], exchangeActions=ExchangeActions [startCaches=[SQL_PUBLIC_FSDZ], stopCaches=null, startGrps=[SQL_PUBLIC_FSDZ], stopGrps=[], resetParts=null, stateChangeRequest=null], startCaches=false], affTopVer=AffinityTopologyVersion [topVer=6347, minorTopVer=2], super=DiscoveryEvent [evtNode=TcpDiscoveryNode [id=f48eb58b-381b-429a-9133-b6b4dfa41567, addrs=[0:0:0:0:0:0:0:1%lo, 10.244.1.29, 127.0.0.1], sockAddrs=[/0:0:0:0:0:0:0:1%lo:0, /10.244.1.29:0, /127.0.0.1:0], discPort=0, order=5872, intOrder=2946, lastExchangeTime=1563526460403, loc=false, ver=2.7.0#20181130-sha1:256ae401, isClient=true], topVer=6347, nodeId8=43ace095, msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1563540162933]], nodeId=f48eb58b, evt=DISCOVERY_CUSTOM_EVT]
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
	at java.util.ArrayList.rangeCheck(ArrayList.java:653)
	at java.util.ArrayList.get(ArrayList.java:429)
	at org.apache.ignite.internal.processors.cache.CacheGroupContext.singleCacheContext(CacheGroupContext.java:387)
	at org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.(GridDhtLocalPartition.java:200)
	at org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.getOrCreatePartition(GridDhtPartitionTopologyImpl.java:853)
	at org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.initPartitions(GridDhtPartitionTopologyImpl.java:406)
	at org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.beforeExchange(GridDhtPartitionTopologyImpl.java:585)
	at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1470)
	at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:806)
	at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667)
	at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539)
	at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
	at java.lang.Thread.run(Thread.java:745)

Re: IGFS block at startup

[Denis Magda]

Oscar,

IGFS won't longer be supported by the community:
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42405.html

Switch to the solutions of this kind if you're accelerating Hadoop:
https://docs.gridgain.com/docs/bdb-getting-started

-
Denis


On Mon, Jul 8, 2019 at 12:16 AM Oscar Torreno 
wrote:

> Hi,
>
>
>
> I am trying to start a fresh 2 nodes Ignite 2.7.0 cluster (using
> docker-compose) with 2 IGFS configured. When I start both nodes at the same
> time, almost always one of them starts without problems, but the second one
> hangs at line 120 of the IgfsMetaManager class (doing an await on a
> CountDownLatch). Rarely, both nodes progress, so it seems to be a kind of
> race condition/inconsistent state problem because of the simultaneous start.
>
>
>
> Have you experienced such issue before? If yes, is there any workaround to
> overcome it?
>
>
>
> Best regards, thanks in advance.
>
> Oscar
>
>
>
> [image: Logo] 
>
> *Oscar Torreno*
>
> Software Engineer
>
> m: + 34 675 026 952
>
> e: oscar.torr...@shapelets.io
>
> C/ Puerta del Mar 18, 2º. 29005, Málaga,Spain
>
> [image: LinkedIn icon]   [image:
> Twitter icon] 
>
>
>

Re: unsubscribe

[Denis Magda]

Send an email to this alias user-unsubscr...@ignite.apache.org

-
Denis


On Fri, Jul 12, 2019 at 10:22 PM biao gu  wrote:

> unsubscribe
>

Fwd: Sudden node failure on Ignite v2.7.5

[Denis Magda]

I think we'll release the next version in October. GridGain might release
it earlier in its community edition.

-
Denis


-- Forwarded message -
From: ihalilaltun 
Date: Thu, Jul 18, 2019 at 11:39 PM
Subject: Re: Sudden node failure on Ignite v2.7.5
To: 


Hi Ivan

Thanks for the reply. I've checked the jira issue and it says it will be
released in v2.8, when do you think v2.8 will be released?



-
İbrahim Halil Altun
Senior Software Engineer @ Segmentify
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Sudden node failure on Ignite v2.7.5

[Denis Magda]

Majid,

Send an email to this address to unsubscribe. We can't do that for you:
user-unsubscr...@ignite.apache.org

-
Denis


On Mon, Jul 15, 2019 at 1:42 AM Majid Salimi  wrote:

> unsubscribe me, please! I don't want to receive emails.
>
> On Mon, Jul 15, 2019 at 1:06 PM Pavel Vinokurov 
> wrote:
>
>> Hi,
>>
>> It looks like the issue described in
>> https://issues.apache.org/jira/browse/IGNITE-11953
>> There a two options:
>> 1. I believe it will be fixed very soon. Thus you could create a build
>> based on 2.7.5 with cherry-picked fix.
>> 2. You could remove the cachegroup property from the cache configuration.
>> In this case you have to start a new cluster and it requires much more
>> heap memory on the startup since there are about 650 caches.
>>
>> Thanks,
>> Pavel
>>
>> сб, 13 июл. 2019 г. в 18:18, ihalilaltun :
>>
>>> Hi Igniters,
>>>
>>> Recently (11.07.2019), we have upgraded our ignite versin from 2.7.0 to
>>> 2.7.5. Just like after 11 hours one of our nodes killed itself without
>>> any
>>> notification. I am adding the details that I could get from the server
>>> and
>>> the topology we use;
>>>
>>> *Ignite version*: 2.7.5
>>> *Cluster size*: 16
>>> *Client size*: 22
>>> *Cluster OS version*: Centos 7
>>> *Cluster Kernel version*: 4.4.185-1.el7.elrepo.x86_64
>>> *Java version* :
>>> openjdk version "1.8.0_212"
>>> OpenJDK Runtime Environment (build 1.8.0_212-b04)
>>> OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
>>>
>>> By the way this is a production environment and we have been using this
>>> topology for almost 5 months. Our average tps size is ~5000 for the
>>> cluster.
>>> We have 8 to 10 different object that we persist on ignite, some of them
>>> relatively big and some ara just strings.
>>>
>>> ignite.zip
>>> 
>>> gc.current
>>> 
>>> hs_err_pid18537.log
>>> <
>>> http://apache-ignite-users.70518.x6.nabble.com/file/t2515/hs_err_pid18537.log>
>>>
>>>
>>>
>>>
>>>
>>> -
>>> İbrahim Halil Altun
>>> Senior Software Engineer @ Segmentify
>>> --
>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>>
>>
>>
>> --
>>
>> Regards
>>
>> Pavel Vinokurov
>>
>
>
> --
>
>
>
>
> *Regards,Majid Salimi BeniM.Sc. Student of Computer Engineering,Department
> of Computer Science and Engineering & IT*
> *Shiraz University*
> Attachments area
>

Re: Sudden node failure on Ignite v2.7.5

[Павлухин Иван]

Unfortunately I do not know. Currently there is no release activity on 2.8.

пт, 19 июл. 2019 г. в 09:39, ihalilaltun :
>
> Hi Ivan
>
> Thanks for the reply. I've checked the jira issue and it says it will be
> released in v2.8, when do you think v2.8 will be released?
>
>
>
> -
> İbrahim Halil Altun
> Senior Software Engineer @ Segmentify
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/



-- 
Best regards,
Ivan Pavlukhin

Re: Sudden node failure on Ignite v2.7.5

[ihalilaltun]

Hi Ivan

Thanks for the reply. I've checked the jira issue and it says it will be
released in v2.8, when do you think v2.8 will be released?



-
İbrahim Halil Altun
Senior Software Engineer @ Segmentify
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/