[FLUME-2689] reloading conf file leads syslogTcpSource not receives any event

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.5.1
• Fix Version/s: 1.8.1
• Component/s: Sinks+Sources

Environment

configuring syslog sending logs to remote flume agent

• Assignee: Wei Yang
• Reporter: Wei Yang
• Created: 28/Apr/15 11:13
• Updated: 12/Sep/17 13:24

Description

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.

Issue Links

• links to: Review request for FLUME-2689 on review board