Hi there Aashish,
Could you possibly provide a little more information, as to the getAll()
operation.
Just for interest sake:
* How many keys are part of the getAll() request
* How large are your value objects?
* Is this request made from a client?
* Is there any memory pressure on the client? Are there any gc's
taking place at that time?
* Have you configured a CacheLoader?
* What about eviction and eviction thresholds.
The reason I'm asking is that when you initiate a getAll() the server(s)
might be able to respond in a reasonable time frame, BUT, if there
keys/values are really large, you might be seeing that the servers spend
some time serializing the data. When that data is returned to the
client, the client needs to provision all that space for the
deserialized data. Given that Geode operations are not yet streaming
enabled, means that you hit "all-or-nothing" semantics. Which means, to
retrieve the result from the getAll, requires all the data to have been
delivered and deserialized before it is made available as a response object.
Even with non-single hop enabled, I do not see any real reason as to the
30s response times. So there must be other factors here...
Maybe to help us, try and help you, some more information about
operation, key/values sizes, amount of keys, gc state, logs could be
more helpful.
--Udo
On 10/25/18 11:36, aashish choudhary wrote:
Hi,
We have an issue wherein our getAll operations are taking too long to
respond (in some cases as high as 30 seconds) which is not acceptable
from IMDG like Geode. Also this seems to be an existing issue as per
the link given below and being fixed in 1.8 version.
https://issues.apache.org/jira/browse/GEODE-5649
We are on version 1.2 and wanted to confirm if this issue exits in
that version too. If yes is there any workaround for that?. Not sure
if 1.8 is available for download.
With best regards,
Ashish
