[
https://issues.apache.org/jira/browse/GEODE-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330658#comment-16330658
]
ASF GitHub Bot commented on GEODE-4312:
---------------------------------------
jdeppe-pivotal opened a new pull request #1302: GEODE-4312: Wait for
rebalancing to complete as part of teardown
URL: https://github.com/apache/geode/pull/1302
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in
the commit message?
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically `develop`)?
- [ ] Is your initial contribution a single, squashed commit?
- [ ] Does `gradlew build` run cleanly?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and
submit an update to your PR as soon as possible. If you need help, please
send an
email to [email protected].
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> CI failure: org.apache.geode.cache30.CacheXml80DUnitTest >
> testPartitionedRegionAttributesForCoLocation3 FAILED
> ---------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-4312
> URL: https://issues.apache.org/jira/browse/GEODE-4312
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Reporter: Jens Deppe
> Priority: Major
> Labels: ci, pull-request-available
>
> Test produces this:
> {noformat}
> 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 157
> [error 2018/01/17 03:31:42.318 UTC <ResourceManagerRecoveryThread 0>
> tid=0x2c6] Unexpected exception during bucket recovery
> java.lang.IllegalStateException: Region specified in 'colocated-with'
> (Customer) for region /Order does not exist. It should be created before
> setting 'colocated-with' attribute for this region.
> at
> org.apache.geode.internal.cache.ColocationHelper.getColocatedRegion(ColocationHelper.java:94)
> at
> org.apache.geode.internal.cache.ColocationHelper.getLeaderRegion(ColocationHelper.java:455)
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.<init>(PartitionedRegionRebalanceOp.java:134)
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.<init>(PartitionedRegionRebalanceOp.java:114)
> at
> org.apache.geode.internal.cache.PRHARedundancyProvider$3.run2(PRHARedundancyProvider.java:1568)
> at
> org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:61)
> at
> org.apache.geode.internal.OneTaskOnlyExecutor$DelegatingRunnable.run(OneTaskOnlyExecutor.java:134)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The relevant section of the log is this:
> {noformat}
> [info 2018/01/17 03:31:42.248 UTC <Test worker> tid=0x16] Initializing region
> __PR
> [info 2018/01/17 03:31:42.248 UTC <Test worker> tid=0x16] Initialization of
> region __PR completed
> [info 2018/01/17 03:31:42.249 UTC <Test worker> tid=0x16] Partitioned Region
> /Customer is born with prId=4 ident:#Customer
> [info 2018/01/17 03:31:42.271 UTC <Test worker> tid=0x16] Partitioned Region
> /Order is born with prId=5 ident:#Order
> [info 2018/01/17 03:31:42.314 UTC <Test worker> tid=0x16] GemFireCache[id =
> 1650399312; isClosing = true; isShutDownAll = false; created = Wed Jan 17
> 03:31:41 UTC 2018; server = false; copyOnRead = false; lockLease = 120;
> lockTimeout = 60]: Now closing.
> [error 2018/01/17 03:31:42.318 UTC <ResourceManagerRecoveryThread 0>
> tid=0x2c6] Unexpected exception during bucket recovery
> java.lang.IllegalStateException: Region specified in 'colocated-with'
> (Customer) for region /Order does not exist. It should be created before
> setting 'colocated-with' attribute for this region.
> at
> org.apache.geode.internal.cache.ColocationHelper.getColocatedRegion(ColocationHelper.java:94)
> at
> org.apache.geode.internal.cache.ColocationHelper.getLeaderRegion(ColocationHelper.java:455)
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.<init>(PartitionedRegionRebalanceOp.java:134)
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.<init>(PartitionedRegionRebalanceOp.java:114)
> at
> org.apache.geode.internal.cache.PRHARedundancyProvider$3.run2(PRHARedundancyProvider.java:1568)
> at
> org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:61)
> at
> org.apache.geode.internal.OneTaskOnlyExecutor$DelegatingRunnable.run(OneTaskOnlyExecutor.java:134)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> It looks like the test is actually running quickly enough that the cache
> starts up and shuts down before the ResourceManager can initialize correctly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
