From ce60b64ee1560d0e6f9f4f19b4e860292a235bad Mon Sep 17 00:00:00 2001 From: spenugondaa Date: Mon, 19 Apr 2021 18:24:35 -0700 Subject: [PATCH] removed few lines from eventd warm boot support that are not applicable Signed-off-by: spenugondaa --- doc/event-alarm-framework/event-alarm-framework.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/doc/event-alarm-framework/event-alarm-framework.md b/doc/event-alarm-framework/event-alarm-framework.md index a188cdbb5e..20302eb1ea 100644 --- a/doc/event-alarm-framework/event-alarm-framework.md +++ b/doc/event-alarm-framework/event-alarm-framework.md @@ -1071,9 +1071,6 @@ They would Records from applications are stored in a table, called EVENTPUBSUB. By using table of type ProducerTable, records that are being written will be queued when the consumer (eventd) is down. -The eventnotify from each application would write events to EVENTPUBSUB table that eventd subscribes to. -eventnotify uses event-id and a local sequence-id as the key while writing records to this table. - During normal operation, eventd reads, processes whenever a new record is added to the table. When eventd is restarted, events and alarms raised by applications will be waiting in a queue while eventd is coming up.