[
https://issues.apache.org/jira/browse/TS-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841512#comment-13841512
]
Leif Hedstrom commented on TS-1606:
-----------------------------------
[~ymarkovitch] Any updates on this? What should we do with this ? Uri I'm going
to assign this to you for now, maybe you can help too. In particular, there are
no responses to the review questions.
> Log buffers are not flushed periodically when TS is launched with
> NO_REMOTE_MANAGEMENT flag
> -------------------------------------------------------------------------------------------
>
> Key: TS-1606
> URL: https://issues.apache.org/jira/browse/TS-1606
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Affects Versions: 3.3.0, 3.2.0
> Reporter: Yakov Markovitch
> Assignee: Yunkai Zhang
> Fix For: 4.2.0
>
> Attachments: trafficserver-periodic-tasks.patch
>
>
> When TS binary is launched with NO_REMOTE_MANAGEMENT flag (e.g., when
> launched not as a daemon but directly - this is extremely convenient for
> debugging), the PeriodicWakeup event is not scheduled.
> As a result, Log::flush_thread_main() does not wake up periodically, but only
> on log buffer overflow. Coupled with a horribly wrong activation check in
> Log::flush_thread_main():
> {code}
> if (now > last_time) {
> if ((now % PERIODIC_TASKS_INTERVAL) == 0) {
> // We run only when waken up at the moment which is exact
> // multiple of PERIODIC_TASKS_INTERVAL!
> {code}
> this leads to that probability of any log output is low.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
