You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Aliaksandr Kazlou <al...@gmail.com> on 2021/10/14 07:48:51 UTC

Verification of near cache works

Hi, guys. What is the best way to verify near caching works? So far Visor
shows 0 hit on it.

What if SQL is used on top of the caches where near-cache is configured,
will SQL takes into account this, or SQL query always has to run on remote,
and never on local/near cache data?

Overall we have the feeling so far that near-cache either doesn't work, or
we don't understand fully how it should work.

Due to this we are planning to keep local cache/data exclusively for the
node where the application is running using Caffeine, but really would like
to use Apache Ignite, but so far it seems near-cache doesn't do what it
promises.

Any thoughts?

Re: Verification of near cache works

Posted by Pavel Tupitsyn <pt...@apache.org>.
Hi, you can try IgniteCache#localPeek(CachePeekMode.NEAR),
localSize(CachePeekMode.NEAR), and localEntries(CachePeekMode.NEAR) to
check the data in the near cache.

On Thu, Oct 14, 2021 at 10:49 AM Aliaksandr Kazlou <
aliaksandr.kazlou@gmail.com> wrote:

> Hi, guys. What is the best way to verify near caching works? So far Visor
> shows 0 hit on it.
>
> What if SQL is used on top of the caches where near-cache is configured,
> will SQL takes into account this, or SQL query always has to run on remote,
> and never on local/near cache data?
>
> Overall we have the feeling so far that near-cache either doesn't work, or
> we don't understand fully how it should work.
>
> Due to this we are planning to keep local cache/data exclusively for the
> node where the application is running using Caffeine, but really would like
> to use Apache Ignite, but so far it seems near-cache doesn't do what it
> promises.
>
> Any thoughts?
>