[jira] [Created] (MYRIAD-190) Tests fail on more recent versions of YARN

2016-03-13 Thread DarinJ (JIRA)
DarinJ created MYRIAD-190:
-

 Summary: Tests fail on more recent versions of YARN
 Key: MYRIAD-190
 URL: https://issues.apache.org/jira/browse/MYRIAD-190
 Project: Myriad
  Issue Type: Bug
  Components: Scheduler
Affects Versions: Myriad 0.1.0, Myriad 0.2.0
Reporter: DarinJ
Assignee: DarinJ
Priority: Minor


For Hadoop Versions 2.6.2+ the test fail do to a missing method in the mock 
rmContext.  While it doesn't effect the runtime or the build, some users may 
wish to build against their specific hadoop version to ensure no broken 
dependencies.  Adding the mocked method corrects the behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (MYRIAD-188) Zero sized node managers can cause the Resource Manager to crash with an NPE

2016-03-13 Thread DarinJ (JIRA)

 [ 
https://issues.apache.org/jira/browse/MYRIAD-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

DarinJ resolved MYRIAD-188.
---
Resolution: Fixed

> Zero sized node managers can cause the Resource Manager to crash with an NPE
> 
>
> Key: MYRIAD-188
> URL: https://issues.apache.org/jira/browse/MYRIAD-188
> Project: Myriad
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: Myriad 0.1.0
>Reporter: DarinJ
>Assignee: DarinJ
> Fix For: Myriad 0.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (MYRIAD-156) NullPointerException from "Error in handling event type NODE_RESOURCE_UPDATE to the scheduler"

2016-03-13 Thread DarinJ (JIRA)

 [ 
https://issues.apache.org/jira/browse/MYRIAD-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

DarinJ reassigned MYRIAD-156:
-

Assignee: DarinJ  (was: Swapnil Daingade)

> NullPointerException from "Error in handling event type NODE_RESOURCE_UPDATE 
> to the scheduler"
> --
>
> Key: MYRIAD-156
> URL: https://issues.apache.org/jira/browse/MYRIAD-156
> Project: Myriad
>  Issue Type: Bug
>Reporter: Sarjeet Singh
>Assignee: DarinJ
>
> The NPE happens where there is a node in cluster becomes unhealthy, and 
> scheduler removes them from internal data structure. However, when the node 
> heartbeats and scheduler tries to search for this node, and try to operate on 
> it, it gets nullPointerException there. Here is the code snippet where this 
> is causing NPE: 
> SchedulerNode node = getSchedulerNode(nm.getNodeID());
> the node object is Null causing the Null pointer exception.
> Here is the RM log for caused exception:
> 15/10/06 09:18:09 INFO handlers.ResourceOffersEventHandler: Offer not
> sufficient for task with, cpu: 4.4, memory: 5504.0, spindles: 4.0, ports: 996
> 15/10/06 09:18:11 FATAL resourcemanager.ResourceManager: Error in handling
> event type NODE_RESOURCE_UPDATE to the scheduler
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.AbstractYarnScheduler.updateNodeResource(AbstractYarnScheduler.java:548)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.updateNodeResource(FairScheduler.java:1712)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:1293)
> at
> com.ebay.myriad.scheduler.yarn.MyriadFairScheduler.handle(MyriadFairScheduler.java:64)
> at
> com.ebay.myriad.scheduler.yarn.MyriadFairScheduler.handle(MyriadFairScheduler.java:17)
> at
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:693)
> at java.lang.Thread.run(Thread.java:745)
> 15/10/06 09:18:11 INFO resourcemanager.ResourceManager: Exiting, bbye..



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MYRIAD-156) NullPointerException from "Error in handling event type NODE_RESOURCE_UPDATE to the scheduler"

2016-03-13 Thread DarinJ (JIRA)

[ 
https://issues.apache.org/jira/browse/MYRIAD-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15192515#comment-15192515
 ] 

DarinJ commented on MYRIAD-156:
---

As [~sarjeet] pointed out this looks to be the same bug as [MYRIAD-188].  I've 
submitted a PR which fixes the issue.

> NullPointerException from "Error in handling event type NODE_RESOURCE_UPDATE 
> to the scheduler"
> --
>
> Key: MYRIAD-156
> URL: https://issues.apache.org/jira/browse/MYRIAD-156
> Project: Myriad
>  Issue Type: Bug
>Reporter: Sarjeet Singh
>Assignee: Swapnil Daingade
>
> The NPE happens where there is a node in cluster becomes unhealthy, and 
> scheduler removes them from internal data structure. However, when the node 
> heartbeats and scheduler tries to search for this node, and try to operate on 
> it, it gets nullPointerException there. Here is the code snippet where this 
> is causing NPE: 
> SchedulerNode node = getSchedulerNode(nm.getNodeID());
> the node object is Null causing the Null pointer exception.
> Here is the RM log for caused exception:
> 15/10/06 09:18:09 INFO handlers.ResourceOffersEventHandler: Offer not
> sufficient for task with, cpu: 4.4, memory: 5504.0, spindles: 4.0, ports: 996
> 15/10/06 09:18:11 FATAL resourcemanager.ResourceManager: Error in handling
> event type NODE_RESOURCE_UPDATE to the scheduler
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.AbstractYarnScheduler.updateNodeResource(AbstractYarnScheduler.java:548)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.updateNodeResource(FairScheduler.java:1712)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:1293)
> at
> com.ebay.myriad.scheduler.yarn.MyriadFairScheduler.handle(MyriadFairScheduler.java:64)
> at
> com.ebay.myriad.scheduler.yarn.MyriadFairScheduler.handle(MyriadFairScheduler.java:17)
> at
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:693)
> at java.lang.Thread.run(Thread.java:745)
> 15/10/06 09:18:11 INFO resourcemanager.ResourceManager: Exiting, bbye..



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)