geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jinmei Liao (JIRA)" <>
Subject [jira] [Commented] (GEODE-66) exporting cluster-config does not export resource-manager settings
Date Fri, 08 Jan 2016 00:40:39 GMT


Jinmei Liao commented on GEODE-66:

I understand the need for it, but the fact that resource manager is set per server posses
an issue.  In case a developer has issued these following commands in gfsh:
gfsh>start locator --name=loc1
gfsh>start server --name=server1 --eviction-heap-percentage=90
gfsh>start server --name=server2 --eviction-heap-percentage=80
gfsh>create region --name=usertable --type=PARTITION_REDUNDANT_HEAP_LRU
gfsh>export cluster-configuration

What do you expect to see in the cluster configuration?

> exporting cluster-config does not export resource-manager settings
> ------------------------------------------------------------------
>                 Key: GEODE-66
>                 URL:
>             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
> {code}
> 3. unzip to notice that cluster/cluster.xml does not a resource-manager

This message was sent by Atlassian JIRA

View raw message