🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Publish block when over the memory / disk threshold
There is a feature (https://www.rabbitmq.com/alarms.html) RabbitMQ will block connections that publish messages when over the memory/disk threshold.
I see there is a way to set the threshold in solace: https://docs.solace.com/Monitoring/Configuring-System-Event-Thresholds.htm
But are there similar feature that can block publication or notify client in solace? any guideline?
Thanks in advance
Best Answer
-
Hi @Elaine ,
About memory thresholds: This is not needed, because the Solace broker pod requires all the memory during startup that is needed at maximum for operations.
About disk threshold:
I'm assuming, you're talking about persistent messaging (Solace calls this "guaranteed messaging") where each message is persisted to disk before broker sends back an ACK to the publisher.If disk space is exhausted and the message can't be persisted to disk, there will be a negative ACK back to the publisher to inform the publisher about that condition.
There is another "special case" for it:
If overall disk space is good, but one (of possible multiple) queues, that would receive that message, are over queue-quota, you can set "reject-msg-to-sender-on-discard" to inform the publisher. (for details see here: )
Does that answer your questions ?Uli
1
Answers
-
Hi @Elaine ,
About memory thresholds: This is not needed, because the Solace broker pod requires all the memory during startup that is needed at maximum for operations.
About disk threshold:
I'm assuming, you're talking about persistent messaging (Solace calls this "guaranteed messaging") where each message is persisted to disk before broker sends back an ACK to the publisher.If disk space is exhausted and the message can't be persisted to disk, there will be a negative ACK back to the publisher to inform the publisher about that condition.
There is another "special case" for it:
If overall disk space is good, but one (of possible multiple) queues, that would receive that message, are over queue-quota, you can set "reject-msg-to-sender-on-discard" to inform the publisher. (for details see here: )
Does that answer your questions ?Uli
1
