:) Yes, you are right. The yarn.acl.enable property in yarn-default.xml is
set true. If the property is true by default, then this makes it mandatory
for users to either specify a value for hadoop.http.staticuser.user
property explicitly or to change the acl's to false. Am I right to assume
this?
Yes you are right. If it is true by default we probably want to update
the documentation for the web services to indicate this. Could you file a
JIRA for improving that documentation?
Thanks,
Bobby
On 7/27/12 3:11 AM, Prajakta Kalmegh pkalm...@gmail.com wrote:
:) Yes, you are right. The
Hi Bobby
Thanks for the reply. My REST calls are working fine since I set the
'hadoop.http.staticuser.user' property to 'prajakta' instead of Dr.Who in
core-site.xml . I didn't get time to figure out the reason behind it as I
just moved on to further coding :)
Thanks,
Prajakta
On Thu, Jul 26,
OK I think I understand it now. You probably have ACLs enabled, but no
web filter on the RM to let you sign in as a given user. As such the
default filter is making you be Dr. Who, or whomever else it is, but the
ACL check in the web service is rejecting Dr Who, because that is not the
correct
I am sorry it has taken me so long to respond. Work has been crazy :).
I really am at a loss right now why you are getting the connection refused
error. The error is happening between the RM and the AM. The Dr who is
something you can ignore. It is the default name that is given to a web
user
Hmm, that is very odd. It only checks the user if security is enabled to
warn the user about potentially accessing something unsafe. I am not sure
why that would cause an issue.
--Bobby Evans
On 7/9/12 6:07 AM, Prajakta Kalmegh pkalm...@gmail.com wrote:
Hi Robert
I figured out the problem
Hi Robert
I started the proxyserver explicitly by specifying a value for the
yarn.web-proxy.address in yarn-site.xml. The proxyserver did start and I
tried getting the JSON response using the following command :
curl --compressed -H Accept: application/json -X GET
Re-posting as I haven't got a solution yet. Sorry for spamming. I won't be
able to proceed in my code until I get a JSON response using AppMaster REST
URL. :(
Thanks,
Prajakta
On Wed, Jul 4, 2012 at 5:55 PM, Prajakta Kalmegh pkalm...@gmail.com wrote:
Hi Robert/Harsh
Thanks for your reply.
Sorry I did not respond sooner. The default behavior is to have the proxy
server run as part of the RM. I am not really sure why it is not doing
this in your case. If you set the config yourself to be a URI that is
different from that of the RM then you need to launch a standalone proxy
server.
Robert , Thanks for the response. If I do not provide any explicit
configuration for the proxy server, do I still need to start it using the
'yarn start proxy server'? I am currently not doing it.
Also, I am able to access the html page for proxy using the
What version of hadoop are you using? It could be that the version you
have does not have the RESTful APIs in it yet, and the proxy is working
just fine.
--Bobby Evans
On 7/6/12 12:06 PM, Prajakta Kalmegh pkalm...@gmail.com wrote:
Robert , Thanks for the response. If I do not provide any
I am using hadoop trunk (forked from github). It supports RESTful APIs as I
am able to retrieve JSON objects for RM (cluster/nodes info)+
Historyserver. The only issue is with AppMaster REST API.
Regards,
Prajakta
On Fri, Jul 6, 2012 at 10:55 PM, Robert Evans ev...@yahoo-inc.com wrote:
What
Hi Robert/Harsh
Thanks for your reply.
My RM is starting just fine. The problem is with the use of
http://proxy httpddress:port/proxy/{appid}/ws/v1/mapreduce
to get the JSON response.
As I said before, I had not configured the yarn.web-proxy.address
property in yarn-site.xml. I assumed it will
Please don't file that JIRA. The proxy server is intended to front the
web server for all calls to the AM. This is so you only have to go to a
single location to get to any AM's web service. The proxy server is a
very simple proxy and just forwards the extra part of the path on to the
AM.
If
Hi
I am trying to get the ApplicationMaster info using the http://proxy http
address:port/proxy/{appid}/ws/v1/mapreduce/info link as described on the
http://hadoop.apache.org/common/docs/r2.0.0-alpha/hadoop-yarn/hadoop-yarn-site/MapredAppMasterRest.html
page.
I am able to access and retrieve
As far as I can tell, the MR WebApp, as the name itself indicates on
its doc page, starts only at the MR AM (which may be running at any
NM), and it starts as an ephemeral port logged at in the AM logs
usually as:
INFO Web app /mapreduce started at [PORT]
That it starts its own server with an
Hi Harsh
Can you tell me where can I find my AM logs? I could find the
RM/NM/HistoryServer/Container logs but not AM logs :(
I looked in the RM logs to see if I have any entry for 'Web app /mapreduce'
to see if it actually starts on RM as indicated in the link, but it does
not.
I will file a
17 matches
Mail list logo
