You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Roman Khachatryan (Jira)" <ji...@apache.org> on 2020/07/06 09:06:00 UTC
[jira] [Commented] (FLINK-18163) Should be volatile:
network.api.writer.RecordWriter.flusherException
[ https://issues.apache.org/jira/browse/FLINK-18163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151896#comment-17151896 ]
Roman Khachatryan commented on FLINK-18163:
-------------------------------------------
[~NicoK] ,
I see you were involved in a discussion of RecordWriter.flusherException with [~pnowojski] .
What do you think about having a volatile field (in addition to non-volatile) and check it periodically (say once per 100 emits)?
I filed a PR showing this approach: [https://github.com/apache/flink/pull/12827 |https://github.com/apache/flink/pull/12827]
> Should be volatile: network.api.writer.RecordWriter.flusherException
> ---------------------------------------------------------------------
>
> Key: FLINK-18163
> URL: https://issues.apache.org/jira/browse/FLINK-18163
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
> Affects Versions: 1.11.0
> Reporter: Roman Khachatryan
> Assignee: Roman Khachatryan
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)