You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ferenc Szabo (JIRA)" <ji...@apache.org> on 2017/09/12 13:24:01 UTC
[jira] [Updated] (FLUME-2689) reloading conf file leads
syslogTcpSource not receives any event
[ https://issues.apache.org/jira/browse/FLUME-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ferenc Szabo updated FLUME-2689:
--------------------------------
Fix Version/s: (was: 1.8.0)
1.8.1
> reloading conf file leads syslogTcpSource not receives any event
> ----------------------------------------------------------------
>
> Key: FLUME-2689
> URL: https://issues.apache.org/jira/browse/FLUME-2689
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: 1.5.1
> Environment: configuring syslog sending logs to remote flume agent
> Reporter: yangwei
> Assignee: yangwei
> Fix For: 1.8.1
>
> Attachments: flume-2689-1.patch, flume-2689-3.patch, flume-2689-trunk.patch
>
>
> Reloading conf file will stop old syslog source and start new syslog source. Stopping syslog tcp source only closes the NioServerSocketChannel, resulting in the client sends data through the old channel. In that case, the new source never receives data. The tcpdump shows the events have received but the new source doesn't and ss shows the client connection stays same with old one.
> The right way to stop syslog source is close both the NioSocketChannel and NioServerSocketChannel, and shutdown the executor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)