Jason Huynh created GEODE-8282:
----------------------------------

             Summary: Creating diskstore with size appened to name doesn't seem 
to work as documented
                 Key: GEODE-8282
                 URL: https://issues.apache.org/jira/browse/GEODE-8282
             Project: Geode
          Issue Type: New Feature
            Reporter: Jason Huynh


The create diskstore --dir option is documented with:

...Optionally, directory names may be followed by {{#}} and the maximum number 
of megabytes that the disk store can use in the directory. For example:

{code:java}
--dir=/data/ds1 
--dir=/data/ds2#5000
{code}


When creating a disk store through gfsh with the size appended, it does not 
appear to limit the size of the directory.  There also doesn't seem to be much 
validation...
for example, when using a negative value we can see that the size described 
does not match what we expected to be our limit.

{code:java}
gfsh>describe disk-store --name=diskstore-2#-1000000000000000 --member=server1
Disk Store ID                      : 643cb4b4-3cb0-40ec-b123-6945b23f165a
Disk Store Name                    : diskstore-2#-1000000000000000
Member ID                          : 192.168.0.3(server1:16006)<v1>:41001
Member Name                        : server1
Allow Force Compaction             : No
Auto Compaction                    : Yes
Compaction Threshold               : 50
Max Oplog Size                     : 1024
Queue Size                         : 0
Time Interval                      : 1000
Write Buffer Size                  : 32768
Disk Usage Warning Percentage      : 90.0
Disk Usage Critical Percentage     : 99.0
PDX Serialization Meta-Data Stored : No
                          Disk Directory                            | Size
------------------------------------------------------------------- | ----------
/Users/jhuynh/apache-geode-1.12.0/bin/server1 | 2147483647
{code}


It also appears in code to only affect calculation of disk usage etc, but I 
didn't dig very deep.  If it is used there, the negative value will probably 
mess with that calculation.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to