[infinispan-issues] [JBoss JIRA] (ISPN-8861) DIST Iteration shouldn't go remote when a shared cache store is present

[William Burns (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-8861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536484#comment-13536484 ] 

William Burns commented on ISPN-8861:
-------------------------------------

Unfortunately we would still have to go to the remote database to make sure there are not extra entries. In this case we still have an essentially unbounded query which will return everything - so we might as well utilize what it returned. And actually by going remote we would then have N requests to the database to go over everything (until we have segment based stores) - instead of just 1. This would put even more strain on the underlying remote store implementation.

> DIST Iteration shouldn't go remote when a shared cache store is present
> -----------------------------------------------------------------------
>
>                 Key: ISPN-8861
>                 URL: https://issues.jboss.org/browse/ISPN-8861
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Loaders and Stores
>            Reporter: William Burns
>            Assignee: William Burns
>             Fix For: 9.3.0.Final
>
>
> When a user runs a distributed iteration operation with a shared cache store, this shouldn't go remote as the local node would have all the data available to it. This is similar to the optimization when we don't go remote if the current node is an owner for all required segments.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)