[
https://issues.apache.org/jira/browse/IGNITE-18494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-18494:
-------------------------------------
Description:
The problem:
On affinity nodes everything works.
On client nodes and non-affinity nodes (i.e. filtered by some node filter) --
near configuration ignored when starting cache on demand from descriptor.
-------
_The documentation
(https://ignite.apache.org/docs/latest/configuring-caches/near-cache#configuring-near-cache)
says:
"Once configured in this way, the near cache is created on any node that
requests data from the underlying cache, including both server nodes and client
nodes."
We expect the Near cache to be created for the cache proxy obtained with
getCache, and getOrCreateNearCache does not need to be called because the
NearConfiguration was initialized when the cache was created.
Reproducers show that this is not so.
Java reproducer [^Issue.java] without platformcache. _
was:
The documentation
(https://ignite.apache.org/docs/latest/configuring-caches/near-cache#configuring-near-cache)
says:
"Once configured in this way, the near cache is created on any node that
requests data from the underlying cache, including both server nodes and client
nodes."
We expect the Near cache to be created for the cache proxy obtained with
getCache, and getOrCreateNearCache does not need to be called because the
NearConfiguration was initialized when the cache was created.
Reproducers show that this is not so.
Java reproducer [^Issue.java] without platformcache.
> Near cache not created with getCache
> ------------------------------------
>
> Key: IGNITE-18494
> URL: https://issues.apache.org/jira/browse/IGNITE-18494
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.14
> Reporter: Luchnikov Alexander
> Assignee: Ivan Daschinsky
> Priority: Major
> Labels: ise
> Attachments: Issue.java, NearCacheTest.cs, NearCacheTest.java
>
>
> The problem:
> On affinity nodes everything works.
> On client nodes and non-affinity nodes (i.e. filtered by some node filter) --
> near configuration ignored when starting cache on demand from descriptor.
> -------
> _The documentation
> (https://ignite.apache.org/docs/latest/configuring-caches/near-cache#configuring-near-cache)
> says:
> "Once configured in this way, the near cache is created on any node that
> requests data from the underlying cache, including both server nodes and
> client nodes."
> We expect the Near cache to be created for the cache proxy obtained with
> getCache, and getOrCreateNearCache does not need to be called because the
> NearConfiguration was initialized when the cache was created.
> Reproducers show that this is not so.
> Java reproducer [^Issue.java] without platformcache. _
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
