Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Event Log replication queue OUTQ is full. xxx event(s) is (are) discarded of (total) size xxx.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Cluster Service?
As per Microsoft: "The Cluster Service replicates events from the local node's event log to the event logs of other nodes in the same cluster. Events to be replicated are queued and replicated when possible. If a node cannot process events quickly or if the node is offline, this event may appear in the event log when the maximum queue length is exceeded. By default, event log replication is enabled". See the link to "Windows Cluster Service Troubleshooting and Maintenance" to download the original white paper.
See ME224969 for information on how to configure event log replication in Windows 2000 cluster servers.
See also ME320333.
As per Microsoft: "This issue occurs because server clusters send event log entries from each node to all other nodes in the cluster so that each node has all of the event log entries.". See the link below for more details and resolution.
|Private comment: Subscribers only. See example of private comment|
|Links: ME224969, ME283078, ME320333, Windows Cluster Service Troubleshooting and Maintenance|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated