You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/05/28 23:10:02 UTC
[jira] [Updated] (FLINK-21161) Investigate Datadog OOM on timeout
[ https://issues.apache.org/jira/browse/FLINK-21161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-21161:
-----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> Investigate Datadog OOM on timeout
> ----------------------------------
>
> Key: FLINK-21161
> URL: https://issues.apache.org/jira/browse/FLINK-21161
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Affects Versions: 1.11.3
> Reporter: Chesnay Schepler
> Priority: Major
> Labels: auto-unassigned, stale-major
>
> The datadog reporter sends reports to datagod via asynchronous calls made with okhttp.
> okhttp buffers requests if they cannot be submitted; if any connection issues it might be possible for enough data to be buffered to cause an OOM.
> By default the number of concurrent requests is set to 64. We should try to reproduce the problem, and check whether setting this to a lower value would solve it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)