[
https://issues.apache.org/jira/browse/GEODE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jared Stewart updated GEODE-2779:
---------------------------------
Description:
Members of a cluster (with cluster configuration enabled) can end up with
inconsistent deployed jars even when they belong to the same groups.
Here are the steps to reproduce:
{noformat}
gfsh> start locator --name=loc1
gfsh> start server --name=server1 --group=group1
gfsh> start server --name=server2 --group=group2
gfsh> start server --name=server3 --group=group1,group2
gfsh> deploy --jar=/myJar.jar --group=group1,group2
gfsh> undeploy --jar=myJar.jar --group=group1
gfsh> start server --name=server4 --group=group1,group2
{noformat}
Then server 4 will have myJar.jar (brought from cluster_config/group2/myJar.jar
on the locator) whereas server 3 will not have myJar.jar (it got deleted from
server 3 when we undeployed myJar from group 1).
was:
Members of a cluster (with cluster configuration enabled) can end up with
inconsistent deployed jars even when they belong to the same groups.
Here are the steps to reproduce:
```
gfsh> start locator --name=loc1
gfsh> start server --name=server1 --group=group1
gfsh> start server --name=server2 --group=group2
gfsh> start server --name=server3 --group=group1,group2
gfsh> deploy --jar=/myJar.jar --group=group1,group2
gfsh> undeploy --jar=myJar.jar --group=group1
gfsh> start server --name=server4 --group=group1,group2
```
Then server 4 will have myJar.jar (brought from cluster_config/group2/myJar.jar
on the locator) whereas server 3 will not have myJar.jar (it got deleted from
server 3 when we undeployed myJar from group 1).
> Inconsistent jars deployed on members belonging to the same group
> -----------------------------------------------------------------
>
> Key: GEODE-2779
> URL: https://issues.apache.org/jira/browse/GEODE-2779
> Project: Geode
> Issue Type: Bug
> Components: configuration
> Affects Versions: 1.1.0, 1.1.1
> Reporter: Jared Stewart
>
> Members of a cluster (with cluster configuration enabled) can end up with
> inconsistent deployed jars even when they belong to the same groups.
> Here are the steps to reproduce:
> {noformat}
> gfsh> start locator --name=loc1
> gfsh> start server --name=server1 --group=group1
> gfsh> start server --name=server2 --group=group2
> gfsh> start server --name=server3 --group=group1,group2
> gfsh> deploy --jar=/myJar.jar --group=group1,group2
> gfsh> undeploy --jar=myJar.jar --group=group1
> gfsh> start server --name=server4 --group=group1,group2
> {noformat}
> Then server 4 will have myJar.jar (brought from
> cluster_config/group2/myJar.jar on the locator) whereas server 3 will not
> have myJar.jar (it got deleted from server 3 when we undeployed myJar from
> group 1).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
