Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
MapReduce >> mail # user >> Re: Requesting containers on a specific host


Copy link to this message
-
Re: Requesting containers on a specific host
I could resolve this error with a simple host name change to a fully
qualified one including the domain name. But to go ahead running some of my
old example code, I am observing at least the following changes :
1) ClientRMProtocol and AMRMProtocol are removed.
2) ContainerManager is removed.
3) YarnRemoteException is removed.
4) ContainerRequest is removed.

It looks like it is now compulsory to modify my application accordingly,
where as on earlier versions, I could have run the same application without
any modifications.

Thanks,
Kishore
On Fri, Jul 5, 2013 at 7:37 PM, Krishna Kishore Bonagiri <
[EMAIL PROTECTED]> wrote:

> Hi Devaraj,
>
>    Thanks for pointing me to this RC. I am trying this out, and getting
> this error for NM to get started. My RM is running fine, but NM is failing
> and saying that it is disallowed by RM and received a SHUTDOWN message.
> Please give me clue to resolve this.
>
> 2013-07-05 09:49:20,043 ERROR
> org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl: Unexpected
> error starting NodeStatusUpdater
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Recieved SHUTDOWN
> signal from Resourcemanager ,Registration of NodeManager failed, Message
> from ResourceManager: Disallowed NodeManager from
> isredeng.swg.usma.ibm.com, Sending SHUTDOWN signal to the NodeManager.
>         at
> org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.registerWithRM(NodeStatusUpdaterImpl.java:290)
>         at
> org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.serviceStart(NodeStatusUpdaterImpl.java:156)
>         at
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
>         at
> org.apache.hadoop.service.CompositeService.serviceStart(CompositeService.java:101)
>         at
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceStart(NodeManager.java:213)
>         at
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
>         at
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:401)
>         at
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:447)
>
> Thanks,
> Kishore
>
>
> On Fri, Jul 5, 2013 at 8:52 AM, Devaraj k <[EMAIL PROTECTED]> wrote:
>
>>  Hi Kishore,****
>>
>> ** **
>>
>> hadoop-2.1.0 beta release is in voting process now.****
>>
>> ** **
>>
>> You can try out from hadoop-2.1.0 beta RC
>> http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc0/ or you could
>> check the same with trunk build.****
>>
>> ** **
>>
>> Thanks****
>>
>> Devaraj k****
>>
>> ** **
>>
>> *From:* Krishna Kishore Bonagiri [mailto:[EMAIL PROTECTED]]
>> *Sent:* 04 July 2013 21:33
>>
>> *To:* [EMAIL PROTECTED]
>> *Subject:* Re: Requesting containers on a specific host****
>>
>>  ** **
>>
>> Thanks Arun, it seems to be available with 2.1.0-beta, when will that be
>> released? Or if I want it now, could I get from the trunk?****
>>
>> ** **
>>
>> -Kishore****
>>
>> ** **
>>
>> On Thu, Jul 4, 2013 at 5:58 PM, Arun C Murthy <[EMAIL PROTECTED]>
>> wrote:****
>>
>> To guarantee nodes on a specific container you need to use the whitelist
>> feature we added recently:****
>>
>> https://issues.apache.org/jira/browse/YARN-398****
>>
>>  Arun****
>>
>> ** **
>>
>> On Jul 4, 2013, at 3:14 AM, Krishna Kishore Bonagiri <
>> [EMAIL PROTECTED]> wrote:****
>>
>>
>>
>> ****
>>
>> I could get containers on specific nodes using addContainerRequest() on
>> AMRMClient. But there are issues with it. I have two nodes, node1 and node2
>> in my cluster. And, my Application Master is trying to get 3 containers on
>> node1, and 3 containers on node2 in that order. ****
>>
>> ** **
>>
>> While trying to request on node1, it sometimes gives me those on node2,
>> and vice verse. When I get a container on a different node than the one I
>> need, I release it and make a fresh request. I am having to do like that
>> forever to get a container on the node I need. ****