[ 
https://issues.apache.org/jira/browse/FLINK-15924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-15924:
-----------------------------------
    Labels: auto-deprioritized-major stale-minor  (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 issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Detect and log blocking main thread operations
> ----------------------------------------------
>
>                 Key: FLINK-15924
>                 URL: https://issues.apache.org/jira/browse/FLINK-15924
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.10.0
>            Reporter: Till Rohrmann
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> When using the {{RpcEndpoint}} it is important that all operations which run 
> on the main thread are never blocking. We have seen in the past that it is 
> quite hard to always catch blocking operations in reviews and sometimes these 
> changes caused instabilities in Flink. Once this happens it is not trivial to 
> find the culprit which is responsible for the blocking operation.
> One way to make debugging easier is to add a monitor which detects and logs 
> if a {{RpcEndpoint}} operation takes longer than {{n}} seconds for example. 
> Depending on the overhead of this monitor one could even think about enabling 
> it only via a special configuration (e.g. debug mode).
> A proper class to introduce this monitor could be the {{AkkaRpcActor}} which 
> is responsible for executing main thread operations. Whenever we schedule an 
> operation, we could start a timeout which if triggered and the operation has 
> not been completed will log a warning.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to