Re: Mesos Web UI

[Adam Bordelon]

Backported to 0.28.x and 0.27.x. The relevant change/typo wasn't introduced
until 0.27.x, so I left 0.26.x alone.

On Fri, Apr 29, 2016 at 9:57 AM, Vinod Kone  wrote:

> Adam, since you committed this, feel free to backport it to the relevant
> stable branches (26.x, 27.x, 28.x). They will be included in the next patch
> releases.
>
> On Fri, Apr 29, 2016 at 9:31 AM, Gilbert Song 
> wrote:
>
>> Julian, since the fix was after 0.28, could you try it again by applying
>> the patch @haosdent provided, or try with mesos master head?
>>
>> On Fri, Apr 29, 2016 at 8:52 AM, Julian Gonzalez Llorente <
>> jgonza...@medallia.com> wrote:
>>
>>> Hello list,
>>>
>>> I found one little error on the web UI of mesos.
>>> In the "Slaves" tab there are a table with the columns: ID, Host, CPUs,
>>> Mem, Disk, Registered and Re-Registered.
>>> But in the "Offers" tab there is two times Mem. : ID, Framework, Host,
>>> Cpus, Mem, Mem.
>>> The second Mem should be Disk instead.
>>>
>>> I suppose that should be easy to fix.
>>>
>>> Regards,
>>> Julian
>>>
>>
>>
>

Re: Mesos Web UI

[Vinod Kone]

Adam, since you committed this, feel free to backport it to the relevant
stable branches (26.x, 27.x, 28.x). They will be included in the next patch
releases.

On Fri, Apr 29, 2016 at 9:31 AM, Gilbert Song  wrote:

> Julian, since the fix was after 0.28, could you try it again by applying
> the patch @haosdent provided, or try with mesos master head?
>
> On Fri, Apr 29, 2016 at 8:52 AM, Julian Gonzalez Llorente <
> jgonza...@medallia.com> wrote:
>
>> Hello list,
>>
>> I found one little error on the web UI of mesos.
>> In the "Slaves" tab there are a table with the columns: ID, Host, CPUs,
>> Mem, Disk, Registered and Re-Registered.
>> But in the "Offers" tab there is two times Mem. : ID, Framework, Host,
>> Cpus, Mem, Mem.
>> The second Mem should be Disk instead.
>>
>> I suppose that should be easy to fix.
>>
>> Regards,
>> Julian
>>
>
>

Re: Mesos Web UI

[Gilbert Song]

Julian, since the fix was after 0.28, could you try it again by applying
the patch @haosdent provided, or try with mesos master head?

On Fri, Apr 29, 2016 at 8:52 AM, Julian Gonzalez Llorente <
jgonza...@medallia.com> wrote:

> Hello list,
>
> I found one little error on the web UI of mesos.
> In the "Slaves" tab there are a table with the columns: ID, Host, CPUs,
> Mem, Disk, Registered and Re-Registered.
> But in the "Offers" tab there is two times Mem. : ID, Framework, Host,
> Cpus, Mem, Mem.
> The second Mem should be Disk instead.
>
> I suppose that should be easy to fix.
>
> Regards,
> Julian
>

Re: Mesos Web UI

[haosdent]

Yes, it has already fixed in https://reviews.apache.org/r/44888/

On Fri, Apr 29, 2016 at 11:52 PM, Julian Gonzalez Llorente <
jgonza...@medallia.com> wrote:

> Hello list,
>
> I found one little error on the web UI of mesos.
> In the "Slaves" tab there are a table with the columns: ID, Host, CPUs,
> Mem, Disk, Registered and Re-Registered.
> But in the "Offers" tab there is two times Mem. : ID, Framework, Host,
> Cpus, Mem, Mem.
> The second Mem should be Disk instead.
>
> I suppose that should be easy to fix.
>
> Regards,
> Julian
>



-- 
Best Regards,
Haosdent Huang

Mesos Web UI

[Julian Gonzalez Llorente]

Hello list,

I found one little error on the web UI of mesos.
In the "Slaves" tab there are a table with the columns: ID, Host, CPUs,
Mem, Disk, Registered and Re-Registered.
But in the "Offers" tab there is two times Mem. : ID, Framework, Host,
Cpus, Mem, Mem.
The second Mem should be Disk instead.

I suppose that should be easy to fix.

Regards,
Julian

Re: configuring framework id/task id for mesos web ui/logs

[haosdent]

As I know, Mesos don't support this. You could fill out a ticket in
https://issues.apache.org/jira/browse/MESOS if you think this requirement
is necessary.

On Wed, Mar 9, 2016 at 4:15 AM, Haripriya Ayyalasomayajula <
aharipriy...@gmail.com> wrote:

> All,
>
> Currently, mesos web ui I have on a cluster shows the framework generated
> id and task id. It gets difficult to distinguish different frameworks - Is
> it possible to configure these fields? for ex: I am running Spark and
> another framework on Marathon. Is there any setting I can change to reflect
> the ids displayed say with "spark-"as a prefix etc?
>
>
> Also, can we turn on a similar setting for the logs?
>
> Currently we are using the default -
>
> in directory of the form slave-X/fw-Y/Z, where X is the slave ID, Y is
> the framework ID, and multiple subdirectories Z are created for each
> attempt to run an executor for the framework.
>
> ex-
>
>
> /tmp/mesos/slaves/20150810-152945-201369792-5050-970-S5/frameworks/20150729-132646-201369792-5050-43093-0011/executors/2015-224-13-44-25.017283.3eb36779-40f8-11e5-94ec-0001010b/runs/latest
>
> With multiple frameworks, it gets hard to debug. Is there a way I can
> configure the slave Id/ framework id, executor ids?
>
> I appreciate your help - Thanks.
> --
> Regards,
> Haripriya Ayyalasomayajula
>
>


-- 
Best Regards,
Haosdent Huang

configuring framework id/task id for mesos web ui/logs

[Haripriya Ayyalasomayajula]

All,

Currently, mesos web ui I have on a cluster shows the framework generated
id and task id. It gets difficult to distinguish different frameworks - Is
it possible to configure these fields? for ex: I am running Spark and
another framework on Marathon. Is there any setting I can change to reflect
the ids displayed say with "spark-"as a prefix etc?


Also, can we turn on a similar setting for the logs?

Currently we are using the default -

in directory of the form slave-X/fw-Y/Z, where X is the slave ID, Y is the
framework ID, and multiple subdirectories Z are created for each attempt to
run an executor for the framework.

ex-

/tmp/mesos/slaves/20150810-152945-201369792-5050-970-S5/frameworks/20150729-132646-201369792-5050-43093-0011/executors/2015-224-13-44-25.017283.3eb36779-40f8-11e5-94ec-0001010b/runs/latest

With multiple frameworks, it gets hard to debug. Is there a way I can
configure the slave Id/ framework id, executor ids?

I appreciate your help - Thanks.
-- 
Regards,
Haripriya Ayyalasomayajula

Mesos web ui sandbox help

[betarvel]

Hi guys,

I spend too much time on the issue about showing sandbox stdout, stderr log on 
my own mesos framework (under the webapp). My requirement is simple: The user 
can check the log information of a specified task at any time on our own web 
app but not on the mesos web ui.
 
At last, I can not find a highly avaliable approach for this. I did some 
research on other open source mesos frameworks. Here is the status:

Mesos web-ui: support showing logs
 
Chronos: do not support showing logs.

Marathon: do not support showing logs,  but the issue list on marathon-ui 
provided a approach for making up the url from mesos web-ui and putting a “a” 
tag link on web page (just a redirect to the mesos web ui sandbox page).   

Aurora: support showing logs by a heavy approach via theremos.

Singularity: do not support showing logs, but implementing a independent server 
on each slave for Logstash



Some one said it’s duplicated with what the mesos web-ui support. But I found 
that:

1. The log files are stored at each slaves.

2. The slave ID will automatically change  if the slaves restart after a long 
while from the last crash. Then,  the sandbox page url of the previous task 
will be unvalid. But the log files of the previous task are really still on the 
file system where the slaves matched. 

3. I can not find a way to make the slave ID fixed.

4. The mesos frameworks can not depend on this if the mesos cluster or even the 
target slave crashed.

5. If we can accept the 4th point. Is there some other suggestion I can adopt? 



Sorry for my poor english.  Thanks.



Mail From Tian


 

Re: Mesos web ui sandbox help

[haosdent]

Hello, @betarvel. As I know, /files/read.json would check the permission.
If the old slave is stop and start a new slave in same machine, we could
not get the log content through /files/read.json although the stdout/stderr
of tasks in old slave is still exists.

So how about send the tasks log to your log collect tool like
logstash/scribed when slave is alive? And let the log query is not depends
on mesos?

On Fri, Aug 7, 2015 at 5:05 PM, betarvel betar...@outlook.com wrote:

 Hi guys,

 I spend too much time on the issue about showing sandbox stdout, stderr
 log on my own mesos framework (under the webapp). My requirement is simple:
 The user can check the log information of a specified task at any time on
 our own web app but not on the mesos web ui.

 At last, I can not find a highly avaliable approach for this. I did some
 research on other open source mesos frameworks. Here is the status:

 Mesos web-ui: support showing logs

 Chronos: do not support showing logs.

 Marathon: do not support showing logs,  but the issue list on marathon-ui
 provided a approach for making up the url from mesos web-ui and putting a
 “a” tag link on web page (just a redirect to the mesos web ui sandbox
 page).

 Aurora: support showing logs by a heavy approach via theremos.

 Singularity: do not support showing logs, but implementing a independent
 server on each slave for Logstash



 Some one said it’s duplicated with what the mesos web-ui support. But I
 found that:

 1. The log files are stored at each slaves.

 2. The slave ID will automatically change  if the slaves restart after a
 long while from the last crash. Then,  the sandbox page url of the previous
 task
 will be unvalid. But the log files of the previous task are really still
 on the file system where the slaves matched.

 3. I can not find a way to make the slave ID fixed.

 4. The mesos frameworks can not depend on this if the mesos cluster or
 even the target slave crashed.

 5. If we can accept the 4th point. Is there some other suggestion I
 can adopt?



 Sorry for my poor english.  Thanks.



 Mail From Tian








-- 
Best Regards,
Haosdent Huang