Set the config value to 100% if you don't wish the check to block before you have actual disk full, but it's actually saving you here from having disk filling fully and giving you a chance to get onto the broker to rectify.
Question is why are you consumers not consuming messages or if you really have that amount of delay or genuine pause in consumption you should increase your disk capacity on sda to meet the requirement, 91% disk usage isn't something to be ignored and simply override the config to let it continue for an hour or two more for then an even more catastrophic issue to occur. Sent from my iPhone > On 29 May 2017, at 09:00, shimix <sima...@gmail.com> wrote: > > Hi guys, > > I have problem with Artemis 2.1.0 + Docker 17.05.0-ce. > > Artemis reports: AMQ222210: Storage usage is beyond max-disk-usage. System > will start blocking producers. > > Docker image disk space: > Filesystem Size Used Avail Use% Mounted on > none 219G 188G 21G 91% / > tmpfs 7.9G 0 7.9G 0% /dev > tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup > /dev/sda1 219G 188G 21G 91% /etc/hosts > shm 64M 0 64M 0% /dev/shm > tmpfs 7.9G 0 7.9G 0% /sys/firmware > > Artemis 1.4.0 worked fine. > > Any idea how to avoid this check? > > Thank you. > Shimix > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Storage-usage-is-beyond-max-disk-usage-tp4726638.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
