Hi all,

Bump! Any clues on what might be causing this?

On Wed, Jan 6, 2016 at 10:36 AM, anu sudarsan <[email protected]> wrote:

> Hi
>
> I tried with HDP 2.3 and still getting the same error. Any ideas what
> might be causing this? As I said, the same appConfig and resources.json
> configurations and cluster works for Slider 0.80.0.
>
> Relevant parameters from the resources.json
>
> {
>   "schema": "http://example.org/specification/v2.0.0";,
>   "metadata": {
>   },
>   "global": {
>     "yarn.vcores": "1"
>   },
>   "components": {
>     "slider-appmaster": {
>     },
>     "COORDINATOR": {
>       "yarn.role.priority": "1",
>       "yarn.component.instances": "1",
>       "yarn.memory": "256",
>       "yarn.label.expression": "coord"
>     }
>   }
>
>
> On Tue, Jan 5, 2016 at 2:30 PM, anu sudarsan <[email protected]>
> wrote:
>
>> Hi
>>
>>  I am trying to use Slider 0.81.1 with *yarn.label.expression* feature
>> and getting the following error. This is from slider-agent.log for
>> slider-appmaster.
>>
>> ERROR appmaster.SliderAppMaster - Exception in AmExecutor-006: 
>> org.apache.hadoop.yarn.client.api.InvalidContainerRequestException: relax 
>> location flag doesn't match container priority: OutstandingRequest{roleId=1, 
>> node=null, hostname='null', hasLocation=true, 
>> requestedTimeMillis=1452019991722, mayEscalate=false, escalated=true, 
>> escalationTimeoutMillis=1452020021722, 
>> issuedRequest=Capability[<memory:1500, vCores:1>]Priority[1073741825]; 
>> relaxLocality=true; nodeLabels=coord; }
>> org.apache.hadoop.yarn.client.api.InvalidContainerRequestException: relax 
>> location flag doesn't match container priority: OutstandingRequest{roleId=1, 
>> node=null, hostname='null', hasLocation=true, 
>> requestedTimeMillis=1452019991722, mayEscalate=false, escalated=true, 
>> escalationTimeoutMillis=1452020021722, 
>> issuedRequest=Capability[<memory:1500, vCores:1>]Priority[1073741825]; 
>> relaxLocality=true; nodeLabels=coord; }
>>      at 
>> org.apache.slider.server.appmaster.state.OutstandingRequest.validate(OutstandingRequest.java:406)
>>      at 
>> org.apache.slider.server.appmaster.state.OutstandingRequest.buildContainerRequest(OutstandingRequest.java:232)
>>      at 
>> org.apache.slider.server.appmaster.state.RoleHistory.requestInstanceOnNode(RoleHistory.java:598)
>>      at 
>> org.apache.slider.server.appmaster.state.RoleHistory.requestNode(RoleHistory.java:613)
>>      at 
>> org.apache.slider.server.appmaster.state.AppState.createContainerRequest(AppState.java:1232)
>>      at 
>> org.apache.slider.server.appmaster.state.AppState.buildContainerResourceAndRequest(AppState.java:1213)
>>      at 
>> org.apache.slider.server.appmaster.state.AppState.reviewOneRole(AppState.java:1938)
>>      at 
>> org.apache.slider.server.appmaster.state.AppState.reviewRequestAndReleaseNodes(AppState.java:1812)
>>      at 
>> org.apache.slider.server.appmaster.SliderAppMaster.executeNodeReview(SliderAppMaster.java:1804)
>>      at 
>> org.apache.slider.server.appmaster.SliderAppMaster.handleReviewAndFlexApplicationSize(SliderAppMaster.java:1790)
>>      at 
>> org.apache.slider.server.appmaster.actions.ReviewAndFlexApplicationSize.execute(ReviewAndFlexApplicationSize.java:41)
>>      at 
>> org.apache.slider.server.appmaster.actions.QueueExecutor.run(QueueExecutor.java:73)
>>
>> The same configuration works fine when I remove "*yarn.label.expression*"
>> from the resources.json.
>>
>> Does Slider 0.81.1 require Hadoop 2.7? I am using HDP 2.2, and thus have
>> Hadoop 2.6. I have no issues deploying the application using yarn labels
>> when using Slider 0.80.0, the problem is only with Slider 0.81.1.
>>
>> Thanks
>> -Anu
>>
>
>

Reply via email to