OpenSAF / Tickets / #3106 dtm: flush the logtrace asap when the logtrace owner is terminated

Description has changed:

Diff:

--- old
+++ new
@@ -2,6 +2,6 @@
 1) The size of trace buffer is big enough
 2) It is over 15second from last flush

-So, there is a possibility of losing traces from trace files when the logtrace owner process is terminated, and short time later the node is rebooted; and the reboot happens before the logtrace server does the flush.
+So, there is a possibility of losing traces from trace files when the logtrace owner process is terminated, and short time later the node is rebooted before the logtrace server does the flush.

 This ticket adds a machanism in logtrace server, so that it can detect the logtrace owner terminated and do the flush right away to avoid losing traces.

Description has changed:

Diff:

--- old
+++ new
@@ -1,7 +1 @@
-Logtrace server flushes traces from its own buffers into trace files in two cases:
-1) The size of trace buffer is big enough
-2) It is over 15second from last flush
-
-So, there is a possibility of losing traces from trace files when the logtrace owner process is terminated, and short time later the node is rebooted before the logtrace server does the flush.
-
-This ticket adds a machanism in logtrace server, so that it can detect the logtrace owner terminated and do the flush right away to avoid losing traces.
+This ticket will add a machanism in logtrace server, so that it can detect the logtrace owner terminated and does the flush right away to avoid losing traces from trace files.

Vu Minh Nguyen - 2019-10-25

status: assigned --> review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gary Lee - 2020-02-15

Milestone: 5.20.02 --> 5.20.05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gary Lee - 2020-05-30

Milestone: 5.20.05 --> 5.20.08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gary Lee - 2020-08-31

Milestone: 5.20.08 --> 5.20.11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gary Lee - 2020-12-01

Milestone: 5.20.11 --> 5.21.03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gary Lee - 2021-03-01

Milestone: 5.21.03 --> 5.21.06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gary Lee - 2021-06-01

Milestone: 5.21.06 --> 5.21.10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gary Lee - 2021-09-14

Milestone: 5.21.09 --> future
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Thien Minh Huynh - 2022-11-04

assigned_to: Vu Minh Nguyen --> Thien Minh Huynh
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Thien Minh Huynh - 2023-02-21

status: review --> fixed

Milestone: future --> 5.23.03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Thien Minh Huynh - 2023-02-21

commit 9c34b746228c65f96bb894082c910ac59cc951ef (HEAD -> develop, origin/develop, ticket-3106)
Author: thien.m.huynh thien.m.huynh@dektech.com.au
Date: Fri Oct 25 15:18:06 2019 +0700

dtm: flush logtrace asap when logtrace owner is terminated [#3106] To avoid the risk of losing traces, logtrace server should flush traces as soon as possible when logtrace owner is terminated. This patch also refactors LogServer::Run().
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

dtm: flush the logtrace asap when the logtrace owner is terminated

Milestone

Searches

Help

#3106 dtm: flush the logtrace asap when the logtrace owner is terminated

Related

Discussion