> Put and tryget are in two different methods called one after another
That would be a very apparent bug in Ignite, and I don't see anything like
that in JIRA or release notes.
Perhaps something else is involved here, another thread or node changing
the value?
Please prepare a small project that we can run to reproduce the issue.
On Wed, Jun 5, 2024 at 9:18 PM Charlin S <charli...@hotelhub.com> wrote:
> Hi,
> Put and tryget are in two different methods called one after another one
> with some time gap based on work flow process
>
> We felt Ignite 2.10 okay for us.
>
> Thanks and Regards
> Charlin
>
> On Wed, 5 Jun, 2024, 8:23 pm Pavel Tupitsyn, <ptupit...@apache.org> wrote:
>
>> - Do you run Put and TryGet on the same node?
>> - Do you have a reproducer?
>> - Ignite 2.10 was released 3 years ago, have you tried a newer version?
>>
>> On Wed, Jun 5, 2024 at 3:49 PM Charlin S <charli...@hotelhub.com> wrote:
>>
>>> Hi All,
>>> I am unable to fetch data from cache by reading by
>>> key.intermittently (very rarely).
>>>
>>> Ignite version: 2.10
>>> Cache mode: Partition
>>> Client : C# with Ignite thick client
>>>
>>> Scenario:
>>> My C# application received a request for cache data insertion @ 09:09:35
>>> and successfully insertion initiated at application side.
>>> Thereafter @ 09:10:21 C# application received a request to read cache
>>> data for the same key and Ignite TryGet could not fetch data.
>>> Note: We are able to get cache data by the same key after some time.
>>>
>>> Cache creation code
>>> var IgniteCache= IIgnite.GetCache<string, cacheModel>("cacheModel")
>>> .WithExpiryPolicy(new ExpiryPolicy(
>>> TimeSpan.FromMinutes(60),
>>> TimeSpan.FromMinutes(60),
>>> TimeSpan.FromMinutes(60)
>>> ));
>>>
>>> Cache data insertion code
>>> IgniteCache.Put(cacheKey, (T)data);
>>>
>>> Cache data reading code
>>> IgniteCache.TryGet(Key, out var value);
>>>
>>> Thanks & Regards,
>>> Charlin
>>>
>>>
>>>
>>>
