[
https://issues.apache.org/jira/browse/MESOS-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380010#comment-14380010
]
Joerg Schad commented on MESOS-2323:
------------------------------------
In my opinion the Json output is ok for the following reason:
1. it is shown only once when starting the master/slave
2. unlike other information in the log (where is might just skim over to find
and Error or Failed message) the slave information is only relevant after a
crash/failure (otherwise I could also query the state.json). In such case I
don't mind using a json parser (or at least spending some more effort)
3. Otherwise (i.e. one line per flag) as you mentioned the output is just too
long. And (as said before) this log message is supposed to be used for
debugging a crashed/failed master/slave, hence after an issue occurred. imagine
some (potentially new) user having a problem and sending you hist log files....
But maybe other people have another opinion on this... [~drobinson]?
> write flags to log at startup
> -----------------------------
>
> Key: MESOS-2323
> URL: https://issues.apache.org/jira/browse/MESOS-2323
> Project: Mesos
> Issue Type: Improvement
> Reporter: David Robinson
> Assignee: Joerg Schad
> Priority: Minor
>
> Whilst troubleshooting problems it's sometimes useful to see the exact flags
> that were set when Mesos started. The flags are exposed via the /state.json
> endpoint whilst Mesos is running, but it's not possible to know exactly what
> flags were set during a previous run. Writing this information to the logs
> during startup would make troubleshooting problems much easier.
> Some of the flag's settings can be inferred from log entries, but some, such
> as --attributes can not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
