Skip to content

Latest commit

 

History

History
12 lines (10 loc) · 1.29 KB

HIGH_AVAILABILITY.md

File metadata and controls

12 lines (10 loc) · 1.29 KB

ULS High Availability

This document describes high availability options for the ULS software.
ULS itself does not bring HA capabilities out of the box, but it was built to support different HA techniques.

Docker

To use high availability alongside with the provided ULS docker container, a HA orchestration layer like SWARM, KUBERNETES or others is required.
It is highly recommended, to enable the ULS auto-resume feature and store the according "resume - data" on a persistent volume which is available accross different compute nodes (e.g. PVC, NFS, ...).
This setup allows the ULS container(s) to maintain HA across multiple compute nodes.

Daemon

Whenever container usage isn't an option, high availability can be achieved by using OS-based high availability systems like pacemaker / corosync or heartbeat.
To avoid duplicate events in the SIEM, it is highly recommended to enable the ULS auto-resume feature and store the according "resume - data" on a persistent volume that is available across the designated n odes (e.g. DRBD, NFS, ...).

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy