- **summary**: ntf: saNtfNotificationSend take a lot of time and may timeout
--> ntf: saNtfNotificationSend take time due to write to log file error with
try again
- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -1 +1,10 @@
-Ntf need to write all notification in the queue to the log file, if there are
some notification in the queue. But in meanwhile, ntf get write callback with
writting notification fail with TRY_AGAIN error , it push this notification
again to the queue. This may cause the ntf take a lot of time to empty this
queue if there are a lot of notification in the list and the writing to log
file also is timeout due to
+With api "saNtfNotificationSend " , NTF writes the notificaion to the log
file. In case, the writing notification fail with TRY_AGAIN error for long
time. due to issue in the disk... LOG service will return in callback with
TRY_AGAIN and NTF will push this notification again to one list. If the log
service return try again for long time, the list is going to very BIG.
+Everytime NTFD process for "saNtfNotificationSend ", it will write all the
notifications in the queue first then write the notification of the request.
+
+
+If so, NTFD will take a lot of time and be delayed due to:
+ + Take time to handle a lot of write callback with TRY_AGAIN error. Push the
notification back to list
+ + Take time to write all notificaion in the very big list
+
+
+During NTFD is delayed, a lot of request come to and be pushed in mbx. if
NTFD doesn't handle the request on time, the request is timeout.
~~~~
- **Type**: defect --> enhancement
---
** [tickets:#2961] ntf: saNtfNotificationSend take time due to write to log
file error with try again**
**Status:** invalid
**Milestone:** 5.18.12
**Created:** Thu Nov 15, 2018 06:52 AM UTC by Canh Truong
**Last Updated:** Fri Nov 23, 2018 07:52 AM UTC
**Owner:** Canh Truong
With api "saNtfNotificationSend " , NTF writes the notificaion to the log file.
In case, the writing notification fail with TRY_AGAIN error for long time. due
to issue in the disk... LOG service will return in callback with TRY_AGAIN and
NTF will push this notification again to one list. If the log service return
try again for long time, the list is going to very BIG.
Everytime NTFD process for "saNtfNotificationSend ", it will write all the
notifications in the queue first then write the notification of the request.
If so, NTFD will take a lot of time and be delayed due to:
+ Take time to handle a lot of write callback with TRY_AGAIN error. Push the
notification back to list
+ Take time to write all notificaion in the very big list
During NTFD is delayed, a lot of request come to and be pushed in mbx. if NTFD
doesn't handle the request on time, the request is timeout.
---
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
