Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Cant acces from host to cloudera WEBHDFS (Guest)

Cant acces from host to cloudera WEBHDFS (Guest)

New Contributor

made the needed settings in cloudera ( virtual box) to make webhdfs enable testing directly on cloudera works:

 

[cloudera@quickstart ~]$ curl -i -L "http://10.0.0.88:50070/webhdfs/v1/user/cloudera/testdir/testFile?op=OPEN"
HTTP/1.1 307 TEMPORARY_REDIRECT
http://quickstart.cloudera:50075/webhdfs/v1/user/cloudera/testdir/testFile?op=OPEN&namenoderpcaddres...
Content-Length: 0
Server: Jetty(6.1.26.cloudera.4)
HTTP/1.1 200 OK
Cache-Control: no-cache
Expires: Tue, 01 Dec 2015 14:08:07 GMT
Date: Tue, 01 Dec 2015 14:08:07 GMT
Access-Control-Allow-Methods: GET
Access-Control-Allow-Origin: *
Server: Jetty(6.1.26.cloudera.4)
trying directly on cloudera web browser also work for :
http://10.0.0.88:50070/webhdfs/v1/user/cloudera/testdir/testFile?op=OPEN

 


I am able to send PING C:\Users\User>ping 10.0.0.88
Telnet working for port 50070.

 

But when trying this command outside the cluster it dosnt work (HOST)
"http://10.0.0.88:50070/webhdfs/v1/user/cloudera/testdir/testFile?op=OPEN"
more info

 

LISTSTATUS works from HOST


http://10.0.0.88:50070/webhdfs/v1/user/cloudera/testdir/testFileop=LISTSTATUS&user.name=hadoop`
returns
{"FileStatuses":{"FileStatus":[
{"accessTime":1448982310759,"blockSize":134217728,"childrenNum":0,"fileId":26625,"group":"cloudera","length":47,"modificationTime":1448978300739,"owner":"cloudera","pathSuffix":"","permission":"644","replication":1,"type":"FILE"}
]}}

 

 

but op=OPEN from HOST


"http://10.0.0.88:50070/webhdfs/v1/user/cloudera/testdir/testFile?op=OPEN&user.name=hadoop"
returns

This webpage is not available
what could be the problem ?

1 REPLY 1
Highlighted

Re: Cant acces from host to cloudera WEBHDFS (Guest)

Expert Contributor
You may be using virtual ip or a private ip. You need to port forward that virtual/private ip to any public IP so that it can be resolved from anywhere.

If your namenode has HA above solution also doesn't work in case of namenode failover, another solution would be using httpfs server. You may also need to configure httpfs ha if you want that to be resilient.
Em Jay