Random2LruPageEvictionTracker causing hanging in our integration tests

2020-04-27 Thread scottmf
I'm seeing our integration tests hang. The cause is something in Random2LruPageEvictionTracker, i'm able to reproduce this 100% of time on many different laptops and in our ci/cd. I was able to work around this by disabling PageEviction in our Default Data Region during the tests. I don't see th

[VOTE][EXTENSION] Release Apache Ignite Spring Boot extensions 1.0.0 RC1

2020-04-27 Thread Nikolay Izhikov
Dear Community, I have uploaded a release candidate of the two extension modules `ignite-spring-boot-autoconfigure` and `ignite-spring-boot-client-autoconfigure`. The following staging can be used for testing: https://repository.apache.org/content/repositories/orgapacheignite-1478/ Tag with na

Re: Insertions slow on high load on Ignite 2.7.5

2020-04-27 Thread Ilya Kasnacheev
Hello! Your understanding is correct. Yes, if you have more RAM and larger data region, the process should slow down less rapidly. Regards, -- Ilya Kasnacheev пн, 27 апр. 2020 г. в 17:56, Shubham Agrawal : > Hi Ilya, > > This data loading is not a one time activity for our scenario. So, I gu

Re: Insertions slow on high load on Ignite 2.7.5

2020-04-27 Thread Shubham Agrawal
Hi Ilya, This data loading is not a one time activity for our scenario. So, I guess turning off the WAL would not be a solution since turning off and on every time is not feasible every time the data loading happens. Please let me know if my understanding is correct. I'll try to increase time bet

Re: Insertions slow on high load on Ignite 2.7.5

2020-04-27 Thread Ilya Kasnacheev
Hello! My recommendation is to increase time between checkpoints (checkpointFrequency) and, maybe, also increase checkpoint page buffer. If you do data loading in bursts, it may make sense to turn off WAL why you do data loading. You may still expect some data degradation as time goes on (what's

Re: EPOCH seconds in future!

2020-04-27 Thread dbutkovic
Hi Ilya, thnx for replay, I think that Ignite CURRENT_TIMESTAMP() is NOT TIMESTAMP WITH TIME ZONE. Below it test with inserting CURRENT_TIMESTAMP in two tables, one with data type TIMESTAMP and second with TIMESTAMP WITH TIME ZONE. First of all, in Ignite documentation I can't find that CURRENT

Re: EPOCH seconds in future!

2020-04-27 Thread Ilya Kasnacheev
Hello! In Ignite, CURRENT_TIMESTAMP() is TIMESTAMP WITH TIME ZONE. Regards, -- Ilya Kasnacheev вс, 26 апр. 2020 г. в 14:51, dbutkovic : > Hi Ilya, > > thanks a lot for the reply, > it is surprising that EPOCH is not always the same regardless of the > timezone. > I did a test on two Ignite i

Re: remote ignite server and L4(for loadbalacing) with java thin client

2020-04-27 Thread kay
Hi, Could you share about "partition awareness" detail information? like, example link. And you said Ignite thin client on startup select's random server to connect available address. This selection(connect to server node) is not going to be change before server node is shut down?? or my applica

Re: TcpDiscoverySharedFsIpFinder with different machine..

2020-04-27 Thread kay
yes, i mean same disk. oh.. I see. Thank you so much for help -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Loading cache from Oracle Table

2020-04-27 Thread yossi
Hi Prasad, Any update on this? I have a similar use case when I have to load 10million of records from a mysql database table but I keep getting the error "(jvm-pause-detector-worker) Possible too long JVM pause" even ignite persistence is enabled (which should write in disk the data when the d

Re: TcpDiscoverySharedFsIpFinder with different machine..

2020-04-27 Thread Stephen Darlington
What do you mean by “I wrote a path and it worked at same machine”? Do you mean that it’s a local disk? TcpDiscoverySharedFsIpFinder is designed to work with a shared filesystem, i.e., all four of your nodes mount the same disk. > On 27 Apr 2020, at 09:55, kay wrote: > > yes, I wrote a path

Re: TcpDiscoverySharedFsIpFinder with different machine..

2020-04-27 Thread kay
yes, I wrote a path and it worked at same machine(it means same IP). My question is how can i set *different machine*(different IP,). For example) I have 4 node --> machine 1 IP list 41.1.122.122:12200-> a 41.1.122.122:12202-> b - machine 2 IP list 41.1.122.123:12200-> c 41.1.

Re: TcpDiscoverySharedFsIpFinder with different machine..

2020-04-27 Thread Stephen Darlington
The path is defined with the path parameter: ... https://apacheignite.readme.io/docs/tcpip-discovery > On 27 Apr 2020, at 08:44, kay wrote: > > Hello, > > I'd like to start 4 node at each different machine. > Is is possible for us

Re: Multicast Address

2020-04-27 Thread Stephen Darlington
Multicast generally only works on the same subnet, so I don’t think that’s going to work. The next most obvious solution would be to use a static list, as Evgenii said. If you don’t want to do that, you’re left with options like the JDBC or Shared File System IP finder (https://apacheignite.rea

Re: Multicast Address

2020-04-27 Thread bribridnl
I'd like to keep their IP dynamically managed that's why I use the TCP/IP discovery but you have to provide a multicast adress. My issue is that I don't know which one to use -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

TcpDiscoverySharedFsIpFinder with different machine..

2020-04-27 Thread kay
Hello, I'd like to start 4 node at each different machine. Is is possible for use TcpDiscoverySharedFsIpFinder for node clustering?? I figured out it was working with in same machine. but I'm wondering about different machine 'TcpDiscoverySharedFsIpFinder' . if it is possible how can i set the