[ https://issues.apache.org/jira/browse/HADOOP-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626723#comment-13626723 ]
Chris Nauroth commented on HADOOP-9455: --------------------------------------- Hi, Sangjin. I've been reviewing this and HIVE-3936. I haven't been able to repro this problem running just the hadoop script, but I do see how an interaction between the hive script and the hadoop script could cause this problem if running hive with both the --debug option and a HADOOP_CLIENT_OPTS environment variable containing the JDWP options: # hive with --debug option calls get_debug_params in ext/debug.sh. # get_debug_params exports HIVE_MAIN_CLIENT_DEBUG_OPTS with value set to JDWP options. # hive appends HIVE_MAIN_CLIENT_DEBUG_OPTS to HADOOP_CLIENT_OPTS. If your HADOOP_CLIENT_OPTS already contained the JDWP options, then they would be duplicated after this step executes. # hive service scripts like ext/hiveserver.sh and ext/jar.sh run hadoop. # hadoop launches JVM, and we get the failure you described. This problem would be triggered only by running hive with both --debug and HADOOP_CLIENT_OPTS containing the JDWP options. Can you check to see if this is how you were running it? > HADOOP_CLIENT_OPTS is appended twice, causing JVM failures > ---------------------------------------------------------- > > Key: HADOOP-9455 > URL: https://issues.apache.org/jira/browse/HADOOP-9455 > Project: Hadoop Common > Issue Type: Bug > Components: bin > Affects Versions: 2.0.3-alpha > Reporter: Sangjin Lee > Priority: Minor > > If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the > HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures > for cases like adding debug flags. > For example, > {noformat} > HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y' > hadoop jar anything > ERROR: Cannot load this JVM TI agent twice, check your java command line for > duplicate jdwp options. > Error occurred during initialization of VM > agent library failed to init: jdwp > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira