Darin

Allong those lines we'll need to just ensure 1.0.0 will run as there may be breaking changes (as in 0.10.0). Fun as I haven't fully migrated to 0.10.x yet...

So when I've done this in the past, I used mesos -dns and set the nimbus hostname to nimbus.marathon.mesos (taskid of nimbus was nimbus). On Oct 20, 2016 6:45 PM,...

I've done this and could write something up over the weekend. On Oct 14, 2016 6:30 AM, "dinoba" [email protected] wrote: > Is there any way to update documentatio, how to...

Currently I deploy the Storm/Mesos Nimbus via a dedicated node. Some use external volumes and reservations with marathon, the reason is that the Nimbus stores some of its state locally...

viswram answers to your questions: 1) no it can be on a completely different server, I've even run it in marathon (though it requires knowledge of service discovery, so do...

1) That is incorrect - You'll need to setup HDFS separately, i.e, Namenodes, Secondary Namenodes and datanodes. The mesos-hadoop Framework only sets up the Jobtracker and tasktrackers. 2) I'm not...

I've done this, it's best to setup roles (and ussuaully mapred.mesos.role.strict) if your going to do this.

I've been contemplating better scaleup/scaledown policies based on expected response times of tasks in the queue (involves keeping some stats as jobs start/finish how they come on the queue) and...

@tarnfeld here's a short write up of my idea. Sorry for the delay got swamped by other things. Any comments/suggestions would be appreciated. The idea is to keep the framework...

I hit the same thing. Removing the synchronized (this.scheduler) block in MesosTracker.idleCheck removed the deadlock, it's calling methods on scheduler that are synchronized on this (context is MesosSchedules here) which...