To be Reviewed By: 22 April 2022

Authors: Mario Ivanac

Status: Draft | Discussion | Active | Dropped | Superseded

Superseded by: N/A

Related: N/A

Problem

In case we are using persistent regions, and we are using asynchronous disk writes, currently in geode there is no way to monitor possible problems with disk writes.

What has been observed, if we have slower disk writes, or halted writing,  events would be queued in asyncQueue, without any indication to user.

If we have consistent problem then queue can be fill up OOM exception occurs.

Anti-Goals

/

Solution

Solution would be to extend existing thread monitoring to monitor async writer thread, and report warning level alert in case thread is stack more then 15 seconds.

New solution: https://github.com/apache/geode/pull/7667

Old draft proposal of implementation: https://github.com/apache/geode/pull/7574

Changes and Additions to Public Interfaces

NA

Performance Impact

NA

Backwards Compatibility and Upgrade Path

No impacts.

Prior Art

NA

FAQ

Answers to questions you’ve commonly been asked after requesting comments for this proposal.

Errata

What are minor adjustments that had to be made to the proposal since it was approved?