GitHub user keith-turner opened an issue:

    https://github.com/apache/incubator-fluo/issues/820

    Twill is not working with netty 3.10.5

    I recently tried running Fluo with the latest version of Zookeeper, which 
brought in a newer version of netty.  For an unknown reason this newer version 
of netty causes the Twill application master to not work.  I constantly see 
errors like the following when trying to start a Fluo applications.  
    
    ```
    15:31:04.182 [main] ERROR o.a.twill.yarn.ResourceReportClient - Exception 
getting resource report from http://node1:39796/resources.
    java.net.SocketException: Unexpected end of file from server
        at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:792) 
~[na:1.8.0_121]
        at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) 
~[na:1.8.0_121]
        at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:789) 
~[na:1.8.0_121]
        at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) 
~[na:1.8.0_121]
        at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569)
 ~[na:1.8.0_121]
        at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
 ~[na:1.8.0_121]
        at java.net.URL.openStream(URL.java:1045) ~[na:1.8.0_121]
        at 
org.apache.twill.yarn.ResourceReportClient.get(ResourceReportClient.java:52) 
~[twill-yarn-0.10.0.jar:0.10.0]
        at 
org.apache.twill.yarn.YarnTwillController.getResourceReport(YarnTwillController.java:326)
 [twill-yarn-0.10.0.jar:0.10.0]
        at 
org.apache.fluo.cluster.runner.YarnAppRunner.getResourceReport(YarnAppRunner.java:302)
 [fluo-cluster-1.0.0-incubating.jar:1.0.0-incubating]
        at 
org.apache.fluo.cluster.runner.YarnAppRunner.start(YarnAppRunner.java:232) 
[fluo-cluster-1.0.0-incubating.jar:1.0.0-incubating]
        at 
org.apache.fluo.cluster.command.FluoCommand.main(FluoCommand.java:74) 
[fluo-cluster-1.0.0-incubating.jar:1.0.0-incubating]
    
    ```
    
    I also tried the following 
    
    ```
    $ wget -d http://node1:39796/resources
    DEBUG output created by Wget 1.17.1 on linux-gnu.
    
    Reading HSTS entries from /home/keith/.wget-hsts
    URI encoding = ‘UTF-8’
    --2017-04-06 15:38:35--  http://node1:39796/resources
    Resolving node1 (node1)... 127.0.1.1
    Caching node1 => 127.0.1.1
    Connecting to node1 (node1)|127.0.1.1|:39796... connected.
    Created socket 3.
    Releasing 0x0000560c6417fb50 (new refcount 1).
    
    ---request begin---
    GET /resources HTTP/1.1
    User-Agent: Wget/1.17.1 (linux-gnu)
    Accept: */*
    Accept-Encoding: identity
    Host: node1:39796
    Connection: Keep-Alive
    
    ---request end---
    HTTP request sent, awaiting response... No data received.
    Closed fd 3
    Retrying.
    
    --2017-04-06 15:38:36--  (try: 2)  http://node1:39796/resources
    Found node1 in host_name_addresses_map (0x560c6417fb50)
    Connecting to node1 (node1)|127.0.1.1|:39796... connected.
    Created socket 3.
    Releasing 0x0000560c6417fb50 (new refcount 1).
    
    ---request begin---
    GET /resources HTTP/1.1
    User-Agent: Wget/1.17.1 (linux-gnu)
    Accept: */*
    Accept-Encoding: identity
    Host: node1:39796
    Connection: Keep-Alive
    
    ---request end---
    HTTP request sent, awaiting response... No data received.
    Closed fd 3
    Retrying.
    
    --2017-04-06 15:38:38--  (try: 3)  http://node1:39796/resources
    Found node1 in host_name_addresses_map (0x560c6417fb50)
    Connecting to node1 (node1)|127.0.1.1|:39796... connected.
    Created socket 3.
    Releasing 0x0000560c6417fb50 (new refcount 1).
    
    ```
    There are no errors in the Twill AM log.  If I put netty 3.9.9 high on the 
classpath OR use an older version of zookeeper (which has an older version of 
netty), then everything works ok.  
    
    I also tried netty 3.10.6 and experienced the same problem.

----

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to