[RATIS-302] Bump the version of grpc-java and netty

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.2.0
• Target Version/s: 0.3.0
• Assignee: Marton Elek
• Reporter: Marton Elek
• Created: 22/Aug/18 15:04
• Updated: 10/Sep/18 22:10
• Resolved: 24/Aug/18 07:43

Description

I got multiple errors during ozone tests with ratis:

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)

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.

Issue Links

• is duplicated by: RATIS-287 "URISyntaxException" warning should not print the stacktrace while ozoneFs command-line execution