[
https://issues.apache.org/jira/browse/FLUME-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342400#comment-14342400
]
Johny Rufus commented on FLUME-2527:
------------------------------------
[~mungeol], 'File has been modified since being read' when I'm using
spooldir',
is thrown, when after placing a file in the spooling directory, the file gets
modified. This is against the spooling directory assumption, that a file after
being placed in the spooling directory will not be modified. So having multiple
-Xmx should not have anything to do with this error.
And flume-env.sh, is the right place to override any default options. [Also any
-Xmx mentioned in command line takes precedence over the default one, as thats
how most JVM implementations seem to handle it, even though we should not rely
on this behavior]
> Unstable java option
> --------------------
>
> Key: FLUME-2527
> URL: https://issues.apache.org/jira/browse/FLUME-2527
> Project: Flume
> Issue Type: Bug
> Reporter: mungeol heo
> Assignee: Johny Rufus
>
> Command 'apache-flume-1.5.0.1-bin/bin/flume-ng -help' gives a bunch of
> information includes '-Xproperty=value sets a Java -X option'.
> If I start a flume agent by using 'bin/flume-ng agent -n tier1 -f
> conf/flume-conf.properties -Xmx1g', Then there will be a process start with
> '/usr/bin/java -Xmx20m -Xmx1g ...'.
> This causes using spooldir source become unstable.
> I mean it gives an error which is 'File has been modified since being read'
> when I'm using spooldir.
> This problem is solved by setting java option at flume-env.sh instead of
> using -X option at command line.
> So, it should give an error when using -X option with command.
> Or, the problem which is '-Xmx20m -Xmx1g' should be solved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
