[jira] [Commented] (HDFS-6704) Fix the command to launch JournalNode in HDFS-HA document

2014-07-23 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071820#comment-14071820
 ] 

Hudson commented on HDFS-6704:
--

SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1840 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1840/])
HDFS-6704. Fix the command to launch JournalNode in HDFS-HA document. 
Contributed by Akira AJISAKA. (jing9: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1612613)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/apt/HDFSHighAvailabilityWithQJM.apt.vm


> Fix the command to launch JournalNode in HDFS-HA document
> -
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Fix For: 2.6.0
>
> Attachments: HDFS-6704.2.patch, HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must 
> start the JournalNode daemons on the set of machines where they will run. 
> This can be done by running the command "hdfs-daemon.sh journalnode" and 
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-6704) Fix the command to launch JournalNode in HDFS-HA document

2014-07-23 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071732#comment-14071732
 ] 

Hudson commented on HDFS-6704:
--

FAILURE: Integrated in Hadoop-Hdfs-trunk #1813 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1813/])
HDFS-6704. Fix the command to launch JournalNode in HDFS-HA document. 
Contributed by Akira AJISAKA. (jing9: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1612613)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/apt/HDFSHighAvailabilityWithQJM.apt.vm


> Fix the command to launch JournalNode in HDFS-HA document
> -
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Fix For: 2.6.0
>
> Attachments: HDFS-6704.2.patch, HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must 
> start the JournalNode daemons on the set of machines where they will run. 
> This can be done by running the command "hdfs-daemon.sh journalnode" and 
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-6704) Fix the command to launch JournalNode in HDFS-HA document

2014-07-23 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071601#comment-14071601
 ] 

Hudson commented on HDFS-6704:
--

FAILURE: Integrated in Hadoop-Yarn-trunk #621 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/621/])
HDFS-6704. Fix the command to launch JournalNode in HDFS-HA document. 
Contributed by Akira AJISAKA. (jing9: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1612613)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/apt/HDFSHighAvailabilityWithQJM.apt.vm


> Fix the command to launch JournalNode in HDFS-HA document
> -
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Fix For: 2.6.0
>
> Attachments: HDFS-6704.2.patch, HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must 
> start the JournalNode daemons on the set of machines where they will run. 
> This can be done by running the command "hdfs-daemon.sh journalnode" and 
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-6704) Fix the command to launch JournalNode in HDFS-HA document

2014-07-22 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070538#comment-14070538
 ] 

Hudson commented on HDFS-6704:
--

FAILURE: Integrated in Hadoop-trunk-Commit #5938 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/5938/])
HDFS-6704. Fix the command to launch JournalNode in HDFS-HA document. 
Contributed by Akira AJISAKA. (jing9: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1612613)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/apt/HDFSHighAvailabilityWithQJM.apt.vm


> Fix the command to launch JournalNode in HDFS-HA document
> -
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Fix For: 2.6.0
>
> Attachments: HDFS-6704.2.patch, HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must 
> start the JournalNode daemons on the set of machines where they will run. 
> This can be done by running the command "hdfs-daemon.sh journalnode" and 
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-6704) Fix the command to launch JournalNode in HDFS-HA document

2014-07-22 Thread Jing Zhao (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070527#comment-14070527
 ] 

Jing Zhao commented on HDFS-6704:
-

+1. I will commit it shortly.

> Fix the command to launch JournalNode in HDFS-HA document
> -
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Attachments: HDFS-6704.2.patch, HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must 
> start the JournalNode daemons on the set of machines where they will run. 
> This can be done by running the command "hdfs-daemon.sh journalnode" and 
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-6704) Fix the command to launch JournalNode in HDFS-HA document

2014-07-18 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067389#comment-14067389
 ] 

Hadoop QA commented on HDFS-6704:
-

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12656690/HDFS-6704.2.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+0 tests included{color}.  The patch appears to be a 
documentation patch that doesn't require tests.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-hdfs-project/hadoop-hdfs.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/7398//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7398//console

This message is automatically generated.

> Fix the command to launch JournalNode in HDFS-HA document
> -
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Attachments: HDFS-6704.2.patch, HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must 
> start the JournalNode daemons on the set of machines where they will run. 
> This can be done by running the command "hdfs-daemon.sh journalnode" and 
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-6704) Fix the command to launch JournalNode in HDFS-HA document

2014-07-18 Thread Akira AJISAKA (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067336#comment-14067336
 ] 

Akira AJISAKA commented on HDFS-6704:
-

[~jingzhao], you are right. I'll update the patch shortly.

> Fix the command to launch JournalNode in HDFS-HA document
> -
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Attachments: HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must 
> start the JournalNode daemons on the set of machines where they will run. 
> This can be done by running the command "hdfs-daemon.sh journalnode" and 
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-6704) Fix the command to launch JournalNode in HDFS-HA document

2014-07-18 Thread Jing Zhao (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066644#comment-14066644
 ] 

Jing Zhao commented on HDFS-6704:
-

We should also add "start" into the command? 

> Fix the command to launch JournalNode in HDFS-HA document
> -
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Attachments: HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must 
> start the JournalNode daemons on the set of machines where they will run. 
> This can be done by running the command "hdfs-daemon.sh journalnode" and 
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-6704) Fix the command to launch JournalNode in HDFS-HA document

2014-07-18 Thread Stephen Chu (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066509#comment-14066509
 ] 

Stephen Chu commented on HDFS-6704:
---

LGTM, +1 (non-binding). 

> Fix the command to launch JournalNode in HDFS-HA document
> -
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Attachments: HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must 
> start the JournalNode daemons on the set of machines where they will run. 
> This can be done by running the command "hdfs-daemon.sh journalnode" and 
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-6704) Fix the command to launch JournalNode in HDFS-HA document

2014-07-18 Thread Akira AJISAKA (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066163#comment-14066163
 ] 

Akira AJISAKA commented on HDFS-6704:
-

The patch looks unrelated to the failed test. It was reported at HDFS-6694.

> Fix the command to launch JournalNode in HDFS-HA document
> -
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Attachments: HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must 
> start the JournalNode daemons on the set of machines where they will run. 
> This can be done by running the command "hdfs-daemon.sh journalnode" and 
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-6704) Fix the command to launch JournalNode in HDFS-HA document

2014-07-18 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066144#comment-14066144
 ] 

Hadoop QA commented on HDFS-6704:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12656444/HDFS-6704.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+0 tests included{color}.  The patch appears to be a 
documentation patch that doesn't require tests.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-hdfs-project/hadoop-hdfs:

  
org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/7380//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7380//console

This message is automatically generated.

> Fix the command to launch JournalNode in HDFS-HA document
> -
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Attachments: HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must 
> start the JournalNode daemons on the set of machines where they will run. 
> This can be done by running the command "hdfs-daemon.sh journalnode" and 
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)