[
https://issues.apache.org/jira/browse/FLUME-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482466#comment-14482466
]
Hudson commented on FLUME-1934:
-------------------------------
UNSTABLE: Integrated in flume-trunk #726 (See
[https://builds.apache.org/job/flume-trunk/726/])
FLUME-1934. Spooling Directory Source dies on encountering zero-byte files.
(hshreedharan:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=4d2a34e931554baa1c1b255d95540a46354a521f)
*
flume-ng-core/src/test/java/org/apache/flume/source/TestSpoolDirectorySource.java
*
flume-ng-core/src/main/java/org/apache/flume/client/avro/ReliableSpoolingFileEventReader.java
> Spoolingdir source exception when reading multiple zero size files
> ---------------------------------------------------------------------
>
> Key: FLUME-1934
> URL: https://issues.apache.org/jira/browse/FLUME-1934
> Project: Flume
> Issue Type: Bug
> Affects Versions: v1.3.1
> Environment: windows 7, flume 1.3.1, spooling dir source.
> Reporter: andy zhou
> Assignee: Grant Henke
> Fix For: v1.6.0
>
> Attachments: FLUME-1934.patch
>
>
> move more than one files to the spool dir, and each file size is 0, then
> flume agent will throw IllegalStateException forever, and never work
> again,its' main cause is commited flag will not set to true.
> logs:
> 08 三月 2013 08:00:14,406 ERROR [pool-5-thread-1]
> (org.apache.flume.source.SpoolDirectorySource$SpoolDirectoryRunnable.run:148)
> - Uncaught exception in Runnable
> java.lang.IllegalStateException: File should not roll when commit is
> outstanding.
> at
> org.apache.flume.client.avro.SpoolingFileLineReader.readLines(SpoolingFileLineReader.java:164)
> at
> org.apache.flume.source.SpoolDirectorySource$SpoolDirectoryRunnable.run(SpoolDirectorySource.java:135)
> 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)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
