[
https://issues.apache.org/jira/browse/IGNITE-12334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964807#comment-16964807
]
Stanislav Lukyanov commented on IGNITE-12334:
---------------------------------------------
The right answer to this is probably not to use getAll in such cases.
If you want to load data in batches then you should either split the keys
yourself or use Query APIs, like ScanQuery or SqlQuery.
I suggest to close this as Won't Fix for now if we don't find a particular use
cases to implement this.
> Throttle getAll operations on the grid
> --------------------------------------
>
> Key: IGNITE-12334
> URL: https://issues.apache.org/jira/browse/IGNITE-12334
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.7.5
> Reporter: ABHISHEK SHUBH GUPTA
> Priority: Major
>
> Per [this
> thread|http://apache-ignite-users.70518.x6.nabble.com/Throttling-getAll-tt29956.html],
> in a situation where a large number of keys are requested using getAll
> and/or the value objects are large, there is a worry about GC
> issues/humongous objects/OOM on the grid. It would, therefore, be beneficial
> to the stability of the product if there was throttling available on the
> ignition nodes when clients do large getAll operations.
> The throttling could perhaps be based on the number of keys passed on to
> getAll. If it exceeds threshold it could reject the request or optionally,
> auto-create multiple smaller batches.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
