Diane Hardman created GEODE-6217:
------------------------------------

             Summary: Region created with --group option does NOT get saved in 
cluster config
                 Key: GEODE-6217
                 URL: https://issues.apache.org/jira/browse/GEODE-6217
             Project: Geode
          Issue Type: Bug
          Components: configuration
            Reporter: Diane Hardman


I have created a server in a group and then created a region to only be put on 
servers in that group. When I then export cluster config to my screen, the 
region is not shown.

Here are the steps to reproduce:

```

gfsh>start locator --name=locator1 

gfsh>configure pdx --read-serialized=true 
--auto-serializable-classes=io.pivotal.gemfire.demo.entity.*

gfsh>start server --name=server1 --group=PersonGroup

#NOTE: this second server is NOT in the group

gfsh>start server --name=server2 --server-port=40405   

#NOTE: the describe server commands show one server is in the group, the other 
not

gfsh>describe member --name=server1

Name        : server1

Id          : 172.17.0.2(server1:1257)<v1>:41001

Host        : gpdb.pivotal.io

Regions     : 

PID         : 1257

Groups      : PersonGroup

Used Heap   : 74M

Max Heap    : 1324M

Working Dir : /root/demo/server1

Log file    : /root/demo/server1/server1.log

Locators    : 172.17.0.2[10334]

 

Cache Server Information

Server Bind              : 

Server Port              : 40404

Running                  : true

Client Connections       : 0

 

gfsh>describe member --name=server2

Name        : server2

Id          : 172.17.0.2(server2:1348)<v2>:41002

Host        : gpdb.pivotal.io

Regions     : 

PID         : 1348

Groups      : 

Used Heap   : 50M

Max Heap    : 1324M

Working Dir : /root/demo/server2

Log file    : /root/demo/server2/server2.log

Locators    : 172.17.0.2[10334]

 

Cache Server Information

Server Bind              : 

Server Port              : 40405

Running                  : true

Client Connections       : 0

#Now create a new region for the server group; i.e. only add the region to 
server1

gfsh>create region --name=Parent --type=PARTITION --redundant-copies=1 
--group=PersonGroup

Member  | Status | Message

------- | ------ | -------------------------------------

server1 | OK     | Region "/Parent" created on "server1"

 

 

 

 

Changes to configuration for group 'PersonGroup' are persisted.

gfsh>describe region --name=Parent

..........................................................

Name            : Parent

Data Policy     : partition

Hosting Members : server1

 

Non-Default Attributes Shared By Hosting Members 

 

  Type    |       Name       | Value

--------- | ---------------- | ---------

Region    | size             | 0

          | data-policy      | PARTITION

Partition | redundant-copies | 1

#Add another region without the server group so it's stored on both servers

gfsh>create region --name=LargeRegion --type=PARTITION --redundant-copies=0

Member  | Status | Message

------- | ------ | ------------------------------------------

server1 | OK     | Region "/LargeRegion" created on "server1"

server2 | OK     | Region "/LargeRegion" created on "server2"

 

 

 

 

Changes to configuration for group 'cluster' are persisted.

#Now export cluster config to the screen:

gfsh>export cluster-configuration

cluster.xml: 

<?xml version="1.0" encoding="UTF-8" standalone="no"?><cache version="1.0" 
xsi:schemaLocation="http://geode.apache.org/schema/lucene 
http://geode.apache.org/schema/lucene/lucene-1.0.xsd 
http://geode.apache.org/schema/cache 
http://geode.apache.org/schema/cache/cache-1.0.xsd 
http://geode.apache.org/schema/jdbc 
http://geode.apache.org/schema/jdbc/jdbc-1.0.xsd gpdb 
http://schema.pivotal.io/gemfire/gpdb/gpdb-3.3.xsd gpdb 
http://schema.pivotal.io/gemfire/gpdb/gpdb-3.3.xsd"; 
xmlns="http://geode.apache.org/schema/cache"; 
xmlns:gpdb="http://schema.pivotal.io/gemfire/gpdb"; 
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";>

    <pdx read-serialized="true" ignore-unread-fields="false" persistent="false">

        <pdx-serializer>

            
<class-name>org.apache.geode.pdx.ReflectionBasedAutoSerializer</class-name>

            <parameter name="classes">

                <string>io.pivotal.gemfire.demo.entity.*</string>

            </parameter>

        </pdx-serializer>

    </pdx>

    <jndi-bindings>

        <jndi-binding 
connection-url="jdbc:postgresql://localhost:5432/gemfire_db" 
jndi-name="datasource" password="changeme" type="SimpleDataSource" 
user-name="g2c_user"/>

    </jndi-bindings>

    <region name="LargeRegion">

        <region-attributes concurrency-level="16" data-policy="partition" 
enable-async-conflation="false" enable-subscription-conflation="false" 
multicast-enabled="false" disk-synchronous="true" statistics-enabled="false" 
cloning-enabled="false" concurrency-checks-enabled="true" off-heap="false">

            <partition-attributes local-max-memory="null" recovery-delay="null" 
redundant-copies="0" startup-recovery-delay="null" total-max-memory="null" 
total-num-buckets="null"/>

        </region-attributes>

    </region>

    <gpdb:gpfdist port="8000:8001"/>

</cache>

#The exported cluster config shows LargeRegion but NOT Parent region. 

```



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to