[
https://issues.apache.org/jira/browse/FLINK-10332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nico Kruber resolved FLINK-10332.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.5.5
1.6.2
1.7.0
Fixed via:
- release-1.5: 607c5675a108114254c747ca3565c6f03a98434e
- release-1.6: 5b2b0f71cb33fa749b9332ffd386f39c9acf6a0e
- master: c15ba1cd5a97ced3bb6411d588c3fb68df8a2869
> Move data available notification in PipelinedSubpartition out of the
> synchronized block
> ---------------------------------------------------------------------------------------
>
> Key: FLINK-10332
> URL: https://issues.apache.org/jira/browse/FLINK-10332
> Project: Flink
> Issue Type: Sub-task
> Components: Network
> Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.6.0, 1.7.0
> Reporter: Nico Kruber
> Assignee: Nico Kruber
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0, 1.6.2, 1.5.5
>
>
> Currently, calls to {{PipelinedSubpartition#notifyDataAvailable();}} are
> unnecessarily executed inside a {{synchronized (buffers)}} block which may
> lead to lock contention.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
