[
https://issues.apache.org/jira/browse/GEODE-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5237:
----------------------------------
Labels: pull-request-available (was: )
> DiskAccessException can sometimes state that actual usage is less than
> critical
> -------------------------------------------------------------------------------
>
> Key: GEODE-5237
> URL: https://issues.apache.org/jira/browse/GEODE-5237
> Project: Geode
> Issue Type: Bug
> Components: persistence
> Reporter: Lynn Gallinat
> Assignee: Lynn Gallinat
> Priority: Major
> Labels: pull-request-available
>
> It's possible that GEODE can throw a DiskAccessException stating that the
> current file system usage exceeds the critical threshold, but the exception's
> message states that the file system usage is UNDER the critical threshold, as
> follows. This appears to be only an error in what is logged and GEODE really
> is over critical.
> org.apache.geode.cache.DiskAccessException: For DiskStore: dmDiskStore_3604:
> Critical disk usage threshold exceeded for volume
> /var/vcap/data/scratch/serialParRegHABridgePersistParOffline-0516-200217/vm_2_bridge3_disk_1:
> the file system is 5% full, which exceeds the critical threshold of
> 5.203678%.
> The problem is that GEODE rounds the file system usage before logging it in
> the message in the method DiskUsage.update(float, float), and this can cause
> the problem when it gets rounded down:
> double use = 100.0 * (total - remaining) / total;
> recordStats(total, remaining, elapsed);
> String pct = Math.round(use) + "%"; <=====
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
