There's no way to kill a single task through the Mesos control
surfaces, but if you let the "chaos" framework launch tasks as a
privileged user, you can run wild.
On Thu, Feb 25, 2016 at 2:49 PM, Srikanth Viswanathan
> Sorry, ignore my first question. A framework can
Sorry, ignore my first question. A framework can obviously kill tasks. I
was just unsure as to whether it can kill foreign tasks, which leaves only
my second question.
On Thu, Feb 25, 2016 at 5:23 PM, Srikanth Viswanathan
> Appreciate all the responses here. I'll
Appreciate all the responses here. I'll look into `mesos-execute`.
I was thinking about the framework idea in passing but my mesos knowledge
isn't up to scratch yet, so I haven't been able pursue it yet. There are
many questions in my mind w.r.t designing this as a framework:
* Doesn't a
I think you could approximate that tool's behavior with some scripting
plus `mesos-execute` (ships with the distribution) or by writing a
really simple framework that just turns things off.
On Thu, Feb 25, 2016 at 1:14 PM, Srikanth Viswanathan
> Thanks. Craig and
Thanks. Craig and David. I'm curious about the design and use of that tool.
Based on the video, it looks close to what I hope to do.
A web search didn't yield any results about it, however. Does anyone here
know more about the dcos chaos tool?
On Thu, Feb 25, 2016 at
here's a direct link in the video
On Thu, Feb 25, 2016 at 12:17 PM, David Wood wrote:
> The DCOS tutorial mentions a chaos tool at the end of the video. Not sure
> if that's what your looking for, but it might be something to follow up on
The DCOS tutorial mentions a chaos tool at the end of the video. Not sure
if that's what your looking for, but it might be something to follow up on
Computing Systems for Wireless Networks
IBM TJ Watson Research Center
Mail list logo