[
https://issues.apache.org/jira/browse/FLINK-22235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22235:
-----------------------------------
Labels: auto-deprioritized-major stale-assigned (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> Document stability concerns of flamegraphs for heavier jobs
> -----------------------------------------------------------
>
> Key: FLINK-22235
> URL: https://issues.apache.org/jira/browse/FLINK-22235
> Project: Flink
> Issue Type: Improvement
> Components: Documentation, Runtime / Web Frontend
> Reporter: Chesnay Schepler
> Assignee: Alexander Fedulov
> Priority: Minor
> Labels: auto-deprioritized-major, stale-assigned
> Fix For: 1.18.0
>
>
> The FlameGraph feature added in FLINK-13550 has some known scalability
> issues, because it issues 1 RPC call per subtask. This may put a lot of
> pressure on the RPC system, and as such it should be used with caution for
> heavier jobs until we improved this a bit.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
