You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found through the report on #725 (comment).
Now when warning/error get raised from leo_watchdog, leo_storage execute this code block https://github.com/leo-project/leofs/blob/1.3.4/apps/leo_storage/src/leo_storage_watchdog_sub.erl#L83-L99, as a result leo_mq stop to consume items anymore in case warning/error(s) keep happening around a few minutes. This behavior can be problematic if the warning/error caused by the disk usage as it may take time to ensure more disk capacity or erase unnecessary files.
What happen
batch of msgs get to 0 and will not go up again until the warning/error gone.
leo_watchdog_disk_util for checking the disk utilization via iostat
leo_watchdog_disk_usage for checking the disk usage via df
and define the handle_notify callback function for each of them and make the one for leo_watchdog_disk_usage not to control the rate to consume items in leo_mq.
The text was updated successfully, but these errors were encountered:
Found through the report on #725 (comment).
Now when warning/error get raised from leo_watchdog, leo_storage execute this code block https://github.com/leo-project/leofs/blob/1.3.4/apps/leo_storage/src/leo_storage_watchdog_sub.erl#L83-L99, as a result leo_mq stop to consume items anymore in case warning/error(s) keep happening around a few minutes. This behavior can be problematic if the warning/error caused by the disk usage as it may take time to ensure more disk capacity or erase unnecessary files.
What happen
batch of msgs get to 0 and will not go up again until the warning/error gone.
Solution
We may have to divide leo_watchdog_disk into two
and define the handle_notify callback function for each of them and make the one for leo_watchdog_disk_usage not to control the rate to consume items in leo_mq.
The text was updated successfully, but these errors were encountered: