[jira] [Updated] (GEODE-9770) CI Failure: ConflictingPersistentDataException in PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
[
https://issues.apache.org/jira/browse/GEODE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9770:
--
Labels: GeodeOperationAPI needsTriage pull-request-available (was:
GeodeOperationAPI needsTriage)
> CI Failure: ConflictingPersistentDataException in
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
> -
>
> Key: GEODE-9770
> URL: https://issues.apache.org/jira/browse/GEODE-9770
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI, needsTriage, pull-request-available
>
> This ConflictingPersistentDataException has popped up multiple number of
> times.
> GEODE-6975
> GEODE-7898
>
> {noformat}
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest$$Lambda$477/1255368072.run
> in VM 0 running on Host
> heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testRecoverAfterConflict(PersistentRecoveryOrderDUnitTest.java:1328)
> Caused by:
> org.apache.geode.cache.CacheClosedException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote
> member heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002
> with persistent data
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
> created at timestamp 1635009815552 version 0 diskStoreId
> bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
> system as the local data from
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
> created at timestamp 1635009814986 version 0 diskStoreId
> cc4c64d81e9d4119-9e7320b29f540199 name , caused by
> org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote
> member heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002
> with persistent data
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
> created at timestamp 1635009815552 version 0 diskStoreId
> bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
> system as the local data from
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
> created at timestamp 1635009814986 version 0 diskStoreId
> cc4c64d81e9d4119-9e7320b29f540199 name
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5223)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4259)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4253)
> at
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1175)
> at
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1095)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3108)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3002)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2986)
> at
> org.apache.geode.cache.RegionFactory.create(RegionFactory.java:773)
> at
> org.apache.geode.internal.cache.InternalRegionFactory.create(InternalRegionFactory.java:75)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.createReplicateRegion(PersistentRecoveryOrderDUnitTest.java:1358)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.createReplicateRegion(PersistentRecoveryOrderDUnitTest.java:1362)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.lambda$testRecoverAfterConflict$bb17a952$5(PersistentRecoveryOrderDUnitTest.java:1330)
> Caused by:
>
> org.apache.geode.cache.persistence.ConflictingPersistentDataE
[jira] [Comment Edited] (GEODE-9770) CI Failure: ConflictingPersistentDataException in PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
[
https://issues.apache.org/jira/browse/GEODE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458864#comment-17458864
]
Jianxia Chen edited comment on GEODE-9770 at 12/14/21, 2:26 AM:
When there is a `ConflictingPersistentDataException`, it spawn a separate
thread as `Disk store exception handler` which closes the cache:
```
[vm0] [info 2021/11/20 21:44:35.930 UTC
tid=0x4f4] GemFireCache[id = 704547712; isClosing = true; isShutDownAll =
false; created = Sat Nov 20 21:44:35 UTC 2021; server = false; copyOnRead =
false; lockLease = 120; lockTimeout = 60]: Now closing.
```
The `Disk store exception handler` code:
[https://github.com/apache/geode/blob/0d9e4bded24ebf91a50e5a786dc07af2b416c6d7/geode-core/src/main/java/org/apache/geode/internal/cache/DiskStoreImpl.java#L3345-L3354]
Depending on the thread scheduling, `Disk store exception handler` on vm0 could
close the cache, when at the same time, vm0 is creating the replicated
persistent region, which is exactly what this Jira reports:
```
[vm0] [info 2021/11/20 21:44:35.948 UTC
tid=0x4f4] Reinitializing JarDeploymentService with new working directory: null
[vm0] [info 2021/11/20 21:44:35.949 UTC
tid=0xc3] Got result: EXCEPTION_OCCURRED
[vm0] org.apache.geode.cache.CacheClosedException: Region
/PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote member
heavy-lifter-c3cb1c34-fd30-576b-addd-38d714500ad3(544324):58502 with
persistent data
/10.0.2.15:/tmp/junit8548396335072425119/rootDir-testRecoverAfterConflict/vm-1
created at timestamp 1637444675574 version 0 diskStoreId
b87c4dfb7d7c4b01-822c586f1bb04481 name was not part of the same distributed
system as the local data from
/10.0.2.15:/tmp/junit8548396335072425119/rootDir-testRecoverAfterConflict/vm-0
created at timestamp 1637444674993 version 0 diskStoreId
1341906c3d8249c9-89bde5e19b52a55b name , caused by
org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region
/PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote member
heavy-lifter-c3cb1c34-fd30-576b-addd-38d714500ad3(544324):58502 with
persistent data
/10.0.2.15:/tmp/junit8548396335072425119/rootDir-testRecoverAfterConflict/vm-1
created at timestamp 1637444675574 version 0 diskStoreId
b87c4dfb7d7c4b01-822c586f1bb04481 name was not part of the same distributed
system as the local data from
/10.0.2.15:/tmp/junit8548396335072425119/rootDir-testRecoverAfterConflict/vm-0
created at timestamp 1637444674993 version 0 diskStoreId
1341906c3d8249c9-89bde5e19b52a55b name
```
was (Author: jchen21):
When there is a `ConflictingPersistentDataException`, it spawn a separate
thread as `Disk store exception handler` which closes the cache:
```
[vm0] [info 2021/11/20 21:44:35.930 UTC
tid=0x4f4] GemFireCache[id = 704547712; isClosing = true; isShutDownAll =
false; created = Sat Nov 20 21:44:35 UTC 2021; server = false; copyOnRead =
false; lockLease = 120; lockTimeout = 60]: Now closing.
```
The `Disk store exception handler` code:
[https://github.com/apache/geode/blob/0d9e4bded24ebf91a50e5a786dc07af2b416c6d7/geode-core/src/main/java/org/apache/geode/internal/cache/DiskStoreImpl.java#L3345-L3354]
Depending on the thread scheduling, `Disk store exception handler` on vm0 could
close the cache, when at the same time, vm0 is creating the replicated
persistent region, which is exactly what this Jira reports.
> CI Failure: ConflictingPersistentDataException in
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
> -
>
> Key: GEODE-9770
> URL: https://issues.apache.org/jira/browse/GEODE-9770
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI, needsTriage
>
> This ConflictingPersistentDataException has popped up multiple number of
> times.
> GEODE-6975
> GEODE-7898
>
> {noformat}
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest$$Lambda$477/1255368072.run
> in VM 0 running on Host
> heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testRecoverAfterConflict(PersistentRecoveryOrderDUnitTest.java:1328)
> Caused by:
> org.apache.geode.cache.Cach
[jira] [Commented] (GEODE-9770) CI Failure: ConflictingPersistentDataException in PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
[
https://issues.apache.org/jira/browse/GEODE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458864#comment-17458864
]
Jianxia Chen commented on GEODE-9770:
-
When there is a `ConflictingPersistentDataException`, it spawn a separate
thread as `Disk store exception handler` which closes the cache:
```
[vm0] [info 2021/11/20 21:44:35.930 UTC
tid=0x4f4] GemFireCache[id = 704547712; isClosing = true; isShutDownAll =
false; created = Sat Nov 20 21:44:35 UTC 2021; server = false; copyOnRead =
false; lockLease = 120; lockTimeout = 60]: Now closing.
```
The `Disk store exception handler` code:
[https://github.com/apache/geode/blob/0d9e4bded24ebf91a50e5a786dc07af2b416c6d7/geode-core/src/main/java/org/apache/geode/internal/cache/DiskStoreImpl.java#L3345-L3354]
Depending on the thread scheduling, `Disk store exception handler` on vm0 could
close the cache, when at the same time, vm0 is creating the replicated
persistent region, which is exactly what this Jira reports.
> CI Failure: ConflictingPersistentDataException in
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
> -
>
> Key: GEODE-9770
> URL: https://issues.apache.org/jira/browse/GEODE-9770
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI, needsTriage
>
> This ConflictingPersistentDataException has popped up multiple number of
> times.
> GEODE-6975
> GEODE-7898
>
> {noformat}
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest$$Lambda$477/1255368072.run
> in VM 0 running on Host
> heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testRecoverAfterConflict(PersistentRecoveryOrderDUnitTest.java:1328)
> Caused by:
> org.apache.geode.cache.CacheClosedException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote
> member heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002
> with persistent data
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
> created at timestamp 1635009815552 version 0 diskStoreId
> bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
> system as the local data from
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
> created at timestamp 1635009814986 version 0 diskStoreId
> cc4c64d81e9d4119-9e7320b29f540199 name , caused by
> org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote
> member heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002
> with persistent data
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
> created at timestamp 1635009815552 version 0 diskStoreId
> bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
> system as the local data from
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
> created at timestamp 1635009814986 version 0 diskStoreId
> cc4c64d81e9d4119-9e7320b29f540199 name
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5223)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4259)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4253)
> at
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1175)
> at
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1095)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3108)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3002)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2986)
> at
> org.apache.geode.cache.RegionFactory.cre
[jira] [Updated] (GEODE-9897) ClientUserAuthsTest leaves some seemingly tested responsibilities untested
[
https://issues.apache.org/jira/browse/GEODE-9897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery updated GEODE-9897:
--
Labels: GeodeOperationAPI (was: )
> ClientUserAuthsTest leaves some seemingly tested responsibilities untested
> --
>
> Key: GEODE-9897
> URL: https://issues.apache.org/jira/browse/GEODE-9897
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI
>
> *Problem 1:* The test class's {{before()}} method uses the {{spy()}}
> mechanism to override {{getNextId()}} on the {{ClientUserAuths}} it is
> testing. This bypasses the actual implementation for all tests, leaving
> untested the following important {{ClientUserAuths}} responsibilities:
> - Detect when all IDs have all been used.
> - Clear all existing authentications when all IDs have been used, to force
> reauthentication.
> - Re-seed the ID generator when all IDs have been used.
> The tests are likely doing this because {{getNextId()}} relies on a
> {{{}Random{}}}, which is uncontrollable by design. Because
> {{ClientUserAuths}} creates the {{{}Random{}}}, the tests are unable to
> inject a testable instance, and so instead must bypass the
> {{ClientUserAuths}} methods that interact with the {{{}Random{}}}.
> The solution to this problem is to extract and test an ID generator that
> accepts a {{Random}} as a constructor parameter, thus allowing tests to
> control it.
> This also frees {{ClientUserAuths}} from the responsibility to generate IDs,
> so it can instead focus on how it uses the IDs. Then it will be
> straightforward to write tests to verify that {{ClientUserAuths}} forces
> reauthentication when the generator runs out of IDs.
> *Problem 2:* Several tests in this class attempt to verify certain
> responsibilities only by spying on how the {{ClientUserAuths}} interacts with
> itself. Verifying only these internal interactions leaves the actual
> responsibilities (how the {{ClientUserAuths}} responds to subsequent calls)
> untested.
> The tests can instead verify the actual responsibilities by calling public
> methods and making assertions about the returned values.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9897) ClientUserAuthsTest leaves some seemingly tested responsibilities untested
[
https://issues.apache.org/jira/browse/GEODE-9897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery reassigned GEODE-9897:
-
Assignee: Dale Emery
> ClientUserAuthsTest leaves some seemingly tested responsibilities untested
> --
>
> Key: GEODE-9897
> URL: https://issues.apache.org/jira/browse/GEODE-9897
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
>
> *Problem 1:* The test class's {{before()}} method uses the {{spy()}}
> mechanism to override {{getNextId()}} on the {{ClientUserAuths}} it is
> testing. This bypasses the actual implementation for all tests, leaving
> untested the following important {{ClientUserAuths}} responsibilities:
> - Detect when all IDs have all been used.
> - Clear all existing authentications when all IDs have been used, to force
> reauthentication.
> - Re-seed the ID generator when all IDs have been used.
> The tests are likely doing this because {{getNextId()}} relies on a
> {{{}Random{}}}, which is uncontrollable by design. Because
> {{ClientUserAuths}} creates the {{{}Random{}}}, the tests are unable to
> inject a testable instance, and so instead must bypass the
> {{ClientUserAuths}} methods that interact with the {{{}Random{}}}.
> The solution to this problem is to extract and test an ID generator that
> accepts a {{Random}} as a constructor parameter, thus allowing tests to
> control it.
> This also frees {{ClientUserAuths}} from the responsibility to generate IDs,
> so it can instead focus on how it uses the IDs. Then it will be
> straightforward to write tests to verify that {{ClientUserAuths}} forces
> reauthentication when the generator runs out of IDs.
> *Problem 2:* Several tests in this class attempt to verify certain
> responsibilities only by spying on how the {{ClientUserAuths}} interacts with
> itself. Verifying only these internal interactions leaves the actual
> responsibilities (how the {{ClientUserAuths}} responds to subsequent calls)
> untested.
> The tests can instead verify the actual responsibilities by calling public
> methods and making assertions about the returned values.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9897) ClientUserAuthsTest leaves some seemingly tested responsibilities untested
Dale Emery created GEODE-9897:
-
Summary: ClientUserAuthsTest leaves some seemingly tested
responsibilities untested
Key: GEODE-9897
URL: https://issues.apache.org/jira/browse/GEODE-9897
Project: Geode
Issue Type: Test
Components: tests
Reporter: Dale Emery
*Problem 1:* The test class's {{before()}} method uses the {{spy()}} mechanism
to override {{getNextId()}} on the {{ClientUserAuths}} it is testing. This
bypasses the actual implementation for all tests, leaving untested the
following important {{ClientUserAuths}} responsibilities:
- Detect when all IDs have all been used.
- Clear all existing authentications when all IDs have been used, to force
reauthentication.
- Re-seed the ID generator when all IDs have been used.
The tests are likely doing this because {{getNextId()}} relies on a
{{{}Random{}}}, which is uncontrollable by design. Because {{ClientUserAuths}}
creates the {{{}Random{}}}, the tests are unable to inject a testable instance,
and so instead must bypass the {{ClientUserAuths}} methods that interact with
the {{{}Random{}}}.
The solution to this problem is to extract and test an ID generator that
accepts a {{Random}} as a constructor parameter, thus allowing tests to control
it.
This also frees {{ClientUserAuths}} from the responsibility to generate IDs, so
it can instead focus on how it uses the IDs. Then it will be straightforward to
write tests to verify that {{ClientUserAuths}} forces reauthentication when the
generator runs out of IDs.
*Problem 2:* Several tests in this class attempt to verify certain
responsibilities only by spying on how the {{ClientUserAuths}} interacts with
itself. Verifying only these internal interactions leaves the actual
responsibilities (how the {{ClientUserAuths}} responds to subsequent calls)
untested.
The tests can instead verify the actual responsibilities by calling public
methods and making assertions about the returned values.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9896) Upgrade dependencies
[ https://issues.apache.org/jira/browse/GEODE-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458807#comment-17458807 ] ASF GitHub Bot commented on GEODE-9896: --- pivotal-jbarrett removed a comment on pull request #899: URL: https://github.com/apache/geode-native/pull/899#issuecomment-992973833 Test failures are know flaky tests. -- 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. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade dependencies > > > Key: GEODE-9896 > URL: https://issues.apache.org/jira/browse/GEODE-9896 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > Labels: pull-request-available > > * ACE 7.0.5 > * Boost 1.78.0 > * SQLite 3.37 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9850) flaky test: testGetOldestTombstoneTimeForReplicateTombstoneSweeper
[
https://issues.apache.org/jira/browse/GEODE-9850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458801#comment-17458801
]
ASF subversion and git services commented on GEODE-9850:
Commit 5335f404a2b4d6dfbad9066ce46dfd8050b8edc7 in geode's branch
refs/heads/feature/GEODE-9850 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5335f40 ]
GEODE-9850: resolve the flaky test in getting the oldest tombstone
> flaky test: testGetOldestTombstoneTimeForReplicateTombstoneSweeper
> --
>
> Key: GEODE-9850
> URL: https://issues.apache.org/jira/browse/GEODE-9850
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.13.5
>Reporter: Bill Burcham
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> First saw this failure in PR pipeline on support/1.13 here:
> [https://concourse.apachegeode-ci.info/builds/3912569]
> {code:java}
> org.apache.geode.internal.cache.versions.TombstoneDUnitTest >
> testGetOldestTombstoneTimeForReplicateTombstoneSweeper FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.versions.TombstoneDUnitTest$$Lambda$42/2046302475.run
> in VM 0 running on Host 9a305b2d7db7 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at
> org.apache.geode.internal.cache.versions.TombstoneDUnitTest.testGetOldestTombstoneTimeForReplicateTombstoneSweeper(TombstoneDUnitTest.java:228)
> Caused by:
> java.lang.AssertionError:
> Expecting:
> <-1637701703343L>
> to be greater than:
> <0L>
> at
> org.apache.geode.internal.cache.versions.TombstoneDUnitTest.lambda$testGetOldestTombstoneTimeForReplicateTombstoneSweeper$bb17a952$3(TombstoneDUnitTest.java:237)
> {code}
> I believe the fix is to wrap this assertion in an awaitility call.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9896) Upgrade dependencies
[ https://issues.apache.org/jira/browse/GEODE-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9896: -- Labels: pull-request-available (was: ) > Upgrade dependencies > > > Key: GEODE-9896 > URL: https://issues.apache.org/jira/browse/GEODE-9896 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > Labels: pull-request-available > > * ACE 7.0.5 > * Boost 1.78.0 > * SQLite 3.37 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9896) Upgrade dependencies
[ https://issues.apache.org/jira/browse/GEODE-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458752#comment-17458752 ] ASF GitHub Bot commented on GEODE-9896: --- pivotal-jbarrett commented on pull request #899: URL: https://github.com/apache/geode-native/pull/899#issuecomment-992973833 Test failures are know flaky tests. -- 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. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade dependencies > > > Key: GEODE-9896 > URL: https://issues.apache.org/jira/browse/GEODE-9896 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > > * ACE 7.0.5 > * Boost 1.78.0 > * SQLite 3.37 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9896) Upgrade dependencies
[ https://issues.apache.org/jira/browse/GEODE-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Barrett reassigned GEODE-9896: Assignee: Jacob Barrett > Upgrade dependencies > > > Key: GEODE-9896 > URL: https://issues.apache.org/jira/browse/GEODE-9896 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > > * ACE 7.0.5 > * Boost 1.78.0 > * SQLite 3.37 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9896) Upgrade dependencies
Jacob Barrett created GEODE-9896: Summary: Upgrade dependencies Key: GEODE-9896 URL: https://issues.apache.org/jira/browse/GEODE-9896 Project: Geode Issue Type: Improvement Components: native client Reporter: Jacob Barrett * ACE 7.0.5 * Boost 1.78.0 * SQLite 3.37 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9895) CI Failure: ConnectionPoolDUnitTest > basicTestLifetimeExpire
[
https://issues.apache.org/jira/browse/GEODE-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458741#comment-17458741
]
Geode Integration commented on GEODE-9895:
--
Seen in [distributed-test-openjdk8
#421|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/421]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639210839/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639210839/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> CI Failure: ConnectionPoolDUnitTest > basicTestLifetimeExpire
> -
>
> Key: GEODE-9895
> URL: https://issues.apache.org/jira/browse/GEODE-9895
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
>
> {{ConnectionPoolDUnitTest > basicTestLifetimeExpire FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 2 running
> on Host
> heavy-lifter-8ad734f8-fc08-5ba3-bad2-7388aa23c427.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:435)
> at
> org.apache.geode.cache.ConnectionPoolDUnitTest.basicTestLifetimeExpire(ConnectionPoolDUnitTest.java:813)
> Caused by:
> org.apache.geode.cache.client.ServerOperationException: remote server
> on
> heavy-lifter-8ad734f8-fc08-5ba3-bad2-7388aa23c427(121494:loner):40384:38a873a8:
> : While performing a remote put
> at
> org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processAck(PutOp.java:372)
> at
> org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processResponse(PutOp.java:274)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:221)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:394)
> at
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:284)
> at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:358)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:760)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:151)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805)
> at
> org.apache.geode.cache.client.internal.PutOp.execute(PutOp.java:92)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:158)
> at
> org.apache.geode.internal.cache.LocalRegion.serverPut(LocalRegion.java:3045)
> at
> org.apache.geode.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3160)
> at
> org.apache.geode.internal.cache.map.RegionMapPut.invokeCacheWriter(RegionMapPut.java:244)
> at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutIfPreconditionsSatisified(AbstractRegionMapPut.java:295)
> at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutOnSynchronizedRegionEntry(AbstractRegionMapPut.java:282)
> at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutOnRegionEntryInMap(AbstractRegionMapPut.java:273)
> at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.addRegionEntryToMapAndDoPut(AbstractRegionMapPut.java:251)
> at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutRetryingIfNeeded(AbstractRegionMapPut.java:216)
> at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doWithIndexInUpdateMode(AbstractRegionMapPut.java:198)
> at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPut(AbstractRegionMapPut.java:180)
> at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.runWhileLockedForCacheModification(AbstractRegionMapPut.java:119)
> at
> org.apache.geode.internal.cache.map.RegionMapPut.runWhileLockedForCacheModification(RegionMapPut.java:161)
> at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.put(AbstractRegionMapPut.java:169)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.basicPut(AbstractRegio
[jira] [Created] (GEODE-9895) CI Failure: ConnectionPoolDUnitTest > basicTestLifetimeExpire
Ray Ingles created GEODE-9895:
-
Summary: CI Failure: ConnectionPoolDUnitTest >
basicTestLifetimeExpire
Key: GEODE-9895
URL: https://issues.apache.org/jira/browse/GEODE-9895
Project: Geode
Issue Type: Bug
Components: client/server
Affects Versions: 1.15.0
Reporter: Ray Ingles
{{ConnectionPoolDUnitTest > basicTestLifetimeExpire FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 2 running
on Host
heavy-lifter-8ad734f8-fc08-5ba3-bad2-7388aa23c427.c.apachegeode-ci.internal
with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:435)
at
org.apache.geode.cache.ConnectionPoolDUnitTest.basicTestLifetimeExpire(ConnectionPoolDUnitTest.java:813)
Caused by:
org.apache.geode.cache.client.ServerOperationException: remote server
on
heavy-lifter-8ad734f8-fc08-5ba3-bad2-7388aa23c427(121494:loner):40384:38a873a8:
: While performing a remote put
at
org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processAck(PutOp.java:372)
at
org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processResponse(PutOp.java:274)
at
org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:221)
at
org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:394)
at
org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:284)
at
org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:358)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:760)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:151)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120)
at
org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805)
at
org.apache.geode.cache.client.internal.PutOp.execute(PutOp.java:92)
at
org.apache.geode.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:158)
at
org.apache.geode.internal.cache.LocalRegion.serverPut(LocalRegion.java:3045)
at
org.apache.geode.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3160)
at
org.apache.geode.internal.cache.map.RegionMapPut.invokeCacheWriter(RegionMapPut.java:244)
at
org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutIfPreconditionsSatisified(AbstractRegionMapPut.java:295)
at
org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutOnSynchronizedRegionEntry(AbstractRegionMapPut.java:282)
at
org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutOnRegionEntryInMap(AbstractRegionMapPut.java:273)
at
org.apache.geode.internal.cache.map.AbstractRegionMapPut.addRegionEntryToMapAndDoPut(AbstractRegionMapPut.java:251)
at
org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutRetryingIfNeeded(AbstractRegionMapPut.java:216)
at
org.apache.geode.internal.cache.map.AbstractRegionMapPut.doWithIndexInUpdateMode(AbstractRegionMapPut.java:198)
at
org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPut(AbstractRegionMapPut.java:180)
at
org.apache.geode.internal.cache.map.AbstractRegionMapPut.runWhileLockedForCacheModification(AbstractRegionMapPut.java:119)
at
org.apache.geode.internal.cache.map.RegionMapPut.runWhileLockedForCacheModification(RegionMapPut.java:161)
at
org.apache.geode.internal.cache.map.AbstractRegionMapPut.put(AbstractRegionMapPut.java:169)
at
org.apache.geode.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:2045)
at
org.apache.geode.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5615)
at
org.apache.geode.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5593)
at
org.apache.geode.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:157)
at
org.apache.geode.internal.cache.LocalRegion.basicPut(LocalRegion.java:5050)
at
org.apache.geode.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1646)
at
org.apache.geode.internal.cache.LocalRegion.put(LocalRegion.java:1633)
at
org.apache.geode.internal.cache.AbstractRegion.put(AbstractRegion.java:445)
at
org.apache.geode.cache.ConnectionPoolDUnitTest.lambda$basicTestLifetimeExpire$f09ad7da$1(ConnectionPoolDUnitTest.java:825)
Caused by:
org.apache.geode.cache.RegionDestroyedException: Server connection
from [id
[jira] [Commented] (GEODE-9894) CI Failure: RedundancyLevelPart1DUnitTest > testRedundancySpecifiedNonPrimaryEPFailsDetectionByUnregisterInterest
[
https://issues.apache.org/jira/browse/GEODE-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458739#comment-17458739
]
Geode Integration commented on GEODE-9894:
--
Seen in [distributed-test-openjdk8
#446|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/446]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639229145/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639229145/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> CI Failure: RedundancyLevelPart1DUnitTest >
> testRedundancySpecifiedNonPrimaryEPFailsDetectionByUnregisterInterest
> -
>
> Key: GEODE-9894
> URL: https://issues.apache.org/jira/browse/GEODE-9894
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
>
> {{> Task :geode-core:distributedTest
> RedundancyLevelPart1DUnitTest >
> testRedundancySpecifiedNonPrimaryEPFailsDetectionByUnregisterInterest FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest
> Expecting value to be true but was false within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:166)
> 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:939)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByUnregisterInterest(RedundancyLevelPart1DUnitTest.java:326)
> Caused by:
> org.opentest4j.AssertionFailedError:
> Expecting value to be true but was false
> at sun.reflect.GeneratedConstructorAccessor25.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.lambda$testRedundancySpecifiedNonPrimaryEPFailsDetectionByUnregisterInterest$13(RedundancyLevelPart1DUnitTest.java:329)}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9894) CI Failure: RedundancyLevelPart1DUnitTest > testRedundancySpecifiedNonPrimaryEPFailsDetectionByUnregisterInterest
Ray Ingles created GEODE-9894:
-
Summary: CI Failure: RedundancyLevelPart1DUnitTest >
testRedundancySpecifiedNonPrimaryEPFailsDetectionByUnregisterInterest
Key: GEODE-9894
URL: https://issues.apache.org/jira/browse/GEODE-9894
Project: Geode
Issue Type: Bug
Components: client queues, client/server
Affects Versions: 1.15.0
Reporter: Ray Ingles
{{> Task :geode-core:distributedTest
RedundancyLevelPart1DUnitTest >
testRedundancySpecifiedNonPrimaryEPFailsDetectionByUnregisterInterest FAILED
org.awaitility.core.ConditionTimeoutException: Assertion condition defined
as a org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest
Expecting value to be true but was false within 5 minutes.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:166)
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:939)
at
org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
at
org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByUnregisterInterest(RedundancyLevelPart1DUnitTest.java:326)
Caused by:
org.opentest4j.AssertionFailedError:
Expecting value to be true but was false
at sun.reflect.GeneratedConstructorAccessor25.newInstance(Unknown
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.lambda$testRedundancySpecifiedNonPrimaryEPFailsDetectionByUnregisterInterest$13(RedundancyLevelPart1DUnitTest.java:329)}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9893) Add new logging tests for using log4j2.formatMsgNoLookups with Geode
Kirk Lund created GEODE-9893: Summary: Add new logging tests for using log4j2.formatMsgNoLookups with Geode Key: GEODE-9893 URL: https://issues.apache.org/jira/browse/GEODE-9893 Project: Geode Issue Type: Test Reporter: Kirk Lund Add new logging tests for using log4j2.formatMsgNoLookups with Geode. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-7739) JMX managers may fail to federate mbeans for other members
[ https://issues.apache.org/jira/browse/GEODE-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458735#comment-17458735 ] Geode Integration commented on GEODE-7739: -- Seen in [distributed-test-openjdk8 #411|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/411] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639203880/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639203880/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz]. > JMX managers may fail to federate mbeans for other members > -- > > Key: GEODE-7739 > URL: https://issues.apache.org/jira/browse/GEODE-7739 > Project: Geode > Issue Type: Bug > Components: jmx >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > JMX Manager may fail to federate one or more MXBeans for other members > because of a race condition during startup. When ManagementCacheListener is > first constructed, it is in a state that will ignore all callbacks because > the field readyForEvents is false. > > Debugging with JMXMBeanReconnectDUnitTest revealed this bug. > The test starts two locators with jmx manager configured and started. > Locator1 always has all of locator2's mbeans, but locator2 is intermittently > missing the personal mbeans of locator1. > I think this is caused by some sort of race condition in the code that > creates the monitoring regions for other members in locator2. > It's possible that the jmx manager that hits this bug might fail to have > mbeans for servers as well as other locators but I haven't seen a test case > for this scenario. > The exposure of this bug means that a user running more than one locator > might have a locator that is missing one or more mbeans for the cluster. > > Studying the JMX code also reveals the existence of *GEODE-8012*. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-7732) CI Failure: JMXMBeanReconnectDUnitTest.serverMXBeansOnLocatorAreRestoredAfterCrashedServerReturns failed
[
https://issues.apache.org/jira/browse/GEODE-7732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458733#comment-17458733
]
Geode Integration commented on GEODE-7732:
--
Seen in [distributed-test-openjdk8
#411|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/411]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639203880/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639203880/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> CI Failure:
> JMXMBeanReconnectDUnitTest.serverMXBeansOnLocatorAreRestoredAfterCrashedServerReturns
> failed
>
>
> Key: GEODE-7732
> URL: https://issues.apache.org/jira/browse/GEODE-7732
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Affects Versions: 1.12.0
>Reporter: Eric Shu
>Assignee: Kirk Lund
>Priority: Major
> Labels: flaky
> Fix For: 1.13.0
>
>
> This failed @
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1487
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.JMXMBeanReconnectDUnitTest$$Lambda$209/0x000840bb5c40.call
> in VM 2 running on Host e8b6d1c09a6c with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.setUp(JMXMBeanReconnectDUnitTest.java:177)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.dunit.rules.AbstractDistributedRule$1.evaluate(AbstractDistributedRule.java:59)
> at
> org.apache.geode.test.dunit.rules.AbstractDistributedRule$1.evaluate(AbstractDistributedRule.java:59)
> at
> org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method
[jira] [Created] (GEODE-9892) Create Infrastructure for Redis Lists
Wayne created GEODE-9892: Summary: Create Infrastructure for Redis Lists Key: GEODE-9892 URL: https://issues.apache.org/jira/browse/GEODE-9892 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Create the infrastructure for supporting Redis Lists including: * Use of the appropriate underlying Java collection * Implementing the [LPUSH|https://redis.io/commands/lpush] Command * Implementing the [LRANGE|https://redis.io/commands/lrange] command +Acceptance Critera+ The LPUSH and LRANGE commands have been implemented with appropriate unit testing. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9891) CacheStatisticsPartitionedRegionDUnitTest > testDisabledStatistics FAILED
Ray Ingles created GEODE-9891:
-
Summary: CacheStatisticsPartitionedRegionDUnitTest >
testDisabledStatistics FAILED
Key: GEODE-9891
URL: https://issues.apache.org/jira/browse/GEODE-9891
Project: Geode
Issue Type: Bug
Components: core
Affects Versions: 1.15.0
Reporter: Ray Ingles
{{> Task :geode-core:distributedTest}}
{{CacheStatisticsPartitionedRegionDUnitTest > testDisabledStatistics FAILED}}
{{org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
Failures (2 failures)}}
{{ org.apache.geode.distributed.DistributedSystemDisconnectedException:
Distribution manager on
heavy-lifter-531607ac-c474-5030-83b9-b0e677f37a36(231826):46001 started at
Sat Dec 11 19:06:24 UTC 2021: Member isn't responding to heartbeat requests}}
{{ java.lang.AssertionError: Suspicious strings were written to the log
during this run.}}
{{Fix the strings or use IgnoredException.addIgnoredException to ignore.}}
{{---}}
{{Found suspect string in 'dunit_suspect-local.log' at line 535}}
{{[fatal 2021/12/11 19:06:44.320 UTC tid=83]
Membership service failure: Member isn't responding to heartbeat requests}}
{{ ...}}
{{Caused by:}}
{{org.apache.geode.distributed.DistributedSystemDisconnectedException:
Distribution manager on
heavy-lifter-531607ac-c474-5030-83b9-b0e677f37a36(231826):46001 started at
Sat Dec 11 19:06:24 UTC 2021: Member isn't responding to heartbeat requests,
caused by org.apache.geode.ForcedDisconnectException: Member isn't responding
to heartbeat requests}}
{{...}}
{{Caused by:}}
{{org.apache.geode.ForcedDisconnectException: Member isn't
responding to heartbeat requests}}
{{at
org.apache.geode.distributed.internal.DistributionImpl$LifecycleListenerImpl.forcedDisconnect(DistributionImpl.java:941)}}
{{at
org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$uncleanShutdownDS$0(GMSMembership.java:1793)}}
{{at java.lang.Thread.run(Thread.java:748)}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9891) CacheStatisticsPartitionedRegionDUnitTest > testDisabledStatistics FAILED
[
https://issues.apache.org/jira/browse/GEODE-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458667#comment-17458667
]
Geode Integration commented on GEODE-9891:
--
Seen in [distributed-test-openjdk8
#480|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/480]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639255218/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639255218/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> CacheStatisticsPartitionedRegionDUnitTest > testDisabledStatistics FAILED
> -
>
> Key: GEODE-9891
> URL: https://issues.apache.org/jira/browse/GEODE-9891
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
>
>
> {{> Task :geode-core:distributedTest}}
> {{CacheStatisticsPartitionedRegionDUnitTest > testDisabledStatistics FAILED}}
> {{org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
> Failures (2 failures)}}
> {{ org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-531607ac-c474-5030-83b9-b0e677f37a36(231826):46001 started
> at Sat Dec 11 19:06:24 UTC 2021: Member isn't responding to heartbeat
> requests}}
> {{ java.lang.AssertionError: Suspicious strings were written to the log
> during this run.}}
> {{Fix the strings or use IgnoredException.addIgnoredException to ignore.}}
> {{
> ---}}
> {{Found suspect string in 'dunit_suspect-local.log' at line 535}}
> {{[fatal 2021/12/11 19:06:44.320 UTC receiver,heavy-lifter-531607ac-c474-5030-83b9-b0e677f37a36-57822> tid=83]
> Membership service failure: Member isn't responding to heartbeat requests}}
> {{ ...}}
> {{Caused by:}}
> {{
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-531607ac-c474-5030-83b9-b0e677f37a36(231826):46001 started
> at Sat Dec 11 19:06:24 UTC 2021: Member isn't responding to heartbeat
> requests, caused by org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests}}
> {{...}}
> {{Caused by:}}
> {{org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests}}
> {{at
> org.apache.geode.distributed.internal.DistributionImpl$LifecycleListenerImpl.forcedDisconnect(DistributionImpl.java:941)}}
> {{at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$uncleanShutdownDS$0(GMSMembership.java:1793)}}
> {{at java.lang.Thread.run(Thread.java:748)}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9890) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents FAILED
[
https://issues.apache.org/jira/browse/GEODE-9890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458664#comment-17458664
]
Geode Integration commented on GEODE-9890:
--
Seen on support/1.12 in [distributed-test-openjdk8
#8|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/8]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.7-build.0319/test-results/distributedTest/1639270940/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.7-build.0319/test-artifacts/1639270940/distributedtestfiles-openjdk8-1.12.7-build.0319.tgz].
> DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents FAILED
> -
>
> Key: GEODE-9890
> URL: https://issues.apache.org/jira/browse/GEODE-9890
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.12.0
>Reporter: Ray Ingles
>Priority: Major
>
> This has similar behavior to GEODE-7702, but Gester states that the
> underlying cause doesn't apply to 1.12, so we're opening up a new ticket. The
> error seen is:
>
> {{> Task :geode-core:distributedTest}}
> {{org.apache.geode.cache30.DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents FAILED}}
> {{org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.cache30.MultiVMRegionTestCase expected:<[6]> but was:<[3]>
> within 300 seconds.}}
> {{at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)}}
> {{at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)}}
> {{at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)}}
> {{at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)}}
> {{at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)}}
> {{at
> org.apache.geode.cache30.MultiVMRegionTestCase.versionTestClearOnNonReplicateWithConcurrentEvents(MultiVMRegionTestCase.java:6447)}}
> {{at
> org.apache.geode.cache30.DistributedAckRegionCCEDUnitTest.testClearOnNonReplicateWithConcurrentEvents(DistributedAckRegionCCEDUnitTest.java:268)}}
> {{Caused by:}}
> {{org.junit.ComparisonFailure: expected:<[6]> but was:<[3]>}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9890) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents FAILED
[
https://issues.apache.org/jira/browse/GEODE-9890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458662#comment-17458662
]
Geode Integration commented on GEODE-9890:
--
Seen on support/1.13 in [upgrade-test-openjdk11
#12|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/12]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.6-build.0628/test-results/upgradeTest/1639269488/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.6-build.0628/test-artifacts/1639269488/upgradetestfiles-openjdk11-1.13.6-build.0628.tgz].
> DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents FAILED
> -
>
> Key: GEODE-9890
> URL: https://issues.apache.org/jira/browse/GEODE-9890
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.12.0
>Reporter: Ray Ingles
>Priority: Major
>
> This has similar behavior to GEODE-7702, but Gester states that the
> underlying cause doesn't apply to 1.12, so we're opening up a new ticket. The
> error seen is:
>
> {{> Task :geode-core:distributedTest}}
> {{org.apache.geode.cache30.DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents FAILED}}
> {{org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.cache30.MultiVMRegionTestCase expected:<[6]> but was:<[3]>
> within 300 seconds.}}
> {{at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)}}
> {{at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)}}
> {{at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)}}
> {{at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)}}
> {{at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)}}
> {{at
> org.apache.geode.cache30.MultiVMRegionTestCase.versionTestClearOnNonReplicateWithConcurrentEvents(MultiVMRegionTestCase.java:6447)}}
> {{at
> org.apache.geode.cache30.DistributedAckRegionCCEDUnitTest.testClearOnNonReplicateWithConcurrentEvents(DistributedAckRegionCCEDUnitTest.java:268)}}
> {{Caused by:}}
> {{org.junit.ComparisonFailure: expected:<[6]> but was:<[3]>}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9890) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents FAILED
Ray Ingles created GEODE-9890:
-
Summary: DistributedAckRegionCCEDUnitTest >
testClearOnNonReplicateWithConcurrentEvents FAILED
Key: GEODE-9890
URL: https://issues.apache.org/jira/browse/GEODE-9890
Project: Geode
Issue Type: Bug
Components: client/server
Affects Versions: 1.12.0
Reporter: Ray Ingles
This has similar behavior to GEODE-7702, but Gester states that the underlying
cause doesn't apply to 1.12, so we're opening up a new ticket. The error seen
is:
{{> Task :geode-core:distributedTest}}
{{org.apache.geode.cache30.DistributedAckRegionCCEDUnitTest >
testClearOnNonReplicateWithConcurrentEvents FAILED}}
{{org.awaitility.core.ConditionTimeoutException: Assertion condition
defined as a lambda expression in
org.apache.geode.cache30.MultiVMRegionTestCase expected:<[6]> but was:<[3]>
within 300 seconds.}}
{{at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)}}
{{at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)}}
{{at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)}}
{{at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)}}
{{at
org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)}}
{{at
org.apache.geode.cache30.MultiVMRegionTestCase.versionTestClearOnNonReplicateWithConcurrentEvents(MultiVMRegionTestCase.java:6447)}}
{{at
org.apache.geode.cache30.DistributedAckRegionCCEDUnitTest.testClearOnNonReplicateWithConcurrentEvents(DistributedAckRegionCCEDUnitTest.java:268)}}
{{Caused by:}}
{{org.junit.ComparisonFailure: expected:<[6]> but was:<[3]>}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-8117) ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458651#comment-17458651
]
Geode Integration commented on GEODE-8117:
--
Seen on support/1.13 in [integration-test-openjdk8
#11|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/integration-test-openjdk8/builds/11]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.6-build.0628/test-results/integrationTest/1639264722/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.6-build.0628/test-artifacts/1639264722/integrationtestfiles-openjdk8-1.13.6-build.0628.tgz].
> ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile fails
> intermittently
>
>
> Key: GEODE-8117
> URL: https://issues.apache.org/jira/browse/GEODE-8117
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> {noformat}
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase
> expected:<[online]> but was:<[not responding]> within 5 minutes.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 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:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:211)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:190)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:201)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:131)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:127)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile(ServerLauncherRemoteIntegrationTest.java:91)
> Caused by: org.junit.ComparisonFailure: expected:<[online]> but was:<[not
> responding]>
> at
> jdk.internal.reflect.GeneratedConstructorAccessor25.newInstance(Unknown
> Source)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(ServerLauncherRemoteIntegrationTestCase.java:213)
> at
> org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:222)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:209)
> at java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ... 1 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9889) LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
[
https://issues.apache.org/jira/browse/GEODE-9889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458648#comment-17458648
]
Geode Integration commented on GEODE-9889:
--
Seen on support/1.14 in [integration-test-openjdk11
#11|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/integration-test-openjdk11/builds/11]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.2-build.0897/test-results/integrationTest/1639264779/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.2-build.0897/test-artifacts/1639264779/integrationtestfiles-openjdk11-1.14.2-build.0897.tgz].
> LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
> ---
>
> Key: GEODE-9889
> URL: https://issues.apache.org/jira/browse/GEODE-9889
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Ray Ingles
>Priority: Major
>
> Seen in a CI build:
>
> {{> Task :geode-apis-compatible-with-redis:integrationTest}}
> {{org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest
> > subscribePsubscribeSameClient FAILED}}
> {{org.junit.ComparisonFailure: expected:<[2]L> but was:<[0]L>}}
> {{770 tests completed, 1 failed, 5 skipped}}
> {{=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=}}
> {{[*http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.2-build.0897/test-results/integrationTest/1639264779/*]}}
> {{=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=}}
> {{Test report artifacts from this job are available at:}}
> {{[*http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.2-build.0897/test-artifacts/1639264779/integrationtestfiles-openjdk11-1.14.2-build.0897.tgz*]}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9889) LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
[
https://issues.apache.org/jira/browse/GEODE-9889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ray Ingles updated GEODE-9889:
--
Description:
Seen in a CI build:
{{> Task :geode-apis-compatible-with-redis:integrationTest}}
{{org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest
> subscribePsubscribeSameClient FAILED}}
{{org.junit.ComparisonFailure: expected:<[2]L> but was:<[0]L>}}
was:
Seen in a CI build:
{{> Task :geode-apis-compatible-with-redis:integrationTest}}
{{org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest
> subscribePsubscribeSameClient FAILED}}
{{org.junit.ComparisonFailure: expected:<[2]L> but was:<[0]L>}}
{{770 tests completed, 1 failed, 5 skipped}}
{{=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=}}
{{[*http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.2-build.0897/test-results/integrationTest/1639264779/*]}}
{{=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=}}
{{Test report artifacts from this job are available at:}}
{{[*http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.2-build.0897/test-artifacts/1639264779/integrationtestfiles-openjdk11-1.14.2-build.0897.tgz*]}}
> LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
> ---
>
> Key: GEODE-9889
> URL: https://issues.apache.org/jira/browse/GEODE-9889
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Ray Ingles
>Priority: Major
>
> Seen in a CI build:
>
> {{> Task :geode-apis-compatible-with-redis:integrationTest}}
> {{org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest
> > subscribePsubscribeSameClient FAILED}}
> {{org.junit.ComparisonFailure: expected:<[2]L> but was:<[0]L>}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9889) LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
Ray Ingles created GEODE-9889:
-
Summary: LettucePubSubIntegrationTest >
subscribePsubscribeSameClient FAILED
Key: GEODE-9889
URL: https://issues.apache.org/jira/browse/GEODE-9889
Project: Geode
Issue Type: Bug
Components: redis
Affects Versions: 1.14.0
Reporter: Ray Ingles
Seen in a CI build:
{{> Task :geode-apis-compatible-with-redis:integrationTest}}
{{org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest
> subscribePsubscribeSameClient FAILED}}
{{org.junit.ComparisonFailure: expected:<[2]L> but was:<[0]L>}}
{{770 tests completed, 1 failed, 5 skipped}}
{{=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=}}
{{[*http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.2-build.0897/test-results/integrationTest/1639264779/*]}}
{{=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=}}
{{Test report artifacts from this job are available at:}}
{{[*http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.2-build.0897/test-artifacts/1639264779/integrationtestfiles-openjdk11-1.14.2-build.0897.tgz*]}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9770) CI Failure: ConflictingPersistentDataException in PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
[
https://issues.apache.org/jira/browse/GEODE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianxia Chen reassigned GEODE-9770:
---
Assignee: Jianxia Chen (was: Kirk Lund)
> CI Failure: ConflictingPersistentDataException in
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
> -
>
> Key: GEODE-9770
> URL: https://issues.apache.org/jira/browse/GEODE-9770
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI, needsTriage
>
> This ConflictingPersistentDataException has popped up multiple number of
> times.
> GEODE-6975
> GEODE-7898
>
> {noformat}
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest$$Lambda$477/1255368072.run
> in VM 0 running on Host
> heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testRecoverAfterConflict(PersistentRecoveryOrderDUnitTest.java:1328)
> Caused by:
> org.apache.geode.cache.CacheClosedException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote
> member heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002
> with persistent data
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
> created at timestamp 1635009815552 version 0 diskStoreId
> bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
> system as the local data from
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
> created at timestamp 1635009814986 version 0 diskStoreId
> cc4c64d81e9d4119-9e7320b29f540199 name , caused by
> org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote
> member heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002
> with persistent data
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
> created at timestamp 1635009815552 version 0 diskStoreId
> bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
> system as the local data from
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
> created at timestamp 1635009814986 version 0 diskStoreId
> cc4c64d81e9d4119-9e7320b29f540199 name
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5223)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4259)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4253)
> at
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1175)
> at
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1095)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3108)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3002)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2986)
> at
> org.apache.geode.cache.RegionFactory.create(RegionFactory.java:773)
> at
> org.apache.geode.internal.cache.InternalRegionFactory.create(InternalRegionFactory.java:75)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.createReplicateRegion(PersistentRecoveryOrderDUnitTest.java:1358)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.createReplicateRegion(PersistentRecoveryOrderDUnitTest.java:1362)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.lambda$testRecoverAfterConflict$bb17a952$5(PersistentRecoveryOrderDUnitTest.java:1330)
> Caused by:
>
> org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRe
[jira] [Commented] (GEODE-7702) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents is showing a product bug
[
https://issues.apache.org/jira/browse/GEODE-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458605#comment-17458605
]
Geode Integration commented on GEODE-7702:
--
Seen on support/1.12 in [distributed-test-openjdk8
#8|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/8]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.7-build.0319/test-results/distributedTest/1639270940/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.7-build.0319/test-artifacts/1639270940/distributedtestfiles-openjdk8-1.12.7-build.0319.tgz].
> DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents is showing a product bug
> ---
>
> Key: GEODE-7702
> URL: https://issues.apache.org/jira/browse/GEODE-7702
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.14.0
>
>
> testClearOnNonReplicateWithConcurrentEvents in
> DistributedAckRegionCCEDUnitTest.java
> versionTestClearOnNonReplicateWithConcurrentEvents in
> MultiVMRegionTestCase.java
> doOpsLoop
> doOpsLoopNoFlush
> {noformat}
> case 5:
> if (includeClear) {
> CCRegion.clear();
> break;
> } else {
> if (CCRegion.getAttributes().getDataPolicy().withReplication()) {
> if (oldkey != null) {
> CCRegion.putIfAbsent(oldkey, value);
> }
> break;
> } // else fall through to invalidate
> } {noformat}
> the addition of this chunk of code causes this test to fail.
> The core of the problem is that a putall and a clear are happening
> concurrently and the "system" does not respond by either clearing all entries
> or letting all entries persist.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9850) flaky test: testGetOldestTombstoneTimeForReplicateTombstoneSweeper
[
https://issues.apache.org/jira/browse/GEODE-9850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458586#comment-17458586
]
Geode Integration commented on GEODE-9850:
--
Seen in [distributed-test-openjdk8
#425|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/425]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639210838/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639210838/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> flaky test: testGetOldestTombstoneTimeForReplicateTombstoneSweeper
> --
>
> Key: GEODE-9850
> URL: https://issues.apache.org/jira/browse/GEODE-9850
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.13.5
>Reporter: Bill Burcham
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> First saw this failure in PR pipeline on support/1.13 here:
> [https://concourse.apachegeode-ci.info/builds/3912569]
> {code:java}
> org.apache.geode.internal.cache.versions.TombstoneDUnitTest >
> testGetOldestTombstoneTimeForReplicateTombstoneSweeper FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.versions.TombstoneDUnitTest$$Lambda$42/2046302475.run
> in VM 0 running on Host 9a305b2d7db7 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at
> org.apache.geode.internal.cache.versions.TombstoneDUnitTest.testGetOldestTombstoneTimeForReplicateTombstoneSweeper(TombstoneDUnitTest.java:228)
> Caused by:
> java.lang.AssertionError:
> Expecting:
> <-1637701703343L>
> to be greater than:
> <0L>
> at
> org.apache.geode.internal.cache.versions.TombstoneDUnitTest.lambda$testGetOldestTombstoneTimeForReplicateTombstoneSweeper$bb17a952$3(TombstoneDUnitTest.java:237)
> {code}
> I believe the fix is to wrap this assertion in an awaitility call.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7739) JMX managers may fail to federate mbeans for other members
[ https://issues.apache.org/jira/browse/GEODE-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458580#comment-17458580 ] Geode Integration commented on GEODE-7739: -- Seen in [distributed-test-openjdk8 #456|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/456] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639237023/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639237023/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz]. > JMX managers may fail to federate mbeans for other members > -- > > Key: GEODE-7739 > URL: https://issues.apache.org/jira/browse/GEODE-7739 > Project: Geode > Issue Type: Bug > Components: jmx >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > JMX Manager may fail to federate one or more MXBeans for other members > because of a race condition during startup. When ManagementCacheListener is > first constructed, it is in a state that will ignore all callbacks because > the field readyForEvents is false. > > Debugging with JMXMBeanReconnectDUnitTest revealed this bug. > The test starts two locators with jmx manager configured and started. > Locator1 always has all of locator2's mbeans, but locator2 is intermittently > missing the personal mbeans of locator1. > I think this is caused by some sort of race condition in the code that > creates the monitoring regions for other members in locator2. > It's possible that the jmx manager that hits this bug might fail to have > mbeans for servers as well as other locators but I haven't seen a test case > for this scenario. > The exposure of this bug means that a user running more than one locator > might have a locator that is missing one or more mbeans for the cluster. > > Studying the JMX code also reveals the existence of *GEODE-8012*. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9885) StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with duplicated append
[
https://issues.apache.org/jira/browse/GEODE-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458578#comment-17458578
]
Geode Integration commented on GEODE-9885:
--
Seen in [distributed-test-openjdk8
#424|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/424]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639212551/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639212551/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with
> duplicated append
>
>
> Key: GEODE-9885
> URL: https://issues.apache.org/jira/browse/GEODE-9885
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
>
> The test appends a lot of strings to a key. It wound up adding (at least one)
> extra string to the stored string:
>
> {{java.util.concurrent.ExecutionException: java.lang.AssertionError:
> unexpected -\{append0}-key-3-27680- at index 27681 iterationCount=61995 in
> string}}
>
> The string "\{append0}-key-3-27680-" appeared twice in sequence.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9885) StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with duplicated append
[
https://issues.apache.org/jira/browse/GEODE-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458576#comment-17458576
]
Geode Integration commented on GEODE-9885:
--
Seen in [distributed-test-openjdk8
#472|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/472]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639250971/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639250971/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with
> duplicated append
>
>
> Key: GEODE-9885
> URL: https://issues.apache.org/jira/browse/GEODE-9885
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
>
> The test appends a lot of strings to a key. It wound up adding (at least one)
> extra string to the stored string:
>
> {{java.util.concurrent.ExecutionException: java.lang.AssertionError:
> unexpected -\{append0}-key-3-27680- at index 27681 iterationCount=61995 in
> string}}
>
> The string "\{append0}-key-3-27680-" appeared twice in sequence.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9885) StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with duplicated append
[
https://issues.apache.org/jira/browse/GEODE-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458577#comment-17458577
]
Geode Integration commented on GEODE-9885:
--
Seen in [distributed-test-openjdk8
#460|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/460]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639239131/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639239131/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with
> duplicated append
>
>
> Key: GEODE-9885
> URL: https://issues.apache.org/jira/browse/GEODE-9885
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
>
> The test appends a lot of strings to a key. It wound up adding (at least one)
> extra string to the stored string:
>
> {{java.util.concurrent.ExecutionException: java.lang.AssertionError:
> unexpected -\{append0}-key-3-27680- at index 27681 iterationCount=61995 in
> string}}
>
> The string "\{append0}-key-3-27680-" appeared twice in sequence.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7822) MemoryThresholdsOffHeapDUnitTest has failures
[
https://issues.apache.org/jira/browse/GEODE-7822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458575#comment-17458575
]
Geode Integration commented on GEODE-7822:
--
Seen in [distributed-test-openjdk8
#485|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/485]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639259391/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639259391/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> MemoryThresholdsOffHeapDUnitTest has failures
> -
>
> Key: GEODE-7822
> URL: https://issues.apache.org/jira/browse/GEODE-7822
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Priority: Major
> Labels: flaky
>
> These two failures were seen in mass test runs...
> {noformat}
> testPRLoadRejection
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/674
> {noformat}
> {noformat}
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest >
> testPRLoadRejection FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$31.call in
> VM 2 running on Host a57bd8581b8d with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest.testPRLoadRejection(MemoryThresholdsOffHeapDUnitTest.java:1045)
> Caused by:
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$31.call(MemoryThresholdsOffHeapDUnitTest.java:1077){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> [http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-results/distributedTest/1582515952/]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-artifacts/1582515952/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0005.tgz]
> {noformat}
> testDRLoadRejection
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/742
> {noformat}
> {noformat}
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest >
> testDRLoadRejection FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$18.call in
> VM 2 running on Host b2c673017cde with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest.testDRLoadRejection(MemoryThresholdsOffHeapDUnitTest.java:667)
> Caused by:
>java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$18.call(MemoryThresholdsOffHeapDUnitTest.java:673)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-results/distributedTest/1582626992/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-artifacts/1582626992/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0005.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7739) JMX managers may fail to federate mbeans for other members
[ https://issues.apache.org/jira/browse/GEODE-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458571#comment-17458571 ] Geode Integration commented on GEODE-7739: -- Seen in [distributed-test-openjdk8 #490|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/490] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639264103/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639264103/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz]. > JMX managers may fail to federate mbeans for other members > -- > > Key: GEODE-7739 > URL: https://issues.apache.org/jira/browse/GEODE-7739 > Project: Geode > Issue Type: Bug > Components: jmx >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > JMX Manager may fail to federate one or more MXBeans for other members > because of a race condition during startup. When ManagementCacheListener is > first constructed, it is in a state that will ignore all callbacks because > the field readyForEvents is false. > > Debugging with JMXMBeanReconnectDUnitTest revealed this bug. > The test starts two locators with jmx manager configured and started. > Locator1 always has all of locator2's mbeans, but locator2 is intermittently > missing the personal mbeans of locator1. > I think this is caused by some sort of race condition in the code that > creates the monitoring regions for other members in locator2. > It's possible that the jmx manager that hits this bug might fail to have > mbeans for servers as well as other locators but I haven't seen a test case > for this scenario. > The exposure of this bug means that a user running more than one locator > might have a locator that is missing one or more mbeans for the cluster. > > Studying the JMX code also reveals the existence of *GEODE-8012*. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-7710) CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest fails intermittently because one locator is missing the LockServiceMXBean
[
https://issues.apache.org/jira/browse/GEODE-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458570#comment-17458570
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#490|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/490]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639264103/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639264103/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest
> fails intermittently because one locator is missing the LockServiceMXBean
> --
>
> Key: GEODE-7710
> URL: https://issues.apache.org/jira/browse/GEODE-7710
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.13.0, 1.14.0, 1.15.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, flaky, pull-request-available
> Time Spent: 5h
> Remaining Estimate: 0h
>
> This test fails due to GEODE-7739. Enter new failures against that ticket.
> Multiple tests in JMXMBeanReconnectDUnitTest may fail an await due to one of
> the locators missing the LockServiceMXBean for the cluster config service.
> {noformat}
> but could not find:
>
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> {noformat}
> These test failures are caused by *GEODE-7739*.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7455) CI Failure: AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean Failed
[
https://issues.apache.org/jira/browse/GEODE-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458569#comment-17458569
]
Geode Integration commented on GEODE-7455:
--
Seen in [distributed-test-openjdk8
#489|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/489]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639262978/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639262978/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> CI Failure:
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> Failed
> --
>
> Key: GEODE-7455
> URL: https://issues.apache.org/jira/browse/GEODE-7455
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Mark Hanson
>Priority: Major
> Labels: GeodeOperationAPI, flaky
>
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> failed in DistributedTestOpenJDK11 below are the relevant details.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1280]
>
> {noformat}
> 13:30:08
> org.apache.geode.management.AEQManagementDUnitTest >
> testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean FAILED
> 13:30:08
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.AEQManagementDUnitTest$$Lambda$200/0x0008407dec40.run
> in VM 0 running on Host 0e592392f6db with 4 VMs
> 13:30:08
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> 13:30:08
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> 13:30:08
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean(AEQManagementDUnitTest.java:245)
> 13:30:0813:30:08
> Caused by:
> 13:30:08
> org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 13:30:08
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.lambda$testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean$d4d42c35$1(AEQManagementDUnitTest.java:250)
> 14:10:3714:10:37
> 793 tests completed, 1 failed, 61 skipped {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-results/distributedTest/1573687903/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-artifacts/1573687903/distributedtestfiles-OpenJDK11-1.12.0-SNAPSHOT.0013.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7822) MemoryThresholdsOffHeapDUnitTest has failures
[
https://issues.apache.org/jira/browse/GEODE-7822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458568#comment-17458568
]
Geode Integration commented on GEODE-7822:
--
Seen in [distributed-test-openjdk8
#488|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/488]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-results/distributedTest/1639262734/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0734/test-artifacts/1639262734/distributedtestfiles-openjdk8-1.15.0-build.0734.tgz].
> MemoryThresholdsOffHeapDUnitTest has failures
> -
>
> Key: GEODE-7822
> URL: https://issues.apache.org/jira/browse/GEODE-7822
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Priority: Major
> Labels: flaky
>
> These two failures were seen in mass test runs...
> {noformat}
> testPRLoadRejection
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/674
> {noformat}
> {noformat}
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest >
> testPRLoadRejection FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$31.call in
> VM 2 running on Host a57bd8581b8d with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest.testPRLoadRejection(MemoryThresholdsOffHeapDUnitTest.java:1045)
> Caused by:
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$31.call(MemoryThresholdsOffHeapDUnitTest.java:1077){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> [http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-results/distributedTest/1582515952/]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-artifacts/1582515952/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0005.tgz]
> {noformat}
> testDRLoadRejection
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/742
> {noformat}
> {noformat}
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest >
> testDRLoadRejection FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$18.call in
> VM 2 running on Host b2c673017cde with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest.testDRLoadRejection(MemoryThresholdsOffHeapDUnitTest.java:667)
> Caused by:
>java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$18.call(MemoryThresholdsOffHeapDUnitTest.java:673)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-results/distributedTest/1582626992/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-artifacts/1582626992/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0005.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-7875) The gfsh create index command sometimes fails with 'Index already exists. Create failed due to duplicate name.' message
[
https://issues.apache.org/jira/browse/GEODE-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-7875:
--
Labels: pull-request-available (was: )
> The gfsh create index command sometimes fails with 'Index already exists.
> Create failed due to duplicate name.' message
> ---
>
> Key: GEODE-7875
> URL: https://issues.apache.org/jira/browse/GEODE-7875
> Project: Geode
> Issue Type: Bug
> Components: gfsh, querying
>Reporter: Barrett Oglesby
>Assignee: Mario Kevo
>Priority: Major
> Labels: pull-request-available
>
> Here is output from the connect, list indexes, create index commands:
> {noformat}
> (1) Executing - connect --locator=localhost[23456]
> Connecting to Locator at [host=localhost, port=23456] ..
> Connecting to Manager at [host=boglesbymac.local, port=1099] ..
> Successfully connected to: [host=boglesbymac.local, port=1099]
> (2) Executing - list indexes
> No Indexes Found
> (3) Executing - create index --name=cusip_index_1 --expression=cusip
> --region=/Trades
>Member| Status | Message
> | -- |
> ---
> 192.168.1.4(server1:88452):41001 | ERROR | Index "cusip_index_1" already
> exists. Create failed due to duplicate name.
> 192.168.1.4(server2:88465):41002 | OK | Index successfully created
> 192.168.1.4(server3:88473):41003 | ERROR | Index "cusip_index_1" already
> exists. Create failed due to duplicate name.
> 192.168.1.4(server4:88480):41004 | ERROR | Index "cusip_index_1" already
> exists. Create failed due to duplicate name.
> {noformat}
> Here is some logging that shows the behavior:
> server2 executes the CreateIndexFunction and creates the index locally:
> {noformat}
> [warn 2020/03/12 16:18:11.273 PDT tid=0x54]
> XXX CreateIndexFunction.execute indexName=cusip_index_1
> [info 2020/03/12 16:18:11.297 PDT tid=0x54]
> Created index locally, sending index creation message to all members, and
> will be waiting for response Index [ Name=cusip_index_1 Type =FUNCTIONAL
> IdxExp=cusip From=/Trades Proj=*]imports : null.
> {noformat}
> It sends the IndexCreationMsg to servers 1, 3 and 4 and processes the
> response:
> {noformat}
> [warn 2020/03/12 16:18:11.297 PDT tid=0x54]
> XXX IndexCreationMsg.send indMsg=cusip_index_1
> [warn 2020/03/12 16:18:11.298 PDT tid=0x54]
> XXX PartitionedRegion.createIndex
> response= from [192.168.1.4(server1:88452):41001,
> 192.168.1.4(server3:88473):41003, 192.168.1.4(server4:88480):41004]>
> {noformat}
> servers 1, 3 and 4 receive the IndexCreationMsg, creates the index and
> respond:
> {noformat}
> [warn 2020/03/12 16:18:11.298 PDT
> tid=0x4b] XXX IndexCreationMsg.operateOnPartitionedRegion about to
> createIndexes
> [warn 2020/03/12 16:18:11.304 PDT
> tid=0x4b] XXX IndexCreationMsg.operateOnPartitionedRegion done createIndexes
> {noformat}
> Then they execute the CreateIndexFunction to create the index locally which
> fails:
> {noformat}
> [warn 2020/03/12 16:18:11.501 PDT tid=0x4e]
> XXX CreateIndexFunction.execute indexName=cusip_index_1
> [warn 2020/03/12 16:18:11.521 PDT tid=0x4e]
> XXX CreateIndexFunction.execute failed due to IndexNameConflictException:
> org.apache.geode.cache.query.IndexNameConflictException: Index named '
> cusip_index_1 ' already exists.
> at
> org.apache.geode.internal.cache.PartitionedRegion.createIndex(PartitionedRegion.java:8453)
> at
> org.apache.geode.internal.cache.PartitionedRegion.createIndex(PartitionedRegion.java:8403)
> at
> org.apache.geode.cache.query.internal.DefaultQueryService.createIndex(DefaultQueryService.java:245)
> at
> org.apache.geode.cache.query.internal.DefaultQueryService.createIndex(DefaultQueryService.java:203)
> at
> org.apache.geode.cache.query.internal.DefaultQueryService.createIndex(DefaultQueryService.java:274)
> at
> org.apache.geode.cache.query.internal.DefaultQueryService.createIndex(DefaultQueryService.java:177)
> at
> org.apache.geode.management.internal.cli.functions.CreateIndexFunction.execute(CreateIndexFunction.java:62)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9881) Fully recoverd Oplogs object indicating unrecoveredRegionCount>0 preventing compaction
[
https://issues.apache.org/jira/browse/GEODE-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9881:
--
Labels: pull-request-available (was: )
> Fully recoverd Oplogs object indicating unrecoveredRegionCount>0 preventing
> compaction
> --
>
> Key: GEODE-9881
> URL: https://issues.apache.org/jira/browse/GEODE-9881
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Reporter: Jakov Varenina
>Assignee: Jakov Varenina
>Priority: Major
> Labels: pull-request-available
>
> We have found problem in case when region is closed with Region.close() and
> then recreated to start the recovery. If you inspect this code in close()
> function you will notice that it doesn't make any sense:
> {code:java}
> void close(DiskRegion dr) {
> // while a krf is being created can not close a region
> lockCompactor();
> try {
> if (!isDrfOnly()) {
> DiskRegionInfo dri = getDRI(dr);
> if (dri != null) {
> long clearCount = dri.clear(null);
> if (clearCount != 0) {
> totalLiveCount.addAndGet(-clearCount);
> // no need to call handleNoLiveValues because we now have an
> // unrecovered region.
> }
> regionMap.get().remove(dr.getId(), dri);
> }
> addUnrecoveredRegion(dr.getId());
> }
> } finally {
> unlockCompactor();
> }
> }
> {code}
> Please notice that addUnrecoveredRegion() marks DiskRegionInfo object as
> unrecovered and increments counter unrecoveredRegionCount. This
> DiskRegionInfo object is contained in regionMap structure. Then afterwards it
> removes DiskRegionInfo object (that was previously marked as unrecovered)
> from the regionMap. This doesn't make any sense, it updated object and then
> removed it from map to be garbage collected. As you will see later on this
> will cause some issues when region is recovered.
> Please check this code at recovery:
> {code:java}
> /**
> * For each dri that this oplog has that is currently unrecoverable check to
> see if a DiskRegion
> * that is recoverable now exists.
> */
> void checkForRecoverableRegion(DiskRegionView dr) {
> if (unrecoveredRegionCount.get() > 0) {
> DiskRegionInfo dri = getDRI(dr);
> if (dri != null) {
> if (dri.testAndSetRecovered(dr)) {
> unrecoveredRegionCount.decrementAndGet();
> }
> }
> }
> }
> {code}
> The problem is that geode will not clear counter unrecoveredRegionCount in
> Oplog objects after recovery is done. This is because
> checkForRecoverableRegion will check unrecoveredRegionCount counter and
> perform testAndSetRecovered. The testAndSetRecovered will always return
> false, because non of the DiskRegionInfo objects in region map have
> unrecovered flag set to true (all object marked as unrecovered were deleted
> by close(), and then they were recreated during recovery see note below).
> The problem here is that all Oplogs will be fully recovered with the counter
> incorrectly indicating unrecoveredRegionCount>0. This will later on prevent
> the compaction of recovered Oplogs (the files that have .crf, .drf and .krf)
> when they reach compaction threshold.
> Note: During recovery regionMap will be recreated from the Oplog files. Since
> all DiskRegionInfo objects are deleted from regionMap during the close(),
> they will be recreated by using function initRecoveredEntry during the
> recovery. All DiskRegionInfo will be created with flag unrecovered set to
> false.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
