[
https://issues.apache.org/jira/browse/GEODE-7940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086207#comment-17086207
]
ASF subversion and git services commented on GEODE-7940:
--------------------------------------------------------
Commit bfbb398891c5d96fa3a5975365b29d71bd849ad6 in geode's branch
refs/heads/mass-test-run from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=bfbb398 ]
GEODE-7940: Fix Tracking of ShadowBuckets Destroyed (#4934)
The BucketAdvisor can now keep track of more than just one shadow
bucket to avoid incorrectly marking all of them as destroyed.
- Added unit and distributed tests.
> A parallel GatewaySender stops sending events if another GatewaySender that
> was attached to the same region is destroyed
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-7940
> URL: https://issues.apache.org/jira/browse/GEODE-7940
> Project: Geode
> Issue Type: Bug
> Components: wan
> Reporter: Barrett Oglesby
> Assignee: Juan Ramos
> Priority: Major
> Labels: GeodeCommons
> Fix For: 1.13.0
>
> Attachments: create-sender-alter-region-all-gfsh_04-01-2020.tgz
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The attached test reproduces this issue. It has a readme that describes how
> to run it.
> It starts 3 distributed systems named ln, ny and tk.
> ny and tk each have a gateway receiver and a region defined.
> Use gfsh in ln to:
> 1. Create sender to ny
> 2. Create region with sender to ny
> 3. Start doing puts from a client (verify updates are happening in ny)
> 4. Create sender to tk
> 5. Alter region add sender to tk (verify updates are happening in tk)
> 6. Stop sender to ny
> 7. Alter region remove sender to ny
> 8. Destroy sender to ny
> Updates should stop to ny but not tk, but updates to both stop.
> The ln log contains no exceptions. The stats show events being received and
> queued by the sender to tk. The eventQueueSize is 0, though.
> If step 8 is not done, updates continue flowing to tk.
> If the ln server is restarted, updates start flowing to tk again.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
