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

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

Yes, I agree with you, [~dbarnes]. I tried to think of the solution and which 
constraints to add in alter region and create region command to prevent this 
scenario. Still, I could not find a suitable solution that doesn't break some 
other valid scenarios. The problem is that I would have to forbid some actions 
that are allowed now, which would break backward compatibility from a user 
point of view. I have sent a couple of questions to the community but haven't 
received any feedback. So I was hesitant to spend a lot of time doing a 
solution that was not interesting to the community and would not be accepted. I 
will try to think of a better solution in the future, but for the time being, I 
think it is good to have this note, at least. If you agree, I could create an 
improvement ticket to consider all scenarios and improve the handling of this 
particular case?

Thank you for the review.

> 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
>              Labels: pull-request-available
>
> 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