Exception when starting second node

classic Classic list List threaded Threaded
3 messages Options
Andrew An Andrew An
Reply | Threaded
Open this post in threaded view
|

Exception when starting second node

Hi,

We are testing with Ignite v1.6.

It was OK with Ignite v1.5 but after upgrade to v1.6, we encountered an Exception like below.

The exception occurs only at starting second node.

We are executing 1 client and 1 server node on 1 JVM(2 ignite nodes on 1 JVM).

The client goes first then if the client receives a message, the client starts server.

The firstly executed JVM is OK, but if we starts another client and server, it makes an exception.

I attached full log and ignite configurations.

I have no idea why it is happening.

Needs your help.

 

[15:47:27,227][INFO ][sys-#19%null%][GridDhtPartitionDemander] <ignite-sys-cache> Starting rebalancing [cache=ignite-sys-cache, mode=SYNC, fromNode=23ed0e1d-a75d-4fa8-9e38-04b919d1deda, partitionsCount=100, topology=AffinityTopologyVersion [topVer=29, minorTopVer=0], updateSeq=1]

[15:47:27,252][ERROR][marshaller-cache-#69%null%][GridCacheIoManager] Failed processing message [senderId=23ed0e1d-a75d-4fa8-9e38-04b919d1deda, msg=GridDhtPartitionSupplyMessageV2 [updateSeq=1, topVer=AffinityTopologyVersion [topVer=29, minorTopVer=0], missed=null, msgSize=0, size=20, parts=[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 17, 16, 19, 18], super=GridCacheMessage [msgId=123, depInfo=null, err=null, skipPrepare=false, cacheId=1325947219, cacheId=1325947219]]]

java.nio.channels.OverlappingFileLockException

           at sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:255)

           at sun.nio.ch.SharedFileLockTable.add(FileLockTable.java:152)

           at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:1042)

           at org.apache.ignite.internal.MarshallerContextImpl$ContinuousQueryListener.onUpdated(MarshallerContextImpl.java:236)

           at org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:769)

           at org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$700(CacheContinuousQueryHandler.java:91)

           at org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:412)

           at org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:343)

           at org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:250)

           at org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3332)

           at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.preloadEntry(GridDhtPartitionDemander.java:684)

           at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:574)

           at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:389)

           at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:374)

           at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:364)

           at org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:622)

           at org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:320)

           at org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$300(GridCacheIoManager.java:81)

           at org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1125)

           at org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)

           at org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:105)

           at org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2456)

           at org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1179)

           at org.apache.ignite.internal.managers.communication.GridIoManager.access$1900(GridIoManager.java:105)

           at org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:1148)

           at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

           at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

           at java.lang.Thread.run(Thread.java:745)

[15:47:27,257][INFO ][marshaller-cache-#69%null%][GridDhtPartitionDemander] <ignite-sys-cache> Completed (final) rebalancing [cache=ignite-sys-cache, fromNode=23ed0e1d-a75d-4fa8-9e38-04b919d1deda, topology=AffinityTopologyVersion [topVer=29, minorTopVer=0], time=30 ms]

[15:47:36,199][INFO ][ignite-update-notifier-timer][GridUpdateNotifier] Your version is up to date.

 

Sincerely,

Andrew


ignite-node-client.xml (7K) Download Attachment
ignite-node-server.xml (7K) Download Attachment
log.txt (30K) Download Attachment
vkulichenko vkulichenko
Reply | Threaded
Open this post in threaded view
|

Re: Exception when starting second node

This is possible under some circumstances, see this ticket (should be fixed soon): https://issues.apache.org/jira/browse/IGNITE-3197

This exception should be harmless, only flooding the logs. Is this the case for you?

-Val
Andrew Andrew
Reply | Threaded
Open this post in threaded view
|

Re: Exception when starting second node

Thanks for reply.
And Yes, the system runs well, though it occurs.
I hope the next version would be released soon.

Sincerely,
Andrew