[
https://issues.apache.org/jira/browse/GEODE-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-1796.
-------------------------------------
Resolution: Duplicate
Fix Version/s: 1.0.0-incubating
duplicate of GEODE-1761
> Clients don't fail back to servers containing non-redundant partitioned
> regions when they are bounced and rebalanced
> --------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-1796
> URL: https://issues.apache.org/jira/browse/GEODE-1796
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Reporter: Bruce Schuchardt
> Fix For: 1.0.0-incubating
>
>
> 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.
> The reason this is happening is the server ends up having the same metadata
> version after being restarted and rebalanced, and clients are configured to
> ignore refresh hints from servers unless the metadata version on the server
> is different than that in the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
