[jira] [Commented] (GEODE-7838) Info about num of servers during rebalance command
[ https://issues.apache.org/jira/browse/GEODE-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080255#comment-17080255 ] ASF subversion and git services commented on GEODE-7838: Commit 93e460bb12c05c9351db0b8d6cb8b9179f18caec in geode's branch refs/heads/develop from Mario Kevo [ https://gitbox.apache.org/repos/asf?p=geode.git;h=93e460b ] GEODE-7838: getNumOfServers while rebalance is executed (#4815) * GEODE-7383: getNumOfServers while rebalance is executed > Info about num of servers during rebalance command > -- > > Key: GEODE-7838 > URL: https://issues.apache.org/jira/browse/GEODE-7838 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Mario Kevo >Assignee: Mario Kevo >Priority: Major > Labels: needs-review, pull-request-available, > pull-requests-available > Time Spent: 2h 10m > Remaining Estimate: 0h > > In case during rebalance some members joined or departed rebalance will > automatically restarted. > But from the user side it can not see on how many members rebalance was > executed. > We have a situation when have 3 servers and during rebalance one is departed > and rebalance is executed on other 2 servers. But after rebalance is finished > server is back and user have a wrong perception on how many servers rebalance > is executed. > It will be good to have another row in result table to print this message. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7383) geode-ci concourse resource doesn't care about all of ci directory
[ https://issues.apache.org/jira/browse/GEODE-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080256#comment-17080256 ] ASF subversion and git services commented on GEODE-7383: Commit 93e460bb12c05c9351db0b8d6cb8b9179f18caec in geode's branch refs/heads/develop from Mario Kevo [ https://gitbox.apache.org/repos/asf?p=geode.git;h=93e460b ] GEODE-7838: getNumOfServers while rebalance is executed (#4815) * GEODE-7383: getNumOfServers while rebalance is executed > geode-ci concourse resource doesn't care about all of ci directory > -- > > Key: GEODE-7383 > URL: https://issues.apache.org/jira/browse/GEODE-7383 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Assignee: Ernest Burghardt >Priority: Major > Fix For: 1.12.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Currently the geode-ci concourse resource is constrained to only care about > parts of the ci directory in the repository. Because this resource does not > trigger any jobs directly, it should pay attention to the entire ci directory. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7977) CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-7977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080115#comment-17080115
]
Bill Burcham commented on GEODE-7977:
-
Ugh my PR won't work (yet) so I created a revert PR:
https://github.com/apache/geode/pull/4940
Once that passes CI I'll merge it. In the morning.
> CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest >
> classMethod FAILED
>
>
> Key: GEODE-7977
> URL: https://issues.apache.org/jira/browse/GEODE-7977
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.1
>Reporter: Anilkumar Gingade
>Assignee: Bill Burcham
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Failure on Windows both jdk8 and jdk11:
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
> java.lang.ExceptionInInitializerError
> Caused by:
> java.lang.IllegalStateException: Could not find docker-compose,
> looked in: DockerCommandLocations{possiblePaths=[null,
> /usr/local/bin/docker-compose, /usr/bin/docker-compose]}
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.lambda$defaultDockerComposePath$26(DockerComposeExecutable.java:40)
> at java.util.Optional.orElseThrow(Optional.java:290)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.defaultDockerComposePath(DockerComposeExecutable.java:40)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.dockerComposePath(DockerComposeExecutable.java:84)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.access$501(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$InitShim.dockerComposePath(ImmutableDockerComposeExecutable.java:93)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:46)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$Builder.build(ImmutableDockerComposeExecutable.java:342)
> at
> com.palantir.docker.compose.DockerComposeRule.dockerComposeExecutable(DockerComposeRule.java:77)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.access$2101(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$InitShim.dockerComposeExecutable(ImmutableDockerComposeRule.java:203)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:93)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$Builder.build(ImmutableDockerComposeRule.java:1354)
> at
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest.(DualServerSNIAcceptanceTest.java:76)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7852) Add client side configuration option to support a SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080113#comment-17080113 ] ASF subversion and git services commented on GEODE-7852: Commit 13cb5523e16783b2c2bf16d31b3b7ec427641889 in geode's branch refs/heads/revert-4925-feature/GEODE-7852-test-cluster from Bill Burcham [ https://gitbox.apache.org/repos/asf?p=geode.git;h=13cb552 ] Revert "GEODE-7852: test SNI client against a geode (2-node) cluster (#4925)" This reverts commit 4f2a6047d5b272982595e3b7e71c624d61c69415. > Add client side configuration option to support a SNI proxy > --- > > Key: GEODE-7852 > URL: https://issues.apache.org/jira/browse/GEODE-7852 > Project: Geode > Issue Type: Improvement > Components: client/server, membership >Reporter: Dan Smith >Assignee: Bruce J Schuchardt >Priority: Major > Fix For: 1.13.0 > > Time Spent: 6h > Remaining Estimate: 0h > > Add an option to the client side configuration to support a the use of a [SNI > proxy|https://www.bamsoftware.com/computers/sniproxy/]. > See also GEODE-7837, which adds a system property to support a SNI proxy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7765) Update dependencies for v1.13
[ https://issues.apache.org/jira/browse/GEODE-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-7765. -- Fix Version/s: 1.13.0 Resolution: Fixed > Update dependencies for v1.13 > - > > Key: GEODE-7765 > URL: https://issues.apache.org/jira/browse/GEODE-7765 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Anthony Baker >Priority: Major > Fix For: 1.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update all the dependencies we can. See > https://github.com/apache/geode/pull/4542 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7765) Update dependencies for v1.13
[ https://issues.apache.org/jira/browse/GEODE-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080089#comment-17080089 ] ASF subversion and git services commented on GEODE-7765: Commit e9993c15d88a5edd2a486fd64339deba37c24945 in geode's branch refs/heads/develop from Anthony Baker [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e9993c1 ] GEODE-7765: Update dependencies for v1.13 Update many but not all dependencies. > Update dependencies for v1.13 > - > > Key: GEODE-7765 > URL: https://issues.apache.org/jira/browse/GEODE-7765 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Anthony Baker >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Update all the dependencies we can. See > https://github.com/apache/geode/pull/4542 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7977) CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-7977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080080#comment-17080080
]
Bill Burcham commented on GEODE-7977:
-
PR is up
> CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest >
> classMethod FAILED
>
>
> Key: GEODE-7977
> URL: https://issues.apache.org/jira/browse/GEODE-7977
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.1
>Reporter: Anilkumar Gingade
>Assignee: Bill Burcham
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Failure on Windows both jdk8 and jdk11:
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
> java.lang.ExceptionInInitializerError
> Caused by:
> java.lang.IllegalStateException: Could not find docker-compose,
> looked in: DockerCommandLocations{possiblePaths=[null,
> /usr/local/bin/docker-compose, /usr/bin/docker-compose]}
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.lambda$defaultDockerComposePath$26(DockerComposeExecutable.java:40)
> at java.util.Optional.orElseThrow(Optional.java:290)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.defaultDockerComposePath(DockerComposeExecutable.java:40)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.dockerComposePath(DockerComposeExecutable.java:84)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.access$501(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$InitShim.dockerComposePath(ImmutableDockerComposeExecutable.java:93)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:46)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$Builder.build(ImmutableDockerComposeExecutable.java:342)
> at
> com.palantir.docker.compose.DockerComposeRule.dockerComposeExecutable(DockerComposeRule.java:77)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.access$2101(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$InitShim.dockerComposeExecutable(ImmutableDockerComposeRule.java:203)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:93)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$Builder.build(ImmutableDockerComposeRule.java:1354)
> at
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest.(DualServerSNIAcceptanceTest.java:76)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7977) CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-7977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080062#comment-17080062
]
Bill Burcham commented on GEODE-7977:
-
I think the problem is that the `IgnoreOnWindowsRule` we created to prevent
running on Windows, protects `@Before` methods but not `@BeforeClass` ones.
This test has a `@BeforeClass` method that runs `DockerComposeRule.exec()`.
Working on a fix…
> CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest >
> classMethod FAILED
>
>
> Key: GEODE-7977
> URL: https://issues.apache.org/jira/browse/GEODE-7977
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.1
>Reporter: Anilkumar Gingade
>Assignee: Bill Burcham
>Priority: Major
>
> Failure on Windows both jdk8 and jdk11:
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
> java.lang.ExceptionInInitializerError
> Caused by:
> java.lang.IllegalStateException: Could not find docker-compose,
> looked in: DockerCommandLocations{possiblePaths=[null,
> /usr/local/bin/docker-compose, /usr/bin/docker-compose]}
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.lambda$defaultDockerComposePath$26(DockerComposeExecutable.java:40)
> at java.util.Optional.orElseThrow(Optional.java:290)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.defaultDockerComposePath(DockerComposeExecutable.java:40)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.dockerComposePath(DockerComposeExecutable.java:84)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.access$501(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$InitShim.dockerComposePath(ImmutableDockerComposeExecutable.java:93)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:46)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$Builder.build(ImmutableDockerComposeExecutable.java:342)
> at
> com.palantir.docker.compose.DockerComposeRule.dockerComposeExecutable(DockerComposeRule.java:77)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.access$2101(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$InitShim.dockerComposeExecutable(ImmutableDockerComposeRule.java:203)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:93)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$Builder.build(ImmutableDockerComposeRule.java:1354)
> at
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest.(DualServerSNIAcceptanceTest.java:76)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7852) Add client side configuration option to support a SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080060#comment-17080060 ] ASF subversion and git services commented on GEODE-7852: Commit e4820c01923b78dac4b8e6d9d9cfbc5b39312cf1 in geode's branch refs/heads/feature/GEODE-7852query from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e4820c0 ] GEODE-7852: Add client side configuration option to support a SNI proxy Adding tests for query, putAll, getAll. Ensuring that a client can receive responses that are streamed through "chunking" from the server. The test now creates the server cluster and client cache in a class rule for faster execution. > Add client side configuration option to support a SNI proxy > --- > > Key: GEODE-7852 > URL: https://issues.apache.org/jira/browse/GEODE-7852 > Project: Geode > Issue Type: Improvement > Components: client/server, membership >Reporter: Dan Smith >Assignee: Bruce J Schuchardt >Priority: Major > Fix For: 1.13.0 > > Time Spent: 5h 50m > Remaining Estimate: 0h > > Add an option to the client side configuration to support a the use of a [SNI > proxy|https://www.bamsoftware.com/computers/sniproxy/]. > See also GEODE-7837, which adds a system property to support a SNI proxy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7965) Modify Redis SADD command to use region.compute
[ https://issues.apache.org/jira/browse/GEODE-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080056#comment-17080056 ] ASF subversion and git services commented on GEODE-7965: Commit 464c7495c35c62241cfd20ace5722c873ff5068b in geode's branch refs/heads/mass-test-run from John Hutchison [ https://gitbox.apache.org/repos/asf?p=geode.git;h=464c749 ] GEODE-7965: Modify Redis SADD command to use region.compute (#4918) * GEODE-7965: Modify Redis SADD command to use region.compute Co-authored-by: Ray Ingles Co-authored-by: John Hutchison > Modify Redis SADD command to use region.compute > > > Key: GEODE-7965 > URL: https://issues.apache.org/jira/browse/GEODE-7965 > Project: Geode > Issue Type: Improvement >Reporter: John Hutchison >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.13.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Geode implementation of this command has been modified to use the > region.compute command to improve reliability. This is stage one of an > experiment to test out an effort to improve both reliability and performance > by a series of changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7852) Add client side configuration option to support a SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080053#comment-17080053 ] ASF subversion and git services commented on GEODE-7852: Commit a12d1fe3e1f66adfcdc8ff5c414abb69f3c8f3cd in geode's branch refs/heads/mass-test-run from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a12d1fe ] Merge pull request #4920 from apache/feature/GEODE-7852doc GEODE-7852: SNI extension support > Add client side configuration option to support a SNI proxy > --- > > Key: GEODE-7852 > URL: https://issues.apache.org/jira/browse/GEODE-7852 > Project: Geode > Issue Type: Improvement > Components: client/server, membership >Reporter: Dan Smith >Assignee: Bruce J Schuchardt >Priority: Major > Fix For: 1.13.0 > > Time Spent: 5h 40m > Remaining Estimate: 0h > > Add an option to the client side configuration to support a the use of a [SNI > proxy|https://www.bamsoftware.com/computers/sniproxy/]. > See also GEODE-7837, which adds a system property to support a SNI proxy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7965) Modify Redis SADD command to use region.compute
[ https://issues.apache.org/jira/browse/GEODE-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080057#comment-17080057 ] ASF subversion and git services commented on GEODE-7965: Commit 464c7495c35c62241cfd20ace5722c873ff5068b in geode's branch refs/heads/mass-test-run from John Hutchison [ https://gitbox.apache.org/repos/asf?p=geode.git;h=464c749 ] GEODE-7965: Modify Redis SADD command to use region.compute (#4918) * GEODE-7965: Modify Redis SADD command to use region.compute Co-authored-by: Ray Ingles Co-authored-by: John Hutchison > Modify Redis SADD command to use region.compute > > > Key: GEODE-7965 > URL: https://issues.apache.org/jira/browse/GEODE-7965 > Project: Geode > Issue Type: Improvement >Reporter: John Hutchison >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.13.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Geode implementation of this command has been modified to use the > region.compute command to improve reliability. This is stage one of an > experiment to test out an effort to improve both reliability and performance > by a series of changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7969) bump netty to 4.1.48
[ https://issues.apache.org/jira/browse/GEODE-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080051#comment-17080051 ] ASF subversion and git services commented on GEODE-7969: Commit 8f9f4b7e869022281a189bc25eed23815e88698e in geode's branch refs/heads/mass-test-run from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8f9f4b7 ] GEODE-7969: bump netty version to latest (#4933) > bump netty to 4.1.48 > > > Key: GEODE-7969 > URL: https://issues.apache.org/jira/browse/GEODE-7969 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Fix For: 1.12.1, 1.13.0 > > Time Spent: 50m > Remaining Estimate: 0h > > as part of GEODE-7798: Fix flakiness in PubSubTest, the netty version was > increased on develop; this version should be the minimum used on support > branches as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7945) Cluster restart recovery from disk blocked by waiting replies of CreateRegionMessage
[ https://issues.apache.org/jira/browse/GEODE-7945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080050#comment-17080050 ] ASF subversion and git services commented on GEODE-7945: Commit 37e2d982f6de16615fa62708ab4f104b402a688a in geode's branch refs/heads/mass-test-run from Jianxia Chen [ https://gitbox.apache.org/repos/asf?p=geode.git;h=37e2d98 ] GEODE-7945: Replace Map with ConcurrentMap for GemFireCacheImpl.rootRegions (#4899) * Remove unnecessary synchronized block * Replace Map.get and remove with remove * Fix the typo in log messages * Remove unnecessary copy of rootRegions values Authored-by: Jianxia Chen > Cluster restart recovery from disk blocked by waiting replies of > CreateRegionMessage > > > Key: GEODE-7945 > URL: https://issues.apache.org/jira/browse/GEODE-7945 > Project: Geode > Issue Type: Improvement >Reporter: Jianxia Chen >Assignee: Jianxia Chen >Priority: Major > Fix For: 1.13.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > A cluster restart recovering from disk has unexpected delays in some of the > members. The logs show that those delayed members are waiting for replies of > CreateRegionMessage, before loading the krf files. And the reason for waiting > the replies of CreateRegionMessage is likely because other members are > holding some lock while busy loading the krf files. Therefore the replies are > delayed. > Once those delayed members get the replies of CreateRegionMessage, it starts > loading the krf files. If the delayed members contain the latest data, this > could block other members waiting for the latest data. > Because the cluster members are blocking each other at different stages > during the cluster restart recovery process, the whole process is > unexpectedly long when the disk store contains large amount of data. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7976) make the "config" param not required when deploy a jar using management rest api
[
https://issues.apache.org/jira/browse/GEODE-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080054#comment-17080054
]
ASF subversion and git services commented on GEODE-7976:
Commit a73dffc4f0b7370a9374797f64d9a513beec3400 in geode's branch
refs/heads/mass-test-run from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a73dffc ]
GEODE-7976: make "config" param optional when deploy using CMS. (#4930)
> make the "config" param not required when deploy a jar using management rest
> api
>
>
> Key: GEODE-7976
> URL: https://issues.apache.org/jira/browse/GEODE-7976
> Project: Geode
> Issue Type: Improvement
> Components: management
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently user has to pass in a "config" param when deploy a jar using the
> rest api, even though most of the time it's just an empty json "{}" if user
> just want to deploy to the "cluster" group. make this parameter optional
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7664) CI Failure: ClientClusterManagementServiceDUnitTest > deleteRegionOnSpecificGroup
[
https://issues.apache.org/jira/browse/GEODE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080058#comment-17080058
]
ASF subversion and git services commented on GEODE-7664:
Commit 63c681d217bdcc3d6ed0150f977f18461be1a785 in geode's branch
refs/heads/mass-test-run from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=63c681d ]
GEODE-7664: calling RegionConfigRealizer.exists methods doesn't need … (#4932)
> CI Failure: ClientClusterManagementServiceDUnitTest >
> deleteRegionOnSpecificGroup
> -
>
> Key: GEODE-7664
> URL: https://issues.apache.org/jira/browse/GEODE-7664
> Project: Geode
> Issue Type: Bug
>Reporter: Ivan Godwin
>Assignee: Jinmei Liao
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1454]
>
> {code:java}
> org.apache.geode.management.client.ClientClusterManagementServiceDUnitTest >
> deleteRegionOnSpecificGroup FAILEDjava.lang.AssertionError: Suspicious
> strings were written to the log during this run.Fix the strings or use
> IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1874 [error 2020/01/09 18:52:37.224 GMT
> tid=353]
> org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
> concurrencyChecksEnabled]
> org.apache.geode.cache.RegionDestroyedException:org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
> concurrencyChecksEnabled]
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
> at
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
> at
> org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256)
> at
> org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:307)
> at
> org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:48)
>
> at
> org.apache.geode.management.internal.configuration.realizers.ConfigurationRealizer.exists(ConfigurationRealizer.java:35)
> at
> org.apache.geode.management.internal.functions.CacheRealizationFunction.executeUpdate(CacheRealizationFunction.java:130)
> at
> org.apache.geode.management.internal.functions.CacheRealizationFunction.execute(CacheRealizationFunction.java:79)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:394)
>
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:458)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:449)
> at
> org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:379)
> at
> org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7852) Add client side configuration option to support a SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080052#comment-17080052 ] ASF subversion and git services commented on GEODE-7852: Commit a12d1fe3e1f66adfcdc8ff5c414abb69f3c8f3cd in geode's branch refs/heads/mass-test-run from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a12d1fe ] Merge pull request #4920 from apache/feature/GEODE-7852doc GEODE-7852: SNI extension support > Add client side configuration option to support a SNI proxy > --- > > Key: GEODE-7852 > URL: https://issues.apache.org/jira/browse/GEODE-7852 > Project: Geode > Issue Type: Improvement > Components: client/server, membership >Reporter: Dan Smith >Assignee: Bruce J Schuchardt >Priority: Major > Fix For: 1.13.0 > > Time Spent: 5h 40m > Remaining Estimate: 0h > > Add an option to the client side configuration to support a the use of a [SNI > proxy|https://www.bamsoftware.com/computers/sniproxy/]. > See also GEODE-7837, which adds a system property to support a SNI proxy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7852) Add client side configuration option to support a SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080055#comment-17080055 ] ASF subversion and git services commented on GEODE-7852: Commit 4f2a6047d5b272982595e3b7e71c624d61c69415 in geode's branch refs/heads/mass-test-run from Bill Burcham [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4f2a604 ] GEODE-7852: test SNI client against a geode (2-node) cluster (#4925) > Add client side configuration option to support a SNI proxy > --- > > Key: GEODE-7852 > URL: https://issues.apache.org/jira/browse/GEODE-7852 > Project: Geode > Issue Type: Improvement > Components: client/server, membership >Reporter: Dan Smith >Assignee: Bruce J Schuchardt >Priority: Major > Fix For: 1.13.0 > > Time Spent: 5h 40m > Remaining Estimate: 0h > > Add an option to the client side configuration to support a the use of a [SNI > proxy|https://www.bamsoftware.com/computers/sniproxy/]. > See also GEODE-7837, which adds a system property to support a SNI proxy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7978) Improve tests for Redis Module SREM Command
John Hutchison created GEODE-7978: - Summary: Improve tests for Redis Module SREM Command Key: GEODE-7978 URL: https://issues.apache.org/jira/browse/GEODE-7978 Project: Geode Issue Type: Improvement Components: redis Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7577) Server is not logging about waiting for missing persistent members
[
https://issues.apache.org/jira/browse/GEODE-7577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080045#comment-17080045
]
Anilkumar Gingade commented on GEODE-7577:
--
This appeared in AcceptanceTestOpenJDK11 #37
{noformat}
org.apache.geode.cache.persistence.MissingDiskStoreAcceptanceTest >
waitingForMembersMessageIsLogged FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[54690c9eca5fe0e5: gfsh -e start locator --name=locator
--dir=/tmp/junit8220715861809755091/locator --port=24180
--locators=localhost[24180] -e start server --name=server1
--dir=/tmp/junit8220715861809755091/server1 --locators=localhost[24180]
--server-port=24181 -e start server --name=server2
--dir=/tmp/junit8220715861809755091/server2 --locators=localhost[24180]
--server-port=24182 -e create region --name=myRegion
--type=REPLICATE_PERSISTENT]] expected:<[0]> but was:<[1]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:114)
at
org.apache.geode.cache.persistence.MissingDiskStoreAcceptanceTest.setUp(MissingDiskStoreAcceptanceTest.java:103)
{noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.13.0-SNAPSHOT.0170/test-results/acceptanceTest/1586470692/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.13.0-SNAPSHOT.0170/test-artifacts/1586470692/acceptancetestfiles-OpenJDK11-1.13.0-SNAPSHOT.0170.tgz
> Server is not logging about waiting for missing persistent members
> --
>
> Key: GEODE-7577
> URL: https://issues.apache.org/jira/browse/GEODE-7577
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Reporter: Kirk Lund
>Priority: Major
> Labels: flaky
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> During startup, a Server is supposed to log when it is waiting for missing
> persistent members. Somehow, this log message is no longer being logged.
> The log message looks like:
> "Region %s has potentially stale data. It is waiting for another member to
> recover the latest data.%sMy persistent id:%s%s%sMembers with potentially new
> data:%s%s%sUse the gfsh show missing-disk-stores command to see all disk
> stores that are being waited on by other members."
> Passing equal numbers into MembershipChangeListener for warningDelay and
> pollDuration seems to be the main cause.
> I also noticed that the formatting of the message was broken when
> LocalizedStrings were removed from Geode.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (GEODE-7017) CI failure: org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored
[
https://issues.apache.org/jira/browse/GEODE-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080041#comment-17080041
]
Anilkumar Gingade edited comment on GEODE-7017 at 4/9/20, 10:34 PM:
Appeared in CI run AcceptanceTestOpenJDK11 #37
{noformat}
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
startupReportsOnlineOnlyAfterRedundancyRestored FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[aa8c65a6d5d24e27: gfsh -e connect --locator=localhost[20959] -e start server
--name=server1 --dir=/tmp/junit2201834701304410433/server1secondfolder
--locators=localhost[20959]]] expected:<[0]> but was:<[1]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:114)
at
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupValueRecoveryNotificationTest.java:146)
org.junit.ComparisonFailure: [Exit value from process started by
[1b1fb99e92f45216: gfsh -e stop server
--dir=/tmp/junit2201834701304410433/server1secondfolder -e stop locator
--dir=/tmp/junit2201834701304410433/locator]] expected:<[0]> but was:<[1]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:114)
at
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest.stopAllMembers(ServerStartupValueRecoveryNotificationTest.java:132)
org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest >
startupReportsOnlineOnlyAfterRedundancyRestored FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[d1e30146b61fe924: gfsh -e start locator --name=locator
--dir=/tmp/junit13171347057076094348/locator --port=21375
--locators=localhost[21375] -e start server --name=server1
--dir=/tmp/junit13171347057076094348/server1 --locators=localhost[21375]
--disable-default-server -e start server --name=server2
--dir=/tmp/junit13171347057076094348/server2 --locators=localhost[21375]
--disable-default-server -e create region --name=myRegion
--type=PARTITION_REDUNDANT --redundant-copies=1 -e create region
--name=mySecondRegion --type=PARTITION_REDUNDANT --redundant-copies=1 -e put
--region=myRegion --key=James --value=Bond -e put --region=mySecondRegion
--key=Derrick --value=Flint]] expected:<[0]> but was:<[1]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:114)
at
org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.redundantRegionThatRequiresRedundancyRecovery(ServerStartupRedundancyRecoveryNotificationTest.java:116)
{noformat}
One thing to notice here is error message has "Exit value from process started
by" not sure if its due any resource issue.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.13.0-SNAPSHOT.0170/test-results/acceptanceTest/1586470692/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.13.0-SNAPSHOT.0170/test-artifacts/1586470692/acceptancetestfiles-OpenJDK11-1.13.0-SNAPSHOT.0170.tgz
was (Author: agingade):
Appeared in CI run
[jira] [Comment Edited] (GEODE-7017) CI failure: org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored
[
https://issues.apache.org/jira/browse/GEODE-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080041#comment-17080041
]
Anilkumar Gingade edited comment on GEODE-7017 at 4/9/20, 10:34 PM:
Appeared in CI run AcceptanceTestOpenJDK11 #37
{noformat}
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
startupReportsOnlineOnlyAfterRedundancyRestored FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[aa8c65a6d5d24e27: gfsh -e connect --locator=localhost[20959] -e start server
--name=server1 --dir=/tmp/junit2201834701304410433/server1secondfolder
--locators=localhost[20959]]] expected:<[0]> but was:<[1]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:114)
at
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupValueRecoveryNotificationTest.java:146)
org.junit.ComparisonFailure: [Exit value from process started by
[1b1fb99e92f45216: gfsh -e stop server
--dir=/tmp/junit2201834701304410433/server1secondfolder -e stop locator
--dir=/tmp/junit2201834701304410433/locator]] expected:<[0]> but was:<[1]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:114)
at
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest.stopAllMembers(ServerStartupValueRecoveryNotificationTest.java:132)
org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest >
startupReportsOnlineOnlyAfterRedundancyRestored FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[d1e30146b61fe924: gfsh -e start locator --name=locator
--dir=/tmp/junit13171347057076094348/locator --port=21375
--locators=localhost[21375] -e start server --name=server1
--dir=/tmp/junit13171347057076094348/server1 --locators=localhost[21375]
--disable-default-server -e start server --name=server2
--dir=/tmp/junit13171347057076094348/server2 --locators=localhost[21375]
--disable-default-server -e create region --name=myRegion
--type=PARTITION_REDUNDANT --redundant-copies=1 -e create region
--name=mySecondRegion --type=PARTITION_REDUNDANT --redundant-copies=1 -e put
--region=myRegion --key=James --value=Bond -e put --region=mySecondRegion
--key=Derrick --value=Flint]] expected:<[0]> but was:<[1]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:114)
at
org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.redundantRegionThatRequiresRedundancyRecovery(ServerStartupRedundancyRecoveryNotificationTest.java:116)
{noformat}
One thing to notice here is error message has "Exit value from process started
by" not sure if its due any resource issue.
was (Author: agingade):
Appeared in CI run AcceptanceTestOpenJDK11 #37
{noformat}
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
startupReportsOnlineOnlyAfterRedundancyRestored FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[aa8c65a6d5d24e27: gfsh -e connect --locator=localhost[20959] -e start server
--name=server1 --dir=/tmp/junit2201834701304410433/server1secondfolder
--locators=localhost[20959]]] expected:<[0]> but was:<[1]>
at
[jira] [Reopened] (GEODE-7017) CI failure: org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored
[
https://issues.apache.org/jira/browse/GEODE-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade reopened GEODE-7017:
--
Appeared in CI run AcceptanceTestOpenJDK11 #37
{noformat}
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
startupReportsOnlineOnlyAfterRedundancyRestored FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[aa8c65a6d5d24e27: gfsh -e connect --locator=localhost[20959] -e start server
--name=server1 --dir=/tmp/junit2201834701304410433/server1secondfolder
--locators=localhost[20959]]] expected:<[0]> but was:<[1]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:114)
at
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupValueRecoveryNotificationTest.java:146)
org.junit.ComparisonFailure: [Exit value from process started by
[1b1fb99e92f45216: gfsh -e stop server
--dir=/tmp/junit2201834701304410433/server1secondfolder -e stop locator
--dir=/tmp/junit2201834701304410433/locator]] expected:<[0]> but was:<[1]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:114)
at
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest.stopAllMembers(ServerStartupValueRecoveryNotificationTest.java:132)
org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest >
startupReportsOnlineOnlyAfterRedundancyRestored FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[d1e30146b61fe924: gfsh -e start locator --name=locator
--dir=/tmp/junit13171347057076094348/locator --port=21375
--locators=localhost[21375] -e start server --name=server1
--dir=/tmp/junit13171347057076094348/server1 --locators=localhost[21375]
--disable-default-server -e start server --name=server2
--dir=/tmp/junit13171347057076094348/server2 --locators=localhost[21375]
--disable-default-server -e create region --name=myRegion
--type=PARTITION_REDUNDANT --redundant-copies=1 -e create region
--name=mySecondRegion --type=PARTITION_REDUNDANT --redundant-copies=1 -e put
--region=myRegion --key=James --value=Bond -e put --region=mySecondRegion
--key=Derrick --value=Flint]] expected:<[0]> but was:<[1]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:114)
at
org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.redundantRegionThatRequiresRedundancyRecovery(ServerStartupRedundancyRecoveryNotificationTest.java:116)
{noformat}
> CI failure:
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored
> ---
>
> Key: GEODE-7017
> URL: https://issues.apache.org/jira/browse/GEODE-7017
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Anilkumar Gingade
>Assignee: Mark Hanson
>Priority: Major
>
> {noformat}
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure:
[jira] [Assigned] (GEODE-7964) Upgrade mockito dependency from 2.23.0 to 3.3.3
[ https://issues.apache.org/jira/browse/GEODE-7964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-7964: Assignee: Kirk Lund > Upgrade mockito dependency from 2.23.0 to 3.3.3 > --- > > Key: GEODE-7964 > URL: https://issues.apache.org/jira/browse/GEODE-7964 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Upgrade mockito dependency from 2.23.0 to 3.3.3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7977) CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-7977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade reassigned GEODE-7977:
Assignee: Bill Burcham
> CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest >
> classMethod FAILED
>
>
> Key: GEODE-7977
> URL: https://issues.apache.org/jira/browse/GEODE-7977
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.1
>Reporter: Anilkumar Gingade
>Assignee: Bill Burcham
>Priority: Major
>
> Failure on Windows both jdk8 and jdk11:
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
> java.lang.ExceptionInInitializerError
> Caused by:
> java.lang.IllegalStateException: Could not find docker-compose,
> looked in: DockerCommandLocations{possiblePaths=[null,
> /usr/local/bin/docker-compose, /usr/bin/docker-compose]}
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.lambda$defaultDockerComposePath$26(DockerComposeExecutable.java:40)
> at java.util.Optional.orElseThrow(Optional.java:290)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.defaultDockerComposePath(DockerComposeExecutable.java:40)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.dockerComposePath(DockerComposeExecutable.java:84)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.access$501(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$InitShim.dockerComposePath(ImmutableDockerComposeExecutable.java:93)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:46)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$Builder.build(ImmutableDockerComposeExecutable.java:342)
> at
> com.palantir.docker.compose.DockerComposeRule.dockerComposeExecutable(DockerComposeRule.java:77)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.access$2101(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$InitShim.dockerComposeExecutable(ImmutableDockerComposeRule.java:203)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:93)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$Builder.build(ImmutableDockerComposeRule.java:1354)
> at
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest.(DualServerSNIAcceptanceTest.java:76)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7977) CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-7977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-7977:
-
Affects Version/s: 1.12.1
> CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest >
> classMethod FAILED
>
>
> Key: GEODE-7977
> URL: https://issues.apache.org/jira/browse/GEODE-7977
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.1
>Reporter: Anilkumar Gingade
>Priority: Major
>
> Failure on Windows both jdk8 and jdk11:
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
> java.lang.ExceptionInInitializerError
> Caused by:
> java.lang.IllegalStateException: Could not find docker-compose,
> looked in: DockerCommandLocations{possiblePaths=[null,
> /usr/local/bin/docker-compose, /usr/bin/docker-compose]}
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.lambda$defaultDockerComposePath$26(DockerComposeExecutable.java:40)
> at java.util.Optional.orElseThrow(Optional.java:290)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.defaultDockerComposePath(DockerComposeExecutable.java:40)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.dockerComposePath(DockerComposeExecutable.java:84)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.access$501(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$InitShim.dockerComposePath(ImmutableDockerComposeExecutable.java:93)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:46)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$Builder.build(ImmutableDockerComposeExecutable.java:342)
> at
> com.palantir.docker.compose.DockerComposeRule.dockerComposeExecutable(DockerComposeRule.java:77)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.access$2101(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$InitShim.dockerComposeExecutable(ImmutableDockerComposeRule.java:203)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:93)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$Builder.build(ImmutableDockerComposeRule.java:1354)
> at
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest.(DualServerSNIAcceptanceTest.java:76)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7977) CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
Anilkumar Gingade created GEODE-7977:
Summary: CI Failure:
org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
Key: GEODE-7977
URL: https://issues.apache.org/jira/browse/GEODE-7977
Project: Geode
Issue Type: Bug
Components: membership
Reporter: Anilkumar Gingade
Failure on Windows both jdk8 and jdk11:
org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
java.lang.ExceptionInInitializerError
Caused by:
java.lang.IllegalStateException: Could not find docker-compose, looked
in: DockerCommandLocations{possiblePaths=[null, /usr/local/bin/docker-compose,
/usr/bin/docker-compose]}
at
com.palantir.docker.compose.execution.DockerComposeExecutable.lambda$defaultDockerComposePath$26(DockerComposeExecutable.java:40)
at java.util.Optional.orElseThrow(Optional.java:290)
at
com.palantir.docker.compose.execution.DockerComposeExecutable.defaultDockerComposePath(DockerComposeExecutable.java:40)
at
com.palantir.docker.compose.execution.DockerComposeExecutable.dockerComposePath(DockerComposeExecutable.java:84)
at
com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.access$501(ImmutableDockerComposeExecutable.java:22)
at
com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$InitShim.dockerComposePath(ImmutableDockerComposeExecutable.java:93)
at
com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:46)
at
com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:22)
at
com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$Builder.build(ImmutableDockerComposeExecutable.java:342)
at
com.palantir.docker.compose.DockerComposeRule.dockerComposeExecutable(DockerComposeRule.java:77)
at
com.palantir.docker.compose.ImmutableDockerComposeRule.access$2101(ImmutableDockerComposeRule.java:32)
at
com.palantir.docker.compose.ImmutableDockerComposeRule$InitShim.dockerComposeExecutable(ImmutableDockerComposeRule.java:203)
at
com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:93)
at
com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:32)
at
com.palantir.docker.compose.ImmutableDockerComposeRule$Builder.build(ImmutableDockerComposeRule.java:1354)
at
org.apache.geode.client.sni.DualServerSNIAcceptanceTest.(DualServerSNIAcceptanceTest.java:76)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7977) CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-7977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080022#comment-17080022
]
Anilkumar Gingade commented on GEODE-7977:
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.13.0-SNAPSHOT.0168/test-results/acceptanceTest/1586464485/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.13.0-SNAPSHOT.0168/test-artifacts/1586464485/windows-acceptancetestfiles-OpenJDK8-1.13.0-SNAPSHOT.0168.tgz
> CI Failure: org.apache.geode.client.sni.DualServerSNIAcceptanceTest >
> classMethod FAILED
>
>
> Key: GEODE-7977
> URL: https://issues.apache.org/jira/browse/GEODE-7977
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Anilkumar Gingade
>Priority: Major
>
> Failure on Windows both jdk8 and jdk11:
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest > classMethod FAILED
> java.lang.ExceptionInInitializerError
> Caused by:
> java.lang.IllegalStateException: Could not find docker-compose,
> looked in: DockerCommandLocations{possiblePaths=[null,
> /usr/local/bin/docker-compose, /usr/bin/docker-compose]}
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.lambda$defaultDockerComposePath$26(DockerComposeExecutable.java:40)
> at java.util.Optional.orElseThrow(Optional.java:290)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.defaultDockerComposePath(DockerComposeExecutable.java:40)
> at
> com.palantir.docker.compose.execution.DockerComposeExecutable.dockerComposePath(DockerComposeExecutable.java:84)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.access$501(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$InitShim.dockerComposePath(ImmutableDockerComposeExecutable.java:93)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:46)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable.(ImmutableDockerComposeExecutable.java:22)
> at
> com.palantir.docker.compose.execution.ImmutableDockerComposeExecutable$Builder.build(ImmutableDockerComposeExecutable.java:342)
> at
> com.palantir.docker.compose.DockerComposeRule.dockerComposeExecutable(DockerComposeRule.java:77)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.access$2101(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$InitShim.dockerComposeExecutable(ImmutableDockerComposeRule.java:203)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:93)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule.(ImmutableDockerComposeRule.java:32)
> at
> com.palantir.docker.compose.ImmutableDockerComposeRule$Builder.build(ImmutableDockerComposeRule.java:1354)
> at
> org.apache.geode.client.sni.DualServerSNIAcceptanceTest.(DualServerSNIAcceptanceTest.java:76)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7474) NetSearchMessagingDUnitTest.testNetSearchFailoverFromReplicate
[
https://issues.apache.org/jira/browse/GEODE-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-7474:
--
Assignee: Mark Hanson (was: Kirk Lund)
> NetSearchMessagingDUnitTest.testNetSearchFailoverFromReplicate
> --
>
> Key: GEODE-7474
> URL: https://issues.apache.org/jira/browse/GEODE-7474
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Mark Hanson
>Priority: Major
> Labels: flaky
> Time Spent: 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1665]
>
> {noformat}
> org.apache.geode.internal.cache.NetSearchMessagingDUnitTest >
> testNetSearchFailoverFromReplicate FAILED
> 19:13:08java.lang.AssertionError: Suspicious strings were written to the
> log during this run.
> 19:13:08Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 19:13:08
> ---
> 19:13:08Found suspect string in log4j at line 2385
> 19:13:08
> 19:13:08[fatal 2019/11/18 03:13:06.977 GMT thread 2> tid=207] Uncaught exception in thread Thread[Geode Failure
> Detection thread 2,5,RMI Runtime]
> 19:13:08java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor$$Lambda$226/1317859019@1274aba9
> rejected from java.util.concurrent.ThreadPoolExecutor@100274c7[Shutting
> down, pool size = 3, active threads = 3, queued tasks = 0, completed tasks =
> 7]
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.checkIfAvailable(GMSHealthMonitor.java:1295)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.processMessage(GMSHealthMonitor.java:1232)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.sendSuspectRequest(GMSHealthMonitor.java:1478)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.initiateSuspicion(GMSHealthMonitor.java:477)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.lambda$checkMember$0(GMSHealthMonitor.java:461)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 19:13:08 at java.lang.Thread.run(Thread.java:748)
> 19:13:08
> 19:13:08
> ---
> 19:13:08Found suspect string in log4j at line 2399
> 19:13:08
> 19:13:08[fatal 2019/11/18 03:13:06.976 GMT thread 4> tid=226] Uncaught exception in thread Thread[Geode Failure
> Detection thread 4,5,RMI Runtime]
> 19:13:08java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor$$Lambda$226/1317859019@143de298
> rejected from java.util.concurrent.ThreadPoolExecutor@100274c7[Shutting
> down, pool size = 3, active threads = 3, queued tasks = 0, completed tasks =
> 7]
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.checkIfAvailable(GMSHealthMonitor.java:1295)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.processMessage(GMSHealthMonitor.java:1232)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.sendSuspectRequest(GMSHealthMonitor.java:1478)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.initiateSuspicion(GMSHealthMonitor.java:477)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.lambda$checkMember$0(GMSHealthMonitor.java:461)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 19:13:08 at
>
[jira] [Updated] (GEODE-7751) Tomcat9CachingClientServerTest.containersShouldExpireInSetTimeframe failed.
[ https://issues.apache.org/jira/browse/GEODE-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-7751: --- Affects Version/s: 1.11.0 > Tomcat9CachingClientServerTest.containersShouldExpireInSetTimeframe failed. > --- > > Key: GEODE-7751 > URL: https://issues.apache.org/jira/browse/GEODE-7751 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.11.0 >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Labels: flaky > Fix For: 1.13.0 > > > Test run > https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2937 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7751) Tomcat9CachingClientServerTest.containersShouldExpireInSetTimeframe failed.
[ https://issues.apache.org/jira/browse/GEODE-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-7751. Fix Version/s: 1.13.0 Resolution: Fixed > Tomcat9CachingClientServerTest.containersShouldExpireInSetTimeframe failed. > --- > > Key: GEODE-7751 > URL: https://issues.apache.org/jira/browse/GEODE-7751 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Labels: flaky > Fix For: 1.13.0 > > > Test run > https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2937 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7664) CI Failure: ClientClusterManagementServiceDUnitTest > deleteRegionOnSpecificGroup
[
https://issues.apache.org/jira/browse/GEODE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080002#comment-17080002
]
ASF subversion and git services commented on GEODE-7664:
Commit 63c681d217bdcc3d6ed0150f977f18461be1a785 in geode's branch
refs/heads/develop from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=63c681d ]
GEODE-7664: calling RegionConfigRealizer.exists methods doesn't need … (#4932)
> CI Failure: ClientClusterManagementServiceDUnitTest >
> deleteRegionOnSpecificGroup
> -
>
> Key: GEODE-7664
> URL: https://issues.apache.org/jira/browse/GEODE-7664
> Project: Geode
> Issue Type: Bug
>Reporter: Ivan Godwin
>Assignee: Jinmei Liao
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1454]
>
> {code:java}
> org.apache.geode.management.client.ClientClusterManagementServiceDUnitTest >
> deleteRegionOnSpecificGroup FAILEDjava.lang.AssertionError: Suspicious
> strings were written to the log during this run.Fix the strings or use
> IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1874 [error 2020/01/09 18:52:37.224 GMT
> tid=353]
> org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
> concurrencyChecksEnabled]
> org.apache.geode.cache.RegionDestroyedException:org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
> concurrencyChecksEnabled]
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
> at
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
> at
> org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256)
> at
> org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:307)
> at
> org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:48)
>
> at
> org.apache.geode.management.internal.configuration.realizers.ConfigurationRealizer.exists(ConfigurationRealizer.java:35)
> at
> org.apache.geode.management.internal.functions.CacheRealizationFunction.executeUpdate(CacheRealizationFunction.java:130)
> at
> org.apache.geode.management.internal.functions.CacheRealizationFunction.execute(CacheRealizationFunction.java:79)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:394)
>
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:458)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:449)
> at
> org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:379)
> at
> org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7965) Modify Redis SADD command to use region.compute
[ https://issues.apache.org/jira/browse/GEODE-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-7965. - Fix Version/s: 1.13.0 Resolution: Fixed > Modify Redis SADD command to use region.compute > > > Key: GEODE-7965 > URL: https://issues.apache.org/jira/browse/GEODE-7965 > Project: Geode > Issue Type: Improvement >Reporter: John Hutchison >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.13.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Geode implementation of this command has been modified to use the > region.compute command to improve reliability. This is stage one of an > experiment to test out an effort to improve both reliability and performance > by a series of changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7965) Modify Redis SADD command to use region.compute
[ https://issues.apache.org/jira/browse/GEODE-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-7965: --- Assignee: Darrel Schneider > Modify Redis SADD command to use region.compute > > > Key: GEODE-7965 > URL: https://issues.apache.org/jira/browse/GEODE-7965 > Project: Geode > Issue Type: Improvement >Reporter: John Hutchison >Assignee: Darrel Schneider >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > Geode implementation of this command has been modified to use the > region.compute command to improve reliability. This is stage one of an > experiment to test out an effort to improve both reliability and performance > by a series of changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7965) Modify Redis SADD command to use region.compute
[ https://issues.apache.org/jira/browse/GEODE-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079991#comment-17079991 ] ASF subversion and git services commented on GEODE-7965: Commit 464c7495c35c62241cfd20ace5722c873ff5068b in geode's branch refs/heads/develop from John Hutchison [ https://gitbox.apache.org/repos/asf?p=geode.git;h=464c749 ] GEODE-7965: Modify Redis SADD command to use region.compute (#4918) * GEODE-7965: Modify Redis SADD command to use region.compute Co-authored-by: Ray Ingles Co-authored-by: John Hutchison > Modify Redis SADD command to use region.compute > > > Key: GEODE-7965 > URL: https://issues.apache.org/jira/browse/GEODE-7965 > Project: Geode > Issue Type: Improvement >Reporter: John Hutchison >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.13.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Geode implementation of this command has been modified to use the > region.compute command to improve reliability. This is stage one of an > experiment to test out an effort to improve both reliability and performance > by a series of changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7965) Modify Redis SADD command to use region.compute
[ https://issues.apache.org/jira/browse/GEODE-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079990#comment-17079990 ] ASF subversion and git services commented on GEODE-7965: Commit 464c7495c35c62241cfd20ace5722c873ff5068b in geode's branch refs/heads/develop from John Hutchison [ https://gitbox.apache.org/repos/asf?p=geode.git;h=464c749 ] GEODE-7965: Modify Redis SADD command to use region.compute (#4918) * GEODE-7965: Modify Redis SADD command to use region.compute Co-authored-by: Ray Ingles Co-authored-by: John Hutchison > Modify Redis SADD command to use region.compute > > > Key: GEODE-7965 > URL: https://issues.apache.org/jira/browse/GEODE-7965 > Project: Geode > Issue Type: Improvement >Reporter: John Hutchison >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.13.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Geode implementation of this command has been modified to use the > region.compute command to improve reliability. This is stage one of an > experiment to test out an effort to improve both reliability and performance > by a series of changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7953) Create Restore Redundancy Internal API
[ https://issues.apache.org/jira/browse/GEODE-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans updated GEODE-7953: --- Component/s: regions > Create Restore Redundancy Internal API > -- > > Key: GEODE-7953 > URL: https://issues.apache.org/jira/browse/GEODE-7953 > Project: Geode > Issue Type: New Feature > Components: regions >Reporter: Donal Evans >Assignee: Donal Evans >Priority: Major > Time Spent: 2h 40m > Remaining Estimate: 0h > > Introduce an internal API to allow redundancy to be restored and primary > bucket hosts reassigned without necessitating a full rebalance. > As described in the RFC found here: > https://cwiki.apache.org/confluence/display/GEODE/Redundancy+Gfsh+Commands -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7852) Add client side configuration option to support a SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079641#comment-17079641 ] ASF subversion and git services commented on GEODE-7852: Commit 4f2a6047d5b272982595e3b7e71c624d61c69415 in geode's branch refs/heads/develop from Bill Burcham [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4f2a604 ] GEODE-7852: test SNI client against a geode (2-node) cluster (#4925) > Add client side configuration option to support a SNI proxy > --- > > Key: GEODE-7852 > URL: https://issues.apache.org/jira/browse/GEODE-7852 > Project: Geode > Issue Type: Improvement > Components: client/server, membership >Reporter: Dan Smith >Assignee: Bruce J Schuchardt >Priority: Major > Fix For: 1.13.0 > > Time Spent: 5h 40m > Remaining Estimate: 0h > > Add an option to the client side configuration to support a the use of a [SNI > proxy|https://www.bamsoftware.com/computers/sniproxy/]. > See also GEODE-7837, which adds a system property to support a SNI proxy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7976) make the "config" param not required when deploy a jar using management rest api
[
https://issues.apache.org/jira/browse/GEODE-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079620#comment-17079620
]
ASF subversion and git services commented on GEODE-7976:
Commit a73dffc4f0b7370a9374797f64d9a513beec3400 in geode's branch
refs/heads/develop from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a73dffc ]
GEODE-7976: make "config" param optional when deploy using CMS. (#4930)
> make the "config" param not required when deploy a jar using management rest
> api
>
>
> Key: GEODE-7976
> URL: https://issues.apache.org/jira/browse/GEODE-7976
> Project: Geode
> Issue Type: Improvement
> Components: management
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently user has to pass in a "config" param when deploy a jar using the
> rest api, even though most of the time it's just an empty json "{}" if user
> just want to deploy to the "cluster" group. make this parameter optional
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7969) bump netty to 4.1.48
[ https://issues.apache.org/jira/browse/GEODE-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-7969: Summary: bump netty to 4.1.48 (was: bump netty to 4.1.48 on support/1.12 to match develop) > bump netty to 4.1.48 > > > Key: GEODE-7969 > URL: https://issues.apache.org/jira/browse/GEODE-7969 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Fix For: 1.12.1, 1.13.0 > > Time Spent: 40m > Remaining Estimate: 0h > > as part of GEODE-7798: Fix flakiness in PubSubTest, the netty version was > increased on develop; this version should be the minimum used on support > branches as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7852) Add client side configuration option to support a SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079396#comment-17079396 ] ASF subversion and git services commented on GEODE-7852: Commit a12d1fe3e1f66adfcdc8ff5c414abb69f3c8f3cd in geode's branch refs/heads/develop from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a12d1fe ] Merge pull request #4920 from apache/feature/GEODE-7852doc GEODE-7852: SNI extension support > Add client side configuration option to support a SNI proxy > --- > > Key: GEODE-7852 > URL: https://issues.apache.org/jira/browse/GEODE-7852 > Project: Geode > Issue Type: Improvement > Components: client/server, membership >Reporter: Dan Smith >Assignee: Bruce J Schuchardt >Priority: Major > Fix For: 1.13.0 > > Time Spent: 5h 20m > Remaining Estimate: 0h > > Add an option to the client side configuration to support a the use of a [SNI > proxy|https://www.bamsoftware.com/computers/sniproxy/]. > See also GEODE-7837, which adds a system property to support a SNI proxy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7852) Add client side configuration option to support a SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079395#comment-17079395 ] ASF subversion and git services commented on GEODE-7852: Commit a12d1fe3e1f66adfcdc8ff5c414abb69f3c8f3cd in geode's branch refs/heads/develop from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a12d1fe ] Merge pull request #4920 from apache/feature/GEODE-7852doc GEODE-7852: SNI extension support > Add client side configuration option to support a SNI proxy > --- > > Key: GEODE-7852 > URL: https://issues.apache.org/jira/browse/GEODE-7852 > Project: Geode > Issue Type: Improvement > Components: client/server, membership >Reporter: Dan Smith >Assignee: Bruce J Schuchardt >Priority: Major > Fix For: 1.13.0 > > Time Spent: 5h 20m > Remaining Estimate: 0h > > Add an option to the client side configuration to support a the use of a [SNI > proxy|https://www.bamsoftware.com/computers/sniproxy/]. > See also GEODE-7837, which adds a system property to support a SNI proxy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7852) Add client side configuration option to support a SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079394#comment-17079394 ] ASF subversion and git services commented on GEODE-7852: Commit 276582533c885092d8e1d076d426a4c9f2e0b908 in geode's branch refs/heads/develop from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2765825 ] GEODE-7852: SNI extension support Modified SNISocketFactory so it can be used in cache.xml Added a test for the new cache.xml element. Updated docs for cache.xml and updated client configuration instructions. > Add client side configuration option to support a SNI proxy > --- > > Key: GEODE-7852 > URL: https://issues.apache.org/jira/browse/GEODE-7852 > Project: Geode > Issue Type: Improvement > Components: client/server, membership >Reporter: Dan Smith >Assignee: Bruce J Schuchardt >Priority: Major > Fix For: 1.13.0 > > Time Spent: 5h 20m > Remaining Estimate: 0h > > Add an option to the client side configuration to support a the use of a [SNI > proxy|https://www.bamsoftware.com/computers/sniproxy/]. > See also GEODE-7837, which adds a system property to support a SNI proxy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (GEODE-7969) bump netty to 4.1.48 on support/1.12 to match develop
[ https://issues.apache.org/jira/browse/GEODE-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-7969: Comment: was deleted (was: note: fixed on develop (1.13) as part of GEODE-7798) > bump netty to 4.1.48 on support/1.12 to match develop > - > > Key: GEODE-7969 > URL: https://issues.apache.org/jira/browse/GEODE-7969 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Fix For: 1.12.1, 1.13.0 > > Time Spent: 40m > Remaining Estimate: 0h > > as part of GEODE-7798: Fix flakiness in PubSubTest, the netty version was > increased on develop; this version should be the minimum used on support > branches as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7969) bump netty to 4.1.48 on support/1.12 to match develop
[ https://issues.apache.org/jira/browse/GEODE-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079118#comment-17079118 ] ASF subversion and git services commented on GEODE-7969: Commit 8f9f4b7e869022281a189bc25eed23815e88698e in geode's branch refs/heads/develop from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8f9f4b7 ] GEODE-7969: bump netty version to latest (#4933) > bump netty to 4.1.48 on support/1.12 to match develop > - > > Key: GEODE-7969 > URL: https://issues.apache.org/jira/browse/GEODE-7969 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Fix For: 1.12.1, 1.13.0 > > Time Spent: 40m > Remaining Estimate: 0h > > as part of GEODE-7798: Fix flakiness in PubSubTest, the netty version was > increased on develop; this version should be the minimum used on support > branches as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7940) A parallel GatewaySender stops sending events if another GatewaySender that was attached to the same region is destroyed
[
https://issues.apache.org/jira/browse/GEODE-7940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079098#comment-17079098
]
Juan Ramos commented on GEODE-7940:
---
The root issue here is that we are tracking *_only one shadow bucket_* per
{{BucketAdvisor}}, even if there's more than one shadow bucket (more than one
parallel {{gateway-sender}}) attached to the same region.
Assuming that we have 2 parallel {{gateway-senders}}, named _*site2*_ and
_*site3*_, attached to the same region, the logs below show what happens when
we destroy _*sender3*_ (the original PR has only one bucket to make
troubleshooting easier):
{noformat}
[vm3] [info 2020/04/09 10:03:10.449 IST
tid=0x13] [JUAN]: Destroying /site3_PARALLEL_GATEWAY_SENDER_QUEUE...
[vm3] [info 2020/04/09 10:03:10.450 IST
tid=0x13] Partitioned Region /site3_PARALLEL_GATEWAY_SENDER_QUEUE with prId=3
is being destroyed.
[vm3] [warn 2020/04/09 10:03:10.451 IST
tid=0x13] Redundancy has dropped below 1 configured copies to 0 actual copies
for /site3_PARALLEL_GATEWAY_SENDER_QUEUE
[vm3] [warn 2020/04/09 10:03:10.451 IST
tid=0x13] All in memory copies of some data have been lost for
/site3_PARALLEL_GATEWAY_SENDER_QUEUE
[vm3] [info 2020/04/09 10:03:10.453 IST
tid=0x13] [JUAN]: Marking bucket
/__PR/_B__site3__PARALLEL__GATEWAY__SENDER__QUEUE_0 as destroyed through
advisor for bucket
/__PR/_B__destroyParallelGatewaySenderShouldNotStopCorruptOtherSendersAttachedToTheRegion_0...
[vm3] [info 2020/04/09 10:03:10.454 IST
tid=0x13] [JUAN]: Marking bucket
/__PR/_B__site3__PARALLEL__GATEWAY__SENDER__QUEUE_0 as destroyed through
advisor for bucket
/__PR/_B__destroyParallelGatewaySenderShouldNotStopCorruptOtherSendersAttachedToTheRegion_0...
Done!.
[vm3] [info 2020/04/09 10:03:10.457 IST
tid=0x13] Configured redundancy of 1 copies has been restored to
/site3_PARALLEL_GATEWAY_SENDER_QUEUE
[vm3] [info 2020/04/09 10:03:10.458 IST
tid=0x13] Partitioned Region /site3_PARALLEL_GATEWAY_SENDER_QUEUE with prId=3
is destroyed.
[vm3] [info 2020/04/09 10:03:10.459 IST
tid=0x13] [JUAN]: Destroying /site3_PARALLEL_GATEWAY_SENDER_QUEUE... Done!.
{noformat}
When other entries are inserted into the region afterwards, we can see that the
{{gateway-sender}} for _*site2*_ refuses to add the event into the queue
(silently, not even a warning) because the "it thinks" that the shadow bucket
has [been
destroyed|https://github.com/apache/geode/blob/develop/geode-core/src/main/java/org/apache/geode/internal/cache/wan/parallel/ParallelGatewaySenderQueue.java#L793-L813]
({{BucketAdvisor}} only keeps track of one shadow bucket per root bucket).
{noformat}
[vm3] [info 2020/04/09 10:03:10.462 IST
tid=0x13] [JUAN]: Putting Event with key Key1 into queue.
[vm3] [info 2020/04/09 10:03:10.462 IST
tid=0x13] [JUAN]: Bucket 0 destroyed for key Key1 and shadowKey 2.
[vm3] [info 2020/04/09 10:03:10.462 IST
tid=0x13] brq.isDestroyed(): false
[vm3] [info 2020/04/09 10:03:10.463 IST
tid=0x13] prQ: /site2_PARALLEL_GATEWAY_SENDER_QUEUE
[vm3] [info 2020/04/09 10:03:10.463 IST
tid=0x13]
prQ.getCoLocatedWithRegion().getRegionAdvisor().getBucketAdvisor(bucketId).getBucket().getFullPath():
/__PR/_B__destroyParallelGatewaySenderShouldNotStopCorruptOtherSendersAttachedToTheRegion_0
[vm3] [info 2020/04/09 10:03:10.463 IST
tid=0x13]
prQ.getCoLocatedWithRegion().getRegionAdvisor().getBucketAdvisor(bucketId).getShadowBucketDestroyed():
true
[vm3] [info 2020/04/09 10:03:10.463 IST
tid=0x13] [JUAN]: Putting Event with key Key1 into queue, done?: false
{noformat}
> A parallel GatewaySender stops sending events if another GatewaySender that
> was attached to the same region is destroyed
>
>
> Key: GEODE-7940
> URL: https://issues.apache.org/jira/browse/GEODE-7940
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barrett Oglesby
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Attachments: create-sender-alter-region-all-gfsh_04-01-2020.tgz
>
>
> The attached test reproduces this issue. It has a readme that describes how
> to run it.
> It starts 3 distributed systems named ln, ny and tk.
> ny and tk each have a gateway receiver and a region defined.
> Use gfsh in ln to:
> 1. Create sender to ny
> 2. Create region with sender to ny
> 3. Start doing puts from a client (verify updates are happening in ny)
> 4. Create sender to tk
> 5. Alter region add sender to tk (verify updates are happening in tk)
> 6. Stop sender to ny
> 7. Alter region remove sender to ny
> 8. Destroy sender to ny
> Updates should stop to ny but not tk, but updates to both stop.
> The ln log contains no exceptions. The stats show
[jira] [Updated] (GEODE-7969) bump netty to 4.1.48 on support/1.12 to match develop
[ https://issues.apache.org/jira/browse/GEODE-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-7969: Summary: bump netty to 4.1.48 on support/1.12 to match develop (was: bump netty to 4.1.45 on support/1.12 to match develop) > bump netty to 4.1.48 on support/1.12 to match develop > - > > Key: GEODE-7969 > URL: https://issues.apache.org/jira/browse/GEODE-7969 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Fix For: 1.12.1, 1.13.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > as part of GEODE-7798: Fix flakiness in PubSubTest, the netty version was > increased on develop; this version should be the minimum used on support > branches as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7969) bump netty to 4.1.45 on support/1.12 to match develop
[ https://issues.apache.org/jira/browse/GEODE-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079005#comment-17079005 ] ASF subversion and git services commented on GEODE-7969: Commit 071be54787f295062a6e4f7bd6e65822eb9bfa0d in geode's branch refs/heads/support/1.12 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=071be54 ] GEODE-7969: bump netty version on support/1.12 to match develop > bump netty to 4.1.45 on support/1.12 to match develop > - > > Key: GEODE-7969 > URL: https://issues.apache.org/jira/browse/GEODE-7969 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Fix For: 1.12.1, 1.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > > as part of GEODE-7798: Fix flakiness in PubSubTest, the netty version was > increased on develop; this version should be the minimum used on support > branches as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
