You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2012/09/07 21:09:07 UTC
[jira] [Created] (MESOS-270) Log viewing broken on mesos-local runs
Benjamin Mahler created MESOS-270:
-------------------------------------
Summary: Log viewing broken on mesos-local runs
Key: MESOS-270
URL: https://issues.apache.org/jira/browse/MESOS-270
Project: Mesos
Issue Type: Bug
Reporter: Benjamin Mahler
Assignee: Benjamin Mahler
The master / slave attach their log files in a hard-coded manner, i.e.
files.attach("mesos-master.INFO")
files.attach("mesos-slave.INFO")
currently we rely on default log filenames from glog, which does not provide access to the filenames, see: http://code.google.com/p/google-glog/issues/detail?id=116
the fix here is to have all the main.cpp's set the log name during logging initialization, and later the master/slave can get the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MESOS-270) Log viewing broken on mesos-local runs
Posted by "Benjamin Mahler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Mahler updated MESOS-270:
----------------------------------
Description:
The master / slave attach their log files in a hard-coded manner, i.e.
files.attach("mesos-master.INFO")
files.attach("mesos-slave.INFO")
and local runs will have "mesos-local.INFO" instead
currently we rely on default log filenames from glog, which does not provide access to the filenames, see: http://code.google.com/p/google-glog/issues/detail?id=116
the fix here is to have all the main.cpp's set the log name during logging initialization, and later the master/slave can get the name
was:
The master / slave attach their log files in a hard-coded manner, i.e.
files.attach("mesos-master.INFO")
files.attach("mesos-slave.INFO")
currently we rely on default log filenames from glog, which does not provide access to the filenames, see: http://code.google.com/p/google-glog/issues/detail?id=116
the fix here is to have all the main.cpp's set the log name during logging initialization, and later the master/slave can get the name
> Log viewing broken on mesos-local runs
> --------------------------------------
>
> Key: MESOS-270
> URL: https://issues.apache.org/jira/browse/MESOS-270
> Project: Mesos
> Issue Type: Bug
> Reporter: Benjamin Mahler
> Assignee: Benjamin Mahler
>
> The master / slave attach their log files in a hard-coded manner, i.e.
> files.attach("mesos-master.INFO")
> files.attach("mesos-slave.INFO")
> and local runs will have "mesos-local.INFO" instead
> currently we rely on default log filenames from glog, which does not provide access to the filenames, see: http://code.google.com/p/google-glog/issues/detail?id=116
> the fix here is to have all the main.cpp's set the log name during logging initialization, and later the master/slave can get the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MESOS-270) Log viewing broken on mesos-local
runs
Posted by "Benjamin Mahler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455518#comment-13455518 ]
Benjamin Mahler commented on MESOS-270:
---------------------------------------
CL: https://reviews.apache.org/r/7061/
> Log viewing broken on mesos-local runs
> --------------------------------------
>
> Key: MESOS-270
> URL: https://issues.apache.org/jira/browse/MESOS-270
> Project: Mesos
> Issue Type: Bug
> Reporter: Benjamin Mahler
> Assignee: Benjamin Mahler
>
> The master / slave attach their log files in a hard-coded manner, i.e.
> files.attach("mesos-master.INFO")
> files.attach("mesos-slave.INFO")
> and local runs will have "mesos-local.INFO" instead
> currently we rely on default log filenames from glog, which does not provide access to the filenames, see: http://code.google.com/p/google-glog/issues/detail?id=116
> the fix here is to have all the main.cpp's set the log name during logging initialization, and later the master/slave can get the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MESOS-270) Log viewing broken on mesos-local
runs
Posted by "Benjamin Mahler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Mahler resolved MESOS-270.
-----------------------------------
Resolution: Fixed
> Log viewing broken on mesos-local runs
> --------------------------------------
>
> Key: MESOS-270
> URL: https://issues.apache.org/jira/browse/MESOS-270
> Project: Mesos
> Issue Type: Bug
> Reporter: Benjamin Mahler
> Assignee: Benjamin Mahler
>
> The master / slave attach their log files in a hard-coded manner, i.e.
> files.attach("mesos-master.INFO")
> files.attach("mesos-slave.INFO")
> and local runs will have "mesos-local.INFO" instead
> currently we rely on default log filenames from glog, which does not provide access to the filenames, see: http://code.google.com/p/google-glog/issues/detail?id=116
> the fix here is to have all the main.cpp's set the log name during logging initialization, and later the master/slave can get the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira