[jira] [Commented] (GEODE-8231) C++ native client keeps trying to connect to down cache server hosting a partitioned region
[ https://issues.apache.org/jira/browse/GEODE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320800#comment-17320800 ] ASF GitHub Bot commented on GEODE-8231: --- alb3rtobr commented on pull request #783: URL: https://github.com/apache/geode-native/pull/783#issuecomment-819334765 This PR also reverts code from GEODE-8565, which was an addition over GEODE-8231 solution. So I think this PR should contain the revert of GEODE-8688, GEODE-8565 and GEODE-8231. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > C++ native client keeps trying to connect to down cache server hosting a > partitioned region > --- > > Key: GEODE-8231 > URL: https://issues.apache.org/jira/browse/GEODE-8231 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > If a C++ client connected to a cluster is sending operations to a partitioned > region and one of the server goes down, the client keeps trying to send > operations to the down server. This can be observed in the logs by a > continuous flow of lines containing: "IO error in handshake with endpoint..." > The Java client, once it detects a server is down, it deletes it from the > client metadata so there are no tries to connect to the server until the > server is up again which is notified via a metadata refresh. > The aim of this ticket is to align the behavior of the C++ native client to > the Java client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321039#comment-17321039
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#148|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/148]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0138/test-results/distributedTest/1618353681/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0138/test-artifacts/1618353681/distributedtestfiles-OpenJDK8-1.15.0-build.0138.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Mark Hanson
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321042#comment-17321042
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#149.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/149.1]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0139/test-results/distributedTest/1618372269/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0139/test-artifacts/1618372269/distributedtestfiles-OpenJDK8-1.15.0-build.0139.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Mark Hanson
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321043#comment-17321043
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#146.2|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/146.2]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0136/test-results/distributedTest/1618364696/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0136/test-artifacts/1618364696/distributedtestfiles-OpenJDK8-1.15.0-build.0136.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Mark Hanson
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9070) CI Failure: ClientServerSessionCacheDUnitTest > addServerToExistingClusterCreatesSessionRegion
[
https://issues.apache.org/jira/browse/GEODE-9070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321046#comment-17321046
]
Geode Integration commented on GEODE-9070:
--
Seen in [DistributedTestOpenJDK8
#149|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/149]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0139/test-results/distributedTest/1618355280/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0139/test-artifacts/1618355280/distributedtestfiles-OpenJDK8-1.15.0-build.0139.tgz].
> CI Failure: ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion
> --
>
> Key: GEODE-9070
> URL: https://issues.apache.org/jira/browse/GEODE-9070
> Project: Geode
> Issue Type: Bug
> Components: ci, http session
>Reporter: Jens Deppe
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion FAILED
> 00:47:45org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$84/1299235653.run
> in VM 1 running on Host 51208612ea94 with 4 VMs
> 00:47:45at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 00:47:45at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.addServerToExistingClusterCreatesSessionRegion(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[] within 5 minutes.
> 00:47:45at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:47:45at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:47:45at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$addServerToExistingClusterCreatesSessionRegion$bb17a952$1(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45java.lang.AssertionError:
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[]
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateBootstrapped(ClientServerSessionCacheDUnitTest.java:258)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateServer(ClientServerSessionCacheDUnitTest.java:245)
> 00:47:53{noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161716/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-artifacts/161716/distributedtestfiles-OpenJDK8-1.15.0-build.0081.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321041#comment-17321041
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#144.3|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/144.3]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0134/test-results/distributedTest/1618363345/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0134/test-artifacts/1618363345/distributedtestfiles-OpenJDK8-1.15.0-build.0134.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Mark Hanson
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9151) Logging Attributes Aren't Honored
Michael Martell created GEODE-9151: -- Summary: Logging Attributes Aren't Honored Key: GEODE-9151 URL: https://issues.apache.org/jira/browse/GEODE-9151 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Martell The Logging Properties below for maximum disk space and maximum file size aren't being honored: * log-disk-space-limit * log-file-size-limit According to the [Native Client documentation|https://gemfire-native-cpp.docs.pivotal.io/102/geode-native-client-cpp/configuring/sysprops.html#attributes-gfcpp__table_logging_props], both of these properties should allow a value of zero to allow unlimited storage. It is possible to get unlimited by setting one of these to zero, but not both. Perhaps the docs should be changed to reflect the actual behavior. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9151) Logging Attributes Aren't Honored
[ https://issues.apache.org/jira/browse/GEODE-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Martell updated GEODE-9151: --- Priority: Minor (was: Major) > Logging Attributes Aren't Honored > - > > Key: GEODE-9151 > URL: https://issues.apache.org/jira/browse/GEODE-9151 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Minor > > The Logging Properties below for maximum disk space and maximum file size > aren't being honored: > * log-disk-space-limit > * log-file-size-limit > According to the [Native Client > documentation|https://gemfire-native-cpp.docs.pivotal.io/102/geode-native-client-cpp/configuring/sysprops.html#attributes-gfcpp__table_logging_props], > both of these properties should allow a value of zero to allow unlimited > storage. > It is possible to get unlimited by setting one of these to zero, but not > both. Perhaps the docs should be changed to reflect the actual behavior. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8231) C++ native client keeps trying to connect to down cache server hosting a partitioned region
[ https://issues.apache.org/jira/browse/GEODE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321056#comment-17321056 ] ASF GitHub Bot commented on GEODE-8231: --- pdxcodemonkey commented on pull request #783: URL: https://github.com/apache/geode-native/pull/783#issuecomment-819570757 > This PR also reverts code from GEODE-8565, which was an addition over GEODE-8231 solution. > So I think this PR should contain the revert of GEODE-8688, GEODE-8565 and GEODE-8231. Agree, this is the revert of all 3 of these. This is just a title change for the PR, though, right? I have reviewed the 3 earlier PRs and see no remaining code from them... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > C++ native client keeps trying to connect to down cache server hosting a > partitioned region > --- > > Key: GEODE-8231 > URL: https://issues.apache.org/jira/browse/GEODE-8231 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > If a C++ client connected to a cluster is sending operations to a partitioned > region and one of the server goes down, the client keeps trying to send > operations to the down server. This can be observed in the logs by a > continuous flow of lines containing: "IO error in handshake with endpoint..." > The Java client, once it detects a server is down, it deletes it from the > client metadata so there are no tries to connect to the server until the > server is up again which is notified via a metadata refresh. > The aim of this ticket is to align the behavior of the C++ native client to > the Java client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8231) C++ native client keeps trying to connect to down cache server hosting a partitioned region
[ https://issues.apache.org/jira/browse/GEODE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321073#comment-17321073 ] ASF GitHub Bot commented on GEODE-8231: --- albertogpz commented on pull request #783: URL: https://github.com/apache/geode-native/pull/783#issuecomment-819593811 I wonder if it would make more sense to write a JIRA to fix the problem caused by the GEODE-8231 PR instead of reverting 3 PRs that have been for months in the develop branch. I do not know if I understood correctly the issue but wouldn't a possible solution be to change the eventId of the "leftover" keys (the keys for those puts that were not sent because the server went down) before sending them in the new thread to another server? If we did so, we could keep the code in the "PRs to be reverted", fix the issue and have a test case to verify that everything works as expected. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > C++ native client keeps trying to connect to down cache server hosting a > partitioned region > --- > > Key: GEODE-8231 > URL: https://issues.apache.org/jira/browse/GEODE-8231 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > If a C++ client connected to a cluster is sending operations to a partitioned > region and one of the server goes down, the client keeps trying to send > operations to the down server. This can be observed in the logs by a > continuous flow of lines containing: "IO error in handshake with endpoint..." > The Java client, once it detects a server is down, it deletes it from the > client metadata so there are no tries to connect to the server until the > server is up again which is notified via a metadata refresh. > The aim of this ticket is to align the behavior of the C++ native client to > the Java client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8231) C++ native client keeps trying to connect to down cache server hosting a partitioned region
[ https://issues.apache.org/jira/browse/GEODE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321075#comment-17321075 ] ASF GitHub Bot commented on GEODE-8231: --- albertogpz edited a comment on pull request #783: URL: https://github.com/apache/geode-native/pull/783#issuecomment-819593811 I wonder if it would make more sense to write a JIRA to fix the problem caused by the GEODE-8231 PR instead of reverting 3 PRs that have been for months in the develop branch taking into account also that it is not making any current test case fail. I do not know if I understood correctly the issue but wouldn't a possible solution be to change the eventId of the "leftover" keys (the keys for those puts that were not sent because the server went down) before sending them in the new thread to another server? If we did so, we could keep the code in the "PRs to be reverted", fix the issue and have a test case to verify that everything works as expected. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > C++ native client keeps trying to connect to down cache server hosting a > partitioned region > --- > > Key: GEODE-8231 > URL: https://issues.apache.org/jira/browse/GEODE-8231 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > If a C++ client connected to a cluster is sending operations to a partitioned > region and one of the server goes down, the client keeps trying to send > operations to the down server. This can be observed in the logs by a > continuous flow of lines containing: "IO error in handshake with endpoint..." > The Java client, once it detects a server is down, it deletes it from the > client metadata so there are no tries to connect to the server until the > server is up again which is notified via a metadata refresh. > The aim of this ticket is to align the behavior of the C++ native client to > the Java client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8231) C++ native client keeps trying to connect to down cache server hosting a partitioned region
[ https://issues.apache.org/jira/browse/GEODE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321077#comment-17321077 ] ASF GitHub Bot commented on GEODE-8231: --- pdxcodemonkey commented on pull request #783: URL: https://github.com/apache/geode-native/pull/783#issuecomment-819596325 > I wonder if it would make more sense to write a JIRA to fix the problem caused by the GEODE-8231 PR instead of reverting 3 PRs that have been for months in the develop branch. > > I do not know if I understood correctly the issue but wouldn't a possible solution be to change the eventId of the "leftover" keys (the keys for those puts that were not sent because the server went down) before sending them in the new thread to another server? > > If we did so, we could keep the code in the "PRs to be reverted", fix the issue and have a test case to verify that everything works as expected. I'm looking into it - don't think this one is going to be merged right away, because the fix may be simpler and IMO lower-risk than reverting all this code. Writing the test is going to be tough - we had to modify Geode server code in order to reproduce the issue in the first place. At any rate I'll update things here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > C++ native client keeps trying to connect to down cache server hosting a > partitioned region > --- > > Key: GEODE-8231 > URL: https://issues.apache.org/jira/browse/GEODE-8231 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > If a C++ client connected to a cluster is sending operations to a partitioned > region and one of the server goes down, the client keeps trying to send > operations to the down server. This can be observed in the logs by a > continuous flow of lines containing: "IO error in handshake with endpoint..." > The Java client, once it detects a server is down, it deletes it from the > client metadata so there are no tries to connect to the server until the > server is up again which is notified via a metadata refresh. > The aim of this ticket is to align the behavior of the C++ native client to > the Java client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8231) C++ native client keeps trying to connect to down cache server hosting a partitioned region
[ https://issues.apache.org/jira/browse/GEODE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321080#comment-17321080 ] ASF GitHub Bot commented on GEODE-8231: --- albertogpz commented on pull request #783: URL: https://github.com/apache/geode-native/pull/783#issuecomment-819597609 > > I wonder if it would make more sense to write a JIRA to fix the problem caused by the GEODE-8231 PR instead of reverting 3 PRs that have been for months in the develop branch. > > I do not know if I understood correctly the issue but wouldn't a possible solution be to change the eventId of the "leftover" keys (the keys for those puts that were not sent because the server went down) before sending them in the new thread to another server? > > If we did so, we could keep the code in the "PRs to be reverted", fix the issue and have a test case to verify that everything works as expected. > > I'm looking into it - don't think this one is going to be merged right away, because the fix may be simpler and IMO lower-risk than reverting all this code. Writing the test is going to be tough - we had to modify Geode server code in order to reproduce the issue in the first place. At any rate I'll update things here. Great. Thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > C++ native client keeps trying to connect to down cache server hosting a > partitioned region > --- > > Key: GEODE-8231 > URL: https://issues.apache.org/jira/browse/GEODE-8231 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > If a C++ client connected to a cluster is sending operations to a partitioned > region and one of the server goes down, the client keeps trying to send > operations to the down server. This can be observed in the logs by a > continuous flow of lines containing: "IO error in handshake with endpoint..." > The Java client, once it detects a server is down, it deletes it from the > client metadata so there are no tries to connect to the server until the > server is up again which is notified via a metadata refresh. > The aim of this ticket is to align the behavior of the C++ native client to > the Java client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8231) C++ native client keeps trying to connect to down cache server hosting a partitioned region
[ https://issues.apache.org/jira/browse/GEODE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321112#comment-17321112 ] ASF GitHub Bot commented on GEODE-8231: --- echobravopapa commented on pull request #783: URL: https://github.com/apache/geode-native/pull/783#issuecomment-819635026 @albertogpz this change alters consistent behavior between clients (java & native) along with data loss, in the near term the most prudent approach is to remove the code causing the issues. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > C++ native client keeps trying to connect to down cache server hosting a > partitioned region > --- > > Key: GEODE-8231 > URL: https://issues.apache.org/jira/browse/GEODE-8231 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > If a C++ client connected to a cluster is sending operations to a partitioned > region and one of the server goes down, the client keeps trying to send > operations to the down server. This can be observed in the logs by a > continuous flow of lines containing: "IO error in handshake with endpoint..." > The Java client, once it detects a server is down, it deletes it from the > client metadata so there are no tries to connect to the server until the > server is up again which is notified via a metadata refresh. > The aim of this ticket is to align the behavior of the C++ native client to > the Java client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8231) C++ native client keeps trying to connect to down cache server hosting a partitioned region
[ https://issues.apache.org/jira/browse/GEODE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321115#comment-17321115 ] ASF GitHub Bot commented on GEODE-8231: --- pivotal-jbarrett commented on pull request #783: URL: https://github.com/apache/geode-native/pull/783#issuecomment-819638960 > @albertogpz this change alters consistent behavior between clients (java & native) along with data loss, in the near term the most prudent approach is to remove the code causing the issues. @echobravopapa I have to say I disagree. The change to fix the PUTALL problem is simple. The impact the targeted removal of bucket metadata is more positive since it affects all single value operations. The only operations degraded are the multikey operations, which are more rare. The timing to get either change in is the same so I would vote to get the more complete fix in. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > C++ native client keeps trying to connect to down cache server hosting a > partitioned region > --- > > Key: GEODE-8231 > URL: https://issues.apache.org/jira/browse/GEODE-8231 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > If a C++ client connected to a cluster is sending operations to a partitioned > region and one of the server goes down, the client keeps trying to send > operations to the down server. This can be observed in the logs by a > continuous flow of lines containing: "IO error in handshake with endpoint..." > The Java client, once it detects a server is down, it deletes it from the > client metadata so there are no tries to connect to the server until the > server is up again which is notified via a metadata refresh. > The aim of this ticket is to align the behavior of the C++ native client to > the Java client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8320) SerialWANStatsDUnitTest.testReplicatedSerialPropagationHAWithGroupTransactionEvents is failiing
[
https://issues.apache.org/jira/browse/GEODE-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Gomez resolved GEODE-8320.
--
Fix Version/s: 1.15.0
Resolution: Fixed
The ConcurrentModification exceptions were provoking that events were not
peeked from the queue to complete transactions. The solution for GEODE-9122
fixes the issue.
> SerialWANStatsDUnitTest.testReplicatedSerialPropagationHAWithGroupTransactionEvents
> is failiing
> ---
>
> Key: GEODE-8320
> URL: https://issues.apache.org/jira/browse/GEODE-8320
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Mark Hanson
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0, 1.15.0
>
>
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest >
> testReplicatedSerialPropagationHAWithGroupTransactionEvents FAILED
> 11:55:01
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest$$Lambda$134/1929719983.run
> in VM 2 running on Host 249227cf2774 with 8 VMs
> 11:55:01
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> 11:55:01
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> 11:55:01
> at
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest.testReplicatedSerialPropagationHAWithGroupTransactionEvents(SerialWANStatsDUnitTest.java:578)
> 11:55:01
> 11:55:01
> Caused by:
> 11:55:01
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined
> as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase
> that uses int, intorg.apache.geode.cache.Region Expected region entries:
> 2 but actual entries: 1 present region keyset [7435200, <*
> Intentionally cut out by Jira submitter *> 8851200] expected:<2> but
> was:<1> within 5 minutes.
> 11:55:01
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 11:55:01
> at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 11:55:01
> at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 11:55:01
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 11:55:01
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 11:55:01
> at
> org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2942)
> 11:55:01
> at
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest.lambda$testReplicatedSerialPropagationHAWithGroupTransactionEvents$bb17a952$8(SerialWANStatsDUnitTest.java:578)
> 11:55:01
> 11:55:01
> Caused by:
> 11:55:01
> java.lang.AssertionError: Expected region entries: 2 but actual entries:
> 1 present region keyset [7435200, <*Intentionally cut out by Jira
> submitter*> ] expected:<2> but was:<1>
> 12:31:11
> {noformat}
>
>
>
>
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0193/test-results/distributedTest/1593463337/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0193/test-artifacts/1593463337/distributedtestfiles-OpenJDK8-1.14.0-build.0193.tgz
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9152) Logging statements using log markers should be INFO level
Kirk Lund created GEODE-9152: Summary: Logging statements using log markers should be INFO level Key: GEODE-9152 URL: https://issues.apache.org/jira/browse/GEODE-9152 Project: Geode Issue Type: Bug Components: logging Reporter: Kirk Lund Logging statements using log markers should be INFO level. Having log markers at TRACE or DEBUG is worthless because you have to set the log-level to TRACE and also enable that log marker which will fill the disk with logging. All of the logging statements with log markers should be changed to INFO level. Then having the log-level set to INFO and enabling the log marker will enable that log statement which is the expectation that most users and developers have. In Geode, all log markers are defined in geode-core/src/main/java/org/apache/internal/logging/log4j/LogMarker. The ideal test would simply be a LogMarker test which enables one LogMarker at a time and verifies that logging it at INFO level results in it being logged as expected. Then all uses of that LogMarker should be changed to INFO level. I don't think every class using that LogMarker needs to have tests for enabling or disabling it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9153) alpine-tools image fails to build
Sean Goller created GEODE-9153: -- Summary: alpine-tools image fails to build Key: GEODE-9153 URL: https://issues.apache.org/jira/browse/GEODE-9153 Project: Geode Issue Type: Bug Components: ci Reporter: Sean Goller The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9153: -- Labels: pull-request-available (was: ) > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321331#comment-17321331 ] ASF subversion and git services commented on GEODE-9153: Commit 3b4d4acb7a981fec56125cde6d235d5a4db84dff in geode's branch refs/heads/develop from Sean Goller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3b4d4ac ] GEODE-9153: Fix alpine-tools docker image (#6321) * Use same image for builder as deployment * Add py3-yaml package so python doesn't try to build it. > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321334#comment-17321334 ] ASF subversion and git services commented on GEODE-9153: Commit ca026371d092492e88c88e0f73e5e9a3d3747fea in geode's branch refs/heads/support/1.12 from Sean Goller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ca02637 ] GEODE-9153: Fix alpine-tools docker image (#6321) * Use same image for builder as deployment * Add py3-yaml package so python doesn't try to build it. > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321335#comment-17321335 ] ASF subversion and git services commented on GEODE-9153: Commit 25d42c721dd3d3e5d5ffbf45b23e1f7b1e46d1be in geode's branch refs/heads/support/1.13 from Sean Goller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=25d42c7 ] GEODE-9153: Fix alpine-tools docker image (#6321) * Use same image for builder as deployment * Add py3-yaml package so python doesn't try to build it. > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Goller reassigned GEODE-9153: -- Assignee: Sean Goller > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Assignee: Sean Goller >Priority: Major > Labels: pull-request-available > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321336#comment-17321336 ] ASF subversion and git services commented on GEODE-9153: Commit 9e01d9b6297f14bf5794dd49d96466cd7a6f5d45 in geode's branch refs/heads/support/1.14 from Sean Goller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9e01d9b ] GEODE-9153: Fix alpine-tools docker image (#6321) * Use same image for builder as deployment * Add py3-yaml package so python doesn't try to build it. > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Assignee: Sean Goller >Priority: Major > Labels: pull-request-available > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Goller resolved GEODE-9153. Fix Version/s: 1.15.0 1.14.0 1.13.3 1.12.2 Resolution: Fixed > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Assignee: Sean Goller >Priority: Major > Labels: pull-request-available > Fix For: 1.12.2, 1.13.3, 1.14.0, 1.15.0 > > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321338#comment-17321338 ] Geode Integration commented on GEODE-9153: -- Seen on support/1.14 in [build-alpine-tools-docker-image #5|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-images/jobs/build-alpine-tools-docker-image/builds/5]. > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Assignee: Sean Goller >Priority: Major > Labels: pull-request-available > Fix For: 1.12.2, 1.13.3, 1.14.0, 1.15.0 > > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321339#comment-17321339 ] Geode Integration commented on GEODE-9153: -- Seen on support/1.13 in [build-alpine-tools-docker-image #5|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-images/jobs/build-alpine-tools-docker-image/builds/5]. > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Assignee: Sean Goller >Priority: Major > Labels: pull-request-available > Fix For: 1.12.2, 1.13.3, 1.14.0, 1.15.0 > > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321342#comment-17321342 ] Geode Integration commented on GEODE-9153: -- Seen in [build-alpine-tools-docker-image #5|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-images/jobs/build-alpine-tools-docker-image/builds/5]. > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Assignee: Sean Goller >Priority: Major > Labels: pull-request-available > Fix For: 1.12.2, 1.13.3, 1.14.0, 1.15.0 > > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321340#comment-17321340 ] Geode Integration commented on GEODE-9153: -- Seen on support/1.12 in [build-alpine-tools-docker-image #5|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-images/jobs/build-alpine-tools-docker-image/builds/5]. > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Assignee: Sean Goller >Priority: Major > Labels: pull-request-available > Fix For: 1.12.2, 1.13.3, 1.14.0, 1.15.0 > > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9153) alpine-tools image fails to build
[ https://issues.apache.org/jira/browse/GEODE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321341#comment-17321341 ] Geode Integration commented on GEODE-9153: -- Seen in [build-alpine-tools-docker-image #5.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-images/jobs/build-alpine-tools-docker-image/builds/5.1]. > alpine-tools image fails to build > - > > Key: GEODE-9153 > URL: https://issues.apache.org/jira/browse/GEODE-9153 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Assignee: Sean Goller >Priority: Major > Labels: pull-request-available > Fix For: 1.12.2, 1.13.3, 1.14.0, 1.15.0 > > > The alpine-tools docker image fails to build properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9101) Attribute VisibleNodes in MemberMXBean is incorrect
[
https://issues.apache.org/jira/browse/GEODE-9101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Kevo updated GEODE-9101:
--
Labels: needs-review pull-request-available (was: pull-request-available)
> Attribute VisibleNodes in MemberMXBean is incorrect
> ---
>
> Key: GEODE-9101
> URL: https://issues.apache.org/jira/browse/GEODE-9101
> Project: Geode
> Issue Type: Bug
> Components: statistics
>Reporter: Mario Kevo
>Assignee: Mario Kevo
>Priority: Major
> Labels: needs-review, pull-request-available
>
> In documentation states:
> _The current number of nodes in this distributed system visible to this
> member._
> But checking the value of the attribute we have a difference between locator
> and server.
> For example, we have the following system:
> {code:java}
>
> gfsh>list members
> Member Count : 4
> Name | Id
> | -
> locator1 | 192.168.0.145(locator1:26377:locator):41000 [Coordinator]
> locator2 | 192.168.0.145(locator2:26509:locator):41001
> server1 | 192.168.0.145(server1:26648):41002
> server2 | 192.168.0.145(server2:26768):41003
>
> {code}
>
> For locators visibleNodes = 2, but for servers visibleNodes = 3.
> Locators see only servers as visible nodes(In this case it sees *server1* and
> *server2*).
> Servers see first locator and all servers, including itself(In this case
> server1 sees *locator1*, *server1* and *server2*).
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
