[jira] [Commented] (GEODE-66) exporting cluster-config does not export resource-manager settings

["Jinmei Liao (JIRA)" <ji...@apache.org>]

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

Jinmei Liao commented on GEODE-66:
----------------------------------

the resource-manager element is there on a server cache xml, but when saved as cluster configuration, it's not. This somewhat makes sense since the eviction-heap-percentage is a per server configuration (set when starting a server), and different server may have different resource managers. It wouldn't be right to export a "per server configuration" to be part of the cluster configuration.

If we have a command that would impose a cluster-level resource management over all servers, then we probably should export that to the cluster configuration.

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