reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reed Umbrasas <>
Subject RE: REEFExecutor in Mesos Runtime
Date Thu, 01 Feb 2018 22:24:56 GMT
Hi Gon,

Yes, we are creating a new runtime package for Azure Batch. I did see that there is quite
a bit of Mesos-specific logic in org.apache.reef.runtime.mesos.evaluator.REEFExecutor; but
I was wondering if there were any plans to provide a generic version that could be used across

In the meantime, I'll just go ahead and create a separate one for Azure Batch unless anyone
have other input.


-----Original Message-----
From: Byung-Gon Chun [] 
Sent: Thursday, February 1, 2018 1:20 PM
Subject: Re: REEFExecutor in Mesos Runtime

Hi Reed,

org.apache.reef.runtime.mesos.evaluator.REEFExecutor implements org.apache.mesos.Executor.
The code has implementation is specific to mesos. It may be better to create a separate executor
class for Azure Batch runtime.

John, could you add comments since you worked on the REEF mesos runtime?

Are you creating a new reef runtime package for Azure Batch?


On Fri, Feb 2, 2018 at 5:37 AM, Reed Umbrasas <
> wrote:

> Hi,
> While developing REEF runtime for Azure Batch we ran into a very 
> similar issue that has been already addressed in the Mesos runtime. 
> Namely, we need to specify a process to start at the time of 
> requesting a resource from Azure Batch. I see that Mesos starts 
> org.apache.reef.runtime.mesos.evaluator.REEFExecutor
> process which sends a message back to the Driver which in turn fires 
> off the AllocatedEvaluator event. Once the application driver handles 
> the event, a message is sent back to the REEFExecutor to start the 
> evaluator via the REEFLauncher.
> Since we need to implement a very similar mechanism for Azure Batch 
> runtime, does it make sense to build a generic version of REEFExecutor 
> or should our implementation reside and be limited to Azure Batch runtime?
> Thanks,
> Reed

Byung-Gon Chun
View raw message