Hi MJ, Extremely sorry for a late response...Had some infrastructure issues
here...
I am using Hadoop 2.3.0. Actually when i was trying to solve this AppMaster
issue, i came up with a strange observation. "STICKY SLOT" of app-master to
only the data node at the Master node if i set the following p
Sorry, it should be accessing http://:8042/conf to check
the value of yarn.resourcemanager.
scheduler.address on the node manager.
On Thu, Mar 6, 2014 at 9:36 AM, Mingjiang Shi wrote:
> Hi Sai,
> A few questions:
> 1. which version of hadoop are you using? yarn.resourcemanager.hostname is
> a n
Hi Sai,
A few questions:
1. which version of hadoop are you using? yarn.resourcemanager.hostname is
a new configuration which is not available old versions.
2. Does your yarn-site.xml contains yarn.resourcemanager.scheduler.address?
If yes, what's the value?
3. or you could access http://:8088/conf
The message means it can not connect to ResourceManager.
Could you share your configuration ? It might be easier to figure out the
real issue.
Thanks
Xuan Gong
On Wed, Mar 5, 2014 at 11:29 AM, Sai Prasanna wrote:
> Hi,
>
> I have a five node cluster. One master and 4 slaves. Infact master also
Hi,
I have a five node cluster. One master and 4 slaves. Infact master also has
a data node running. When ever app master is launched in the master node,
simple wordcount program runs fine. But if it is launched in some slave
nodes, the progress of the application gets hung.
The problem is, though
