You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Eric Shu (Jira)" <ji...@apache.org> on 2020/07/08 21:41:01 UTC
[jira] [Commented] (GEODE-8326) CI Failure:
FixedPartitioningWithTransactionDistributedTest.clientCanRollbackFunctionOnRegionWithoutFilterAndWithSingleHopEnabled
times out waiting for client metadata
[ https://issues.apache.org/jira/browse/GEODE-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154028#comment-17154028 ]
Eric Shu commented on GEODE-8326:
---------------------------------
I could not reproduce it in thousands of runs both in develop and support/1.13 branch.
The wait introduced is trying to make sure client to have correct PR meta data, so it can send transactional function to correct member node. It is been done before any transaction being performed in the test.
I do not see any places in GetClientPRMetadataCommand66 could cause the hang seen in the failure.
I will remove the 5 minute wait in the test, so that we can get the stack dump to see what could be the problem if we see the failure again.
> CI Failure: FixedPartitioningWithTransactionDistributedTest.clientCanRollbackFunctionOnRegionWithoutFilterAndWithSingleHopEnabled times out waiting for client metadata
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-8326
> URL: https://issues.apache.org/jira/browse/GEODE-8326
> Project: Geode
> Issue Type: Bug
> Components: client/server, tests
> Affects Versions: 1.13.0
> Reporter: Kirk Lund
> Assignee: Eric Shu
> Priority: Major
> Labels: caching-applications
>
> CI Failure: http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.0-build.0296/test-results/distributedTest/1592846714/
> {noformat}
> org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningWithTransactionDistributedTest > clientCanRollbackFunctionOnRegionWithoutFilterAndWithSingleHopEnabled[ExecuteFunctionByObject] FAILED
> org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningWithTransactionDistributedTest that uses org.apache.geode.cache.client.internal.ClientMetadataService was not fulfilled within 5 minutes.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
> at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:864)
> at org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningWithTransactionDistributedTest.forceClientMetadataUpdate(FixedPartitioningWithTransactionDistributedTest.java:241)
> at org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningWithTransactionDistributedTest.doFunctionTransactionAndSuspend(FixedPartitioningWithTransactionDistributedTest.java:458)
> at org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningWithTransactionDistributedTest.clientCanRollbackFunctionOnRegionWithoutFilterAndWithSingleHopEnabled(FixedPartitioningWithTransactionDistributedTest.java:254)
> {noformat}
> The failure occurs after waiting 5 minutes for the ClientMetadataService to stabilize. See ClientMetadataService#isMetadataStable.
> The timeout occurs within a block of test code that was introduced by Jake in PR #3840:
> {noformat}
> GEODE-7006: Fixes function execution by id with transactions. (#3840)
> * Fixes test to force and wait for PR metadata to update.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)