[
https://issues.apache.org/jira/browse/GEODE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042256#comment-17042256
]
ASF subversion and git services commented on GEODE-7799:
--------------------------------------------------------
Commit 22403e00c2196ab9239569b82ed34a71af7a7b26 in geode's branch
refs/heads/mass-test-run from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=22403e0 ]
GEODE-7799: Distribute rebalance status to other locators (#4692)
Co-authored-by: Joris Melchior <[email protected]>
Co-authored-by: Darrel Schneider <[email protected]>
Co-authored-by: Dale Emery <[email protected]>
> Rebalance state needs to be distributed to other locators
> ---------------------------------------------------------
>
> Key: GEODE-7799
> URL: https://issues.apache.org/jira/browse/GEODE-7799
> Project: Geode
> Issue Type: Improvement
> Components: management
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> Why
> Within certain environments, users could be connected to a singular locator
> point of contact which is then unintelligently routed to one of the locators.
> If I kick off an operation from one Locator, but then check on it using
> another locator I will get a missing operation message.
> Acceptance Criteria
> Operation in one read by another
> Scenario:
> Given a cluster is up with 2 locators (locater1,locater2) as well as 2 servers
> And a user submits a POST operation to
> locator1:7070/management/experimental/operations/rebalances
> And that rebalance is in progress
> When a user submits a get operation to
> locator2:7070/management/experimental/operations/reblances/{id}
> Then they would receive the status of the operation started on locator1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
