You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Lior Zeno (JIRA)" <ji...@apache.org> on 2016/07/23 08:37:20 UTC

[jira] [Resolved] (FLUME-710) ExecNIOSource blocks indefinitely if an exception is encountered

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

Lior Zeno resolved FLUME-710.
-----------------------------
    Resolution: Invalid

ExecNIOSource was a part of Flume-OG and does not exist anymore.

> ExecNIOSource blocks indefinitely if an exception is encountered
> ----------------------------------------------------------------
>
>                 Key: FLUME-710
>                 URL: https://issues.apache.org/jira/browse/FLUME-710
>             Project: Flume
>          Issue Type: Bug
>          Components: Sinks+Sources
>    Affects Versions: v0.9.5
>            Reporter: E. Sammer
>            Priority: Blocker
>
> In the ExecNIOSource, any exception that occurs in one of the two reader threads causes the source to stop transferring data[1] but continue to run. This, in turn, leaves the source in a state that requires human intervention (i.e. the configuration needs to be refreshed or the node restarted).
> [1] This is because the reader thread for one of stderr or stdout will exit but the next() call which is reading from a blocking queue won't know a thread died.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)