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

ASF subversion and git services commented on GEODE-8996:
--------------------------------------------------------

Commit d9e1a12c30eb551fa05ae5689441c704e64ccb3f in geode's branch 
refs/heads/support/1.12 from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d9e1a12 ]

GEODE-8996: Fixed rebalance gfsh and REST API in mixed version mode (… (#6257)

   * GEODE-8996: Fixed rebalance gfsh and REST API in mixed version mode (#6080)

   * Moved new child RebalanceFunction and CacheRealizationFunction to pre 
1.12.0 locations.
   * While talking to pre-1.12.0 servers, the locators send the function from 
the old package.
   * While talking to 1.12.0 server, the new package function is used.
   * For RebalanceFunction and CacheRealizationFunction the serialVersionUID is 
set to the one created by 1.11.0 for old package location and serialVersionUID 
created by 1.12.0 for the latter.
   * Update GfshCompatibilityTest.java
(cherry picked from commit 3faf283c038880755a7356fe570a4f92a46826cd)



> Rebalance GFSH commands and restore redundancy commands were not backward 
> compatible
> ------------------------------------------------------------------------------------
>
>                 Key: GEODE-8996
>                 URL: https://issues.apache.org/jira/browse/GEODE-8996
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh, rest (admin)
>            Reporter: Nabarun Nag
>            Assignee: Nabarun Nag
>            Priority: Major
>              Labels: blocks-1.14.0​, pull-request-available
>             Fix For: 1.13.2, 1.14.0, 1.15.0
>
>
> Issue:
>  * Rebalance command when executed with 1.12.0+ locator and older servers, 
> the command failed
>  * This was because the Rebalance function moved to a new package
>  * Similar problem with REST calls because of moving CacheRealizationFunction 
> to a new package
>  * There was another problem where Serializable classes with UIDs were 
> changed in couple of releases
>  * The variation of the UIDs caused deserialization issues when REST commands 
> were executed from new locators and old servers.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to