Re: Query does not include objects added into Cache from within a transaction

2016-09-16 Thread vkulichenko
Andrey, This was just a wrong link. Nikolay already provided the correct one above: https://issues.apache.org/jira/browse/IGNITE-3478 -Val -- View this message in context:

Re: One failing node stalling the whole cluster

2016-09-16 Thread yfernando
Unfortunately iam unable to send the full logs files but they contain the following exceptions [14 Sep 2016 11:14:30.290 EDT] [pub-#16%DataGridServer-Development%] ERROR 11223 (OrderHolderSaveRunnable.java:273) exception ocurred while generating Trade Order for Order: OrderKey [traderId=5 207,

Re: One failing node stalling the whole cluster

2016-09-16 Thread DLopez
FWIW, in our case, the GC was not the problem with Ignite. The heap issue was already diagnosed, well known and unrelated. The problem was that the slow down in one node was causing all the other nodes in the grid to basically lock when reading from the cache, without suffering any GC issue. A

Re: One failing node stalling the whole cluster

2016-09-16 Thread Anmol Rattan
That would be topic for discussion on how off heap actually work. My understanding is to start with object creation will happen on heap (YG) and then moved to Old or Off heap. If allocation of object creation (I believe after that only you will associating them in a map (key.value cache), is

Re: One failing node stalling the whole cluster

2016-09-16 Thread Denis Magda
It’s a topology change that impacts transactions rollback, not vice verse. I would wait while more experienced Apache committers who maintain caching components will chime in. They should be able to get to the bottom. In the meanwhile please attach the logs from all the nodes (servers and

Re: One failing node stalling the whole cluster

2016-09-16 Thread Denis Magda
Vladimir Ozerov as far as I recall you have faced with the issue when a slow client affected performance of the whole cluster recently. Please chime in this discussion confirming that the symptoms are the same. Most likely you already created a JIRA ticket for this issue. > Also it's not clear

Re: One failing node stalling the whole cluster

2016-09-16 Thread Denis Magda
Is the node that expected a long GC pause and failed eventually is a client node? This is important to know. From thread dumps I see that some of the nodes unable to rollback transactions "pub-#1%DataGridServer-Development%" Id=35 in WAITING on

Re: AtomicSequence not working when shutting down one server node from a cluster

2016-09-16 Thread Denis Magda
Even simpler and more correct is to increase a number of backups for AtomicConfiguration that is used for your sequence. This can be done by setting AtomicConfiguration.setBackups to value higher than 0. This will make your partitioned AtomicSequence fault tolerant unless all primaries and

Error building Ignite against Spark 2.0.0

2016-09-16 Thread phadnis
Hello, I am trying to build Ignite with Spark 2.0.0. as follows: mvn clean package -Dspark.version=2.0.0 -DskipTests And it fails with following error: [INFO] [INFO] Building ignite-spark 1.8.0-SNAPSHOT [INFO]

Re: One failing node stalling the whole cluster

2016-09-16 Thread yfernando
Thanks for your reply Anmol. Do you know if there is a bug logged against this which we can track? Also it's not clear why the nodes would require to GC because all the caches are held off-heap and we have a 10G heap running G1GC. -- View this message in context:

Re: One failing node stalling the whole cluster

2016-09-16 Thread Anmol Rattan
That is known error at least in 1.6. I am not sure a fix for this is even in 1.7. For gc pause, if there are actually any, worth considering jvm tuning and seeing allocation and promotion rate. In our case, we had to increase younger gen to have 8GB space to deal with. However, slow client

Re: Data Streamer error

2016-09-16 Thread matt
I've been at this for a while but having no luck. Some of this might be the way that we have dependencies setup or something else in our app that's preventing ignite streaming to work fully. But generally, what I'm seeing is that I can send messages into Ignite, and the receiver can take them out.

Re: AtomicSequence not working when shutting down one server node from a cluster

2016-09-16 Thread hitansu
Is it like replication ?But if the AtomicSequnce is cluster wide, then it should work even one of the node is down.Isn't it?Why is it computing the AtomicSequnce only in one node ? -- View this message in context:

Re: Argument Type Mismatch for Oracle CLOB

2016-09-16 Thread Alexey Kuznetsov
Hi Kenan! I prepared sample project with sample MyTransformer class. Sample project will start in-memory H2 database server. Populate some data, load from db and executes some queries. See DemoStartup class. MyTransformer works as expected. PojoTransformerDemo.zip

Re: One failing node stalling the whole cluster

2016-09-16 Thread yfernando
Hi Denis, We have been able to reproduce this situation where a node failure freezes the entire grid. Please find the full thread dumps of the 5 nodes that are locked up. The memoryMode of the caches are configured to be OFFHEAP_TIERED The cacheMode is PARTITIONED The atomicityMode is

Re: Official Apache Ignite meetup - Sept. 22nd - London

2016-09-16 Thread Christos Erotocritou
We will try to stream the event live. But we will certainly share the video and slides following the meetup. On Friday, 16 September 2016, Alexey Kuznetsov wrote: > It is possible to see slides or even meetup video? > > 16 Сен 2016 г. 14:09 пользователь "Christos

Re: Official Apache Ignite meetup - Sept. 22nd - London

2016-09-16 Thread Alexey Kuznetsov
It is possible to see slides or even meetup video? 16 Сен 2016 г. 14:09 пользователь "Christos Erotocritou" < chris...@gridgain.com> написал: > Hello Igniters! > > Following our first and successful official Ignite meetup > in London, we are now >

Re: Cannot recreate cache after cache.destroy()

2016-09-16 Thread aosmakoff
Hi Val, We discovered that in the test above following your suggestion the cache gets recreated and however the part swapped to the disk has not been cleared. The file is still there after cache.destroy() gets called. The cache swapSize does not go to 0 either. The newly created cache allows new