Skip to content

Conversation

@jhkimqd
Copy link

@jhkimqd jhkimqd commented Apr 16, 2024

Background

There has been some observations of the executor failing due to OOM in production environments. This was caused due to the executor configuration which allowed using more memory (as db caches pile up) than available. There is no warning about this, and this can be extremely hard to debug.

Suggestion

This PR aims to output a warning log if the executor is configured to use more than 50% of the available memory as cache, so developers will have a better idea on the consequences of their configs.

@cla-bot
Copy link

cla-bot bot commented Apr 16, 2024

We require contributors/corporates @jhkimqd to read our Contributor License Agreement, please check the Individual CLA document/Corporate CLA document

@jhkimqd jhkimqd force-pushed the feature/executor-memory-warning branch from bcef7b7 to 3b32b46 Compare April 16, 2024 01:48
@cla-bot
Copy link

cla-bot bot commented Apr 16, 2024

We require contributors/corporates @jhkimqd to read our Contributor License Agreement, please check the Individual CLA document/Corporate CLA document

@jhkimqd jhkimqd requested a review from fractasy April 16, 2024 14:27
@jhkimqd jhkimqd force-pushed the feature/executor-memory-warning branch from 3b32b46 to 7c5da01 Compare April 16, 2024 14:35
@cla-bot
Copy link

cla-bot bot commented Apr 16, 2024

We require contributors/corporates @jhkimqd to read our Contributor License Agreement, please check the Individual CLA document/Corporate CLA document

@jhkimqd jhkimqd force-pushed the feature/executor-memory-warning branch from 7c5da01 to 7831492 Compare April 16, 2024 14:38
@cla-bot
Copy link

cla-bot bot commented Apr 16, 2024

We require contributors/corporates @jhkimqd to read our Contributor License Agreement, please check the Individual CLA document/Corporate CLA document

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant