Non-loopback local Ips:172.17.0.1...

Hello, I have 2 disk and each have 2 nodes so I have 4 nodes. A few days ago, when I starting node there is these log.. Non-loopback local Ips:172.17.0.1, 'disk local Ip' what is 172.17.0.1 Ip?? it clustered and started well with rest of the nodes. I used SystemView to get local node Ip.

Re: Cache Expiry policy not working..

Hello, There is a get method in my code. but that method is not for expiry check that method to check if data is saved well. I figured out in GirdGain webconsole cache size after 4hours data put(expiry policy is 4 minutes). -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite NPE when try to loadCache from persistent mysql database

Hi Experts, When try to loadCache from 3rd party mysql database, (this.balanceCache.loadCache(null);) met ignite NullPointerException, thanks a lot for some clues, 10:21:15,376 [mgmt-#66] ERROR org.apache.ignite.internal.processors.task.GridTaskWorker - Failed to obtain remote job result

Re: Ignite Queue

Yes the common pattern is not documented. So was expecting if no exception is thrown that I'm getting a queue and can put something on it. But then if I don't check for null I'll get a NullpointerException. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to map SQL query

Hi, Most likely, the query intermediate result doesn't fit to JVM heap memory. The query may require all table data fetched before applying sorting. You can try to create a composite index over "act_id,mer_id,score" columns. On Tue, Aug 25, 2020 at 8:42 AM 1115098...@qq.com wrote: > Hi,an

Re: Cache Expiry policy not working..

Hello, here is my code for test. public class CachePutLoopTest { /** * @param args */ public static void main(String[] args) { /* cache의 ip, port 파라미터를 받아서 특정노드에 데이터를 저장 */ System.out.println("┌ Cache Rebalance Put/Get Start

Lag before records are visible after transaction commit

Hi, I am performing the following operation on node 1 of my 3 node cluster (All caches use CacheRebalanceMode.SYNC, CacheWriteSynchronizationMode.FULL_SYNC, CacheAtomicityMode.TRANSACTIONAL): try (Transaction tx = ignite.transactions().txStart(

Executing select query in Partition mode (cluster with two nodes) taking more than 10 minutes.

Hi Team, I have created cluster with two nodes. After creating new table , we are executing select query for first time , It is taking too much time to fetch data. (almost 10+ min) Please find attachment my server xml configuration and below is client

Re: Isolating IgniteCache instances across JVMs on same machine by id

Hi, Is there a solution to this? We are experiencing a similar issue. We have two separate clusters on the same physical server with 3 persistence enabled nodes in each cluster. We are not able to restart nodes in one cluster without restarting both the clusters. Thanks Nagarjun -- Sent from:

Re: Ignite Queue

I see it's already being picked up in another thread: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Queue-Documentation-or-Code-defect-td33703.html I can't delete this thread. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cache Expiry policy not working..

Well, in the code you've shared you're not waiting between puts and checks after that. I used this expiry policy for cache: FactoryBuilder.factoryOf(new CreatedExpiryPolicy(new Duration(SECONDS, 1 and added Thread.sleep(2000) before puts and gets in your code and ExpiryPolicy world for me

Re: 2.8.1 : Server cluster node startup issue

Veena, I am not getting the same issue/thread dump when I run a similar use case. In your case it looks like Ignite has not fully started before Ignition.ignite() has been called. The check inside that function is specifically designed to prevent such cases. Here is the function you are

Ignite 3.0 meetups

Igniters, As was discussed before, we've scheduled two meetups devoted to Ignite 3.0: - Sep 15 (in English): https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/272675408/ - Sep 17 (in Russian): https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/272675398/ I will

Re: Ignite 3.0 meetups

Hi Val, Thank you for scheduling the meetups. Will join and connect on Ignite 3.0 release planning. Regards, Saikat On Tue, Aug 25, 2020 at 4:49 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igniters, > > As was discussed before, we've scheduled two meetups devoted to Ignite

Re: Lag before records are visible after transaction commit

Hi, It looks like you need to use https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheWriteSynchronizationMode.html, just set it to FULL_SYNC for the cache using CacheConfiguration. setWriteSynchronizationMode. Evgenii вт, 25 авг. 2020 г. в 02:27, ssansoy : > Hi, I

Re: Lag before records are visible after transaction commit

Thanks for the reply but we are already using that setting which is the strange thing (All caches use CacheRebalanceMode.SYNC, CacheWriteSynchronizationMode.FULL_SYNC, CacheAtomicityMode.TRANSACTIONAL): As an update, the same behaviour is observed if B is retrieved using a ScanQuery rather than

Re: Failed to map SQL query

If it's expected that the SQL query will produce a large data set then consider using the memory quotas feature with the offloading to disk option . It's not available in Ignite though. GridGain releases it

Item not found, B+Tree is corrupted and critical error detected after add nodes to baseline topology

Hi community, Currently I have 25 nodes in my ignite cluster and all of them were added into the baseline, and I was trying to add another 5 nodes into it. The data in my cluster is about 8TB and the persistence is enabled. At first I start all the 5 nodes; then execute in the command line: ```