I use Ignite as a session store and need to allow write access only for authentication services.

On 11/04/2018 00:45, Denis Magda wrote:
The filter excludes the nodes from the list of those which can store data. That's why those nodes would never receive any requests.

Considering your follow-up questions, I guess you are looking for multi-tenancy capabilities. Do you want to prevent some of your applications to update data stored in the cluster?


On Tue, Apr 10, 2018 at 11:49 AM, Alew <ale...@gmail.com <mailto:ale...@gmail.com>> wrote:

    Hi, Denis

    Thank you for your answer.

    What effect will filter have? Does it mean that read-only node
    doesn't have own data copy? Is it like partitioned cache? If so,
    why is it read-only?

    On 10/04/2018 02:37, Denis Magda wrote:

    Yes, you can tap into NodeFilter interface applying it for your
    CacheConfiguration in a way similar to ServiceConfiguration as
    shown here:


    On Mon, Apr 9, 2018 at 4:23 PM, Alew <ale...@gmail.com
    <mailto:ale...@gmail.com>> wrote:

         I have a relicated cache. Is there a way to forbid insert
        and update data in the cache for some nodes in a cluster?


Reply via email to