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

Josh Elser edited comment on ACCUMULO-4019 at 10/8/15 6:48 PM:
---------------------------------------------------------------

FYI [~afuchs], consider using {{mvn verify -DskipITs}} in the future. The build 
was failing after your commits due to a checkstyle failure. I've since fixed 
the build.


was (Author: elserj):
FYI [~afuchs], consider using {{mvn verify -DskipITs}} in the future. The build 
was failing after your commits due to a checkstyle failure.

> thrift proxy no longer listening on all interfaces
> --------------------------------------------------
>
>                 Key: ACCUMULO-4019
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4019
>             Project: Accumulo
>          Issue Type: Bug
>          Components: proxy
>    Affects Versions: 1.7.0
>            Reporter: Adam Fuchs
>            Assignee: Adam Fuchs
>             Fix For: 1.7.1, 1.8.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> In updating the thrift proxy to use HostAndPort-style configuration, we 
> changed the behavior from listening on all interfaces to only listening on 
> the canonical host name interface. This broke the proxy for some users:
> {code}
> -    TServer server = createProxyServer(AccumuloProxy.class, 
> ProxyServer.class, port, protoFactoryClass, opts.prop);
> -    server.serve();
> +    HostAndPort address = 
> HostAndPort.fromParts(InetAddress.getLocalHost().getCanonicalHostName(), 
> port);
> +    ServerAddress server = createProxyServer(address, protoFactory, 
> opts.prop);
> {code}
> Does anybody know what prompted this change? To fix this, I think we should 
> hardcode it to listen to all interfaces. Would the correct way of doing that 
> be to use the following address?:
> {code}
> HostAndPort address = HostAndPort.fromParts("::", port);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to