Re: Escaped characters in the 'env' argument passed to mesos-execute

Yes, need add quotes for --env='{"key": "value"}' flag. On Thu, Jun 30, 2016 at 4:39 AM, Chris Baker wrote: > It's your shell: > > $ echo {"MY_FILEPATH": "/home/john/temp_output/test.csv"} > {MY_FILEPATH: /home/john/temp_output/test.csv} > > On Wed, Jun 29, 2016 at 4:05

On a whim I sync'd my local master branch

And ran the unit tests (through jenkins) [--] Global test environment tear-down [==] 1209 tests from 140 test cases ran. (360352 ms total) [ PASSED ] 1209 tests. YOU HAVE 6 DISABLED TESTS Finished: *SUCCESS* That's a result I hadn't seen in a few days. Good to see the

Re: Escaped characters in the 'env' argument passed to mesos-execute

It's your shell: $ echo {"MY_FILEPATH": "/home/john/temp_output/test.csv"} {MY_FILEPATH: /home/john/temp_output/test.csv} On Wed, Jun 29, 2016 at 4:05 PM June Taylor wrote: > hasodent, > > I admit I don't see much of a difference in your version. Are you saying > that Mesos

Re: Escaped characters in the 'env' argument passed to mesos-execute

hasodent, I admit I don't see much of a difference in your version. Are you saying that Mesos doesn't escape the values, and that our program may be doing that on the executor end? Thanks, June Taylor System Administrator, Minnesota Population Center University of Minnesota On Wed, Jun 29,

Escaped characters in the 'env' argument passed to mesos-execute

Greetings, We are using mesos-execute and passing an argument that contains a Unix filepath, as follows: *mesos-execute --master=cluster.example.com:5050 --name=test-program --command=/home/john/anaconda3/bin/python /home/john/mesos/error_msg.py read

Re: Mesos CLI

https://docs.google.com/document/d/1r6Iv4Efu8v8IBrcUTjgYkvZ32WVscgYqrD07OyIglsA/edit?ts=57573bba# On Wed, Jun 29, 2016 at 9:33 AM Kevin Klues wrote: > Here is a link to the design doc again in case you missed it before. There > is a section at the bottom describing what

Re: Mesos CLI

Here is a link to the design doc again in case you missed it before. There is a section at the bottom describing what equivalent commands would look like in the new design vs the old. Would it be a big burden to update your scripts to use the new format for the commands or would you require strict

Re: Executor downloads for every task

You can use Fetching through the cache to download file only once. śr., 29.06.2016 o 15:19 użytkownik Scott Weiss napisał: > Every time my framework launches a task, it downloads the (custom) > executor from the URI I

Executor downloads for every task

Every time my framework launches a task, it downloads the (custom) executor from the URI I provide. then when the task finishes executing, the framework gets the message Executor lost. this seems to cause the slaves to download the executor binary every time they launch a task. Is there a way to

Re: Mesos CLI

Hi, we're using `mesos tail -f`, `mesos cat`, `mesos ps` quite a lot. It would be nice if you keep those. Is there a document describing changes that you're planning? just few ideas, it would be nice to have a command for: - listing all instances of a given task - join stderr and stdout (for