You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bradford D. Boyle (JIRA)" <ji...@apache.org> on 2018/09/11 18:25:00 UTC
[jira] [Created] (GEODE-5727) Export cluster-configuration does not
work filename only
Bradford D. Boyle created GEODE-5727:
----------------------------------------
Summary: Export cluster-configuration does not work filename only
Key: GEODE-5727
URL: https://issues.apache.org/jira/browse/GEODE-5727
Project: Geode
Issue Type: Bug
Components: gfsh
Reporter: Bradford D. Boyle
Fix For: 1.7.0
Using the latest Geode snapshot (aaac1e5cefe6ad7ca533a7ca87eef9dd779912e4), exporting cluster config with only a filename (no path) results in an error:
{code}
gfsh> start locator
gfsh> start server
gfsh> create region --name=test --type=PARTITION
gfsh> export cluster-configuration --zip-file-name=cluster-config.zip
Could not process command due to error. null
{code}
It does (sort of) work if you use a path:
{code}
gfsh> start locator
gfsh> start server
gfsh> create region --name=test --type=PARTITION
gfsh> export cluster-configuration --zip-file-name=./cluster-config.zip
{code}
However, it appears that the cluster config file is written to both the specified path and the current working directory.
{code}
gfsh > export cluster-configuration --zip-file-name=/tmp/cluster-config.zip
{code}
{code}
$ md5 /tmp/cluster-config.zip cluster-config.zip
MD5 (/tmp/cluster-config.zip) = 50022493fa54f54da700adfc1a8f709c
MD5 (cluster-config.zip) = 50022493fa54f54da700adfc1a8f709c
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)