2.4.0 with Tomcat 8.5 and Java 9

Hello, >From the suggestion on my other thread to try a newer Tomcat, I decided to spin up Tomcat 8.5.29 with Oracle JDK 9.0.4. I'm attempting to use web session clustering based on the following pages [1] and [2] as I saw the 2.4.0 release notes say Java 9 is now supported. I copied the

Re: Slow data load in ignite from S3

When I did this, I found that with Ignite Persistence, there is a lot of write amplification (many times more bytes written to SSD than data bytes written) the during the checkpoints, which makes sense because ignite writes whole pages, and each record written dirties pieces of many pages. The

Re: How to insert multiple rows/data into Cache once

1a. No. DataStreamer doesn't supports transactions. 1b. SQL doesn't support transactions and it is under active development for now [1]. 2. DataStreamer updates is not propagated to CacheStore by default, you can force this with allowOverwrite option [2]. DataStreamer uses individual entry

Re: Using 3rd party DB together with native persistence (WAS: GettingInvalid state exception when Persistance is enabled.)

Hi It is very easy for user to shoot himself in a foot... and they do it again and again e.g. like this one [1]. [1] http://apache-ignite-users.70518.x6.nabble.com/Data-Loss-while-upgrading-custom-jar-from-old-jar-in-server-and-client-nodes-td20505.html On Thu, Mar 8, 2018 at 11:28 PM,

Re: Any idea what this is ?

Hi, Config looks ok. Looks like some object still can't be unmarshalled due to some reason. Can you share a reproducer? On Wed, Mar 28, 2018 at 2:13 PM, Mikael wrote: > Hi! > > It behaves a bit different if I try to use BinaryConfiguration.SetClassNames, > I added

Re: Performance of Ignite integrating with PostgreSQL

Hi, 1. Have you tried to test your disk write speed? it is possible it was formatted with no align respect. 2. Have you tried to check if there is any Postgres issues? E.g. via querying postgres directly. Do you see higher disk pressure? 3. Is it possible you generate data too slowly? Have you

Re: Spark 'close' API call hangs within ignite service grid

Hi, Socket exception can be caused by wrong network configuration or firewall configuration. If node will not be able to send an response to other node then it can cause grid hanging. (Un)marshall exceptions (that is not caused by network exceptions) is a signal that smth goes wrong. On Fri,

Using Ignite grid during rebalancing operations

I’ve been reading how Ignite manages rebalancing as a result of topology changes here: https://apacheignite.readme.io/docs/rebalancing It does not say so explicitly, but reading between the lines suggests that the Ignite grid will respond to both read and write activity while rebalancing is in

Re: Running heavy queries on Ignite cluster on backing store directly without impacting the cluster

Hi, >In this case also, since we dont have eviction in place, all the time data >is retrieved from RAM only, the only time request goes to Oracle is for >Upserts and delete. Here, all queries run on data in RAM only. Ignite just propagate updates to back store (to Oracle via CacheStore impl) with

Re: Ignite Client Heap out of Memory issue

Hi Shawn, The OOM error occurs on remote server node, there were not sufficient memory to process request, but other threads were not affected by this. Looks like, Ignite was able to recover from the error as it was suppressed and reply to client has been sended. On Mon, Apr 2, 2018 at 8:22

Re: Distributed lock

Hi, If lock will be resides on node that hold the lock, how newly joined node will discover just locked lock instance by lock name to add itself in waiting queue? Who will be responsible for waiting queue handing? Does the queue should be transferred when owner has changed? And finally, how this

Re: Slow data load in ignite from S3

Hi Rahul, Possibly, mostly a new data is loaded to Ignite. I meant, Ignite allocate new pages, rather than update ones. In that case, you may not get benefit from increasing checkpoint region size. It will just deffer a checkpoint. Also, you can try to move WAL and ignite store to different

Re: Upgrade from 2.1.0 to 2.4.0 resulting in error within transaction block

Cross posting to dev. Vladimir Ozerov, can you please take a look at NPE from query processor (see below - GridQueryProcessor.typeByValue(GridQueryProcessor.java:1901))? --Yakov 2018-03-29 0:19 GMT+03:00 smurphy : > Code works in Ignite 2.1.0. Upgrading to 2.4.0 produces

Re: Distributed lock

Hi,Roman Thank you for the reply. I think i should change the value of cacheMode to replicated, it is more safe. why not cache the lock on the node who own the lock? If the node leaves topology, it will has no effect on other nodes. Thanks -- Sent from:

Re: stop sending messages pls

Hello, To unsubscribe from the user mailing list send a letter to user-unsubscr...@ignite.apache.org with a word "Unsubscribe" without quotes as a topic. If you have a mailing client, follow an unsubscribe link here: https://ignite.apache.org/community/resources.html#mail-lists Thanks, S.

Re: Distributed lock

Hi, Yes, you are right. Default backups count is zero by default. This way it is possible to lose some locks if one of the nodes leaves topology. You are able to set backups count in AtomicConfiguration: ...

stop sending messages pls

My email is andriy.kasat...@kyivstar.net. Can you please unsubscribe this mail.

Re: Slow data load in ignite from S3

Hi Andrey, Yes we are using SSD. Earlier we were using default checkpoint buffer 256 MB , in order to reduce the frequency, we increased the buffer size , but it didn’t have any impact on performance On Fri, 30 Mar 2018 at 10:49 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Hi, >

Distributed lock

Hi I want to use reentrantLock of ignite. In the code, the default backups is zero in AtomicConfiguration. When a node leaves topology, some locks cached on this node will lost? Should i modify the configuration of atomicConfiguration? Thanks -- Sent from:

Re: Running heavy queries on Ignite cluster on backing store directly without impacting the cluster

HI Let me rephrase my question, guess I have conveyed my question correctly. Lets take an example Ignite cluster with backing store as RDBMS - oracle and no eviction in place. As we all know, we can run complex queries on Oracle to retrieve desired data. In this case also, since we dont have

Re: Where is the data stored in Durable Memory?

Hi Lucky, Please, check if IGNITE_HOME env. variable or JVM property is properly configured. The persisting data should be located in ${IGNITE_HOME}/work directory. If you are on linux, check /tmp/ignite directory as a default one. Details about file types and folder structure you can find here