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

xiaojian zhou commented on GEODE-6514:
--------------------------------------

Discussed with Jen, it looks like gfsh followed the same behavior of java API. 
So it maybe should be kept as is?

> gfsh does not allow to create an region with PARTITION_PROXY if other member 
> specified different bucketNum
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6514
>                 URL: https://issues.apache.org/jira/browse/GEODE-6514
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh
>            Reporter: xiaojian zhou
>            Priority: Major
>
> run following gfsh commands:
> start server --group=bridge
> start server --group=listen --server-port=40405
> create region --total-num-buckets=10 --name=DefaultRegion 
> --local-max-memory=1305 --if-not-exists=true --type=PARTITION --group=bridge
> gfsh>create region --name=DefaultRegion --if-not-exists=true 
> --type=PARTITION_PROXY --group=listen
>         Member         | Status | Message
> ---------------------- | ------ | 
> -------------------------------------------------------------------------------------------------------
> jog-uninterested-sigma | ERROR  | The total number of buckets found in 
> PartitionAttributes ( 113 ) is incompatible with the total numbe..
> gfsh>create region --name=DefaultRegion --if-not-exists=true 
> --type=PARTITION_PROXY --group=listen --total-num-buckets=10
>         Member         | Status | Message
> ---------------------- | ------ | 
> -----------------------------------------------------------
> jog-uninterested-sigma | OK     | Region "/DefaultRegion" created on 
> "jog-uninterested-sigma"
> Changes to configuration for group 'listen' are persisted.
> For PARTITION_PROXY region, it should not require to specify 
> "--total-num-buckets=10"



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

Reply via email to