Hi, I understand that blocking the producer when address paging is enabled and the disk is full is the intended behavior. I would like to propose considering not only the addressFullMessagePolicy parameter but also the pageFullMessagePolicy when the disk is full and acting accordingly. It seems that addressFullMessagePolicy relates to memory, while pageFullMessagePolicy concerns disk usage.
In my case, the problem looks like this: - Clients should fail fast if there is any problem sending messages and switch to another message broker. - It is impossible to predict message distribution between queues and set page byte limits accurately. - Once the disk usage reaches its limits, clients get blocked for an unknown period of time, without any possibility to redirect messages to another broker. - Changing the addressFullMessagePolicy to FAIL would stop message paging. Regards Iliya Grushevskiy
