[
https://issues.apache.org/jira/browse/MESOS-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380836#comment-14380836
]
Joerg Schad commented on MESOS-2323:
------------------------------------
How do you feel about the following output format: single line and same format
as for specifying flags, therefore allowing copy/paste of flags?
0325 22:07:38.684937 373452800 master.cpp:358] Master
20150325-220738-2315653804-5050-48844 (172.18.6.138) started on
172.18.6.138:5050
I0325 22:07:38.684963 373452800 master.cpp:360] Flags at startup:
--allocation_interval="1secs" --authenticate="false"
--authenticate_slaves="false" --authenticators="crammd5"
--framework_sorter="drf" --help="false" --initialize_driver_logging="true"
--log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
--port="5050" --quiet="false" --recovery_slave_removal_limit="100%"
--registry="replicated_log" --registry_fetch_timeout="1mins"
--registry_store_timeout="5secs" --registry_strict="false"
--root_submissions="true" --slave_reregister_timeout="10mins"
--user_sorter="drf" --version="false"
--webui_dir="/Users/joergschad/mesos/build/../src/webui"
--work_dir="/tmp/mesos" --zk_session_timeout="10secs"
I0325 22:07:38.685098 373452800 master.cpp:407] Master allowing unauthenticated
frameworks to register
> 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)
