[
https://issues.apache.org/jira/browse/FLINK-15966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler closed FLINK-15966.
------------------------------------
Fix Version/s: (was: 1.10.1)
Resolution: Fixed
master: 2746e6a4f3f84e05425484ad63ea096c5536c77f
> Capture the call stack of RPC ask() calls.
> ------------------------------------------
>
> Key: FLINK-15966
> URL: https://issues.apache.org/jira/browse/FLINK-15966
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, when an RPC ask() call fails, we get a rather unhelpful exception
> with a stack trace from akka's internal scheduler.
> Instead, we should capture the call stack during the invocation and use it to
> give a helpful error message when the RPC call failed. This is especially
> helpful in cases where the future (and future handlers) are passed for later
> asynchronous result handling (which is the common case in most components (JM
> / TM / RM).
> The options should have a flag to turn it off, because when having a lot of
> concurrent ask calls (hundreds of thousands, during large deploy phases), it
> may be possible that the captured call.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
