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/06/05 22:49: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-deprioritized-major auto-unassigned  (was: auto-unassigned stale-major)
    Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> 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: Minor
>              Labels: auto-deprioritized-major, auto-unassigned
>
> 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)