You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2011/03/14 21:49:29 UTC
[jira] Created: (WHIRR-262) Services should not have to do reverse
DNS lookups
Services should not have to do reverse DNS lookups
--------------------------------------------------
Key: WHIRR-262
URL: https://issues.apache.org/jira/browse/WHIRR-262
Project: Whirr
Issue Type: Improvement
Reporter: Tom White
Assignee: Tom White
Currently Hadoop and HBase use DNSUtil to do reverse DNS lookups to get the correct public hostname, but the other services don't which means they may not run correctly in some environments (such as when launched from within EC2, see WHIRR-128 for background). The framework should do these lookups on the service's behalf.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WHIRR-262) Services should not have to do reverse
DNS lookups
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-262:
----------------------------
Attachment: WHIRR-262.patch
Here's a patch which constructs the InetAddress instances with the correctly resolved hostname. We already do a reverse lookup for each host to write the instances file, so this shouldn't make things slower.
On the other hand, we might consider making this lazier, by adding methods like getPublicIP(), getPublicHostName(), getPrivateIP(), getPrivateHostName() to Instance so that reverse lookups are performed only for the instances that need it. We could replace the public hostname in the instances file with an IP address.
> Services should not have to do reverse DNS lookups
> --------------------------------------------------
>
> Key: WHIRR-262
> URL: https://issues.apache.org/jira/browse/WHIRR-262
> Project: Whirr
> Issue Type: Improvement
> Reporter: Tom White
> Assignee: Tom White
> Attachments: WHIRR-262.patch
>
>
> Currently Hadoop and HBase use DNSUtil to do reverse DNS lookups to get the correct public hostname, but the other services don't which means they may not run correctly in some environments (such as when launched from within EC2, see WHIRR-128 for background). The framework should do these lookups on the service's behalf.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-262) Services should not have to do
reverse DNS lookups
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016355#comment-13016355 ]
Andrei Savu commented on WHIRR-262:
-----------------------------------
+1 integration tests for HBase are passing on AWS
> Services should not have to do reverse DNS lookups
> --------------------------------------------------
>
> Key: WHIRR-262
> URL: https://issues.apache.org/jira/browse/WHIRR-262
> Project: Whirr
> Issue Type: Improvement
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.5.0
>
> Attachments: WHIRR-262.patch, WHIRR-262.patch
>
>
> Currently Hadoop and HBase use DNSUtil to do reverse DNS lookups to get the correct public hostname, but the other services don't which means they may not run correctly in some environments (such as when launched from within EC2, see WHIRR-128 for background). The framework should do these lookups on the service's behalf.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-262) Services should not have to do reverse
DNS lookups
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-262:
----------------------------
Attachment: WHIRR-262.patch
This patch takes the second approach, minimizing reverse DNS lookups.
> Services should not have to do reverse DNS lookups
> --------------------------------------------------
>
> Key: WHIRR-262
> URL: https://issues.apache.org/jira/browse/WHIRR-262
> Project: Whirr
> Issue Type: Improvement
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.5.0
>
> Attachments: WHIRR-262.patch, WHIRR-262.patch
>
>
> Currently Hadoop and HBase use DNSUtil to do reverse DNS lookups to get the correct public hostname, but the other services don't which means they may not run correctly in some environments (such as when launched from within EC2, see WHIRR-128 for background). The framework should do these lookups on the service's behalf.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-262) Services should not have to do reverse
DNS lookups
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-262:
----------------------------
Status: Patch Available (was: Open)
> Services should not have to do reverse DNS lookups
> --------------------------------------------------
>
> Key: WHIRR-262
> URL: https://issues.apache.org/jira/browse/WHIRR-262
> Project: Whirr
> Issue Type: Improvement
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.5.0
>
> Attachments: WHIRR-262.patch, WHIRR-262.patch
>
>
> Currently Hadoop and HBase use DNSUtil to do reverse DNS lookups to get the correct public hostname, but the other services don't which means they may not run correctly in some environments (such as when launched from within EC2, see WHIRR-128 for background). The framework should do these lookups on the service's behalf.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-262) Services should not have to do reverse
DNS lookups
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-262:
----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I've just committed this. Thanks for the review Andrei.
> Services should not have to do reverse DNS lookups
> --------------------------------------------------
>
> Key: WHIRR-262
> URL: https://issues.apache.org/jira/browse/WHIRR-262
> Project: Whirr
> Issue Type: Improvement
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.5.0
>
> Attachments: WHIRR-262.patch, WHIRR-262.patch
>
>
> Currently Hadoop and HBase use DNSUtil to do reverse DNS lookups to get the correct public hostname, but the other services don't which means they may not run correctly in some environments (such as when launched from within EC2, see WHIRR-128 for background). The framework should do these lookups on the service's behalf.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-262) Services should not have to do reverse
DNS lookups
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-262:
----------------------------
Fix Version/s: 0.5.0
> Services should not have to do reverse DNS lookups
> --------------------------------------------------
>
> Key: WHIRR-262
> URL: https://issues.apache.org/jira/browse/WHIRR-262
> Project: Whirr
> Issue Type: Improvement
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.5.0
>
> Attachments: WHIRR-262.patch
>
>
> Currently Hadoop and HBase use DNSUtil to do reverse DNS lookups to get the correct public hostname, but the other services don't which means they may not run correctly in some environments (such as when launched from within EC2, see WHIRR-128 for background). The framework should do these lookups on the service's behalf.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira