Ignite already has this functionality, it is implemented in CacheStoreBalancingWrapper. All concurrent loads with the batch size up to loadAllThreshold are tracked and only one request is issued to the underlying store. The reason for this differentiation is that multi-key loads require additional overhead and it is more beneficial not to track these loads starting from some batch size large enough.
However, it turns out that there is no way to configure this threshold. I created a ticket for it: https://issues.apache.org/jira/browse/IGNITE-1681 Folks, can you review the suggested way of configuring this parameter? (described in the ticket). Once the community agrees on the ticket, it will be fairly easy to fix and I think it is a good point to start contributing to Ignite :) 2015-10-14 11:19 GMT+03:00 endian675 <[email protected]>: > I created a fork on Github last night and am in the process of getting my > environment set up. It is not quite building yet, but hopefully it will be > soon. > > Did you manage to find the JIRA ticket? > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/CacheStore-servicing-multiple-requests-for-same-key-tp1589p1608.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
