[FLUME-1417] File Channel checkpoint can be bad leading to the channel being unable to start.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Assignee: Hari Shreedharan
• Reporter: Hari Shreedharan
• Created: 02/Aug/12 05:00
• Updated: 06/Aug/12 00:12
• Resolved: 06/Aug/12 00:12

Description

ERROR file.Log: Failed to initialize Log on [channel=file-channel]
java.lang.NullPointerException
at org.apache.flume.channel.file.Log.writeCheckpoint(Log.java:739)
at org.apache.flume.channel.file.Log.replay(Log.java:261)
at org.apache.flume.channel.file.FileChannel.start(FileChannel.java:228)
at org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:228)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
ERROR file.FileChannel: Failed to start the file channel [channel=file-channel]
java.lang.NullPointerException
at org.apache.flume.channel.file.Log.writeCheckpoint(Log.java:739)
at org.apache.flume.channel.file.Log.replay(Log.java:261)
at org.apache.flume.channel.file.FileChannel.start(FileChannel.java:228)
at org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:228)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

Issue Links

• is related to: FLUME-1426 FileChannel Replay could be faster
• is related to: FLUME-1428 File Channel should not consider a file as inactive until all takes are committed.
• links to: Reviewboard link