Hello Marco,
The Wazuh cluster plays a crucial role in maintaining synchronization between the master and its worker nodes. In essence, any modifications made to decoders, rules, or lists on the master are automatically propagated to the workers, ensuring that they mirror the exact content of the master. Consequently, even if the master node becomes unavailable, the workers remain fully operational, capable of receiving events and generating alerts.
However, during the period when the master is offline, certain functions are temporarily compromised. Specifically, the ability to synchronize new changes and perform centralized tasks, such as creating groups or modifying group configurations, becomes unavailable. Additionally, using the API is not possible for obvious reasons, resulting in limitations, such as the dashboard being unable to access Wazuh information or perform tasks like restarting agents or managers.
Nonetheless, it's important to note that the cluster continues to function, allowing the querying of all newly indexed alerts originating from the worker nodes, ensuring the ongoing monitoring and detection of security events.
Regards !