You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Brian Cho (JIRA)" <ji...@apache.org> on 2015/04/30 05:11:06 UTC

[jira] [Updated] (REEF-293) reef-tests NullPointerException on Mesos

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

Brian Cho updated REEF-293:
---------------------------
    Description: 
Some jobs throw NullPointerExceptions in reef-tests on Mesos after the protobuf to POJO changes. On the previous Mesos tests this was not caught because a sanity check was not performed to see if jobs had timed out.

For reference, driver.stderr reads:
{code}
Apr 30, 2015 2:04:54 AM org.apache.reef.runtime.mesos.driver.REEFScheduler statusUpdate
SEVERE: Task Status Update:
Exception in thread "Thread-12" java.lang.NullPointerException
        at org.apache.reef.runtime.common.driver.evaluator.EvaluatorManagerFactory.getNewEvaluatorManager(EvaluatorMana
gerFactory.java:93)
        at org.apache.reef.runtime.common.driver.evaluator.Evaluators.put(Evaluators.java:110)
        at org.apache.reef.runtime.common.driver.resourcemanager.ResourceAllocationHandler.onNext(ResourceAllocationHan
dler.java:60)
        at org.apache.reef.runtime.common.driver.resourcemanager.ResourceAllocationHandler.onNext(ResourceAllocationHan
dler.java:32)
        at org.apache.reef.runtime.mesos.driver.REEFEventHandlers.onResourceAllocation(REEFEventHandlers.java:59)
        at org.apache.reef.runtime.mesos.driver.REEFScheduler.handleNewExecutor(REEFScheduler.java:389)
        at org.apache.reef.runtime.mesos.driver.REEFScheduler.statusUpdate(REEFScheduler.java:199)
I0430 02:04:54.248558 25813 sched.cpp:772] Aborting framework '20150429-222950-167815360-5050-20608-0091'
{code}

  was:Some jobs throw NullPointerExceptions in reef-tests on Mesos after the protobuf to POJO changes. On the previous Mesos tests this was not caught because a sanity check was not performed to see if jobs had timed out.


> reef-tests NullPointerException on Mesos
> ----------------------------------------
>
>                 Key: REEF-293
>                 URL: https://issues.apache.org/jira/browse/REEF-293
>             Project: REEF
>          Issue Type: Bug
>          Components: REEF-Runtime-Mesos
>            Reporter: Brian Cho
>            Assignee: Brian Cho
>
> Some jobs throw NullPointerExceptions in reef-tests on Mesos after the protobuf to POJO changes. On the previous Mesos tests this was not caught because a sanity check was not performed to see if jobs had timed out.
> For reference, driver.stderr reads:
> {code}
> Apr 30, 2015 2:04:54 AM org.apache.reef.runtime.mesos.driver.REEFScheduler statusUpdate
> SEVERE: Task Status Update:
> Exception in thread "Thread-12" java.lang.NullPointerException
>         at org.apache.reef.runtime.common.driver.evaluator.EvaluatorManagerFactory.getNewEvaluatorManager(EvaluatorMana
> gerFactory.java:93)
>         at org.apache.reef.runtime.common.driver.evaluator.Evaluators.put(Evaluators.java:110)
>         at org.apache.reef.runtime.common.driver.resourcemanager.ResourceAllocationHandler.onNext(ResourceAllocationHan
> dler.java:60)
>         at org.apache.reef.runtime.common.driver.resourcemanager.ResourceAllocationHandler.onNext(ResourceAllocationHan
> dler.java:32)
>         at org.apache.reef.runtime.mesos.driver.REEFEventHandlers.onResourceAllocation(REEFEventHandlers.java:59)
>         at org.apache.reef.runtime.mesos.driver.REEFScheduler.handleNewExecutor(REEFScheduler.java:389)
>         at org.apache.reef.runtime.mesos.driver.REEFScheduler.statusUpdate(REEFScheduler.java:199)
> I0430 02:04:54.248558 25813 sched.cpp:772] Aborting framework '20150429-222950-167815360-5050-20608-0091'
> {code}



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