[
https://issues.apache.org/jira/browse/GEODE-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419270#comment-15419270
]
Bruce Schuchardt commented on GEODE-1761:
-----------------------------------------
Barry suggested that we fix this by changing the client to always refresh its
metadata if told to do so by a server, even if the metadata version hasn't
changed.
> Clients don't fail back to servers containing non-redundant partitioned
> regions when they are bounced and rebalanced
> --------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-1761
> URL: https://issues.apache.org/jira/browse/GEODE-1761
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Reporter: Bruce Schuchardt
>
> Clients don't fail back to servers containing non-redundant partitioned
> regions when they are bounced and rebalanced.
> When one of the servers is stopped, the client switches to the server(s)
> containing the new primary. When the server is restarted and rebalanced
> (which recovers primaryness), the clients do not switch back even though the
> server continually sends the metadata refresh byte on each operation.
> If the partitioned region has a redundant copy, clients do switch back.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
