[
https://issues.apache.org/jira/browse/RATIS-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton updated RATIS-302:
-------------------------------
Attachment: RATIS-302.001.patch
> Bump the version of grpc-java and netty
> ---------------------------------------
>
> Key: RATIS-302
> URL: https://issues.apache.org/jira/browse/RATIS-302
> Project: Ratis
> Issue Type: Improvement
> Affects Versions: 0.2.0
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Attachments: RATIS-302.001.patch
>
>
> I got multiple errors during ozone tests with ratis:
> {code}
> WARNING: Failed to construct URI for proxy lookup, proceeding without proxy
> java.net.URISyntaxException: Illegal character in hostname at index 13:
> https://ozone_datanode_3.ozone_default:9858
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.parseHostname(URI.java:3387)
> at java.net.URI$Parser.parseServer(URI.java:3236)
> at java.net.URI$Parser.parseAuthority(URI.java:3155)
> at java.net.URI$Parser.parseHierarchical(URI.java:3097)
> at java.net.URI$Parser.parse(URI.java:3053)
> at java.net.URI.<init>(URI.java:673)
> {code}
> It came from the shaded io.grpc during the proxy detection. Unfortunately
> this is a limitation of the docker-compose. I use docker-compose to create
> clusters but compose use underscore in the dns names which are invalid. It's
> checked in one of the constructor of the java.net.URI/URL.
> See also: https://github.com/docker/compose/issues/229
> There is no real fix for that. Fortunately in the latest grpc-java the proxy
> detection part is improved and I can't see similar errors (even if my host
> names still invalid).
> I propose to use the latest grpc and (just to make it easier) swtich to the
> same netty which is used by grpc-java.
> I tested the change with ozone pseudo cluster and it worked well.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
