Thank you for this, it's very helpful. One question, I've been launching two tasks via my custom executor (which just launches stress at the moment), and according to the webui, the second task is being registered as killed instead of finished. Why does it do this? Here's my executor and scheduler code (pretty much based off the examples): https://gist.github.com/markehammons/ce1b5b28c59a0f54c95b0dd8c7ec1f69
On Saturday, July 16, 2016 04:02:32 PM [email protected] wrote: > There are some custom executors in the RENDLER example framework. See > https://github.com/mesosphere/RENDLER. > > Sent from my iPhone > > > On Jul 16, 2016, at 14:29, Mark Hammons <[email protected]> > > wrote: > > > > Hi All, > > > > I'm trying to make a service in our labs into a custom framework that will > > launch tasks in our (prospective) mesos cluster. The framework will use > > something similar to the command executor, except when the command being > > run by the executor is finished, some of the resulting data in the > > sandbox will be uploaded to another location. I've got a scheduler and > > executor up and running using the built in examples, but the examples > > don't show how to activate the custom executor on the slaves. Manually > > executing it using the command executor and launching the custom executor > > with java -jar seems to work somewhat, but some of the tasks are > > reporting errors after I do that. > > > > Does anyone have some good examples of actually using a custom executor? > > -- > > Mark Hammons - +33 06 03 69 56 56 > > Research Engineer @ BioEmergences > > Lab Phone: 01 69 82 34 19-- Mark Hammons - +33 06 03 69 56 56 Research Engineer @ BioEmergences[1] Lab Phone: 01 69 82 34 19 -------- [1] bioemergences.iscpif.fr
signature.asc
Description: This is a digitally signed message part.
