reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Weimer <>
Subject Re: Design Considerations on reef-1791
Date Wed, 14 Jun 2017 15:32:34 GMT
On Tue, Jun 13, 2017 at 4:17 PM, Saikat Kanjilal <> wrote:
> 1) the mesos runtime is currently using google protcol buffer and the mesos
> task API, am assuming we don't need any of this for the spark runtime or
> any of the interfaces with avro, is that assumption correct

Yes, I don't think we need any interfacing via protobuf for this.

> 2) I see a lot of classes in the org.apache.reef.runtime.mesos.driver
> package associated with Launching, Releasing,Requesting Resources, in the
> interim I renamed all these to Spark versions and am assuming we can still
> reuse these, do you see any issues with this, if we can reuse these they
> will be available through the SparkDriverConfiguration which extends
> ConfigurationModuleBuilder (again similar to Mesos implementation)

You will need similar classes, but with different content :)

> 3) I also renamed all of the mesos evaluator packages to their spark
> counterparts, do you see any issues with reusing the evaluator parameters
> classes

No, as long as they are in a new package.

> 4) Finally I am looking at the mesos util directory and I am wondering if
> we can do without any of the Remote management functionality (i..e
> MesosRemoteManager etc)

I don't think we need the mesos remoting support for Spark.


View raw message