[
https://issues.apache.org/jira/browse/FLUME-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858882#comment-13858882
]
Brock Noland commented on FLUME-2285:
-------------------------------------
bq. 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.
Flume is using the standard java apis to get this information. Are you sure
that flume is actually storing it's logs on the disk with free space?
bq. If I am wrong here, then the exception message should at least be more
clear,
I don't disagree, but it is *much* better than if we didn't have this check :)
without the check users got one of half dozen runtime errors.
bq. 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.)
That would be cool! The line of code requiring a change is here:
https://github.com/apache/flume/blob/trunk/flume-ng-channels/flume-file-channel/src/main/java/org/apache/flume/channel/file/Log.java#L610
> 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.1.5#6160)
