Ignite 2.16 cache update taking longer time

[Charlin S <ch...@hotelhub.com>]

Hi All,

I am using Ignite 2.16 two nodes partition mode cache. Ignite client
applications that fail to read cache for some time after initiating the
cache update. I am able to fetch data in the second attempt or third
attempt some time (not always).

My real scenario: Cache was not available for more than 1 minute. My
clients are getting impacted due to this issue.

Is there any configuration to read cache data while updating by another
thread/jvm.Please let me know.

Thanks & Regards,
Charlin

Re: Ignite 2.16 cache update taking longer time

[Jeremy McMillan <jt...@gridgain.com>]

You may have the opposite need compared to the problem expressed in this
post:

https://stackoverflow.com/questions/67598175/ignite-read-stale-data-from-backup-node

If you want to serve up stale data from backup partitions while concurrent
updates are happening on primary partitions, use backup partitions>=1, and
also set readFromBackup.

readFromBackup == true

On Fri, Feb 7, 2025 at 8:16 AM Charlin S <ch...@hotelhub.com> wrote:

> Hi All,
>
> I am using Ignite 2.16 two nodes partition mode cache. Ignite client
> applications that fail to read cache for some time after initiating the
> cache update. I am able to fetch data in the second attempt or third
> attempt some time (not always).
>
> My real scenario: Cache was not available for more than 1 minute. My
> clients are getting impacted due to this issue.
>
> Is there any configuration to read cache data while updating by another
> thread/jvm.Please let me know.
>
> Thanks & Regards,
> Charlin
>
>
>
>
>