Thank you for your answers!
On Tue, Jan 13, 2015 at 5:15 PM, Tim Chen <[email protected]> wrote:
> You can get the slave_id, framework_id and executor_id of a task all from
> state.json.
>
> ie:
>
>
> - {
> - executor_id: "20141231-115728-16777343-5050-49193-S0",
> - framework_id: "20141231-115728-16777343-5050-49193-0000",
> - id: "1",
> - labels: [ ],
> - name: "Task 1",
> - resources:
> {
> - cpus: 6,
> - disk: 0,
> - mem: 13312
> },
> - slave_id: "20141231-115728-16777343-5050-49193-S0",
> - state: "TASK_KILLED",
> - statuses:
> [
> -
> {
> - state: "TASK_RUNNING",
> - timestamp: 1420056049.88177
> },
> -
> {
> - state: "TASK_KILLED",
> - timestamp: 1420056124.66483
> }
> ]
> },
>
>
> On Tue, Jan 13, 2015 at 1:48 PM, David Greenberg <[email protected]>
> wrote:
>
>> I was trying to figure out how to programmatically access a task's stdout
>> & stderr, and I don't fully understand how the URL is constructed. It seems
>> to be of the form http://
>> $slave_url:5050/read.json?$work_dir/work/slaves/$slave_id/frameworks/$framework_id/executors/$executor_id/runs/$something
>>
>> What is the $something? Is there an easier way, given just the task_id,
>> to find where the output is?
>>
>> Thanks,
>> David
>>
>
>
