Closed fnerdwq closed 8 years ago
This might be https://github.com/cloudera/hue/commit/8747b7cb5c65d88782cd5b8e9430e1d7bc7e3be6 (wrong doAs user could be used)
An alternative would also be to issue the command sent by Hue to the RM with curl as the Hue user to confirm your Yarn supports it
This patch is hard to test on 3.9.0, since a lot of code seems to have changed arround this.
Actually issuing a
curl -u : --negotiate -v -X PUT -d '{ "state" : "KILLED" }' -H "Content-type:application/json" http://resourcemanager:8088/ws/v1/cluster/apps/application_1453892619275_0070/state
leads to the same error The default static user cannot carry out this operation.
. Hmmm, not clear to me why that's the case. So this might be nothing on the hue side...
In Cloudera Manager or your YARN config , "You have to check the box for "Enable Kerberos Authentication for HTTP Web-Consoles" in the Yarn configuration to make this work[1]. Then restart Yarn"
In Hue 3.9.0 connected to a kerberized (HDP 2.3.4) cluster (not testet w/o security enabled) we have the issue, that a job cannot be killed in the Jobbrowser. Hitting the kill button and clicking "Yes" in the confirmation dialog, just leaves me with a in progress "Yes..." button greyed out and the following error in the
runcpserver.log
:Is this is miscounfiguration issue? Or a but I'm experiencing?