[jira] [Updated] (GEODE-9390) DistributedSystem nodes is counted twice on each server member

2022-05-04 Thread Jinmei Liao (Jira) 


 [ 
https://issues.apache.org/jira/browse/GEODE-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jinmei Liao updated GEODE-9390:
---
Fix Version/s: 1.15.0

> DistributedSystem nodes is counted twice on each server member
> --
>
> Key: GEODE-9390
> URL: https://issues.apache.org/jira/browse/GEODE-9390
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Barrett Oglesby
>Assignee: Matthew Reddington
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.15.0
>
>
> Once in ClusterDistributionManager.startThreads:
> {noformat}
> [warn 2021/06/20 16:20:16.152 HST server-1  tid=0x1] 
> ClusterDistributionManager.handleManagerStartup 
> id=192.168.1.8(server-1:58386):41001; kind=10
> [warn 2021/06/20 16:20:16.153 HST server-1  tid=0x1] 
> DistributionStats.incNodes nodes=1
> java.lang.Exception
>   at 
> org.apache.geode.distributed.internal.DistributionStats.incNodes(DistributionStats.java:1362)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.handleManagerStartup(ClusterDistributionManager.java:1809)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.addNewMember(ClusterDistributionManager.java:1062)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.startThreads(ClusterDistributionManager.java:691)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:504)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:326)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:780)
> {noformat}
> And once in ClusterDistributionManager.create:
> {noformat}
> [warn 2021/06/20 16:20:16.155 HST server-1  tid=0x1] 
> ClusterDistributionManager.handleManagerStartup 
> id=192.168.1.8(server-1:58386):41001; kind=10
> [warn 2021/06/20 16:20:16.156 HST server-1  tid=0x1] 
> DistributionStats.incNodes nodes=2
> java.lang.Exception
>   at 
> org.apache.geode.distributed.internal.DistributionStats.incNodes(DistributionStats.java:1362)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.handleManagerStartup(ClusterDistributionManager.java:1809)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.addNewMember(ClusterDistributionManager.java:1062)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:354)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:780)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Resolved] (GEODE-9390) DistributedSystem nodes is counted twice on each server member

2022-05-04 Thread Jinmei Liao (Jira) 


 [ 
https://issues.apache.org/jira/browse/GEODE-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jinmei Liao resolved GEODE-9390.

  Assignee: Matthew Reddington
Resolution: Fixed

> DistributedSystem nodes is counted twice on each server member
> --
>
> Key: GEODE-9390
> URL: https://issues.apache.org/jira/browse/GEODE-9390
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Barrett Oglesby
>Assignee: Matthew Reddington
>Priority: Major
>  Labels: pull-request-available
>
> Once in ClusterDistributionManager.startThreads:
> {noformat}
> [warn 2021/06/20 16:20:16.152 HST server-1  tid=0x1] 
> ClusterDistributionManager.handleManagerStartup 
> id=192.168.1.8(server-1:58386):41001; kind=10
> [warn 2021/06/20 16:20:16.153 HST server-1  tid=0x1] 
> DistributionStats.incNodes nodes=1
> java.lang.Exception
>   at 
> org.apache.geode.distributed.internal.DistributionStats.incNodes(DistributionStats.java:1362)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.handleManagerStartup(ClusterDistributionManager.java:1809)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.addNewMember(ClusterDistributionManager.java:1062)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.startThreads(ClusterDistributionManager.java:691)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:504)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:326)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:780)
> {noformat}
> And once in ClusterDistributionManager.create:
> {noformat}
> [warn 2021/06/20 16:20:16.155 HST server-1  tid=0x1] 
> ClusterDistributionManager.handleManagerStartup 
> id=192.168.1.8(server-1:58386):41001; kind=10
> [warn 2021/06/20 16:20:16.156 HST server-1  tid=0x1] 
> DistributionStats.incNodes nodes=2
> java.lang.Exception
>   at 
> org.apache.geode.distributed.internal.DistributionStats.incNodes(DistributionStats.java:1362)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.handleManagerStartup(ClusterDistributionManager.java:1809)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.addNewMember(ClusterDistributionManager.java:1062)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:354)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:780)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Resolved] (GEODE-10271) CI failure: dead server monitor fails to increment server count after a new server is started

2022-05-11 Thread Jinmei Liao (Jira) 


 [ 
https://issues.apache.org/jira/browse/GEODE-10271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jinmei Liao resolved GEODE-10271.
-
Resolution: Fixed

Cleaned up the test and hopefully it will eliminate this issue.

> CI failure: dead server monitor fails to increment server count after a new 
> server is started
> -
>
> Key: GEODE-10271
> URL: https://issues.apache.org/jira/browse/GEODE-10271
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: needsTriage, pull-request-available
>
> [https://hydradb.hdb.gemfire-ci.info/hdb/testresult/14919517]
>  
> {noformat}
> > Task :geode-core:integrationTest
> ConnectionProxyJUnitTest > testDeadServerMonitorPingNature1 FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition 
> defined as a lambda expression in 
> org.apache.geode.internal.cache.tier.sockets.ConnectionProxyJUnitTest 
> expected:<1> but was:<0> within 5 minutes.
> at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
> at 
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:769)
> at 
> org.apache.geode.internal.cache.tier.sockets.ConnectionProxyJUnitTest.testDeadServerMonitorPingNature1(ConnectionProxyJUnitTest.java:246)
> Caused by:
> java.lang.AssertionError: expected:<1> but was:<0>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at 
> org.apache.geode.internal.cache.tier.sockets.ConnectionProxyJUnitTest.lambda$testDeadServerMonitorPingNature1$0(ConnectionProxyJUnitTest.java:247)
> 4053 tests completed, 1 failed, 84 skipped
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=  Test Results URI 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1131/test-results/integrationTest/1651501470/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1131/test-artifacts/1651501470/integrationtestfiles-openjdk8-1.15.0-build.1131.tgz{noformat}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Updated] (GEODE-10271) CI failure: dead server monitor fails to increment server count after a new server is started

2022-05-11 Thread Jinmei Liao (Jira) 


 [ 
https://issues.apache.org/jira/browse/GEODE-10271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jinmei Liao updated GEODE-10271:

Fix Version/s: 1.16.0

> CI failure: dead server monitor fails to increment server count after a new 
> server is started
> -
>
> Key: GEODE-10271
> URL: https://issues.apache.org/jira/browse/GEODE-10271
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: needsTriage, pull-request-available
> Fix For: 1.16.0
>
>
> [https://hydradb.hdb.gemfire-ci.info/hdb/testresult/14919517]
>  
> {noformat}
> > Task :geode-core:integrationTest
> ConnectionProxyJUnitTest > testDeadServerMonitorPingNature1 FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition 
> defined as a lambda expression in 
> org.apache.geode.internal.cache.tier.sockets.ConnectionProxyJUnitTest 
> expected:<1> but was:<0> within 5 minutes.
> at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
> at 
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:769)
> at 
> org.apache.geode.internal.cache.tier.sockets.ConnectionProxyJUnitTest.testDeadServerMonitorPingNature1(ConnectionProxyJUnitTest.java:246)
> Caused by:
> java.lang.AssertionError: expected:<1> but was:<0>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at 
> org.apache.geode.internal.cache.tier.sockets.ConnectionProxyJUnitTest.lambda$testDeadServerMonitorPingNature1$0(ConnectionProxyJUnitTest.java:247)
> 4053 tests completed, 1 failed, 84 skipped
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=  Test Results URI 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1131/test-results/integrationTest/1651501470/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1131/test-artifacts/1651501470/integrationtestfiles-openjdk8-1.15.0-build.1131.tgz{noformat}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

<    5   6   7   8   9   10