You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2010/11/02 17:22:24 UTC
[jira] Created: (WHIRR-123) Cassandra integration tests hang if
whirr's scripts bucket is missing
Cassandra integration tests hang if whirr's scripts bucket is missing
---------------------------------------------------------------------
Key: WHIRR-123
URL: https://issues.apache.org/jira/browse/WHIRR-123
Project: Whirr
Issue Type: Bug
Components: core, service/cassandra
Affects Versions: 0.2.0
Reporter: Patrick Hunt
Priority: Critical
Fix For: 0.3.0
I don't know if this is specific to cassandra or just a general issue.
I ran the integration tests as part of building the 0.2.0 release candidate. The tests failed while verifying cassandra. Looking on the ec2 host I see the following in the stderr (nothing in stdout). Note - I had not created the 0.2.0-incubating bucket on s3, so while this test would never pass, it seems unusual that the test hangs forever rather than tear down the test and report an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
--------- stderr ---------------
--2010-11-02 05:51:45--
http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
Resolving whirr.s3.amazonaws.com... 72.21.211.174
Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2010-11-02 05:51:45 ERROR 404: Not Found.
runurl: wget failed: 8
--2010-11-02 05:51:45--
http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
Resolving whirr.s3.amazonaws.com... 72.21.211.174
Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2010-11-02 05:51:45 ERROR 404: Not Found.
runurl: wget failed: 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-123) Cassandra integration tests hang if
whirr's scripts bucket is missing
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-123:
----------------------------
Assignee: Tom White
Status: Patch Available (was: Open)
> Cassandra integration tests hang if whirr's scripts bucket is missing
> ---------------------------------------------------------------------
>
> Key: WHIRR-123
> URL: https://issues.apache.org/jira/browse/WHIRR-123
> Project: Whirr
> Issue Type: Bug
> Components: core, service/cassandra
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Assignee: Tom White
> Priority: Critical
> Fix For: 0.3.0
>
> Attachments: WHIRR-123.patch
>
>
> I don't know if this is specific to cassandra or just a general issue.
> I ran the integration tests as part of building the 0.2.0 release candidate. The tests failed while verifying cassandra. Looking on the ec2 host I see the following in the stderr (nothing in stdout). Note - I had not created the 0.2.0-incubating bucket on s3, so while this test would never pass, it seems unusual that the test hangs forever rather than tear down the test and report an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
> --------- stderr ---------------
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-123) Cassandra integration tests hang if
whirr's scripts bucket is missing
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-123:
----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I've just committed this.
> Cassandra integration tests hang if whirr's scripts bucket is missing
> ---------------------------------------------------------------------
>
> Key: WHIRR-123
> URL: https://issues.apache.org/jira/browse/WHIRR-123
> Project: Whirr
> Issue Type: Bug
> Components: core, service/cassandra
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Assignee: Tom White
> Priority: Critical
> Fix For: 0.3.0
>
> Attachments: WHIRR-123.patch
>
>
> I don't know if this is specific to cassandra or just a general issue.
> I ran the integration tests as part of building the 0.2.0 release candidate. The tests failed while verifying cassandra. Looking on the ec2 host I see the following in the stderr (nothing in stdout). Note - I had not created the 0.2.0-incubating bucket on s3, so while this test would never pass, it seems unusual that the test hangs forever rather than tear down the test and report an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
> --------- stderr ---------------
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WHIRR-123) Cassandra integration tests hang if
whirr's scripts bucket is missing
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971761#action_12971761 ]
Tom White commented on WHIRR-123:
---------------------------------
This passes integration tests for Cassandra, Hadoop, and ZooKeeper for me, so I'll commit it soon unless there are further comments.
> Cassandra integration tests hang if whirr's scripts bucket is missing
> ---------------------------------------------------------------------
>
> Key: WHIRR-123
> URL: https://issues.apache.org/jira/browse/WHIRR-123
> Project: Whirr
> Issue Type: Bug
> Components: core, service/cassandra
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Assignee: Tom White
> Priority: Critical
> Fix For: 0.3.0
>
> Attachments: WHIRR-123.patch, WHIRR-123.patch
>
>
> I don't know if this is specific to cassandra or just a general issue.
> I ran the integration tests as part of building the 0.2.0 release candidate. The tests failed while verifying cassandra. Looking on the ec2 host I see the following in the stderr (nothing in stdout). Note - I had not created the 0.2.0-incubating bucket on s3, so while this test would never pass, it seems unusual that the test hangs forever rather than tear down the test and report an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
> --------- stderr ---------------
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WHIRR-123) Cassandra integration tests hang if
whirr's scripts bucket is missing
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White resolved WHIRR-123.
-----------------------------
Resolution: Fixed
I've just committed this.
> Cassandra integration tests hang if whirr's scripts bucket is missing
> ---------------------------------------------------------------------
>
> Key: WHIRR-123
> URL: https://issues.apache.org/jira/browse/WHIRR-123
> Project: Whirr
> Issue Type: Bug
> Components: core, service/cassandra
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Assignee: Tom White
> Priority: Critical
> Fix For: 0.3.0
>
> Attachments: WHIRR-123.patch, WHIRR-123.patch
>
>
> I don't know if this is specific to cassandra or just a general issue.
> I ran the integration tests as part of building the 0.2.0 release candidate. The tests failed while verifying cassandra. Looking on the ec2 host I see the following in the stderr (nothing in stdout). Note - I had not created the 0.2.0-incubating bucket on s3, so while this test would never pass, it seems unusual that the test hangs forever rather than tear down the test and report an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
> --------- stderr ---------------
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-123) Cassandra integration tests hang if
whirr's scripts bucket is missing
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated WHIRR-123:
-------------------------------
ps. the test doesn't cleanup properly in this case (ctrl-c after the hang) so be sure to check your ec2 instances and terminate any zombies assoc with the test.
> Cassandra integration tests hang if whirr's scripts bucket is missing
> ---------------------------------------------------------------------
>
> Key: WHIRR-123
> URL: https://issues.apache.org/jira/browse/WHIRR-123
> Project: Whirr
> Issue Type: Bug
> Components: core, service/cassandra
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Priority: Critical
> Fix For: 0.3.0
>
>
> I don't know if this is specific to cassandra or just a general issue.
> I ran the integration tests as part of building the 0.2.0 release candidate. The tests failed while verifying cassandra. Looking on the ec2 host I see the following in the stderr (nothing in stdout). Note - I had not created the 0.2.0-incubating bucket on s3, so while this test would never pass, it seems unusual that the test hangs forever rather than tear down the test and report an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
> --------- stderr ---------------
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-123) Cassandra integration tests hang if
whirr's scripts bucket is missing
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-123:
----------------------------
Attachment: WHIRR-123.patch
The problem with the previous patch was that arguments to the runurl script were being treated as a part of the URL, which caused a problem when the URL was being checked. Here's a new patch which fixes that.
> Cassandra integration tests hang if whirr's scripts bucket is missing
> ---------------------------------------------------------------------
>
> Key: WHIRR-123
> URL: https://issues.apache.org/jira/browse/WHIRR-123
> Project: Whirr
> Issue Type: Bug
> Components: core, service/cassandra
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Assignee: Tom White
> Priority: Critical
> Fix For: 0.3.0
>
> Attachments: WHIRR-123.patch, WHIRR-123.patch
>
>
> I don't know if this is specific to cassandra or just a general issue.
> I ran the integration tests as part of building the 0.2.0 release candidate. The tests failed while verifying cassandra. Looking on the ec2 host I see the following in the stderr (nothing in stdout). Note - I had not created the 0.2.0-incubating bucket on s3, so while this test would never pass, it seems unusual that the test hangs forever rather than tear down the test and report an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
> --------- stderr ---------------
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (WHIRR-123) Cassandra integration tests hang if
whirr's scripts bucket is missing
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White reopened WHIRR-123:
-----------------------------
This is causing test failures for me. I've reverted it while I investigate.
> Cassandra integration tests hang if whirr's scripts bucket is missing
> ---------------------------------------------------------------------
>
> Key: WHIRR-123
> URL: https://issues.apache.org/jira/browse/WHIRR-123
> Project: Whirr
> Issue Type: Bug
> Components: core, service/cassandra
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Assignee: Tom White
> Priority: Critical
> Fix For: 0.3.0
>
> Attachments: WHIRR-123.patch
>
>
> I don't know if this is specific to cassandra or just a general issue.
> I ran the integration tests as part of building the 0.2.0 release candidate. The tests failed while verifying cassandra. Looking on the ec2 host I see the following in the stderr (nothing in stdout). Note - I had not created the 0.2.0-incubating bucket on s3, so while this test would never pass, it seems unusual that the test hangs forever rather than tear down the test and report an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
> --------- stderr ---------------
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-123) Cassandra integration tests hang if
whirr's scripts bucket is missing
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-123:
----------------------------
Attachment: WHIRR-123.patch
Here's a patch that checks if the runurl exists (using an HTTP HEAD request).
> Cassandra integration tests hang if whirr's scripts bucket is missing
> ---------------------------------------------------------------------
>
> Key: WHIRR-123
> URL: https://issues.apache.org/jira/browse/WHIRR-123
> Project: Whirr
> Issue Type: Bug
> Components: core, service/cassandra
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Priority: Critical
> Fix For: 0.3.0
>
> Attachments: WHIRR-123.patch
>
>
> I don't know if this is specific to cassandra or just a general issue.
> I ran the integration tests as part of building the 0.2.0 release candidate. The tests failed while verifying cassandra. Looking on the ec2 host I see the following in the stderr (nothing in stdout). Note - I had not created the 0.2.0-incubating bucket on s3, so while this test would never pass, it seems unusual that the test hangs forever rather than tear down the test and report an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
> --------- stderr ---------------
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WHIRR-123) Cassandra integration tests hang if
whirr's scripts bucket is missing
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969831#action_12969831 ]
Adrian Cole commented on WHIRR-123:
-----------------------------------
patch looks fine and integration tests pass.
Thanks for putting this together.
> Cassandra integration tests hang if whirr's scripts bucket is missing
> ---------------------------------------------------------------------
>
> Key: WHIRR-123
> URL: https://issues.apache.org/jira/browse/WHIRR-123
> Project: Whirr
> Issue Type: Bug
> Components: core, service/cassandra
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Assignee: Tom White
> Priority: Critical
> Fix For: 0.3.0
>
> Attachments: WHIRR-123.patch
>
>
> I don't know if this is specific to cassandra or just a general issue.
> I ran the integration tests as part of building the 0.2.0 release candidate. The tests failed while verifying cassandra. Looking on the ec2 host I see the following in the stderr (nothing in stdout). Note - I had not created the 0.2.0-incubating bucket on s3, so while this test would never pass, it seems unusual that the test hangs forever rather than tear down the test and report an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
> --------- stderr ---------------
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.