AccessedExpirationPolicy with SQL

Hi I am using AccessedExpiryPolicy in my cache setup. I am setting the data in cache using the usual ‘put ‘ method but I am retrieving the data using SqlFieldsQuery. In this setup the expiration policy only considers the time of data creation and hence the data gets expired after the time from

Re: Large durable caches

I ran into this issue as well. I'm running tests on a six node Ignite node cluster, the data load stuck after 1 billion data is ingested. Can someone take a look at this issue please? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite equivalent of @GridUserResource

I'm also reviving a mothballed GridGain system that used a @GridUserResource - moving from Java 6/GridGain 3 to Java 1.8 / Ignite 2.4.0+ To replace it, I'm doing the following: - Use a LifeCycleBean that populates the nodeLocalMap before startup. - the objects placed in the nodeLocalMap are

How are SQL Queries executed on Ignite Cluster

Hi, I would like to understand how SQL queries are executed on Ignite Server Nodes. Each Ignite Server Node has some number of primary partitions it is responsible for. When a query is sent, let' say through JDBC interface, this query is routed to all the server nodes where data resides. So the qu

Baseline topology documentation clarified: usage scenarios and definition

Igniters, With the help of Stanislav Lukyanov and Ivan Rakov, we could make our baseline topology documentation much better and vivid. Check up the new sections that did a better job explaining the topology, cover common usage scenarious and explain how to trigger the rebalancing programmatically

Re: IGNITE-4985: Do not acquire asyncOp semaphore for retry operations and Maximum permit count exceeded on Semaphore in Ignite 2.3...

Lost source codes... IgniteInternalFuture commitTxAsync(final GridNearTxLocal tx) { FutureHolder holder = lastFut.get(); holder.lock(); try { IgniteInternalFuture fut = holder.future(); if (fut != null && !fut.isDone()) { Ignit

Re: Baseline Topology and Node Failure

We've documented your scenario and many others. Please check up this documentation section: https://apacheignite.readme.io/v2.4/docs/cluster-activation#section-usage-scenarios -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

IGNITE-4985: Do not acquire asyncOp semaphore for retry operations and Maximum permit count exceeded on Semaphore in Ignite 2.3...

Hi! Ignite 2.3, Maximum permit count exceeded on Semaphore... GridCacheAdapter.commitTxAsync(): But saveFuture() don't call acquire, only release: May be need *retry = true*? Alexander -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Using a cache as an affinity co-located processing buffer in Ignite.Net

Are cache interceptors an internal Ignite construct not available in the Java client? *From:* Pavel Tupitsyn [mailto:ptupit...@apache.org] *Sent:* Friday, May 18, 2018 1:53 AM *To:* user@ignite.apache.org *Subject:* Re: Using a cache as an affinity co-located processing buffer in Ignite.Net C

Client IgniteStreamer broken after cluster restart

Hi, I ran into a situation where I have a client running, all server nodes are restarted, the client reconnects as expected, but then after creating a new IgniteStreamer all attempts to send data fail due to a ClusterTopologyCheckedException. It appears the streamer is attempting to send data to a

Support for polymorphic SQL Queries

I am using ignite to store different model classes which inherit from the same interface on a single ignite cache. The problem that I am facing is with creating polymorphic queries. Let’s say I have a FinacialSecurity interface with different implementations Bond, CorporateBond, Swap, GovermentBon

Re: Heap exhaustion when querying

Thanks Ilya, but I don't have any code running on the Ignite servers other than the Ignite process. I am connecting with the SQL client DBeaver to run my query and running DBeaver on a separate machine. Are there any adjustments I can make on the Ignite server to insure that an arbitrary user que

Re: Service isn't initialized on cluster re-activation

Got it, makes sense. Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Distribution of backups

Hello David! Yes, I think that should be possible to implement. However, when a node fails there would be a massive backlog of rebalancing on just two nodes, and it might cause a problem on its own. Random placement guarantees that rebalancings are placed evenly in case of node failure Regards,

Distribution of backups

We built a cluster with 8 nodes using Ignite persistence and 1 backup, and had two nodes fail at different times, the first being storage did not get mounted and ran out of space early, and the second an SSD failed. There are some things that we could have done better, but this event brings up th

Re: Heap exhaustion when querying

Hello! Yes, SELECT * FROM cache; will cause problems for you, unless you are using lazy=true, which isn't default. However, if you're using lazy=true, you should probably search for memory leaks in your own code (such as trying to keep all results in memory at the same time instead of iterating).

Re: Heap exhaustion when querying

The query is just: select * from table1; My understanding was that 'lazy=false' is the default. Regardless of whether I set 'lazy=true' or explicitly set 'lazy=false' in my jdbc driver settings then I see the same behavior: Terminating due to java.lang.OutOfMemoryError: Java heap space It was

control.bat authentication support

Hi guys, I configured Ignite user/password authentication by adding custom plugin. It works fine in server/client nodes and visor but I can't find any auth support in control.bat I checked it's source code and don't see any place where I can provide credentials. Should I write my own control tool

Re: Using a cache as an affinity co-located processing buffer in Ignite.Net

Cache interceptors are not available in Ignite.NET and there are no plans to add them. On Tue, May 15, 2018 at 10:37 PM, Raymond Wilson wrote: > Hi Dmitriy, > > > > My question regarding cache interceptor availability in .Net is still > outstanding. > > > > I have working code using a continuous

Re: Ignite-yarn[Ignition] uses almost all memory and vcores available in YARN cluster

Hello! Since we don't seem to have much experience in running YARN here, can you please elaborate on this problem? Is the number of consumed resources wrong or are resources actually get consumed by Ignite? BTW, if you plan to store data inside Ignite, you should also set IGNITE_MEMORY_OVERHEAD_P

Re: Heap exhaustion when querying

Hello! I think that, foremost, you should share your query with us. Have you tried 'lazy=false' BTW? Regards, -- Ilya Kasnacheev 2018-05-16 19:34 GMT+03:00 engrdean : > I am using ignite with a native persistence and loading ~60k rows into a > new > cache via the jdbc driver. When I attempt

Ignite-yarn[Ignition] uses almost all memory and vcores available in YARN cluster

Hi, Ignite-yarn[Ignition] uses almost all memory and vcores available in YARN cluster. The allocated memory to the Ignition server was 40GB and 16 VCores. *When we checked the actual usage with yarn top command the Ignition server is using 380 GB and 140 VCores!!! * When we checked the cache, it

Re: Service isn't initialized on cluster re-activation

Nick, *TcpDiscoveryMetricsUpdateMessage* (aka heartbeats) are processed in the discovery thread, but not the exchange. So, if your *cancel() *method is hanging, then an exchange won't be able to proceed, but discovery will work fine. Hanging deactivation is not a pleasant thing, but I think, this

Re: read through cache refresh

Hi, When your data in back store has been changed, you should clear cache to force ignite forget outdated data. Yes cache.clear() will be enough. If you find this method slow and you have a large dataset, then you can try to destroy and recreate a cache instead. Cache will not blocked during cac