You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Gang Yan (JIRA)" <ji...@apache.org> on 2019/04/18 20:32:00 UTC
[jira] [Created] (GEODE-6672) when create disk-store in gfsh , the
folder path in cluster-config file is not same as the inputed value
Gang Yan created GEODE-6672:
-------------------------------
Summary: when create disk-store in gfsh , the folder path in cluster-config file is not same as the inputed value
Key: GEODE-6672
URL: https://issues.apache.org/jira/browse/GEODE-6672
Project: Geode
Issue Type: Bug
Components: gfsh
Reporter: Gang Yan
in the latest build.
# start locator
# start server "g1-s1"
# executed gfsh to create disk-store
{code:java}
create disk-store --name=ds1 --dir=./data/persist
{code}
4. in the file system , we can find:
g1-s1 ---server folder
|
-----data
|
--------persist
5. start another server "g2-s2", in the file system, we can find:
g2-s2 ---server folder
|
--------persist
the folder "data" disappeared.
6. and when we executed "export cluster-configuration", we can find:
{code:java}
cluster.xml:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><cache version="1.0" xsi:schemaLocation="http://geode.apache.org/schema/cache http://geode.apache.org/schema/cache/cache-1.0.xsd http://geode.apache.org/schema/lucene http://geode.apache.org/schema/lucene/lucene-1.0.xsd http://geode.apache.org/schema/jdbc http://geode.apache.org/schema/jdbc/jdbc-1.0.xsd" xmlns="http://geode.apache.org/schema/cache" xmlns:lucene="http://geode.apache.org/schema/lucene" xmlns:jdbc="http://geode.apache.org/schema/jdbc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<disk-store name="ds1" auto-compact="true" compaction-threshold="50" allow-force-compaction="false" max-oplog-size="1024" time-interval="1000" write-buffer-size="32768" queue-size="0" disk-usage-warning-percentage="90" disk-usage-critical-percentage="99">
<disk-dirs>
<disk-dir dir-size="2147483647">persist</disk-dir>
</disk-dirs>
</disk-store>
</cache>
{code}
so the configuration stored in Cluster configuration Service is not as same as we inputed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)