You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "qiang xu (JIRA)" <ji...@apache.org> on 2015/05/17 11:33:00 UTC

[jira] [Comment Edited] (SLIDER-878) Slider cannot support jdk 1.8 for command slider registry --getconf hbase-site --name hb1

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

qiang xu edited comment on SLIDER-878 at 5/17/15 9:32 AM:
----------------------------------------------------------

Hello Steve:
I ran the slider with open source yarn 2.6 without secure.
And today I am trying to understand the work flow, and even want to fix it.
After reading some docs, I have some questions.
In https://mail-archives.apache.org/mod_mbox/incubator-slider-commits/201412.mbox/%3C20141211151707.4DFF3AC094D@hades.apache.org%3E
It mentioned about the "All these services are implemented by the Jersey JAX-RS engine, operating in an embedded Jetty Web engine, with the YARN AmWebFilter class redirecting all requests not coming from the RM Proxy IP address to that RM Proxy via a 302 (redirect-as-GET)"
But I did not find the AmWebFilter, I just find your email, org.apache.hadoop.yarn.server.webproxy.amfilter.AmIpFilter, how do we use AmIpFilter?
I did not find it in slider code.

Then I start to monitor the slider application master, it mentioned about {"uris":{"slider":"http://d64:39876/ws/v1/slider/publisher/slider","exports":"http://d64:39876/ws/v1/slider/publisher/exports"}}
And I use the http://d64:39876/ws/v1/slider/publisher/slider, the address finally redirect to the resource manager.

How do our code configure YARN resource manager to redirect the url to application master?
Why use chrome to query the http://d64:39876/ws/v1/slider/publisher/slider, finally back to resource manager address in the input url?
What code and knowledge for guice or some other thing make these magic happen?

Thanks in advance



was (Author: skaterxu):
Hello Steve:
I ran the slider with open source yarn 2.6 without secure.
And today I am trying to understand the work flow, and even want to fix it.
After reading some docs, I have some questions.
In https://mail-archives.apache.org/mod_mbox/incubator-slider-commits/201412.mbox/%3C20141211151707.4DFF3AC094D@hades.apache.org%3E
It mentioned about the "All these services are implemented by the Jersey JAX-RS engine, operating in an embedded Jetty Web engine, with the YARN AmWebFilter class redirecting all requests not coming from the RM Proxy IP address to that RM Proxy via a 302 (redirect-as-GET)"
But I did not find the AmWebFilter, could you help me point that class.

Then I start to monitor the slider application master, it mentioned about {"uris":{"slider":"http://d64:39876/ws/v1/slider/publisher/slider","exports":"http://d64:39876/ws/v1/slider/publisher/exports"}}
And I use the http://d64:39876/ws/v1/slider/publisher/slider, the address finally redirect to the resource manager.

How do our code configure YARN resource manager to redirect the url to application master?
Why use chrome to query the http://d64:39876/ws/v1/slider/publisher/slider, finally back to resource manager address in the input url?
What code and knowledge for guice or some other thing make these magic happen?

Thanks in advance


> Slider cannot support jdk 1.8 for command slider registry --getconf hbase-site --name hb1
> -----------------------------------------------------------------------------------------
>
>                 Key: SLIDER-878
>                 URL: https://issues.apache.org/jira/browse/SLIDER-878
>             Project: Slider
>          Issue Type: Bug
>          Components: client
>    Affects Versions: Slider 0.61, Slider 0.70, Slider 0.80
>         Environment: Slider 0.61 jdk 1.8
>            Reporter: qiang xu
>
> slider registry --getconf hbase-site --name hb1
> 2015-05-16 11:16:37,829 [main] INFO  impl.TimelineClientImpl - Timeline service address: http://d64:8188/ws/v1/timeline/
> 2015-05-16 11:16:38,472 [main] INFO  client.RMProxy - Connecting to ResourceManager at d64/160.164.0.7:18040
> Exception: java.lang.IllegalStateException: connect in progress
> 2015-05-16 11:16:38,958 [main] ERROR main.ServiceLauncher - Exception: java.lang.IllegalStateException: connect in progress
> com.sun.jersey.api.client.ClientHandlerException: java.lang.IllegalStateException: connect in progress
>         at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:149)
>         at com.sun.jersey.api.client.Client.handle(Client.java:648)
>         at com.sun.jersey.api.client.WebResource.handle(WebResource.java:670)
>         at com.sun.jersey.api.client.WebResource.get(WebResource.java:191)
>         at org.apache.slider.core.registry.retrieve.RegistryRetriever.getConfigurations(RegistryRetriever.java:216)
>         at org.apache.slider.client.SliderClient.actionRegistryGetConfig(SliderClient.java:3117)
>         at org.apache.slider.client.SliderClient.actionRegistry(SliderClient.java:2610)
>         at org.apache.slider.client.SliderClient.exec(SliderClient.java:404)
>         at org.apache.slider.client.SliderClient.runService(SliderClient.java:348)
>         at org.apache.slider.core.main.ServiceLauncher.launchService(ServiceLauncher.java:188)
>         at org.apache.slider.core.main.ServiceLauncher.launchServiceRobustly(ServiceLauncher.java:475)
>         at org.apache.slider.core.main.ServiceLauncher.launchServiceAndExit(ServiceLauncher.java:403)
>         at org.apache.slider.core.main.ServiceLauncher.serviceMain(ServiceLauncher.java:630)
>         at org.apache.slider.Slider.main(Slider.java:49)
> Caused by: java.lang.IllegalStateException: connect in progress
>         at sun.net.www.protocol.http.HttpURLConnection.setRequestMethod(HttpURLConnection.java:516)
>         at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.setRequestMethodUsingWorkaroundForJREBug(URLConnectionClientHandler.java:259)
>         at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:191)
>         at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:147)
>         ... 13 more
> 2015-05-16 11:16:38,963 [main] INFO  util.ExitUtil - Exiting with status 56
> It is caused by the jersey.
> Some reference
> https://bugs.openjdk.java.net/browse/JDK-8029127
> http://stackoverflow.com/questions/27571645/httpurlconnection-getinputstream-to-read-page-and-then-make-post-request



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