What is the difference between expected and actual expiry time? On Wed, Jan 22, 2025 at 8:54 AM Charlin S <charli...@hotelhub.com> wrote:
> Hi Pavel, > This is happening only at production environment and data keynotfound > exception before triggering expiry policy (expiry policy time still longer) > > Following configuration part of xml bean file for communication. Is there > any issue in that please let me know. > <property name="communicationSpi"> > <bean > class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi"> > <property name="sharedMemoryPort" value="-1"/> > <property name="localPort" value="57605"/> > </bean> > </property> > > Thanks & Regards, > Charlin > > > > > On Tue, 21 Jan 2025 at 12:49, Pavel Tupitsyn <ptupit...@apache.org> wrote: > >> Hi, please provide more details. >> >> - Do you have a reproducer? >> - Do you mean that expiry policy triggers sooner than expected? >> >> On Tue, Jan 21, 2025 at 9:14 AM Charlin S <charli...@hotelhub.com> wrote: >> >>> Hi All, >>> I am getting below error while reading data by key but data presents >>> cache as expiry policy time not reached. >>> Cache mode: Partition >>> Number Server Node: 2 >>> Number client Node : 8 >>> The given key was not present in the cache: >>> Test|2711e8b9-7411-41bc-938c-d3d4ae9722ce@$@System.Collections.Generic.KeyNotFoundException: >>> The given key was not present in the cache: >>> Test|2711e8b9-7411-41bc-938c-d3d4ae9722ce >>> at >>> Apache.Ignite.Core.Impl.Cache.CacheImpl`2.<>c__DisplayClass49_0.<Get>b__1(IBinaryStream >>> stream, Int64 res) >>> at >>> Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutLong[TR](Int32 type, >>> Func`2 outAction, Func`3 inAction, Func`2 readErrorAction) >>> at Apache.Ignite.Core.Impl.Cache.CacheImpl`2.Get(TK key) >>> >>> Thanks & Regards, >>> Charlin >>> >>> >>> >>>
