Re: Not able to set off heap max memory for Ignite queues

Hi Ilya, Part of the ignite spec is setting a memory cap on the queue via the CollectionConfiguration. If this isn’t implemented it’s a bug, if it’s not intended to be implemented it’s at least a doc bug. I don’t see how that’s possible though since collectionConfiguration seems very specific to ig

meaning of "Failed to send TTL update request"

Hi, I'm wondering if someone could explain what is going on with the "Failed to send TTL update request" error in a little more detail. We see this happening continuously and I don't think there are any adverse effects other than seeing the message pop up (~50 times in a 6 hour window). This is t

Re: meaning of "Failed to send TTL update request"

eed harmless? Perhaps the TTL request failed but then would it recover? If so, should the error severity change to WARN with a note that it is recoverable? thanks. On Tue, Feb 22, 2022 at 1:33 PM Scott Feldstein wrote: > Hi, > I'm wondering if someone could explain what is going on wit

Re: waiting for partition map exchange questions

Hi Andrei, have you had a chance to check out these logs? Thanks On Sun, Apr 14, 2019 at 17:18 scottmf wrote: > ignite.tgz > > (attached file) > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: Failed to map keys for cache (all partition nodes left the grid)

Yes that is correct. I see the same exceptions when the cache is REPLICATED with backups = 1 in my two node cluster. On Tue, Aug 21, 2018 at 12:37 PM akurbanov wrote: > Hi, > > Do you see the same exception for a REPLICATED cache? > And this exception also appears in two node setup with backups

Re: Ignite as Hibernate L2 Cache

It’s an AbstractMethodError caused since the library isn’t compiled with the 5.2 hibernate spec. On Tue, Oct 9, 2018 at 1:23 AM yarden wrote: > Thanks a lot for your answer. > Can you share what was the error you encountered on Hibernate 5.2? > > > > > > -- > Sent from: http://apache-ignite-user

Re: ignite stops expiring caches after a period of time

Thanks Ilya, I’ll upgrade and see if that works soon. Right now we’ve switched to only using partitioned caches to avoid this issue. If it’s something that isn’t fixed with 2.7 then I’ll create a bug and attach code to reproduce it. I’m really surprised that no one else is complaining about it. Th

Re: ignite stops expiring caches after a period of time

-- > Ilya Kasnacheev > > > вт, 25 дек. 2018 г. в 01:36, Scott Feldstein : > >> Thanks Ilya, I’ll upgrade and see if that works soon. Right now we’ve >> switched to only using partitioned caches to avoid this issue. If it’s >> something that isn’t fixed with 2.7 then

Re: ignite stops expiring caches after a period of time

r 2.7.0 I recommend you to stick with is, since if one would > be fixing 2.6 they will yield 2.7 anyway :) > > Regards, > > -- > Ilya Kasnacheev > > > ср, 26 дек. 2018 г. в 22:25, Scott Feldstein : > >> hi Ilya, >> Why wouldn't many people use

Re: ignite stops expiring caches after a period of time

prone to expiry. > > Regards, > > -- > Ilya Kasnacheev > > > сб, 29 дек. 2018 г. в 00:48, Scott Feldstein : > >> Hi Ilya, >> Thanks. I assume since I’m using persistence that expiry of the data is >> the only way to ensure that it is eventually purged. Is

Re: cache expiry issue

I ran into a expiry issue using 2.6.0 that was fixed in 2.7.0. What version are you on? On Tue, Feb 19, 2019 at 07:35 ignite_user2016 wrote: > any reply please ? > > we have 2 node cluster and we are only seeing expiry issues with few cache > entries which never gets expired unless we restart th

Re: tuning near cache performance

Hi Roman, 1. Cache Configuration NearCacheConfiguration nearCfg = new NearCacheConfiguration<>(); LruEvictionPolicy lruEvictionPolicy = new LruEvictionPolicy<>(5); nearCfg.setNearEvictionPolicy(lruEvictionPolicy); nearCfg.setNearStartSize(5); CacheCo

Re: tuning near cache performance

Thanks Roman, those are interesting suggestions I will try out. Thanks, Scott > On Feb 22, 2018, at 2:10 AM, Roman Guseinov wrote: > > Hi Scott, > > NearCache works fast, except the first get request (NearCache pulls data > from Cache). Avoid entity eviction by setting NearStartSize > size of

Re: eviction performance

Hi Stanislav, Thanks for info and the note on the terminology. So in my setup im partitioning by chunks of time. If I turn eagerttl to false how would the cleanup look? Would I periodically scan the partitions that i want to be expired? Are there any best practices to that end? Additionally ar

Re: eviction performance

Hi Stan, Thanks for the follow up. The part that I'm confused about here is when an expired entry isn't accessed it would simply linger on disk forever. In my prototype I want to be able to store one continuous hour of hot data to be queryable at all times. The volume of data currently sits at 2

Re: TLS warning "closing inbound before receiving peer's close_notify" during node startup

I ran across the same issue several months ago. I’m pretty certain it is harmless as no bugs have come up in our product since then. I didnt figure out a way to suppress the log or make it run “cleanly”. On Mon, May 19, 2025 at 07:01 Nandhini S wrote: > Hi Ignite Team, > > I'm currently using