You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2017/12/08 00:44:00 UTC

[jira] [Commented] (GEODE-3976) Users want more meaningful oplog warning when creating 1GB persistent disk

    [ https://issues.apache.org/jira/browse/GEODE-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282817#comment-16282817 ] 

Darrel Schneider commented on GEODE-3976:
-----------------------------------------

What is triggering this is not actual disk usage but a check that a minimum amount of free space is available.
By default the DiskStoreMonitor makes sure that at least this much free space exists (in megabytes): 20 + maxOplogSIze.
The "20" can be changed using this system property: "gemfire.MIN_DISK_SPACE_FOR_LOGS".
In this case their maxOplogSize is 1G and the file system is 1G so this check immediately fails (1G+20m is always greater than 1G).

The code that creates this obscure message is not told why we have gone critical; just that we have.
If we pass along to it that the minimum was not available then a better message can be given.

> 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
>
> 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)