[
https://issues.apache.org/jira/browse/GEODE-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao updated GEODE-4028:
-------------------------------
Description:
This would have the locators end up with different versions of jars deployed.
Steps to reproduce:
1. start locator 1 and locator 2 in the same cluster
2. connect to locator 1 with gfsh
2. deploy the first version of a.jar, then deploy another version of a.jar.
3. locator1's file system would have the new version, but locator2's file
system is unchanged.
workaround is do an undeploy first then deploy the newer version, but would be
nice to fix this.
was:
This would have the locators end up with different versions of jars deployed.
Steps to reproduce:
1. start locator 1 and locator 2 in the same cluster
2. connect to locator 1 with gfsh
2. deploy the first version of a.jar, then deploy another version of a.jar.
3. locator1's file system would have the new version, but locator2's file
system is unchanged.
> Deploy a newer version of jar file with the same name with multiple locators
> ----------------------------------------------------------------------------
>
> Key: GEODE-4028
> URL: https://issues.apache.org/jira/browse/GEODE-4028
> Project: Geode
> Issue Type: Bug
> Components: gfsh, management
> Affects Versions: 1.3.0
> Reporter: Jinmei Liao
>
> This would have the locators end up with different versions of jars deployed.
> Steps to reproduce:
> 1. start locator 1 and locator 2 in the same cluster
> 2. connect to locator 1 with gfsh
> 2. deploy the first version of a.jar, then deploy another version of a.jar.
> 3. locator1's file system would have the new version, but locator2's file
> system is unchanged.
> workaround is do an undeploy first then deploy the newer version, but would
> be nice to fix this.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
