[FLUME-1004] The SEQ source doesn't seem to stop on a reconfig that should disable it

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.1.0
• Component/s: Sinks+Sources

Environment

RHEL 6.1 64-bit

• Assignee: Unassigned
• Reporter: Will McQueen
• Created: 27/Feb/12 23:21
• Updated: 09/Jul/12 22:21
• Resolved: 26/Mar/12 16:43

Description

Steps:

1) Run the flume node with a config file that has the sink disabled:

a1.sources = r1
a1.channels = c1
#a1.sinks = k1
a1.sources.r1.type = SEQ
a1.sources.r1.channels = c1
a1.channels.c1.type = MEMORY
#a1.sinks.k1.type = logger
#a1.sinks.k1.channel = c1

If you add a print statement to ChannelProcessor.processEvent(), you'll see that the source is sending events to the channel.

2) Modify the config so that the source is disabled, and a new sink is enabled:

#a1.sources = r1
a1.channels = c1
a1.sinks = k1
#a1.sources.r1.type = SEQ
#a1.sources.r1.channels = c1
a1.channels.c1.type = MEMORY
a1.sinks.k1.type = logger
a1.sinks.k1.channel = c1

//exp: The sink should only receive events that were in the channel at the time that the source was enabled (effectively draining the source)
//act: The sink continuously receives events from the same source that is disabled according to the config, but is enabled according to the continuous output seen.

Issue Links

• duplicates: FLUME-1036 Reconfiguration of AVRO or NETCAT source causes port bind exception