[jira] [Commented] (FLUME-2285) FileChannel Erroneously Reports "Usable Space Exhausted"

["yinghua_zh (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLUME-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562566#comment-14562566 ] 

yinghua_zh commented on FLUME-2285:
-----------------------------------

I also encountered the same problem,the log as follow:
Caused by: java.io.IOException: Usable space exhaused, only 191344640 bytes remaining, required 524288000 bytes
	at org.apache.flume.channel.file.Log.writeCheckpoint(Log.java:989)
	at org.apache.flume.channel.file.Log.replay(Log.java:474)

The disk space is not enough,But I clean it and the drive that the checkpoint and data directories reside on has 500GB available (unused) on it, I write the test code to get the usable space on the checkpoint directory diive,the result is 500GB,but the flume agent log show the checkpoint space is not enough for at least one day,I restart the flume agent process,The problem disappears. Do the api( File getUsableSpace）cached the result?

> FileChannel Erroneously Reports "Usable Space Exhausted"
> --------------------------------------------------------
>
>                 Key: FLUME-2285
>                 URL: https://issues.apache.org/jira/browse/FLUME-2285
>             Project: Flume
>          Issue Type: Bug
>    Affects Versions: v1.4.0
>            Reporter: Michael Knapp
>
> I am using Flume 1.4.0, my configuration has a file channel with all of the default settings.  It's checkpoint directory and data directory are both empty and have the correct permissions on them.  When I run flume I get this exception:
> java.lang.IllegalStateException: Channel closed [...]. Due to java.io.IOException: Usable space exhaused, only 99401728 bytes remaining, required 524288000 bytes
> The drive that the checkpoint and data directories reside on has 86GB available (unused) on it.  The flume application is calculating the wrong number for usable space.
> If I am wrong here, then the exception message should at least be more clear, describing how to fix the issue, and where exactly it is getting that number (99401728 bytes).  It would also be nice if the numbers were reported in human readable form (MB, GB, etc.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)