[ https://issues.apache.org/jira/browse/KAFKA-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002932#comment-15002932 ]
ASF GitHub Bot commented on KAFKA-2814: --------------------------------------- GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/517 KAFKA-2814: Make Kafka Connect system test REST requests use hostname that is compatible with running under AWS. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka kafka-2814-connect-rest-on-aws Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/517.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #517 ---- commit 1bd84f31526395ea9e9b879e42672c96e42ea6f4 Author: Ewen Cheslack-Postava <m...@ewencp.org> Date: 2015-11-12T00:48:29Z KAFKA-2814: Make Kafka Connect system test REST requests use hostname that is compatible with running under AWS. ---- > Kafka Connect system tests using REST interface fail on AWS > ----------------------------------------------------------- > > Key: KAFKA-2814 > URL: https://issues.apache.org/jira/browse/KAFKA-2814 > Project: Kafka > Issue Type: Bug > Components: copycat, system tests > Reporter: Ewen Cheslack-Postava > Assignee: Ewen Cheslack-Postava > Fix For: 0.9.1.0 > > > Currently they are using the hostname for the node, which seems sensible but > isn't guaranteed to work on the driver machine because the hostname is a > short name assigned by Vagrant and setup using vagrant-hostmanager on each > instance, but not guaranteed to be setup on the driver machine. Instead we > need to use a special field which contains a hostname that is routable from > the driver but may be worse for logging (e.g., an IP address or long EC2 > hostname containing an encoded version of the IP address). -- This message was sent by Atlassian JIRA (v6.3.4#6332)