You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2007/07/18 22:54:04 UTC

[jira] Created: (HADOOP-1634) EC2 launch-hadoop-cluster awk Problem

EC2 launch-hadoop-cluster awk Problem
-------------------------------------

                 Key: HADOOP-1634
                 URL: https://issues.apache.org/jira/browse/HADOOP-1634
             Project: Hadoop
          Issue Type: Bug
          Components: contrib/ec2
    Affects Versions: 0.13.0
         Environment: ec2-api-tools-1.2-11797
            Reporter: Stu Hood
            Priority: Minor


With Amazon 'ec2-api-tools-1.2-11797' and Hadoop 0.13.0 the output from ec2-describe-instances is being incorrectly AWK'd on the last few lines of the launch-hadoop-cluster script.

Specifically, on the
"""
MASTER_EC2_HOST=`ec2-describe-instances | grep INSTANCE | grep running | awk '{if ($7 == 0) print $4}'`
"""
line, it should be comparing column $8 rather than column $7.

When this command fails, the hostname of the master doesn't get set correctly and the IP lookup finds incorrect results. The last lines of output from the script look something like this:
"""
Appointing master
Master is . Please set up DNS so blah.gotdns.org points to D.ROOT-SERVERS.NET.
I.ROOT-SERVERS.NET.
F.ROOT-SERVERS.NET.
M.ROOT-SERVERS.NET.
J.ROOT-SERVERS.NET.
C.ROOT-SERVERS.NET.
H.ROOT-SERVERS.NET.
E.ROOT-SERVERS.NET.
A.ROOT-SERVERS.NET.
K.ROOT-SERVERS.NET.
G.ROOT-SERVERS.NET.
B.ROOT-SERVERS.NET.
L.ROOT-SERVERS.NET..
Press return to continue.
"""

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


[jira] Updated: (HADOOP-1634) EC2 launch-hadoop-cluster awk Problem

Posted by "Tom White (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White updated HADOOP-1634:
------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Included in HADOOP-1635.

> EC2 launch-hadoop-cluster awk Problem
> -------------------------------------
>
>                 Key: HADOOP-1634
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1634
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/ec2
>    Affects Versions: 0.13.0
>         Environment: ec2-api-tools-1.2-11797
>            Reporter: Stu Hood
>            Priority: Minor
>             Fix For: 0.13.1, 0.14.0, 0.15.0
>
>         Attachments: hadoop-1634.patch
>
>
> With Amazon 'ec2-api-tools-1.2-11797' and Hadoop 0.13.0 the output from ec2-describe-instances is being incorrectly AWK'd on the last few lines of the launch-hadoop-cluster script.
> Specifically, on the
> """
> MASTER_EC2_HOST=`ec2-describe-instances | grep INSTANCE | grep running | awk '{if ($7 == 0) print $4}'`
> """
> line, it should be comparing column $8 rather than column $7.
> When this command fails, the hostname of the master doesn't get set correctly and the IP lookup finds incorrect results. The last lines of output from the script look something like this:
> """
> Appointing master
> Master is . Please set up DNS so blah.gotdns.org points to D.ROOT-SERVERS.NET.
> I.ROOT-SERVERS.NET.
> F.ROOT-SERVERS.NET.
> M.ROOT-SERVERS.NET.
> J.ROOT-SERVERS.NET.
> C.ROOT-SERVERS.NET.
> H.ROOT-SERVERS.NET.
> E.ROOT-SERVERS.NET.
> A.ROOT-SERVERS.NET.
> K.ROOT-SERVERS.NET.
> G.ROOT-SERVERS.NET.
> B.ROOT-SERVERS.NET.
> L.ROOT-SERVERS.NET..
> Press return to continue.
> """

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


[jira] Updated: (HADOOP-1634) EC2 launch-hadoop-cluster awk Problem

Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stu Hood updated HADOOP-1634:
-----------------------------

    Fix Version/s: 0.15.0
                   0.14.0
                   0.13.1
           Status: Patch Available  (was: Open)

> EC2 launch-hadoop-cluster awk Problem
> -------------------------------------
>
>                 Key: HADOOP-1634
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1634
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/ec2
>    Affects Versions: 0.13.0
>         Environment: ec2-api-tools-1.2-11797
>            Reporter: Stu Hood
>            Priority: Minor
>             Fix For: 0.13.1, 0.14.0, 0.15.0
>
>         Attachments: hadoop-1634.patch
>
>
> With Amazon 'ec2-api-tools-1.2-11797' and Hadoop 0.13.0 the output from ec2-describe-instances is being incorrectly AWK'd on the last few lines of the launch-hadoop-cluster script.
> Specifically, on the
> """
> MASTER_EC2_HOST=`ec2-describe-instances | grep INSTANCE | grep running | awk '{if ($7 == 0) print $4}'`
> """
> line, it should be comparing column $8 rather than column $7.
> When this command fails, the hostname of the master doesn't get set correctly and the IP lookup finds incorrect results. The last lines of output from the script look something like this:
> """
> Appointing master
> Master is . Please set up DNS so blah.gotdns.org points to D.ROOT-SERVERS.NET.
> I.ROOT-SERVERS.NET.
> F.ROOT-SERVERS.NET.
> M.ROOT-SERVERS.NET.
> J.ROOT-SERVERS.NET.
> C.ROOT-SERVERS.NET.
> H.ROOT-SERVERS.NET.
> E.ROOT-SERVERS.NET.
> A.ROOT-SERVERS.NET.
> K.ROOT-SERVERS.NET.
> G.ROOT-SERVERS.NET.
> B.ROOT-SERVERS.NET.
> L.ROOT-SERVERS.NET..
> Press return to continue.
> """

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


[jira] Commented: (HADOOP-1634) EC2 launch-hadoop-cluster awk Problem

Posted by "Tom White (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514287 ] 

Tom White commented on HADOOP-1634:
-----------------------------------

I've been using ec2-api-tools-1.2-7546 (the previous release I think - the one you're using came out a couple of weeks ago). I'll see if your patch fixes the problem using both versions of the tools.

BTW which OS are you using?

> EC2 launch-hadoop-cluster awk Problem
> -------------------------------------
>
>                 Key: HADOOP-1634
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1634
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/ec2
>    Affects Versions: 0.13.0
>         Environment: ec2-api-tools-1.2-11797
>            Reporter: Stu Hood
>            Priority: Minor
>             Fix For: 0.13.1, 0.14.0, 0.15.0
>
>         Attachments: hadoop-1634.patch
>
>
> With Amazon 'ec2-api-tools-1.2-11797' and Hadoop 0.13.0 the output from ec2-describe-instances is being incorrectly AWK'd on the last few lines of the launch-hadoop-cluster script.
> Specifically, on the
> """
> MASTER_EC2_HOST=`ec2-describe-instances | grep INSTANCE | grep running | awk '{if ($7 == 0) print $4}'`
> """
> line, it should be comparing column $8 rather than column $7.
> When this command fails, the hostname of the master doesn't get set correctly and the IP lookup finds incorrect results. The last lines of output from the script look something like this:
> """
> Appointing master
> Master is . Please set up DNS so blah.gotdns.org points to D.ROOT-SERVERS.NET.
> I.ROOT-SERVERS.NET.
> F.ROOT-SERVERS.NET.
> M.ROOT-SERVERS.NET.
> J.ROOT-SERVERS.NET.
> C.ROOT-SERVERS.NET.
> H.ROOT-SERVERS.NET.
> E.ROOT-SERVERS.NET.
> A.ROOT-SERVERS.NET.
> K.ROOT-SERVERS.NET.
> G.ROOT-SERVERS.NET.
> B.ROOT-SERVERS.NET.
> L.ROOT-SERVERS.NET..
> Press return to continue.
> """

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


[jira] Commented: (HADOOP-1634) EC2 launch-hadoop-cluster awk Problem

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514087 ] 

Hadoop QA commented on HADOOP-1634:
-----------------------------------

+1

http://issues.apache.org/jira/secure/attachment/12362162/hadoop-1634.patch applied and successfully tested against trunk revision r557790.

Test results:   http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/438/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/438/console

> EC2 launch-hadoop-cluster awk Problem
> -------------------------------------
>
>                 Key: HADOOP-1634
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1634
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/ec2
>    Affects Versions: 0.13.0
>         Environment: ec2-api-tools-1.2-11797
>            Reporter: Stu Hood
>            Priority: Minor
>             Fix For: 0.13.1, 0.14.0, 0.15.0
>
>         Attachments: hadoop-1634.patch
>
>
> With Amazon 'ec2-api-tools-1.2-11797' and Hadoop 0.13.0 the output from ec2-describe-instances is being incorrectly AWK'd on the last few lines of the launch-hadoop-cluster script.
> Specifically, on the
> """
> MASTER_EC2_HOST=`ec2-describe-instances | grep INSTANCE | grep running | awk '{if ($7 == 0) print $4}'`
> """
> line, it should be comparing column $8 rather than column $7.
> When this command fails, the hostname of the master doesn't get set correctly and the IP lookup finds incorrect results. The last lines of output from the script look something like this:
> """
> Appointing master
> Master is . Please set up DNS so blah.gotdns.org points to D.ROOT-SERVERS.NET.
> I.ROOT-SERVERS.NET.
> F.ROOT-SERVERS.NET.
> M.ROOT-SERVERS.NET.
> J.ROOT-SERVERS.NET.
> C.ROOT-SERVERS.NET.
> H.ROOT-SERVERS.NET.
> E.ROOT-SERVERS.NET.
> A.ROOT-SERVERS.NET.
> K.ROOT-SERVERS.NET.
> G.ROOT-SERVERS.NET.
> B.ROOT-SERVERS.NET.
> L.ROOT-SERVERS.NET..
> Press return to continue.
> """

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


[jira] Commented: (HADOOP-1634) EC2 launch-hadoop-cluster awk Problem

Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514300 ] 

Stu Hood commented on HADOOP-1634:
----------------------------------

Great, thanks!

I'm using Ubuntu 7.04.

> EC2 launch-hadoop-cluster awk Problem
> -------------------------------------
>
>                 Key: HADOOP-1634
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1634
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/ec2
>    Affects Versions: 0.13.0
>         Environment: ec2-api-tools-1.2-11797
>            Reporter: Stu Hood
>            Priority: Minor
>             Fix For: 0.13.1, 0.14.0, 0.15.0
>
>         Attachments: hadoop-1634.patch
>
>
> With Amazon 'ec2-api-tools-1.2-11797' and Hadoop 0.13.0 the output from ec2-describe-instances is being incorrectly AWK'd on the last few lines of the launch-hadoop-cluster script.
> Specifically, on the
> """
> MASTER_EC2_HOST=`ec2-describe-instances | grep INSTANCE | grep running | awk '{if ($7 == 0) print $4}'`
> """
> line, it should be comparing column $8 rather than column $7.
> When this command fails, the hostname of the master doesn't get set correctly and the IP lookup finds incorrect results. The last lines of output from the script look something like this:
> """
> Appointing master
> Master is . Please set up DNS so blah.gotdns.org points to D.ROOT-SERVERS.NET.
> I.ROOT-SERVERS.NET.
> F.ROOT-SERVERS.NET.
> M.ROOT-SERVERS.NET.
> J.ROOT-SERVERS.NET.
> C.ROOT-SERVERS.NET.
> H.ROOT-SERVERS.NET.
> E.ROOT-SERVERS.NET.
> A.ROOT-SERVERS.NET.
> K.ROOT-SERVERS.NET.
> G.ROOT-SERVERS.NET.
> B.ROOT-SERVERS.NET.
> L.ROOT-SERVERS.NET..
> Press return to continue.
> """

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


[jira] Updated: (HADOOP-1634) EC2 launch-hadoop-cluster awk Problem

Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stu Hood updated HADOOP-1634:
-----------------------------

    Attachment: hadoop-1634.patch

A patch to fix this issue. The awk line checks the 7th and 8th column (for backwards compatibility).

> EC2 launch-hadoop-cluster awk Problem
> -------------------------------------
>
>                 Key: HADOOP-1634
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1634
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/ec2
>    Affects Versions: 0.13.0
>         Environment: ec2-api-tools-1.2-11797
>            Reporter: Stu Hood
>            Priority: Minor
>             Fix For: 0.13.1, 0.14.0, 0.15.0
>
>         Attachments: hadoop-1634.patch
>
>
> With Amazon 'ec2-api-tools-1.2-11797' and Hadoop 0.13.0 the output from ec2-describe-instances is being incorrectly AWK'd on the last few lines of the launch-hadoop-cluster script.
> Specifically, on the
> """
> MASTER_EC2_HOST=`ec2-describe-instances | grep INSTANCE | grep running | awk '{if ($7 == 0) print $4}'`
> """
> line, it should be comparing column $8 rather than column $7.
> When this command fails, the hostname of the master doesn't get set correctly and the IP lookup finds incorrect results. The last lines of output from the script look something like this:
> """
> Appointing master
> Master is . Please set up DNS so blah.gotdns.org points to D.ROOT-SERVERS.NET.
> I.ROOT-SERVERS.NET.
> F.ROOT-SERVERS.NET.
> M.ROOT-SERVERS.NET.
> J.ROOT-SERVERS.NET.
> C.ROOT-SERVERS.NET.
> H.ROOT-SERVERS.NET.
> E.ROOT-SERVERS.NET.
> A.ROOT-SERVERS.NET.
> K.ROOT-SERVERS.NET.
> G.ROOT-SERVERS.NET.
> B.ROOT-SERVERS.NET.
> L.ROOT-SERVERS.NET..
> Press return to continue.
> """

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