[Dockerapi] add redis pubsub handler for broadcasting requests #5310
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FreddleSpl0it
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a pubsub handler in DockerAPI to enable broadcasting requests to multiple DockerAPI containers connected to the same Redis DB. This helps to perform various tasks in a clustered setup.
In the current setup of a mailcow ha, when a mailbox is deleted, only the mails on the host where the deletion request was executed are removed. However, the mails remain on the second host. To address this, if the variable CLUSTERMODE=replication is set in the mailcow.conf file, PHP will utilize Redis pubsub to broadcast the delete request to the DockerAPI of both hosts.