Re: Random CorruptedTreeException from Apache Ignite

I don't see cacheConfiguration in the provided snippet. Do you create it dynamically? What is your usage pattern? How do you use your cache? SQL, cache API? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Visor Cache command hangs indefinitely.

You could increase failureDetectionTimeout [1] from default value of 1 to 6 or so. https://apacheignite.readme.io/docs/tcpip-discovery#section-failure-detection-timeout -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Row count [select count(*) from table] not matching with the actual row count present in the table

Looks like a problem indeed. Evgenii already assigned the ticket to himself. Once the issue is fixed it will be included in the next release. Thank you for revealing the problem! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to run map query remotely.Failed to execute map query on the node

Let's put this thread on hold then until we understand the circumstances of the problem. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: UPDATE query with JOIN

Hey, something is wrong in your sample SELECT DISTINCT t1.ID AS ID FROM PUBLIC.AAA_STR_HIE_ACCOUNT t1 LEFT JOIN PUBLIC.AAA_STR_HIE_ACCOUNT t2 ON t2.PARENT = t1.ID AND t2.hier = t1.hier WHERE t2.PARENT IS NULL AND t1.hier = 'H4'; The resultset will be either empty or one row with null in it,

Re: client reconnect working?

I think the problem could be with communicationSpi config. You specified connectTimeout as 0, which is interpreted as infinite timeout. Try to change it to a non-zero value. -- Sent from:

Re: Failed to run map query remotely.Failed to execute map query on the node

Hi, Please share full logs from all server nodes. It has to be an exception with a stacktrace related to the incident. Do you have a scenario to reproduce this issue? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: updating a composite Key in Ignite SQL Table

Hi Mahesh, It is not planned at the moment. I think you could simply replace this with a DELETE and INSERT as a workaround. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Random CorruptedTreeException from Apache Ignite

Hi, >From the stacktrace I can tell that there is a problem with an index in your cache. It's hard to tell more from the stacktrace itself. Could you share the cache config as well? In the next release (probably 2.8) such exceptions will be better explained in the logs

Re: Ignite on GCP / GKE

Hi Stephane, Since Ignite is basically just a java process, it's as reliable as any other java application. You should probably set workDirectory, wal and storage to a mounted disk in Ignite config if you use persistent data regions and want your data to survive pod restarts. Those mounted disks

Re: Can we avoid the PME when restarts a node in cluster.

Hi Justin. There is no such option. PME speed was significantly improved in recent releases though. Consider upgrading to 2.7.5 version. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: cache update slow

Glad you met your requirements. I think it is not fair to compare Ignite with direct memory access, so I can't really say whether this is a good result or not. In your case .net process starts a java process and communicates with it via JNI [1]. Also Ignite stores cache data off-heap, which

RE: cache update slow

Thanks for sharing your code. I didn't realise you use .NET. Check out how you can benefit from data streamer in .NET [1]. It was designed to populate your cache faster, so it could help you to improve performance. [1] https://apacheignite-net.readme.io/docs/data-streamers -- Sent from:

Re: Cache question

Let me try to answer this question. 1. I would recommend to avoid this, because Ignite stores objects as binary arrays, so you will have an object from A being stored as an array of bytes in both: cache A and cache C, which obviously takes more memory. Another reason not to use it is that you will

Re: Query Monitoring

Those tickets are targeted to 2.8, so it will be available in the next release. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Visor hangs trying to connect.

Hi, please share the logs from visor node and all server nodes as well. I'll have a look. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: cache update slow

Hi, the execution time depends on the configuration of your cache and your cluster. How many node do you have? What is your cache configuration? Have you tried Ignite data streamer [1] instead of cache.put(K,V)? [1]

Re: Strange behavior with tables partitioned and replicated, and indexes on join

By default Ignite thinks that data is collocated. You have to tell Ignite that it is not. For example, by adding a parameter to JDBC connection: distributedJoins=true or by using this method SqlQueryFields.setDistributedJoins [1] in java API. [1]

Re: Can't use loadCache with IgniteBiPredicate

My assumption was that you used IgniteCache.withKeepBinary(true) in your own method getCache(Foo.class) method. Anyway, congrats on finding a solution. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Production network and backup requirements

Hi Jose, There are no strict requirement for network connection quality as you can adjust network properties [1] for your particular case. Talking about a cache distributed across two separate data centres is totally fine. Just make sure that connection between them is stable and think of a

Re: Strange behavior with tables partitioned and replicated, and indexes on join

Hi, check out this article: https://apacheignite-sql.readme.io/docs/distributed-joins#section-non-collocated-joins -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Read/query TPS is decreasing after enabling mix load i.e. write services

Hi, could you share a reproducer of your problem? We are missing a lot of information here. The configuration of your nodes, cache configurations, what API you use to query and update the data. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: when cluster restart then client need deactived

It hard to tell from your explanation what is the exact problem. Is it the client which cannot connect to the cluster while it is the middle of the activation process? Anyway, could you share the logs from all nodes (client logs as well)? It will help to understand the problem. -- Sent from:

Re: Can't use loadCache with IgniteBiPredicate

You might used the method org.apache.ignite.IgniteCache#withKeepBinary [1] that's why your object wasn't deserialised. [1] https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#withKeepBinary-- Max. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: WeightedRandomLoadBalancingSpi. How to make so that on a node with a big weight the bigger quantity of tasks left?

Did you use ComputeTaskSplitAdapter [1] for your tasks? It works just fine on 2.7.0. [1] https://ignite.apache.org/releases/2.7.0/javadoc/org/apache/ignite/compute/ComputeTaskSplitAdapter.html

Re: WeightedRandomLoadBalancingSpi. How to make so that on a node with a big weight the bigger quantity of tasks left?

Hi Dmitry, There is a test for WeightedRandomLoadBalancingSpi [1]. It passes on master. Which version of Ignite do you use? Could you share a reproducer of the issue so I can have a look? [1]

Re: Which IgniteCompute function?

Hi, Look at Compute.broadcastAsync method [1]. It sends IgniteCallable [2] jobs to all nodes in a cluster. You can use SqlFieldsQuery with setLocal(true) [3] inside your IgniteCallable to extract data. [1]

Re: Ignite with Spring cache

It is not completely clear what exactly you are trying to achieve. Could you describe your case in depth, share a piece of code or pseudo code? If you want to iterate through all cache entries, you can use Ignite cache API for that: org.apache.ignite.Ignite#getOrCreateCache(java.lang.String).

Re: How to get the column names(or fieldsNames) of existing ignite sql table

1. Check out this thread to get a list of fields: http://apache-ignite-users.70518.x6.nabble.com/Get-Field-Names-In-Select-Query-td25258.html 2. "Create table..." command creates a cache under the hood. https://apacheignite-sql.readme.io/docs/create-table -- Sent from:

Re: NearCache entries on heap ?

Near cache is always on-heap. Its not an independent cache, its just a local copy of a cache stored on another node. In some cases it improves performance. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Does it affect the put, get, query operation when add or remove a node?

There is no simple answer to this question. It depends on configuration of your cluster and load profile. Cluster won't stop in any case, because it is designed to support scaling, but the performance could be affected. If you use partitioned caches (default cache configuration) then adding or

Re: Is near cache persistent ?

Near cache is a local cache for faster access to data on client nodes. Client node is a node, which connects to a cluster, does some work and could be disconnected after that, it doesn't store data permanently, that's server node's responsibility. -- Sent from:

Re: Ignite Query Slow

Hello, It is hard to tell what is the bottleneck in your case, could be anything. I suggest tracking CPU and memory usage, enable GC logs. Adding more nodes will definitely help in this case. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.7

It is up to community to decide. You can track the progress here: http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-Last-Mile-td36359i40.html I think it will happen in a matter of weeks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IgniteBiPredicate anonymous class - ClassNotFoundException

I guess you have 2 nodes, but only one of them has that class in its classpath. Check out this article: https://apacheignite.readme.io/docs/zero-deployment#section-peer-class-loading -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Strange issue while call ddl

Looks like a bug to me. If you have a reproducer of this issue, please, share it. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: SQL Affinity colocation

Hi Jose, Seems right to me. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Simple off heap implementation ?

Hi, To use persistence you need to get familiar with the concept of baseline topology: https://apacheignite.readme.io/docs/baseline-topology It basically means, that you need a fixed set of server nodes to store data. You can config which node will store partitions of a particular cache by using

Re: Cluster is not responsive after node segmentation and reconciliation

You definitely need to increase heap size to prevent OOM errors. ./ignite.sh -J-Xmx4g If it doesn't help, provide full logs from all nodes. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Persistence store data not getting distributed across files on different machine in cluster

Looks like you baseline topology (nodes used for persistence) contains only 1 node. Have you tried adding other nodes to the baseline topology? Please follow this guide https://apacheignite.readme.io/docs/baseline-topology#section--add-nodes-to-the-topology to do so. -- Sent from:

RE: Services not initializing in persistence enabled cluster nodes

Your case is well described in docs https://apacheignite.readme.io/docs/baseline-topology#section-adding-new-node Hope, it will help. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Affinity function and partition aware database loading

Hello, If you want to benefit from partition aware data loading, you must set up an affinity key field, without it SQL will make a full scan every time. If you don't plan to use SQL on Ignite's side, then you can set up a custom AffinityFunction

Re: Cluster is not responsive after node segmentation and reconciliation

Without ignite logs it's hard to say what's going on. This file is located at $IGNITE_HOME/work/log -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: lost partition recovery with native persistence

Great idea, I like it. However, it's better to discuss development plans on development list http://apache-ignite-developers.2346864.n4.nabble.com -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: lost partition recovery with native persistence

I'm not an architect of this feature, but the explanation could be quite simple: data stored in lost partitions could have become outdated while nodes containing data were out of the cluster, so it's up to user to decide whether the restored data is OK, or not. -- Sent from:

Re: Persistence store data not getting distributed across files on different machine in cluster

Hi. It might be the case of improperly activated cluster. You can check which nodes are in the base topology by using a command ./control.sh --baseline Here https://apacheignite.readme.io/docs/baseline-topology you can read more about it. Hope it will help. -- Sent from:

Re: Writing binary [] to ignite via memcache binary protocol

Hi, it looks strange to me. Do you have a reproducer? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: fieldsQueryCursor.getAll() performance is really bad

As long as you use IN statement there is no need in additional id > 0 condition. It might lead to retrieving all data that fit for id > 0 and filtering them on the client side. Use could use "explain" to check whether my guess was right

Re: Cluster is not responsive after node segmentation and reconciliation

Please, check the file you attached, it doesn't contain any logs. Persistence will help to save data and prevent running out of memory. Another option is to set an eviction policy: https://apacheignite.readme.io/docs/evictions -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite running on JDK10?

https://issues.apache.org/jira/browse/IGNITE-8441 is still open. However, fix version is 2.7, which is coming soon. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Catch ComputeJob failures on the offending Node.

You can listen to Ignite events . I believe, the event type you are looking for is EVT_JOB_TIMEOUT -- Sent from:

Re: Ignite Cache metrics on K8s

Try to call CacheMetricsMXBean.enableMetrics(). See also https://apacheignite.readme.io/docs/cache-metrics#section-using-jmx-bean -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to Auto Increment ID column

It was already discussed perviously . -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Unreasonable segmentation in Kubernetes on one node reboot

What about logs from other nodes? This one doesn't tell much. Could you share you kubernetes config? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Unreasonable segmentation in Kubernetes on one node reboot

Hi, Can you share the full logs from all nodes? Looks like everything should work just fine. Maxim. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Stupide question about Queue ?

Yes, this this functionality was presented in 2.1.1. Just turn on persistence by calling IgniteConfiguration cfg = new IgniteConfiguration(); cfg.setPersistentStoreConfiguration(new PersistentStoreConfiguration()); In 2.3.1 API has changed. Now it is required to enable persistence in a default

Re: IgniteInterruptedException: Got interrupted while waiting for future to complete

Hello. Do you really need to add all this data in a single transaction? That's not a typical use case. Do you have any other operations running in parallel? Unfortunately, having this stack trace is not enough to help. Could you provide a full ignite log and your configuration as well? -- Sent

Re: AFTER_NODE_START event

Hello! The answer is yes. It is safe to subscribe to AFTER_NODE_START. I've just checked the sequence of events happening during the node startup and org.apache.ignite.events.EventType#EVT_NODE_JOINED happens *before *org.apache.ignite.lifecycle.LifecycleEventType#AFTER_NODE_START. With Regards,