You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jinmei Liao (JIRA)" <ji...@apache.org> on 2016/01/07 17:19:39 UTC
[jira] [Assigned] (GEODE-66) exporting cluster-config does not
export resource-manager settings
[ https://issues.apache.org/jira/browse/GEODE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jinmei Liao reassigned GEODE-66:
--------------------------------
Assignee: Jinmei Liao
> exporting cluster-config does not export resource-manager settings
> ------------------------------------------------------------------
>
> Key: GEODE-66
> URL: https://issues.apache.org/jira/browse/GEODE-66
> Project: Geode
> Issue Type: Bug
> Components: management
> Reporter: Swapnil Bawaskar
> Assignee: Jinmei Liao
> Priority: Minor
>
> When a server is started using gfsh with eviction and/or critical heap percentages specified, and we later do a export cluster-configuration, the eviction threshold is not reflected in the cluster config zip archive.
> To reproduce:
> 1. Start a locator and a server and create some regions:
> {code}
> gfsh>start locator --name=loc1
> gfsh>start server --name=server1 --eviction-heap-percentage=90
> gfsh>create region --name=usertable --type=PARTITION_REDUNDANT_HEAP_LRU
> {code}
> 2. export the cluster configuration:
> {code}
> gfsh>export cluster-configuration --zip-file-name=cluster-config.zip
> {code}
> 3. unzip cluster-config.zip to notice that cluster/cluster.xml does not a resource-manager element.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)