Re: Breaking JSON changes (0.19.1)

Hey Whitney, sorry to hear you were bit by this! I just realized that I misclassified MESOS-1406, the problem ran deeper than I initially thought. In particular, all of the boolean JSON values that were being exported implicitly changed from "1"/"0" to "true"/"false" due to this change: commit de

#MesosCon Hackathon Details Announced

Below are details about the #MesosCon hackathon, which has also been shared on the Mesos blog: http://mesos.apache.org/blog/mesoscon-2014-hackathon-details-announced/ Hope to see many of you there! Dave #MesosCon Hackathon Details Announced After a full day of workshops and talks

Open call to be incl on Mesos support and services list

Hi All, I wanted to revisit a previous thread where I suggested that we add a section to the Mesos website to list companies that provide Mesos services and development. At that time, we heard interest from: * Grand Logic * Mesosphere * Big Data Open

subscribe

Re: mesos build errors

Not written in MPI. Each task is a stand-alone execution of a binary program that takes the 1-2 data file paths as parameters (GCS paths), with the output stored in another GCS file (path as flag). Different tasks do not need to communicate with others. Tasks only talk with GCS to read and write th

Re: mesos build errors

Depends on the nature of your tasks. Your code is written in MPI? You tasks needs to communicate with others? One task will operate on all files, some subset, or just on file? You might have: - one task per machine running on as many cores as possible - many smaller tasks starting in a dy