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

Jakov Varenina commented on GEODE-10215:
----------------------------------------

Hi [~agingade] ,

After checking this issue in more detail, the procedure described in this 
ticket now doesn't seem correct. I think that it shouldn't be allowed to remove 
the gateway sender with the "alter region" command from a partition region that 
has no colocated sub-regions utilizing the same gateway sender. In this case, 
for me, it only makes sense to destroy the gateway-sender before destroying the 
region. Otherwise, if we use the "alter region" command, we leave the 
gateway-sender and its colocated partition region buckets unnecessarily hanging 
in the system. If we reuse that gateway-sender for the other region, we get the 
issue described in this ticket.

What do you think? Do you see any valid scenario where you would use alter 
region gateway-sender-id="" command for the partition region that doesn't have 
colocated regions?

 

> WAN replication not working after re-creating the partitioned region
> --------------------------------------------------------------------
>
>                 Key: GEODE-10215
>                 URL: https://issues.apache.org/jira/browse/GEODE-10215
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Jakov Varenina
>            Assignee: Jakov Varenina
>            Priority: Major
>
> Steps to reproduce the issue:
> Start multi-site with at least 3 servers on each site. If there are less than 
> three servers then issue will not reproduce.
> Configuration site 1:
> {code:java}
> create disk-store --name=queue_disk_store --dir=ds2
> create gateway-sender -id="remote_site_2" --parallel="true" 
> --remote-distributed-system-id="1"  -enable-persistence=true 
> --disk-store-name=queue_disk_store
> create disk-store --name=data_disk_store --dir=ds1
> create region --name=example-region --type=PARTITION_PERSISTENT 
> --gateway-sender-id="remote_site_2" --disk-store=data_disk_store 
> --total-num-buckets=1103 --redundant-copies=1 --enable-synchronous-disk=false
> #Configure the remote site 2 with the region and the gateway-receiver  
> #Run some traffic so that all buckets are created and data is replicated to 
> the other site
> alter region --name=/example-region --gateway-sender-id=""
> destroy region --name=/example-region
> create region --name=example-region --type=PARTITION_PERSISTENT 
> --gateway-sender-id="remote_site_2" --disk-store=data_disk_store 
> --total-num-buckets=1103 --redundant-copies=1 --enable-synchronous-disk=false
> #run traffic to see that some data is not replicated to the remote site 2 
> {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to