This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Event System
Event System

Version management

Difference between version and

At line 1 added 30 lines
!!! Overview
[{$pagename}] is a system which is [event-triggered].
[{$pagename}] may include:
* [Event Monitoring]
* [Event Correlation]
* [Event Sequencer]
* [Event sourcing]
[{$pagename}] is often the [implementation] of [Event-Driven Architecture]
!! [{$pagename}] [eDirectory]
[{$pagename}] within [DHost] for [eDirectory] is where [event] [consumer of services] can register for events and consume them when they occur.
An event handler can be registered as Worker, Inline, or Journal.
The Journal Event queue is expected to report the events in the same order as they occur. With the current Journal Event system, the journal event queue is maintained in memory. If the consumers of the events are slow, or the rate at which events occur is more than the rate at which they can be processed, the Journal queue starts growing. This results in the memory growth of the [NDSD] process.
The Journal [Event System] is modified to allow you to use a combination of memory and disk to maintain events in a queue. This reduces the drastic growth in memory of the [DNSD] process.
Some instances where the events can cause memory growth are:
* [ndstrace] enabled
* [Novell Audit] or [XDAS] enabled
You can control memory growth by enabling Event system caching.
!! [Common Event Format] (CEF)
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop