Re: Error : Commit produced a runtime exception

2017-10-25 Thread Nikolai Tikhonov
No I have not set any memory configuration > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Error-Commit-produced-a-runtime- > exception-tp15768p15824.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >

Re: Error : Commit produced a runtime exception

2017-09-15 Thread colinc
An update on this - after killing the persistent store and reloading the cache, I am now able to start more than one node as expected. I don't know what caused this problem, but I assume it must be something to do with the state of the store. I have also seen some more clear-cut cases where the

Re: Error : Commit produced a runtime exception

2017-09-14 Thread colinc
My configuration is as follows:

Re: Error : Commit produced a runtime exception

2017-09-14 Thread colinc
I am experiencing the same problem with Ignite 2.1 when I have persistence configured. I can start a single node successfully (I have 1M entries persisted) but a second identical node fails with the error. SEVERE: Failed to reinitialize local partitions (preloading will be stopped):

Re: Error : Commit produced a runtime exception

2017-07-31 Thread iostream
No I have not set any memory configuration -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-Commit-produced-a-runtime-exception-tp15768p15824.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Error : Commit produced a runtime exception

2017-07-31 Thread Nikolai Tikhonov
; cacheConfig.setRebalanceBatchSize(524288); > cacheConfig.setRebalanceThrottle(500); > cacheConfig.setRebalanceTimeout(1); > cacheConfig.setOnheapCacheEnabled(FALSE); > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Error-Commit-produced-a-runtime- >

Re: Error : Commit produced a runtime exception

2017-07-30 Thread iostream
:47500..47509 -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-Commit-produced-a-runtime-exception-tp15768p15801.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Error : Commit produced a runtime exception

2017-07-28 Thread Nikolai Tikhonov
. > 70518.x6.nabble.com/Error-Commit-produced-a-runtime- > exception-tp15768p15780.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >

Re: Error : Commit produced a runtime exception

2017-07-28 Thread iostream
Attaching the complete error log file ignite_error_log.log <http://apache-ignite-users.70518.x6.nabble.com/file/n15780/ignite_error_log.log> -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-Commit-produced-a-runtime-exception-tp15768p15780.html Sen

Re: Error : Commit produced a runtime exception

2017-07-28 Thread iostream
.nabble.com/Error-Commit-produced-a-runtime-exception-tp15768p15771.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Error : Commit produced a runtime exception

2017-07-28 Thread Nikolai Tikhonov
ternal.processors.cache.database. > tree.BPlusTree.invokeDown(BPlusTree.java:1673) > at > org.apache.ignite.internal.processors.cache.database. > tree.BPlusTree.invoke(BPlusTree.java:1585) > at > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$ > Ca

Error : Commit produced a runtime exception

2017-07-28 Thread iostream
) at org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3241) -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-Commit-produced-a-runtime-exception-tp15768.html Sent from the Apache Ignite Users mailing list