hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Macdonald (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2857) libhdfs: no way to set JVM args other than classpath
Date Fri, 22 Feb 2008 13:06:19 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Craig Macdonald updated HADOOP-2857:
------------------------------------

    Attachment: patch.libhdfs.jvm.args

Patch attached. Arguments are read from HADOOP_JVM_ARGS env var, space delimited. Applies
cleanly to trunk and 0.16 branch.

> libhdfs: no way to set JVM args other than classpath
> ----------------------------------------------------
>
>                 Key: HADOOP-2857
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2857
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: libhdfs
>    Affects Versions: 0.16.0
>            Reporter: Craig Macdonald
>            Priority: Minor
>         Attachments: patch.libhdfs.jvm.args
>
>   Original Estimate: 5h
>  Remaining Estimate: 5h
>
> I would like a way to set other Java system properties and/or other Java VM arguments
when using libhdfs - i.e. I want to be able to say start a profiler, attach a debugger, or
increase the memory available to the VM.
> At present, new JVMs are initialised from the getJNIEnv(void) method in src/c++/libhdfs/hdfsJniHelper.c
> This method initialises the -Djava.class.path JVM argument from the CLASSPATH environment
variable. I am proposing that another env variable should be added, the contents of which
is passed (almost) verbatim as JVM arguments.
> Eg, say the env var JVM_ARGS is used. The string from the env var would be tokenised
on "one or more spaces", and would be passed as additional JVM arguments, by make a larger
JavaVMOption options[] array, and setting vm_args.nOptions = 1+ number of passed arguments.
> Only flaw I can see with this is that none of the passed parameters can contain spaces.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message