[
https://issues.apache.org/jira/browse/SLIDER-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178166#comment-14178166
]
Steve Loughran commented on SLIDER-546:
---------------------------------------
the problem I'm seeing is that on a cluster with ipc authorization enabled at
the hadoop layer, that requires slider-level auth, which fails if there isn't a
slider ACL property
{code}
[20/10/2014 21:25:58] Steve Loughran: seeing my client not being able to talk
to the AM on an insecure cluster:
[20/10/2014 21:25:59] Steve Loughran: 14/10/20 20:08:30 INFO ipc.Server:
Connection from 240.0.0.1:57757 for protocol
org.apache.slider.server.appmaster.rpc.SliderClusterProtocolPB is unauthorized
for user stevel (auth:SIMPLE)
14/10/20 20:08:30 INFO ipc.Server: Socket Reader #1 for port 47514:
readAndProcess from client 240.0.0.1 threw exception
[org.apache.hadoop.security.authorize.AuthorizationException: Protocol
interface org.apache.slider.server.appmaster.rpc.SliderClusterProtocolPB is not
known.]
{code}
you can't add this property in slider client.xml (or turn off the authorization
in {{hadoop.security.authorization}}, because those values are picked up server
side
> Propagate slider-client.xml values to the AM
> --------------------------------------------
>
> Key: SLIDER-546
> URL: https://issues.apache.org/jira/browse/SLIDER-546
> Project: Slider
> Issue Type: Bug
> Components: appmaster, client
> Affects Versions: Slider 0.60
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Slider client XML properties don't get to the AM except in one or two cases
> where they are passed on the command line of the launched AM.
> This prevents the client XML file from overriding specific cluster-wide
> defaults (such as security options), resulting in the AM not behaving as
> desired.
> Although there is some undocumented support for a slider-server.xml file, it
> may be simplest just to load slider-client.xml server-side too
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)