hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-1520) Classpath assembly doesn't work if ozone is symlinked
Date Tue, 14 May 2019 21:44:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839816#comment-16839816

Eric Yang commented on HDDS-1520:

This issue may have caused by how long a single argument can be in Linux which is defined
by MAX_ARG_STRLEN. The default is PAGE_SIZE*32, which translates to 128KB. The above classpath
is 15KB, which works. If the prefix directory has deeper depths, the length of classpath string
value actually out grown the default limit faster. When this happens, we get class not found
exceptions because some jar files are no longer referenced in CLASSPATH. The solution is to
make sure that we can put jar files in a directory, and use "lib/*" [class path wildcards|https://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html]
provided short hand to reference all jar files.

> Classpath assembly doesn't work if ozone is symlinked
> -----------------------------------------------------
>                 Key: HDDS-1520
>                 URL: https://issues.apache.org/jira/browse/HDDS-1520
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Eric Yang
>            Assignee: Elek, Marton
>            Priority: Major
> [~eyang] reported that the ozone can't be started if the ozone directory is symlinked
due to the classpath assembly. It should work even if the directory is symlinked.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message