Re: Call for presentations for ApacheCon North America 2020 now open

Hi Saikat, Can you please share the slides for both presentations, streaming as well as ignite internals? Thanks, Prasad On Wed 5 Aug, 2020, 7:10 AM Saikat Maitra Hi, > > I learned that my proposal for talk about Data Streaming using Apache Ignite > and Apache Flink has been accepted. > > I have

Re: CountDownLatch issue in Ignite 2.6 version

I just checked the ignite doc for atomic configuration. But it doesn't say that it is applicable to distributed data structures. Is it really applicable to distributed data structures like count down latch On Tue 9 Jun, 2020, 7:26 AM Prasad Bhalerao Hi, > I was under the impress

Re: Read through not working as expected in case of Replicated cache

a value is absent a > reader will receive an actual value from the underlying storage. > > Best regards, > Ivan Pavlukhin > > пн, 2 мар. 2020 г. в 10:41, Prasad Bhalerao >: > > > > Hi Ivan/Denis, > > > > Are you saying that when a value is loaded to cache from an un

Re: Read through not working as expected in case of Replicated cache

; Actually, behavior for PARTITIONED cache is similar, but an > > inconsistency is not observed because SQL queries read data from the > > primary node there. If the primary node leaves a cluster then an SQL > > query will not see the value anymore. So, the same inconsistency will > > a

Re: Read through not working as expected in case of Replicated cache

t; > I think this is by design. You may suggest edits on readme.io. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > пн, 24 февр. 2020 г. в 17:28, Prasad Bhalerao < > > prasadbhalerao1...@gmail.com>: > > > >> Hi,

Re: NodeOrder in GridCacheVersion

Hi, * How do you ensure that there are no concurrent updates on the keys? [Prasad]: The cache for which it is failing is kind of bootstrap cache which changes very rarely. I made sure that I was the only one working on this system while debugging the issue. The cache for which it is failing is

Re: NodeOrder in GridCacheVersion

Hi Alexey, Key value is not getting changed concurrently, I am sure about it. The cache for which I am getting the exception is kind of bootstrap data and it changes very rarely. I have added retry logic in my code and it failed every time giving the same error . Every time if fails in

Fwd: NodeOrder in GridCacheVersion

list discussion, this logging is not aimed at > end-user and you are not supposed to act on it. > > Do you have any context for us, such as reproducer project or complete > logs? > > Regards, > -- > Ilya Kasnacheev > > > ср, 26 февр. 2020 г. в 19:13, Prasad Bhalerao <

Re: Ignite 2.8 documentation

Hi, Can we have this behavior documented? This will help user to design their caches appropriately. *For Replicated Cache:* Reference mail thread: http://apache-ignite-users.70518.x6.nabble.com/Read-through-not-working-as-expected-in-case-of-Replicated-cache-td29990.html read through for

Re: GridGain Web Console is available free of charge for Apache Ignite

without limitations. Just download and use it. > > - > Denis > > > On Tue, Dec 10, 2019 at 1:21 PM Prasad Bhalerao < > prasadbhalerao1...@gmail.com> wrote: > >> Hi, >> >> Can apache ignite users use it for free in their production environments? >> What lic

Re: GridGain Web Console is available free of charge for Apache Ignite

Hi, Can apache ignite users use it for free in their production environments? What license does it fall under? Thanks, Prasad On Fri, Oct 4, 2019 at 5:33 AM Denis Magda wrote: > Igniters, > > There is good news. GridGain made its distribution of Web Console > completely free. It goes with

Native memory tracking of an Ignite Java 1.8 Application

Hi, I have set the off heap size to 500 MB and max heap size to 512 MB. My process is taking around 1.7 GB on Windows 10 as per the task manager. So I decided to track the memory distribution using jcmd to find out if there are any memory leaks in non-heap space. After pushing the data to cache

Re: [IGNITE-10925] After upgrading 2.7 getting Unexpected error occurred during unmarshalling

Server class as a java program 2) Then run com.example.demo.Client as java program. Thanks, Prasad On Sat, Jan 12, 2019 at 11:17 AM Prasad Bhalerao < prasadbhalerao1...@gmail.com> wrote: > No I am not using zookeeper discovery. > Using TcpDiscoveryVmIpFinder. > > Can someon

Re: After upgrading 2.7 getting Unexpected error occurred during unmarshalling

Resending I am not able reproduce this issue in small reproducer project but this is consistently happening in my project. So I debugged this issue and attached the screenshot in this mail. *NOTE: *This issue occurs if the statistics are enabled on cache configuration level

Re: After upgrading 2.7 getting Unexpected error occurred during unmarshalling

Resending with screenshots. > I am not able reproduce this issue in small reproducer project but this is > consistently happening in my project. So I debugged this issue and attached > the screenshot in this mail. > > > > *NOTE: *This issue occurs if the statistics are enabled on cache >

Re: After upgrading 2.7 getting error during unmarshalling (Works fine on 2.6)

Hi Ilya, I am not able reproduce this issue in small reproducer project but this is consistently happening in my project. So I debugged this issue and attached the screenshot in this mail. *NOTE: *This issue occurs if the statistics are enabled on cache configuration level

Fwd: Getting javax.cache.CacheException after upgrading to Ignite 2.7

Can someone please explain if anything has changed in ignite 2.7. Started getting this exception after upgrading to 2.7. -- Forwarded message - From: Prasad Bhalerao Date: Fri 4 Jan, 2019, 8:41 PM Subject: Re: Getting javax.cache.CacheException after upgrading to Ignite 2.7

Query Execution is very slow (Can I create a Jira for this )

Hi, I am executing a SQL with TEMP table join for IN caluse query. Sql is as show below. This sql is taking 20-30 seconds to execute. My cache has only 1.39 million entries but in real scenario I will be having around 40 million entries. I have created a reproducer and uploaded it to GitHub. I