[
https://issues.apache.org/jira/browse/FLINK-7467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321637#comment-17321637
]
Flink Jira Bot commented on FLINK-7467:
---------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> a slow client on the BlobServer may block writing operations
> ------------------------------------------------------------
>
> Key: FLINK-7467
> URL: https://issues.apache.org/jira/browse/FLINK-7467
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination, Runtime / Network
> Affects Versions: 1.3.0, 1.3.1, 1.3.2, 1.4.0
> Reporter: Nico Kruber
> Priority: Minor
> Labels: stale-minor
>
> Since FLINK-6020, a locking mechanism was introduced to isolate reading from
> writing operations. This, however, will cause a slow client to slow down all
> write operations and may not be desirable at this level.
> The current usage patterns, however, first write all BLOBs (during job
> submission) and then read the needed ones when the TaskManagers need them.
> The slowdown may thus materialize only when multiple jobs are submitted
> concurrently and these phases overlap.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
