Hi,
I found the problem. It happened because of small mistake in my code.
Reason: Write through was enabled and the batch size for addBatch operation
in writeAll method was 1. Because of this it was taking time. When I
changed the batch size to 10,000 the problem got resolved.
Thanks,
Prasad
On
Hello!
Then there's an obvious problem than something is trying to join with your
node. I expect it's the node itself, due to network configuration it
doesn't realise that it phones to itself.
--
Ilya Kasnacheev
2018-05-10 20:51 GMT+03:00 JP :
> I am just running only
Hello,
Could you please tell which version are you using and if possible, share
ignite/cache configuration, full log and some short reproducer to this
issue?
Best regards,
Anton
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Are you using Spring-boot 1.5.11+?
Try to explicitly set H2 version to 1.4.196 if you have it in your pom.xml,
this seems to be a known issue
https://issues.apache.org/jira/browse/IGNITE-8197 related to later H2
versions.
Also note that you have
2018-05-11 16:00:23.114 WARN 15888 --- [
Hi,
Seems like a STW/full GC happens on your nodes for quite a long time or some
network issues are there, please try to set failureDetectionTimeout property
in IgniteConfiguration to some and
in logger and see if this is reproduced.
Also having you see "Received incoming connection
Hi,
I am modifying cache entries inside a transaction.
I get updated values when I use cache.get() api within the same transaction
(before doing commit).
But when I try to get the same values using select query with in this
transaction, I do not get the updated values. I get old values.
Is this
Thanks Anton for the information.
Here I re-summarized and added more details and both server and client logs
when the incident happened.
[Cluster configuration]
Windows Azure VM scale set
Windows Server 2016 10.0 amd64 VM x 40 nodes
VM information: Java(TM) SE Runtime Environment
Hi,
This feature is being actively developed in
https://issues.apache.org/jira/browse/IGNITE-4191.
Also please take a look to enchancement proposal on this topic to follow:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-3%3A+Transactional+SQL
Currently transactional guarantees are fully