[FLUME-229] Flume collector not recovering properly if the hdfs namenode goes down.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.9.0, 0.9.1
• Fix Version/s: 0.9.1u1, 0.9.2
• Component/s: Node
• Assignee: Jonathan Hsieh
• Reporter: Jonathan Hsieh
• Created: 17/Sep/10 02:16
• Updated: 13/Dec/10 14:37
• Resolved: 28/Sep/10 22:40

Description

Via Eric van Dewoestine
"""
I'm just getting started with flume and attempting to test the fault
tolerance of the system. We are initially logging to flat files, but
would like to move to logging straight into hdfs. What I'm attempting
to test is the case where:

1. a flume collector receives a message to be logged to hdfs
2. flume cannot connect to hdfs, long enough to exhaust the 10
attempts by the hadoop ipc.Client resulting in a
ConnectionException being logged.
3. bring hdfs up

After bringing hdfs up I'd like to see flume auto connect at some
point so that messages can then be written there, but it appears that
once that ConnectionException is raised, the only way to get flume to
connect to hdfs is a restart.

"""

Issue Links

• relates to: FLUME-249 Use Hadoop's org.apache.hadoop.hdfs.MiniDFSCluster to test namenode failures.