Possible memory leak on Consumer side when ingesting large deltas.

[tomeks86]

When using hollow (v3.3.0) we have observed an excessive rise in memory request on the consumer side when large deltas were produced.

This situation was contrasting to consumer application starting and ingesting these deltas.

Have you come across such an issue and was it potentially fixed in a newer version of hollow?

[ghost]

@tomeks86 we haven't had reports internally about this. We only have a few use-cases where teams produce large deltas. Let me reach out to those teams and see if they're on >= v3.3.0 and whether they've had issues.

[ghost]

Following up. We don't see evidence of a memory leak (JVM live data size is stable across hours and days) in a consumer that ingests large deltas. This is running Hollow v4.7.12.

@tomeks86, are you still observing a leak in your system? If so, can you upgrade/canary the latest Hollow release to see if the leak remains?

[tomeks86]

@toolbear, thank you for the suggestion. Upgrading to v4.7.12 has not lead to improvement of this situation.

Online consumer memory monitoring:

Consumer starting and consuming deltas already prepared: