I'm trying to decouple a Docker image from a configuration file used by the image. The intent is to keep the image fairly generic. The issue is that the application configuration varies slightly due to clustering (there's a master as well as workers). At first I thought I could create two configs-- one for the master and one for the workers and then use a template to examine a node label and include the correct config based on the label. This doesn't seem to work. Any recommendations for conditionally including a config?
Paul Calabro's questions
I have a network of brokers configured as such:
- Broker A <=> Broker B
- Broker B <=> Broker C
- Broker A <=> Broker C
I've noticed that in the "Network" tab under "Network Bridges" it lists a table with this information:
- Remote Broker
- Remote Address
- Created By Duplex
- Messages Enqueued
I've noticed that my enqueue counts are significantly higher than my dequeue counts for each network broker. What's the best way to go about identifying the root cause?
One comment to add is, at times there are messages in the DLQ on each broker for messages that were unable to be processed. When a message is tossed in the DLQ of a remote broker, could this explain why the enqueue number grows, but the dequeue number does not?
A Postfix server was given to me with a transport.db file, but no original transport file from which it was derived? How do I determine what the original contents of the transport file were?