[tickets] [opensaf:tickets] #3106 dtm: flush the logtrace asap when the logtrace owner is terminated
- 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. --- ** [tickets:#3106] dtm: flush the logtrace asap when the logtrace owner is terminated** **Status:** assigned **Milestone:** 5.20.01 **Created:** Thu Oct 24, 2019 03:57 AM UTC by Vu Minh Nguyen **Last Updated:** Thu Oct 24, 2019 04:06 AM UTC **Owner:** Vu Minh Nguyen 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. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [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. --- ** [tickets:#3106] dtm: flush the logtrace asap when the logtrace owner is terminated** **Status:** assigned **Milestone:** 5.20.01 **Created:** Thu Oct 24, 2019 03:57 AM UTC by Vu Minh Nguyen **Last Updated:** Thu Oct 24, 2019 03:57 AM UTC **Owner:** Vu Minh Nguyen 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. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #3106 dtm: flush the logtrace asap when the logtrace owner is terminated
--- ** [tickets:#3106] dtm: flush the logtrace asap when the logtrace owner is terminated** **Status:** assigned **Milestone:** 5.20.01 **Created:** Thu Oct 24, 2019 03:57 AM UTC by Vu Minh Nguyen **Last Updated:** Thu Oct 24, 2019 03:57 AM UTC **Owner:** Vu Minh Nguyen 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; and the reboot happens 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. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
