Return-Path: X-Original-To: apmail-mesos-user-archive@www.apache.org Delivered-To: apmail-mesos-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 715131857E for ; Fri, 7 Aug 2015 09:07:05 +0000 (UTC) Received: (qmail 56334 invoked by uid 500); 7 Aug 2015 09:07:00 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 56286 invoked by uid 500); 7 Aug 2015 09:07:00 -0000 Mailing-List: contact user-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mesos.apache.org Delivered-To: mailing list user@mesos.apache.org Received: (qmail 56276 invoked by uid 99); 7 Aug 2015 09:07:00 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Aug 2015 09:07:00 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A3CDA19DC8D for ; Fri, 7 Aug 2015 09:06:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.979 X-Spam-Level: ** X-Spam-Status: No, score=2.979 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Gh_NYNwzUT3Q for ; Fri, 7 Aug 2015 09:06:58 +0000 (UTC) Received: from BLU004-OMC4S18.hotmail.com (blu004-omc4s18.hotmail.com [65.55.111.157]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id C673120F17 for ; Fri, 7 Aug 2015 09:06:57 +0000 (UTC) Received: from BLU436-SMTP251 ([65.55.111.137]) by BLU004-OMC4S18.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Fri, 7 Aug 2015 02:06:09 -0700 X-TMN: [J0WY8UuvYDvbJTFD1nuIvPdmRD8Umptx] X-Originating-Email: [betarvel@outlook.com] Message-ID: From: betarvel Content-Type: multipart/alternative; boundary="Apple-Mail=_3A37DC16-E07E-4F86-A849-E4E64673D72B" Subject: Mesos web ui sandbox help Date: Fri, 7 Aug 2015 17:05:57 +0800 To: user@mesos.apache.org MIME-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) X-Mailer: Apple Mail (2.2102) X-OriginalArrivalTime: 07 Aug 2015 09:06:08.0499 (UTC) FILETIME=[4C532430:01D0D0F0] --Apple-Mail=_3A37DC16-E07E-4F86-A849-E4E64673D72B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" 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. =20 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 =20 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 =E2=80=9Ca=E2=80=9D tag link on web page (just a redirect = to the mesos web ui sandbox page). =20 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=E2=80=99s 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=20 will be unvalid. But the log files of the previous task are really still = on the file system where the slaves matched.=20 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?=20 Sorry for my poor english. Thanks. Mail =46rom Tian =20 --Apple-Mail=_3A37DC16-E07E-4F86-A849-E4E64673D72B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8" 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 =E2=80=9Ca=E2=80=9D 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=E2=80=99s 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 =46rom = Tian


 


= --Apple-Mail=_3A37DC16-E07E-4F86-A849-E4E64673D72B--