Re: [Webinar] How to Migrate Your Data Schema to Apache Ignite

Recording for those who couldn't join the webinar: https://www.youtube.com/watch?v=fwMRFA7BWTk Ivan, excellent presentation! - Denis On Tue, Dec 3, 2019 at 4:41 PM Kseniya Romanova wrote: > Hi Humphrey! Checked in chrome and firefox - the link is alive and > registration works. Please try aga

Re: [Webinar] Data Streaming Using Apache Flink and Apache Ignite

Thank you Alexey, yes I think all the webinar videos are recorded and shared in youtube. https://www.youtube.com/results?search_query=gridgain+webinar I can share the webinar video once it is available. On Sun, Dec 8, 2019 at 10:28 PM Alexey Zinoviev wrote: > Great to get a video after to watc

Ignite Hanging on startup after OOME

We are running Ignite in LOCAL mode with persistence enabled. For large putAll calls with low off-heap memory enabled, we are able to trigger OOM exceptions, which is something that is being investigated separately. When these exceptions occur and our process is run again, it hangs when calling

IgniteCache clear vs. removeAll

I am a little confused on the exact difference between clear and removeAll in the IgniteCache API. In the documentation for removeAll: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#removeAll--, it mentions this being an expensive operation and that clear sh

Re: PutAll Behavior Single vs Multiple Servers

Any pointers to understand this behavior? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite with Spark Intergration

I integrated spark and ignite using thrift client will that do ? https://github.com/kali786516/ApacheIgnitePoc/blob/master/src/main/scala/com/ignite/examples/spark/SparkClientConnectionTest.scala#L73 On Monday, December 9, 2019, Denis Magda wrote: > Hi, just ensure that "clientMode" is set in

Re: Transaction operations using the Ignite Thin Client Protocol

It worth noting that users should be cautious with SQL transactions. As fair SQL transactions are supported only for TRANSACTIONAL_SNAPSHOT mode which are still kind of experimental feature [1]. [1] https://apacheignite.readme.io/docs/multiversion-concurrency-control пт, 6 дек. 2019 г. в 15:12, I

Topology version changing very frequently

My application nodes are running on VMs and observing that topology version is changing very frequently but I do not see any error/exceptions/warnings in log files. For ignite I have kept the log level to WARN. Timeout settings in millis are as follows: FailureDetectionTimeout = 12 NetworkTi

Re: Local node terminated after segmentation

> Can someone please advise on this? > > -- Forwarded message - > From: Prasad Bhalerao > Date: Fri, Nov 29, 2019 at 7:53 AM > Subject: Re: Local node terminated after segmentation > To: > > > I had checked the resource you mentioned, but I was confused with > grid-gain doc descr

Re: Possible race on node shutdown

Andrey, Sounds reasonable. Would you mind to create a ticket in Jira? пн, 9 дек. 2019 г. в 13:33, Andrey Davydov : > > AFTER_NODE_STOP state was ignored, because JVM stop. In our case it is not a > problem. > I think that there are some scenarios when AFTER_NODE_STOP is important. > > On Thu, De

Re: Deadlock on concurrent calls to getAll and invokeAll on cache with read-through

Hello! Unfortunately you seem to be right and this is an issue. I have filed a ticket https://issues.apache.org/jira/browse/IGNITE-12425 to track it. Regards, -- Ilya Kasnacheev пн, 2 дек. 2019 г. в 16:33, peter108418 : > Hi > > We have recently started to encounter what appears to be deadlo

Re: Failed to start near cache (a cache with the same name without near cache is already started)

Hi! You need to be careful, with copyOnRead disabled, any local read can return a "real" copy of the object and you can cause pretty weird bugs if you modify that object, so be careful with that or best is to only use it for readonly cases. If you see that much performance improvement I woul

Re: Topology version in ignite

My bad... please ignore this mail... I did not see that clients are fluctuating On Mon, Dec 9, 2019 at 5:38 PM Prasad Bhalerao wrote: > Hi, > > My application nodes are running on VMs and observing that topology > version is changing very frequently even though the number of server and > client

Topology version in ignite

Hi, My application nodes are running on VMs and observing that topology version is changing very frequently even though the number of server and client nodes are same. I am observing that the topology version is increasing with change in heap size and number of CPUs. I was under the impression t

Re: Failed to start near cache (a cache with the same name without near cache is already started)

I have disabled copyonread and the time taken to getAll() reduced to 1/3. Earlier it was 300 ms on 10k entries and now it is 100ms. Is disabling copyonread is fine ??? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to start near cache (a cache with the same name without near cache is already started)

Hello! Did you try to profile it? What is taking the time? Regards, -- Ilya Kasnacheev ср, 27 нояб. 2019 г. в 18:59, Hemambara : > Thank you. I am not getting this error now. But not sure if something wrong > with config. When I call getAll(all keys) on near cache, then the > performance is w

Re: Upgrading the Ignite cluster while keeping the system functional

Hello! Unfortunately Apache Ignite has neither rolling version upgrades nor replication of data between clusters. So you should expect to see downtime. However, this is only for version upgrades, you can usually upgrade your own code with rolling restarts (make sure rebalance is done after each on

Re: Does Ignite support nested joins for partitioned cache?

Hello! Can you please throw together a reproducer project? One which runs some nodes, populates some data in tables and then shows the wrong results. Please make it runnable if you want quick response, with Maven, etc. Regards, -- Ilya Kasnacheev пн, 9 дек. 2019 г. в 09:38, DS : > Hi,Its rea

Re: Possible race on node shutdown

AFTER_NODE_STOP state was ignored, because JVM stop. In our case it is not a problem. I think that there are some scenarios when AFTER_NODE_STOP is important. On Thu, Dec 5, 2019 at 11:05 AM Ivan Pavlukhin wrote: > Hi Andrey, > > Do see the exception only in logs or your code experiences the > e

Re: Ignite with Spark Intergration

Hi, just ensure that "clientMode" is set in IgniteConfiguration that you pass to Spark's IgniteContext object. Spark worker will spin up a client node automatically for you and that one will reach out to the server (assuming you properly configured Ignite discovery SPI in the same IgniteConfigurati

Re: Ignite Kafka Connector

Hi, the sink streams data to some of the caches by definition and those caches, to my knowledge, are created by you. Don't you set "dataStreamer" parameters for the Kafka integration? The streamer is always bound to one of the caches. - Denis On Mon, Dec 9, 2019 at 9:13 AM ashishb888 wrote: >

Ignite meetup at Google Headquarters on Dec 18th

Igniters, This month we united with Silicon Valley Java User Group and we'll be repeating In-Memory Computing Essentials for Software Engineers session at Google HQ. Come over to meet in person, a lot of coding and practical examples. RSVP using our local group below (and attend it to not miss fu