[jira] [Commented] (HIVE-3936) Remote debug failed with hadoop 0.23X, hadoop 2.X

2014-01-05 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862754#comment-13862754
 ] 

Hive QA commented on HIVE-3936:
---



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12621546/HIVE-3936.1.patch

{color:green}SUCCESS:{color} +1 4875 tests passed

Test results: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/808/testReport
Console output: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/808/console

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12621546

 Remote debug failed with hadoop 0.23X, hadoop 2.X
 -

 Key: HIVE-3936
 URL: https://issues.apache.org/jira/browse/HIVE-3936
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.8.0, 0.8.1, 0.9.0
Reporter: Xie Long
Assignee: Swarnim Kulkarni
Priority: Minor
 Attachments: HIVE-3936.1.patch


 In $HIVE_HOME/bin/hive and $HADOOP_HOME/bin/hadoop, $HADOOP_CLIENT_OPTS is  
 appended to $HADOOP_OPTS, which leads to the problem.
 hive --debug
 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



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (HIVE-3936) Remote debug failed with hadoop 0.23X, hadoop 2.X

2013-08-16 Thread Mikhail Antonov (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742770#comment-13742770
 ] 

Mikhail Antonov commented on HIVE-3936:
---

http://ben-tech.blogspot.com/2012/11/cdh410-hive-debug-option-bug.html

the issue may be temporarily fixed on target machine by commenting out that 
line in the /usr/lib/hive/bin/hive. So looking at HADOOP-9455, will this issue 
be fixed automatically by the fix in the Hadoop, or that requires a fix at Hive 
side?

 Remote debug failed with hadoop 0.23X, hadoop 2.X
 -

 Key: HIVE-3936
 URL: https://issues.apache.org/jira/browse/HIVE-3936
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.8.0, 0.8.1, 0.9.0
Reporter: Xie Long
Priority: Minor

 In $HIVE_HOME/bin/hive and $HADOOP_HOME/bin/hadoop, $HADOOP_CLIENT_OPTS is  
 appended to $HADOOP_OPTS, which leads to the problem.
 hive --debug
 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

--
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


[jira] [Commented] (HIVE-3936) Remote debug failed with hadoop 0.23X, hadoop 2.X

2013-04-03 Thread Sangjin Lee (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621550#comment-13621550
 ] 

Sangjin Lee commented on HIVE-3936:
---

Shouldn't there also be a JIRA issue opened against Hadoop?

 Remote debug failed with hadoop 0.23X, hadoop 2.X
 -

 Key: HIVE-3936
 URL: https://issues.apache.org/jira/browse/HIVE-3936
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.8.0, 0.8.1, 0.9.0
Reporter: Xie Long
Priority: Minor

 In $HIVE_HOME/bin/hive and $HADOOP_HOME/bin/hadoop, $HADOOP_CLIENT_OPTS is  
 appended to $HADOOP_OPTS, which leads to the problem.
 hive --debug
 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

--
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