[jira] [Resolved] (GEODE-9703) redis benchmarks fail to compile after rename

[ https://issues.apache.org/jira/browse/GEODE-9703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-9703. - Fix Version/s: 1.15.0 Resolution: Fixed > redis benchmarks fail to compile after rename >

[jira] [Commented] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly

[ https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426513#comment-17426513 ] Geode Integration commented on GEODE-8644: -- Seen in [distributed-test-openjdk8

[jira] [Commented] (GEODE-9703) redis benchmarks fail to compile after rename

[ https://issues.apache.org/jira/browse/GEODE-9703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426498#comment-17426498 ] Geode Integration commented on GEODE-9703: -- Seen in [benchmark-radish #122|http

[jira] [Commented] (GEODE-9567) Geode for Redis Rename

[ https://issues.apache.org/jira/browse/GEODE-9567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426461#comment-17426461 ] ASF subversion and git services commented on GEODE-9567: Commit 0

[jira] [Updated] (GEODE-9703) redis benchmarks fail to compile after rename

[ https://issues.apache.org/jira/browse/GEODE-9703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9703: -- Labels: needsTriage pull-request-available (was: needsTriage) > redis benchmarks fail to compi

[jira] [Assigned] (GEODE-9703) redis benchmarks fail to compile after rename

[ https://issues.apache.org/jira/browse/GEODE-9703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols reassigned GEODE-9703: --- Assignee: Owen Nichols > redis benchmarks fail to compile after rename > ---

[jira] [Resolved] (GEODE-9707) artifacts not archived when a ci job fails due to OOM

[ https://issues.apache.org/jira/browse/GEODE-9707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-9707. - Fix Version/s: 1.15.0 Resolution: Fixed > artifacts not archived when a ci job fails due t

[jira] [Commented] (GEODE-9707) artifacts not archived when a ci job fails due to OOM

[ https://issues.apache.org/jira/browse/GEODE-9707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426443#comment-17426443 ] ASF subversion and git services commented on GEODE-9707: Commit 9

[jira] [Updated] (GEODE-9707) artifacts not archived when a ci job fails due to OOM

[ https://issues.apache.org/jira/browse/GEODE-9707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9707: -- Labels: needsTriage pull-request-available (was: needsTriage) > artifacts not archived when a

[jira] [Updated] (GEODE-9707) artifacts not archived when a ci job fails due to OOM

[ https://issues.apache.org/jira/browse/GEODE-9707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9707: - Labels: needsTriage (was: ) > artifacts not archived when a ci job fails due to OOM > --

[jira] [Assigned] (GEODE-9707) artifacts not archived when a ci job fails due to OOM

[ https://issues.apache.org/jira/browse/GEODE-9707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols reassigned GEODE-9707: --- Assignee: Owen Nichols > artifacts not archived when a ci job fails due to OOM > ---

[jira] [Created] (GEODE-9707) artifacts not archived when a ci job fails due to OOM

Owen Nichols created GEODE-9707: --- Summary: artifacts not archived when a ci job fails due to OOM Key: GEODE-9707 URL: https://issues.apache.org/jira/browse/GEODE-9707 Project: Geode Issue Type:

[jira] [Commented] (GEODE-9534) Add tests to verify peer communication when auth expired

[ https://issues.apache.org/jira/browse/GEODE-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426430#comment-17426430 ] ASF subversion and git services commented on GEODE-9534: Commit f

[jira] [Commented] (GEODE-9663) throw and handle AuthenticationExpiredException at login time

[ https://issues.apache.org/jira/browse/GEODE-9663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426428#comment-17426428 ] ASF subversion and git services commented on GEODE-9663: Commit a

[jira] [Updated] (GEODE-9705) When create PR failed with DistributedSystemDisconnectedException, should use it as cause of PartitionedRegionException

[ https://issues.apache.org/jira/browse/GEODE-9705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9705: -- Labels: needsTriage pull-request-available (was: needsTriage) > When create PR failed with Dis

[jira] [Updated] (GEODE-9706) OutOfMemoryDUnitTest can be improved

[ https://issues.apache.org/jira/browse/GEODE-9706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-9706: Affects Version/s: 1.15.0 > OutOfMemoryDUnitTest can be improved >

[jira] [Updated] (GEODE-9706) OutOfMemoryDUnitTest can be improved

[ https://issues.apache.org/jira/browse/GEODE-9706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-9706: Priority: Trivial (was: Major) > OutOfMemoryDUnitTest can be improved > --

[jira] [Updated] (GEODE-9706) OutOfMemoryDUnitTest can be improved

[ https://issues.apache.org/jira/browse/GEODE-9706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-9706: Priority: Minor (was: Trivial) > OutOfMemoryDUnitTest can be improved > --

[jira] [Created] (GEODE-9706) OutOfMemoryDUnitTest can be improved

Darrel Schneider created GEODE-9706: --- Summary: OutOfMemoryDUnitTest can be improved Key: GEODE-9706 URL: https://issues.apache.org/jira/browse/GEODE-9706 Project: Geode Issue Type: Test

[jira] [Commented] (GEODE-9705) When create PR failed with DistributedSystemDisconnectedException, should use it as cause of PartitionedRegionException

[ https://issues.apache.org/jira/browse/GEODE-9705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426413#comment-17426413 ] ASF subversion and git services commented on GEODE-9705: Commit 8

[jira] [Updated] (GEODE-9705) When create PR failed with DistributedSystemDisconnectedException, should use it as cause of PartitionedRegionException

[ https://issues.apache.org/jira/browse/GEODE-9705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9705: - Labels: needsTriage (was: ) > When create PR failed with DistributedSystemDisconnectedEx

[jira] [Created] (GEODE-9705) When create PR failed with DistributedSystemDisconnectedException, should use it as cause of PartitionedRegionException

Xiaojian Zhou created GEODE-9705: Summary: When create PR failed with DistributedSystemDisconnectedException, should use it as cause of PartitionedRegionException Key: GEODE-9705 URL: https://issues.apache.org/ji

[jira] [Updated] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-9704: - Affects Version/s: 1.15.0 > When durable clients recovers, it sends "ready for event" signal befo

[jira] [Updated] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-9704: - Labels: GeodeOperationAPI blocks-1.15.0​ (was: GeodeOperationAPI) > When durable clients recover

[jira] [Updated] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9704: --- Description: This is the old Geode behavior, but may or may not be the correct behavior. When durabl

[jira] [Commented] (GEODE-9641) Benchmark instability in P2pPartitionedPutBytesBenchmark

[ https://issues.apache.org/jira/browse/GEODE-9641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426398#comment-17426398 ] ASF subversion and git services commented on GEODE-9641: Commit 7

[jira] [Updated] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9704: --- Description: This is the old Geode behavior, but may or may not be the correct behavior. When durabl

[jira] [Updated] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9704: --- Description: This is the old Geode behavior, but may or may not be the correct behavior. When durabl

[jira] [Updated] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9704: --- Labels: GeodeOperationAPI (was: needsTriage) > When durable clients recovers, it sends "ready for ev

[jira] [Updated] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9704: - Labels: needsTriage (was: ) > When durable clients recovers, it sends "ready for event"

[jira] [Created] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

Jinmei Liao created GEODE-9704: -- Summary: When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions Key: GEODE-9704 URL: https:

[jira] [Commented] (GEODE-9703) redis benchmarks fail to compile after rename

[ https://issues.apache.org/jira/browse/GEODE-9703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426389#comment-17426389 ] Geode Integration commented on GEODE-9703: -- Seen in [benchmark-radish #119|http

[jira] [Updated] (GEODE-9703) redis benchmarks fail to compile after rename

[ https://issues.apache.org/jira/browse/GEODE-9703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9703: - Labels: needsTriage (was: ) > redis benchmarks fail to compile after rename > --

[jira] [Created] (GEODE-9703) redis benchmarks fail to compile after rename

Owen Nichols created GEODE-9703: --- Summary: redis benchmarks fail to compile after rename Key: GEODE-9703 URL: https://issues.apache.org/jira/browse/GEODE-9703 Project: Geode Issue Type: Bug

[jira] [Commented] (GEODE-7118) RestartOfMemberDistributedTest fails intermittently in precheckin

[ https://issues.apache.org/jira/browse/GEODE-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426371#comment-17426371 ] Dale Emery commented on GEODE-7118: --- This test starts a locator on an ephemeral port, c

[jira] [Commented] (GEODE-9536) Run all Windows distributed tests in CI, in parallel

[ https://issues.apache.org/jira/browse/GEODE-9536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426365#comment-17426365 ] ASF subversion and git services commented on GEODE-9536: Commit 9

[jira] [Commented] (GEODE-9536) Run all Windows distributed tests in CI, in parallel

[ https://issues.apache.org/jira/browse/GEODE-9536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426363#comment-17426363 ] ASF subversion and git services commented on GEODE-9536: Commit 4

[jira] [Commented] (GEODE-9536) Run all Windows distributed tests in CI, in parallel

[ https://issues.apache.org/jira/browse/GEODE-9536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426340#comment-17426340 ] ASF subversion and git services commented on GEODE-9536: Commit 0

[jira] [Commented] (GEODE-9702) public setters added to GatewaySender, not caught by japicmp

[ https://issues.apache.org/jira/browse/GEODE-9702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426333#comment-17426333 ] Owen Nichols commented on GEODE-9702: - see also GEODE-9629 and GEODE-9630, which part

[jira] [Updated] (GEODE-9702) public setters added to GatewaySender, not caught by japicmp

[ https://issues.apache.org/jira/browse/GEODE-9702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9702: - Labels: needsTriage (was: ) > public setters added to GatewaySender, not caught by japic

[jira] [Created] (GEODE-9702) public setters added to GatewaySender, not caught by japicmp

Owen Nichols created GEODE-9702: --- Summary: public setters added to GatewaySender, not caught by japicmp Key: GEODE-9702 URL: https://issues.apache.org/jira/browse/GEODE-9702 Project: Geode Iss

[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified

[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9701: - Description: Bill reported that ClusterStartupRule seems to be creating 4 VMs no matter how few VMs he s

[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified

[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9701: - Labels: GeodeOperationAPI needsTriage (was: needsTriage) > ClusterStartupRule starts 4 VMs even if fewer

[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified

[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9701: - Description: Bill reported that ClusterStartupRule seems to be creating 4 VMs no matter how few VMs he s

[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified

[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9701: - Description: Bill reported that ClusterStartupRule seems to be creating 4 VMs no matter how few VMs he s

[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified

[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9701: - Labels: needsTriage (was: ) > ClusterStartupRule starts 4 VMs even if fewer VMs is speci

[jira] [Created] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified

Kirk Lund created GEODE-9701: Summary: ClusterStartupRule starts 4 VMs even if fewer VMs is specified Key: GEODE-9701 URL: https://issues.apache.org/jira/browse/GEODE-9701 Project: Geode Issue T

[jira] [Commented] (GEODE-6183) CI Failure: LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed with ConditionTimeoutException

[ https://issues.apache.org/jira/browse/GEODE-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426322#comment-17426322 ] Geode Integration commented on GEODE-6183: -- Seen in [integration-test-openjdk8

[jira] [Updated] (GEODE-9689) MultiUserAPIDUnitTest "Failed to find the authenticated user"

[ https://issues.apache.org/jira/browse/GEODE-9689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9689: - Labels: needsTriage region (was: needsTriage) > MultiUserAPIDUnitTest "Failed to find th

[jira] [Updated] (GEODE-9699) ZUNIONSTORE returns 1 instead of 0 when running against non-existing key

[ https://issues.apache.org/jira/browse/GEODE-9699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Zoerner updated GEODE-9699: Description: The following redis TCL test fails when running against Geode for Redis: {code}

[jira] [Updated] (GEODE-9700) ZUNIONSTORE and ZINTERSTORE need to work with regular sets as inputs

[ https://issues.apache.org/jira/browse/GEODE-9700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Zoerner updated GEODE-9700: Description: Some of the Redis TCL tests fail when running against Geode due to ZUNIONSTORE and ZI

[jira] [Updated] (GEODE-9699) ZUNIONSTORE returns 1 instead of 0 when running against non-existing key

[ https://issues.apache.org/jira/browse/GEODE-9699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Zoerner updated GEODE-9699: Description: The following redis TCL test fails when running against Geode for Redis: {code}

[jira] [Resolved] (GEODE-9413) Enable native Redis TCL tests for zset (sorted set) data type

[ https://issues.apache.org/jira/browse/GEODE-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Zoerner resolved GEODE-9413. - Resolution: Fixed > Enable native Redis TCL tests for zset (sorted set) data type > -

[jira] [Commented] (GEODE-9688) .Net core builds should be x64

[ https://issues.apache.org/jira/browse/GEODE-9688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426303#comment-17426303 ] ASF GitHub Bot commented on GEODE-9688: --- echobravopapa commented on pull request #8

[jira] [Updated] (GEODE-9688) .Net core builds should be x64

[ https://issues.apache.org/jira/browse/GEODE-9688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9688: -- Labels: needsTriage pull-request-available (was: needsTriage) > .Net core builds should be x64

[jira] [Commented] (GEODE-9413) Enable native Redis TCL tests for zset (sorted set) data type

[ https://issues.apache.org/jira/browse/GEODE-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426301#comment-17426301 ] ASF subversion and git services commented on GEODE-9413: Commit 3

[jira] [Commented] (GEODE-8760) P2pPartitionedPutBenchmark fails with UnmarshalException

[ https://issues.apache.org/jira/browse/GEODE-8760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426288#comment-17426288 ] Geode Integration commented on GEODE-8760: -- Seen in [benchmark-base #252|https:

[jira] [Commented] (GEODE-8760) P2pPartitionedPutBenchmark fails with UnmarshalException

[ https://issues.apache.org/jira/browse/GEODE-8760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426287#comment-17426287 ] Geode Integration commented on GEODE-8760: -- Seen in [benchmark-base #253|https:

[jira] [Commented] (GEODE-9536) Run all Windows distributed tests in CI, in parallel

[ https://issues.apache.org/jira/browse/GEODE-9536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426284#comment-17426284 ] ASF subversion and git services commented on GEODE-9536: Commit 9

[jira] [Commented] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client

[ https://issues.apache.org/jira/browse/GEODE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426285#comment-17426285 ] ASF subversion and git services commented on GEODE-8616: Commit 9

[jira] [Commented] (GEODE-9567) Geode for Redis Rename

[ https://issues.apache.org/jira/browse/GEODE-9567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426253#comment-17426253 ] ASF subversion and git services commented on GEODE-9567: Commit 2

[jira] [Commented] (GEODE-9700) ZUNIONSTORE and ZINTERSTORE need to work with regular sets as inputs

[ https://issues.apache.org/jira/browse/GEODE-9700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426228#comment-17426228 ] Jens Deppe commented on GEODE-9700: --- All the scores are set to `1` in this case. > ZUN

[jira] [Comment Edited] (GEODE-9700) ZUNIONSTORE and ZINTERSTORE need to work with regular sets as inputs

[ https://issues.apache.org/jira/browse/GEODE-9700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426228#comment-17426228 ] Jens Deppe edited comment on GEODE-9700 at 10/8/21, 3:20 PM: -