Investigate Mesos as an option for running Fluo

[cjnolet]

Mesos is getting much traffic in the cloud community. In fact, there are many companies like Twitter, eBay and Netflix are using it in production at massive scale. Some customers may be abandoning YARN as their scheduling mechanism and trying to lean more towards fully Mesos. It also seems pretty easy to integrate with. It's definitely worth investigating what it would take to get Fluo running on it.

[mikewalch]

I think we should be able to run on Mesos too. YARN was chosen because users need Hadoop installed to run Accumulo. However, we could have users that prefer Mesos and only allocate limited resources to Hadoop. When #289 is done, we coud add a fluo mesos (start|stop|status) command for mesos.

It might be a good idea to do this for the beta release so we don't get too bound to YARN.

[mikewalch]

In #292, a question came up on whether yarn properties should be configured with the oracle (i.e io.fluo.oracle.num.instances or with YARN prefix io.fluo.yarn.oracle.instances. I think the deciding factory is whether or not YARN & Mesos should share properties. This should be decided during the integration of Mesos in this ticket. If they shouldn't be shared, the properties should be re-organized into io.fluo.yarn.* properties and io.fluo.mesos.*.

[keith-turner]

http://aurora.apache.org/

[mikewalch]

Closed by #883