[
https://issues.apache.org/jira/browse/KUDU-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-1192.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
> Periodically flush glog buffers from a thread
> ---------------------------------------------
>
> Key: KUDU-1192
> URL: https://issues.apache.org/jira/browse/KUDU-1192
> Project: Kudu
> Issue Type: Improvement
> Components: util
> Reporter: Mike Percy
> Assignee: William Li
> Labels: newbie
> Fix For: 1.4.0
>
>
> If a tserver or master is started and there are no live tablets, glog will
> buffer the output indefinitely which prevents startup messages from
> appearing. This is confusing and might look like the server is hung.
> There is a flag called --logbufsecs that controls how long glog will buffer
> data before flushing, but it's lazy; if another log message doesn't come in
> after that time, nothing will trigger the flush. There is no auto-flush
> thread.
> The solution is to run a thread that periodically flushes all of the logs by
> calling google::FlushLogFiles(INFO).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
