yangwei created FLUME-2689:
------------------------------
Summary: 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: v1.5.1
Environment: configuring syslog sending logs to remote flume agent
Reporter: yangwei
Fix For: v1.5.2
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.3.4#6332)
