You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jinmei Liao (Jira)" <ji...@apache.org> on 2022/05/23 23:46:00 UTC
[jira] [Comment Edited] (GEODE-10314) [CI Failure] TxCommitMessageBCOldClientToServerTxBothTest > test[1] FAILED
[ https://issues.apache.org/jira/browse/GEODE-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541217#comment-17541217 ]
Jinmei Liao edited comment on GEODE-10314 at 5/23/22 11:45 PM:
---------------------------------------------------------------
I believe this is a temporary resource issue, when vm4 is trying to connect to the cluster, the cluster is having some resource issues and one/more of the members are not able to exchange heartbeat, so vm4 received a connectivity exception when trying to start up for the test to continue. The failure has nothing to do with what the test is trying to test for.
{quote}[vm0] [info 2022/05/13 21:02:57.393 GMT <Geode Failure Detection thread 3> tid=0x124] received suspect message from myself for 172.17.0.6(278)<v23>:41003: Member isn't responding to heartbeat requests
[vm0] [info 2022/05/13 21:02:57.411 GMT <Geode Failure Detection thread 2> tid=0x100] received suspect message from myself for 172.17.0.6(253)<v20>:41002: Member isn't responding to heartbeat requests
[vm0] [info 2022/05/13 21:02:59.111 GMT <Geode Failure Detection thread 4> tid=0x125] received suspect message from myself for 7b66f9a900ce(106:locator)<ec><v0>:41000: Member isn't responding to heartbeat requests
[locator] [info 2022/05/13 21:02:59.064 GMT <Geode Membership View Creator> tid=0x38] finished waiting for responses to view preparation
[vm1] [warn 2022/05/13 21:02:59.237 GMT <StatSampler> tid=0xf6] Statistics sampling thread detected a wakeup delay of 12657 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics.
[locator] [warn 2022/05/13 21:02:59.204 GMT <StatSampler> tid=0x3b] Statistics sampling thread detected a wakeup delay of 13709 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics.
[vm1] [warn 2022/05/13 21:02:59.918 GMT <Geode Heartbeat Sender> tid=0xee] Failure detection heartbeat-generation thread overslept by more than a full period. Asleep time: 13,868,839,079 nanoseconds. Period: 2,500,000,000 nanoseconds.
{quote}
was (Author: jinmeiliao):
I believe this is a temporary resource issue, when vm4 is trying to connect to the cluster, the cluster is having some resource issues and one/more of the members are not able to exchange heartbeat:
{quote}
[vm0] [info 2022/05/13 21:02:57.393 GMT <Geode Failure Detection thread 3> tid=0x124] received suspect message from myself for 172.17.0.6(278)<v23>:41003: Member isn't responding to heartbeat requests
[vm0] [info 2022/05/13 21:02:57.411 GMT <Geode Failure Detection thread 2> tid=0x100] received suspect message from myself for 172.17.0.6(253)<v20>:41002: Member isn't responding to heartbeat requests
[vm0] [info 2022/05/13 21:02:59.111 GMT <Geode Failure Detection thread 4> tid=0x125] received suspect message from myself for 7b66f9a900ce(106:locator)<ec><v0>:41000: Member isn't responding to heartbeat requests
[locator] [info 2022/05/13 21:02:59.064 GMT <Geode Membership View Creator> tid=0x38] finished waiting for responses to view preparation
[vm1] [warn 2022/05/13 21:02:59.237 GMT <StatSampler> tid=0xf6] Statistics sampling thread detected a wakeup delay of 12657 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics.
[locator] [warn 2022/05/13 21:02:59.204 GMT <StatSampler> tid=0x3b] Statistics sampling thread detected a wakeup delay of 13709 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics.
[vm1] [warn 2022/05/13 21:02:59.918 GMT <Geode Heartbeat Sender> tid=0xee] Failure detection heartbeat-generation thread overslept by more than a full period. Asleep time: 13,868,839,079 nanoseconds. Period: 2,500,000,000 nanoseconds.
{quote}
> [CI Failure] TxCommitMessageBCOldClientToServerTxBothTest > test[1] FAILED
> --------------------------------------------------------------------------
>
> Key: GEODE-10314
> URL: https://issues.apache.org/jira/browse/GEODE-10314
> Project: Geode
> Issue Type: Bug
> Components: transactions
> Affects Versions: 1.12.10
> Reporter: Nabarun Nag
> Assignee: Jinmei Liao
> Priority: Major
> Labels: needsTriage
>
>
> {noformat}
> org.apache.geode.internal.cache.TxCommitMessageBCOldClientToServerTxBothTest > test[1] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.TxCommitMessageBCTestBase$$Lambda$60/174734073.run in VM 4 running on Host 7b66f9a900ce with 5 VMs
> Caused by:
> org.apache.geode.SystemConnectException: Unable to join the distributed system in 67530ms{noformat}
>
> {noformat}
> 384 tests completed, 1 failed, 24 skipped
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.10-build.0393/test-results/upgradeTest/1652478284/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.10-build.0393/test-artifacts/1652478284/upgradetestfiles-openjdk8-1.12.10-build.0393.tgz{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)