[
https://issues.apache.org/jira/browse/GEODE-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286526#comment-16286526
]
ASF subversion and git services commented on GEODE-3976:
--------------------------------------------------------
Commit 36b4f5b1cb473042f1fe5e8fdc85f9a36129128c in geode's branch
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=36b4f5b ]
Merge pull request #1146 from dschneider-pivotal/feature/GEODE-3976
GEODE-3976: improve exception message
The message in the exception thrown when the disk monitor
detects we have gone critical (i.e. run out of space) will
now also tell why it went critical.
It will either say something like this:
the file system is 2 percent full, which exceeds the critical threshold of 1.9
percent.
or something like this:
the file system only has 98 bytes free which is below the minimum of 1048576.
Also added unit test for DiskUsage class.
> Users want more meaningful oplog warning when creating 1GB persistent disk
> --------------------------------------------------------------------------
>
> Key: GEODE-3976
> URL: https://issues.apache.org/jira/browse/GEODE-3976
> Project: Geode
> Issue Type: Improvement
> Components: persistence
> Reporter: Fred Krone
> Assignee: Darrel Schneider
>
> Documentation: creating a server with 1GB persistent disk fails because
> GemFire creates a 1GB oplog by default
> When a 1GB persistent disk is created an obscure gemfire error message:
> DiskStore: DEFAULT: Critical disk usage threshold exceeded for volume
> /var/vcap/store/gemfire-server/.: 10% full
> at
> org.apache.geode.internal.cache.DiskStoreMonitor$DirectoryHolderUsage.handleStateChange(DiskStoreMonitor.java:393)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
