[jira] [Resolved] (GEODE-9971) Fix ping distributed test case after switching from docker-compose to testcontainers
[ https://issues.apache.org/jira/browse/GEODE-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Gomez resolved GEODE-9971. -- Fix Version/s: 1.15.0 Resolution: Fixed > Fix ping distributed test case after switching from docker-compose to > testcontainers > > > Key: GEODE-9971 > URL: https://issues.apache.org/jira/browse/GEODE-9971 > Project: Geode > Issue Type: Bug >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.15.0 > > > Due to the changes done by GEODE-9156 to switch from docker-compose to > testcontainers test case > testPingsToReceiversWithSamePortAndHostnameForSendersReachTheRightReceivers > from > SeveralGatewayReceiversWithSamePortAndHostnameForSendersTest was not working > properly even though it was failing. > The test must be enhanced to check that entries are wan replicated to the > other site (for example by checking that entries added locally do not leave > events in the gateway sender queues). > After that, the code of the test must be fixed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9971) Fix ping distributed test case after switching from docker-compose to testcontainers
[ https://issues.apache.org/jira/browse/GEODE-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478364#comment-17478364 ] ASF subversion and git services commented on GEODE-9971: Commit 9f32d7215df70d0ca926c0fd058fdf682965b790 in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9f32d72 ] GEODE-9971: Fix test case after switching from docker-compose to testcontainers (#7277) > Fix ping distributed test case after switching from docker-compose to > testcontainers > > > Key: GEODE-9971 > URL: https://issues.apache.org/jira/browse/GEODE-9971 > Project: Geode > Issue Type: Bug >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: needsTriage, pull-request-available > > Due to the changes done by GEODE-9156 to switch from docker-compose to > testcontainers test case > testPingsToReceiversWithSamePortAndHostnameForSendersReachTheRightReceivers > from > SeveralGatewayReceiversWithSamePortAndHostnameForSendersTest was not working > properly even though it was failing. > The test must be enhanced to check that entries are wan replicated to the > other site (for example by checking that entries added locally do not leave > events in the gateway sender queues). > After that, the code of the test must be fixed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9962) Redis INFO Command Support for Cluster Mode
[ https://issues.apache.org/jira/browse/GEODE-9962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478298#comment-17478298 ] ASF subversion and git services commented on GEODE-9962: Commit 6b204454b94a935303be6e88ceadf0f6cc565e72 in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6b20445 ] GEODE-9962: Update redis INFO command for cluster mode responses (#7273) - Redis version is set to `5.0` - InfoNativeRedisAcceptanceTest changed to use an actual Redis cluster - Responses in cluster mode match native Redis > Redis INFO Command Support for Cluster Mode > --- > > Key: GEODE-9962 > URL: https://issues.apache.org/jira/browse/GEODE-9962 > Project: Geode > Issue Type: Task > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Assignee: Jens Deppe >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.15.0 > > > The Redis INFO command does not show correct information for cluster mode. > > Research what changes must occur to support the correct information for > cluster mode and ensure tickets are created for tracking. > > +Acceptance Criteria+ > > Gaps in cluster mode supported are identified and tickets are created for > tracking. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9712) Genericize All .NET Core Classes
[
https://issues.apache.org/jira/browse/GEODE-9712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478293#comment-17478293
]
ASF GitHub Bot commented on GEODE-9712:
---
mmartell commented on a change in pull request #909:
URL: https://github.com/apache/geode-native/pull/909#discussion_r787267405
##
File path: c-bindings/src/data_serializable_raw.hpp
##
@@ -0,0 +1,53 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+#pragma once
+
+#include
+
+namespace apache {
+namespace geode {
+namespace client {
+namespace internal {
+
+class DataSerializableRaw : public DataSerializablePrimitive , public
CacheableKey {
+ public:
+ DataSerializableRaw(const int8_t* data, size_t size);
+ ~DataSerializableRaw() noexcept override = default;
+
+ static std::shared_ptr create(
+ const int8_t* data, size_t size);
+
+
+ virtual void toData(DataOutput& dataOutput) const override;
Review comment:
Good catch! I guess you're better than clang-tidy.
--
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
> Genericize All .NET Core Classes
>
>
> Key: GEODE-9712
> URL: https://issues.apache.org/jira/browse/GEODE-9712
> Project: Geode
> Issue Type: New Feature
> Components: native client
>Reporter: Michael Martell
>Assignee: Michael Martell
>Priority: Major
> Labels: pull-request-available
>
> We need to implement IRegion in .NET Core. This will require
> writing generic versions of RegionFactory, Region, and Cache.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9929) testTXCreationAndCleanupAtCommit when running RemoteTransactionDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-9929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9929: --- Labels: needsTriage (was: ) > testTXCreationAndCleanupAtCommit when running RemoteTransactionDUnitTest > > > Key: GEODE-9929 > URL: https://issues.apache.org/jira/browse/GEODE-9929 > Project: Geode > Issue Type: Bug >Affects Versions: 1.14.3 >Reporter: Kristen >Priority: Major > Labels: needsTriage > > org.apache.geode.internal.cache.RemoteTransactionDUnitTest > > testTXCreationAndCleanupAtCommit FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.RemoteTransactionDUnitTest$8.call in VM 0 > running on Host 9acb6806d25d with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631) > at org.apache.geode.test.dunit.VM.invoke(VM.java:473) > at > org.apache.geode.internal.cache.RemoteTransactionDUnitTest.doBasicChecks(RemoteTransactionDUnitTest.java:590) > at > org.apache.geode.internal.cache.RemoteTransactionDUnitTest.testTXCreationAndCleanupAtCommit(RemoteTransactionDUnitTest.java:565) > Caused by: > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:87) > at org.junit.Assert.assertTrue(Assert.java:42) > at org.junit.Assert.assertNotNull(Assert.java:713) > at org.junit.Assert.assertNotNull(Assert.java:723) > at > org.apache.geode.internal.cache.RemoteTransactionDUnitTest$8.call(RemoteTransactionDUnitTest.java:595) > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.RemoteTransactionDUnitTest$2.call in VM 1 > running on Host 9acb6806d25d with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631) > at org.apache.geode.test.dunit.VM.invoke(VM.java:473) > at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:121) > at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:109) > at > org.apache.geode.internal.cache.RemoteTransactionDUnitTest.preTearDownCacheTestCase(RemoteTransactionDUnitTest.java:182) > Caused by: > java.lang.AssertionError: Event never occurred after 3 ms: > at org.junit.Assert.fail(Assert.java:89) > at > org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:144) > at > org.apache.geode.internal.cache.RemoteTransactionDUnitTest$2.call(RemoteTransactionDUnitTest.java:149) > 8838 tests completed, 1 failed, 458 skipped -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-7249) GfshInitFileIntegrationTest needs to be rewritten
[ https://issues.apache.org/jira/browse/GEODE-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478292#comment-17478292 ] Geode Integration commented on GEODE-7249: -- Seen in [integration-test-openjdk11 #104|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/integration-test-openjdk11/builds/104] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0792/test-results/integrationTest/1642535963/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0792/test-artifacts/1642535963/integrationtestfiles-openjdk11-1.15.0-build.0792.tgz]. > GfshInitFileIntegrationTest needs to be rewritten > - > > Key: GEODE-7249 > URL: https://issues.apache.org/jira/browse/GEODE-7249 > Project: Geode > Issue Type: Test > Components: gfsh, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > GfshInitFileIntegrationTest fails intermittently and currently uses > reflection to alter values of static variables in Gfsh. > It needs to be disabled in CI until someone has the time and desire to > rewrite this test. > Please refactor Gfsh to be testable instead of using reflection or PowerMock. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9712) Genericize All .NET Core Classes
[
https://issues.apache.org/jira/browse/GEODE-9712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478291#comment-17478291
]
ASF GitHub Bot commented on GEODE-9712:
---
mmartell commented on a change in pull request #909:
URL: https://github.com/apache/geode-native/pull/909#discussion_r787266693
##
File path: c-bindings/src/data_serializable_raw.cpp
##
@@ -0,0 +1,80 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+#include
+
+// C++ client public headers
+#include "geode/DataInput.hpp"
+#include "geode/DataOutput.hpp"
+#include "geode/internal/DataSerializablePrimitive.hpp"
+
+// C client public headers
+#include "data_serializable_raw.hpp"
+
+// C client private headers
+
+using apache::geode::client::DataInput;
+using apache::geode::client::DataOutput;
+
+namespace apache {
+namespace geode {
+namespace client {
+namespace internal {
+
+DataSerializableRaw::DataSerializableRaw(const int8_t* data, size_t size) {
Review comment:
Ideally, the C# layer would have access to the DataInput and DataOutput
buffers via the Region. However, this would likely require moving too much
buffer management code to C#. An alternative that might be worth consideration
is to have an interop buffer in the C++ heap (an std::vector), and give C# its
address. This could be created during the cache create and deleted when the
cache is closed. Always passing the length(s) of interop parameters would allow
growing the buffer as needed.
--
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
> Genericize All .NET Core Classes
>
>
> Key: GEODE-9712
> URL: https://issues.apache.org/jira/browse/GEODE-9712
> Project: Geode
> Issue Type: New Feature
> Components: native client
>Reporter: Michael Martell
>Assignee: Michael Martell
>Priority: Major
> Labels: pull-request-available
>
> We need to implement IRegion in .NET Core. This will require
> writing generic versions of RegionFactory, Region, and Cache.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9712) Genericize All .NET Core Classes
[ https://issues.apache.org/jira/browse/GEODE-9712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478282#comment-17478282 ] ASF GitHub Bot commented on GEODE-9712: --- mmartell commented on a change in pull request #909: URL: https://github.com/apache/geode-native/pull/909#discussion_r787248431 ## File path: c-bindings/include/geode/region.h ## @@ -40,18 +40,41 @@ APACHE_GEODE_C_EXPORT void apache_geode_Region_PutString( apache_geode_region_t* region, const char* key, const char* value); APACHE_GEODE_C_EXPORT void apache_geode_Region_PutByteArray( -apache_geode_region_t* region, const char* key, const char* value, size_t size); +apache_geode_region_t* region, const char* key, size_t keyLength, Review comment: I don't disagree. However, I'm thinking we should consider the single more powerful apache_geode_Region_Put (line 50), which includes lengths for both key and value, and do away with all other versions of the Put API. -- 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 > Genericize All .NET Core Classes > > > Key: GEODE-9712 > URL: https://issues.apache.org/jira/browse/GEODE-9712 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > > We need to implement IRegion in .NET Core. This will require > writing generic versions of RegionFactory, Region, and Cache. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9372) DistributionStats needs a stat for create sender time to help diagnose data replication spikes
[ https://issues.apache.org/jira/browse/GEODE-9372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-9372: Fix Version/s: 1.12.9 1.13.8 1.14.4 > DistributionStats needs a stat for create sender time to help diagnose data > replication spikes > -- > > Key: GEODE-9372 > URL: https://issues.apache.org/jira/browse/GEODE-9372 > Project: Geode > Issue Type: Improvement > Components: statistics >Reporter: Barrett Oglesby >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0 > > Attachments: > PartitionedRegionStats_sendReplicationTime_DistributionStats_sendersTO.gif > > > While debugging an issue with sendReplicationTime, we realized it was all due > to sender creation time. > A statistic for that time would have been very useful. > -- 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=17478255#comment-17478255
]
Geode Integration commented on GEODE-9890:
--
Seen on support/1.12 in [distributed-test-openjdk11
#29|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk11/builds/29]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.9-build.0338/test-results/distributedTest/1642534524/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.9-build.0338/test-artifacts/1642534524/distributedtestfiles-openjdk11-1.12.9-build.0338.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] [Updated] (GEODE-9976) Edit CODEOWNERS mappings for kirklund
[ https://issues.apache.org/jira/browse/GEODE-9976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9976: - Description: Edit CODEOWNERS mappings for kirklund (was: Edit CODEOWNERS mapping for kirklund) > Edit CODEOWNERS mappings for kirklund > - > > Key: GEODE-9976 > URL: https://issues.apache.org/jira/browse/GEODE-9976 > Project: Geode > Issue Type: Wish >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Edit CODEOWNERS mappings for kirklund -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9976) Edit CODEOWNERS mappings for kirklund
[ https://issues.apache.org/jira/browse/GEODE-9976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9976: - Summary: Edit CODEOWNERS mappings for kirklund (was: Edit CODEOWNERS mapping for kirklund) > Edit CODEOWNERS mappings for kirklund > - > > Key: GEODE-9976 > URL: https://issues.apache.org/jira/browse/GEODE-9976 > Project: Geode > Issue Type: Wish >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Edit CODEOWNERS mapping for kirklund -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9976) Edit CODEOWNERS mapping for kirklund
[ https://issues.apache.org/jira/browse/GEODE-9976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-9976: Assignee: Kirk Lund > Edit CODEOWNERS mapping for kirklund > > > Key: GEODE-9976 > URL: https://issues.apache.org/jira/browse/GEODE-9976 > Project: Geode > Issue Type: Wish >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Edit CODEOWNERS mapping for kirklund -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9976) Edit CODEOWNERS mapping for kirklund
Kirk Lund created GEODE-9976: Summary: Edit CODEOWNERS mapping for kirklund Key: GEODE-9976 URL: https://issues.apache.org/jira/browse/GEODE-9976 Project: Geode Issue Type: Wish Reporter: Kirk Lund Edit CODEOWNERS mapping for kirklund -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9907) Geode-for-redis example failed with JedisNoReachableClusterNodeException: No reachable node in cluster
[
https://issues.apache.org/jira/browse/GEODE-9907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478238#comment-17478238
]
Geode Integration commented on GEODE-9907:
--
Seen in [test-examples
#129|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-examples/jobs/test-examples/builds/129].
> Geode-for-redis example failed with JedisNoReachableClusterNodeException: No
> reachable node in cluster
> --
>
> Key: GEODE-9907
> URL: https://issues.apache.org/jira/browse/GEODE-9907
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Kristen
>Assignee: Eric Zoerner
>Priority: Major
> Labels: release-blocker
> Fix For: 1.15.0
>
>
>
> {code:java}
> > Task :geodeForRedis:run FAILED
> Exception in thread "main"
> redis.clients.jedis.exceptions.JedisNoReachableClusterNodeException: No
> reachable node in cluster
> at
> redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnection(JedisSlotBasedConnectionHandler.java:117)
> at
> redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnectionFromSlot(JedisSlotBasedConnectionHandler.java:139)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:118)
> at redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.zadd(JedisCluster.java:1106)
> at
> org.apache.geode_examples.geodeForRedis.Example.populateSortedSet(Example.java:53)
> at org.apache.geode_examples.geodeForRedis.Example.main(Example.java:30)
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':geodeForRedis:run'.
> > Process 'command '/usr/lib/jvm/bellsoft-java8-amd64/bin/java'' finished
> >with non-zero exit value 1
> {code}
>
> This might be related to [https://github.com/apache/geode-examples/pull/110]
> due to the location of the failure of the test
> org.apache.geode_examples.geodeForRedis.Example.main.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9972) remove 'wait overnight' step from release process
[ https://issues.apache.org/jira/browse/GEODE-9972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9972: -- Labels: pull-request-available (was: ) > remove 'wait overnight' step from release process > - > > Key: GEODE-9972 > URL: https://issues.apache.org/jira/browse/GEODE-9972 > Project: Geode > Issue Type: Improvement > Components: release >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > > now that maven central syncs within 1 hour and closer.cgi mirrors use the new > dlcdn which syncs within 15 minutes, we can eliminate the overnight step in > the release steps -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9787) Cascade deprecation of symbols to dependent symbols.
[
https://issues.apache.org/jira/browse/GEODE-9787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9787:
--
Labels: pull-request-available (was: )
> Cascade deprecation of symbols to dependent symbols.
>
>
> Key: GEODE-9787
> URL: https://issues.apache.org/jira/browse/GEODE-9787
> Project: Geode
> Issue Type: Task
>Reporter: Jacob Barrett
>Priority: Major
> Labels: pull-request-available
>
> When deprecated some symbols require that other symbols be modified to match
> types or or other changes. The original versions of these symbols should be
> deprecated in favor of the new. This is a long running ticket to collect all
> those changes.
> For example, when replacing deprecated usage of {{Statistics.getInt()}} with
> {{Statistics.getLong()}} a public API method may need to change to return the
> {{long}} value.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9974) CI: removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile FAILED
[ https://issues.apache.org/jira/browse/GEODE-9974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478230#comment-17478230 ] Geode Integration commented on GEODE-9974: -- Seen in [distributed-test-openjdk8 #601|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/601] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642216284/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642216284/distributedtestfiles-openjdk8-1.15.0-build.0789.tgz]. > CI: > removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile > FAILED > - > > Key: GEODE-9974 > URL: https://issues.apache.org/jira/browse/GEODE-9974 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Kristen >Priority: Major > Labels: needsTriage > > > Task :geode-wan:distributedTest > GatewayReceiverDUnitTest > > removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile > FAILED > 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-vm3.log' at line 673 > [fatal 2022/01/15 02:19:08.273 UTC > tid=88] Possible loss of quorum due to the loss of 1 cache processes: > [heavy-lifter-f3db8ae7-2766-5a80-a4c9-993976bf93f3(887047):49336] > --- > Found suspect string in 'dunit_suspect-vm3.log' at line 675 > [fatal 2022/01/15 02:19:09.275 UTC > tid=88] Membership service failure: Exiting due to possible network partition > event due to loss of 1 cache processes: > [heavy-lifter-f3db8ae7-2766-5a80-a4c9-993976bf93f3(887047):49336] > > org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException: > Exiting due to possible network partition event due to loss of 1 cache > processes: > [heavy-lifter-f3db8ae7-2766-5a80-a4c9-993976bf93f3(887047):49336] > at > org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1807) > at > org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1122) > at > org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1300(GMSJoinLeave.java:80) > at > org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2610) > at > org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2226) > at > org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2308) > at org.junit.Assert.fail(Assert.java:89) > at > org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:422) > at > org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:438) > at > org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:551) > at > org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.doTearDownDistributedTestCase(JUnit4DistributedTestCase.java:498) > at > org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:481) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61) > at
[jira] [Updated] (GEODE-9974) CI: removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile FAILED
[ https://issues.apache.org/jira/browse/GEODE-9974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9974: - Labels: needsTriage (was: ) > CI: > removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile > FAILED > - > > Key: GEODE-9974 > URL: https://issues.apache.org/jira/browse/GEODE-9974 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Kristen >Priority: Major > Labels: needsTriage > > > Task :geode-wan:distributedTest > GatewayReceiverDUnitTest > > removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile > FAILED > 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-vm3.log' at line 673 > [fatal 2022/01/15 02:19:08.273 UTC > tid=88] Possible loss of quorum due to the loss of 1 cache processes: > [heavy-lifter-f3db8ae7-2766-5a80-a4c9-993976bf93f3(887047):49336] > --- > Found suspect string in 'dunit_suspect-vm3.log' at line 675 > [fatal 2022/01/15 02:19:09.275 UTC > tid=88] Membership service failure: Exiting due to possible network partition > event due to loss of 1 cache processes: > [heavy-lifter-f3db8ae7-2766-5a80-a4c9-993976bf93f3(887047):49336] > > org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException: > Exiting due to possible network partition event due to loss of 1 cache > processes: > [heavy-lifter-f3db8ae7-2766-5a80-a4c9-993976bf93f3(887047):49336] > at > org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1807) > at > org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1122) > at > org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1300(GMSJoinLeave.java:80) > at > org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2610) > at > org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2226) > at > org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2308) > at org.junit.Assert.fail(Assert.java:89) > at > org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:422) > at > org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:438) > at > org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:551) > at > org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.doTearDownDistributedTestCase(JUnit4DistributedTestCase.java:498) > at > org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:481) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) > at
[jira] [Created] (GEODE-9974) CI: removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile FAILED
Kristen created GEODE-9974: -- Summary: CI: removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile FAILED Key: GEODE-9974 URL: https://issues.apache.org/jira/browse/GEODE-9974 Project: Geode Issue Type: Bug Affects Versions: 1.15.0 Reporter: Kristen > Task :geode-wan:distributedTest GatewayReceiverDUnitTest > removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile FAILED 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-vm3.log' at line 673 [fatal 2022/01/15 02:19:08.273 UTC tid=88] Possible loss of quorum due to the loss of 1 cache processes: [heavy-lifter-f3db8ae7-2766-5a80-a4c9-993976bf93f3(887047):49336] --- Found suspect string in 'dunit_suspect-vm3.log' at line 675 [fatal 2022/01/15 02:19:09.275 UTC tid=88] Membership service failure: Exiting due to possible network partition event due to loss of 1 cache processes: [heavy-lifter-f3db8ae7-2766-5a80-a4c9-993976bf93f3(887047):49336] org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException: Exiting due to possible network partition event due to loss of 1 cache processes: [heavy-lifter-f3db8ae7-2766-5a80-a4c9-993976bf93f3(887047):49336] at org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1807) at org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1122) at org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1300(GMSJoinLeave.java:80) at org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2610) at org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2226) at org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2308) at org.junit.Assert.fail(Assert.java:89) at org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:422) at org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:438) at org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:551) at org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.doTearDownDistributedTestCase(JUnit4DistributedTestCase.java:498) at org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:481) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) at org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at
[jira] [Updated] (GEODE-9964) ExplicitMoveDirector incorrectly compares Member with InternalDistributedMember.
[
https://issues.apache.org/jira/browse/GEODE-9964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-9964:
-
Labels: (was: needsTriage)
Jake mentioned that this likely has been broken for a very long time. So I am
removing this as an issue needing triage. Still needs to get addressed.
> ExplicitMoveDirector incorrectly compares Member with
> InternalDistributedMember.
>
>
> Key: GEODE-9964
> URL: https://issues.apache.org/jira/browse/GEODE-9964
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.14.2, 1.15.0
>Reporter: Jacob Barrett
>Priority: Major
>
> {{ExplicitMoveDirector}} incorrectly compares {{Member}} with
> {{InternalDistributedMember}} due use of raw types rather than generics. It
> is also likely there is either no testing for this failure case or the test
> is passing for the wrong reasons.
> See
> [here|https://github.com/apache/geode/blob/2b032440eb9d0f3c68a94602289cc41435c68fad/geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/rebalance/ExplicitMoveDirector.java#L93]
> See
> [here|https://github.com/apache/geode/blob/2b032440eb9d0f3c68a94602289cc41435c68fad/geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/rebalance/ExplicitMoveDirector.java#L99]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9969) The region name starting with underscore lead to missing disk store after restart
[
https://issues.apache.org/jira/browse/GEODE-9969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-9969:
-
Labels: (was: needsTriage)
Removing needsTriage label. This issue has been around for a while and
shouldn't hold up any releases. We should address it though!
> The region name starting with underscore lead to missing disk store after
> restart
> -
>
> Key: GEODE-9969
> URL: https://issues.apache.org/jira/browse/GEODE-9969
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.12.8, 1.13.6, 1.14.2, 1.15.0
>Reporter: Mario Kevo
>Assignee: Mario Kevo
>Priority: Major
>
> The problem is when using the region with a name starting with an
> underscore(allowed by documentation
> [region_naming|https://geode.apache.org/docs/guide/114/basic_config/data_regions/region_naming.html]).
> If we stop one of the members and then rename the working dir(include disk
> store dir) to some new name and start the server with the name like renamed
> working dir, it will lead that we have the same disk-store-id in the listed
> disk-stores and in the missing disk store.
> This happens only if we are using the region with an underscore at the
> beginning.
> Steps to reproduce:
> Run locator and 4 servers, create region with name starting by underscore
> # start locator --name=locator
> # start server --name=server1 --server-port=40401
> # start server --name=server2 --server-port=40402
> # start server --name=server3 --server-port=40403
> # start server --name=server4 --server-port=40404
> # create region --name=_test-region --type=PARTITION_REDUNDANT_PERSISTENT
> --redundant-copies=1 --total-num-buckets=10 --enable-synchronous-disk=false
> # query --query="select * from /_test-region"
> From another terminal (Kill server and rename working dir)
> # kill -9 $(cat server4/vf.gf.server.pid)
> # mv server4/ server5
> {code:java}
> gfsh>list disk-stores
> Member Name | Member Id | Disk Store Name | Disk
> Store ID
> --- | -- | --- |
>
> server1 | 192.168.0.145(server1:16916):41001 | DEFAULT |
> d5d17b43-4a06-408b-917f-08e5b2533ebe
> server2 | 192.168.0.145(server2:17004):41002 | DEFAULT |
> 31d47cb4-718e-4b58-bde3-ae15b4657910
> server3 | 192.168.0.145(server3:17094):41003 | DEFAULT |
> f12850c6-a73b-443e-9ee0-87f0819ae6bc
> server5 | 192.168.0.145(server5:17428):41004 | DEFAULT |
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74
> gfsh>show missing-disk-stores
> Missing Disk Stores
> Disk Store ID | Host | Directory
> | - |
>
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74 | 192.168.0.145 |
> /home/mkevo/apache-geode-1.15.0-build.0/bin/server4/.
> No missing colocated region found
> {code}
> Start a new server with a name like you rename your working dir from the
> restarted server.
> # start server --name=server5 --server-port=40405
> Now we have the following output:
> {code:java}
> gfsh>list disk-stores
> Member Name | Member Id| Disk Store Name | Disk
> Store ID
> --- | -- | --- |
>
> server1 | 192.168.0.145(server1:16916):41001 | DEFAULT |
> d5d17b43-4a06-408b-917f-08e5b2533ebe
> server2 | 192.168.0.145(server2:17004):41002 | DEFAULT |
> 31d47cb4-718e-4b58-bde3-ae15b4657910
> server3 | 192.168.0.145(server3:17094):41003 | DEFAULT |
> f12850c6-a73b-443e-9ee0-87f0819ae6bc
> server5 | 192.168.0.145(server5:17428):41004 | DEFAULT |
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74
> gfsh>show missing-disk-stores
> Missing Disk Stores
>Disk Store ID | Host | Directory
> | - |
>
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74 | 192.168.0.145 |
> /home/mkevo/apache-geode-1.15.0-build.0/bin/server4/.
> No missing colocated region found
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9712) Genericize All .NET Core Classes
[
https://issues.apache.org/jira/browse/GEODE-9712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478226#comment-17478226
]
ASF GitHub Bot commented on GEODE-9712:
---
pivotal-jbarrett commented on a change in pull request #909:
URL: https://github.com/apache/geode-native/pull/909#discussion_r787172287
##
File path: c-bindings/src/data_serializable_raw.cpp
##
@@ -0,0 +1,80 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+#include
+
+// C++ client public headers
+#include "geode/DataInput.hpp"
+#include "geode/DataOutput.hpp"
+#include "geode/internal/DataSerializablePrimitive.hpp"
+
+// C client public headers
+#include "data_serializable_raw.hpp"
+
+// C client private headers
+
+using apache::geode::client::DataInput;
+using apache::geode::client::DataOutput;
+
+namespace apache {
+namespace geode {
+namespace client {
+namespace internal {
+
+DataSerializableRaw::DataSerializableRaw(const int8_t* data, size_t size) {
+ bytes_.reserve(size);
+ std::copy(data, data + size, std::back_inserter(bytes_));
+}
+
+std::shared_ptr DataSerializableRaw::create(
+const int8_t* data, size_t size) {
+ return std::make_shared(data, size);
+}
+
+void DataSerializableRaw::toData(DataOutput& dataOutput) const {
+ dataOutput.writeBytesOnly(bytes_.data() + dsCodeSize_,
+bytes_.size() - dsCodeSize_);
+}
+
+void DataSerializableRaw::fromData(DataInput& dataInput) {
+ dataInput.readBytesOnly(bytes_.data() + dsCodeSize_,
+ bytes_.size() - dsCodeSize_);
+}
+
+DSCode DataSerializableRaw::getDsCode() const {
+ return static_cast(bytes_[0]);
+}
+
+bool DataSerializableRaw::operator==(const CacheableKey& other) const {
+ if (auto otherKey = dynamic_cast()) {
+return bytes_ == otherKey->bytes_;
+ }
+
+ return false;
+}
+
+int32_t DataSerializableRaw::hashcode() const {
+ if (hashCode_ == 0) {
+hashCode_ = internal::geode_hash>{}(bytes_);
Review comment:
This is going to result in a hash on the client that is not consistent
with the hash on the server. The hash value needs to come from the
pre-serialized form of the object being serialized here. This will result in
sub-optimal put operations.
##
File path: c-bindings/src/data_serializable_raw.cpp
##
@@ -0,0 +1,80 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+#include
+
+// C++ client public headers
+#include "geode/DataInput.hpp"
+#include "geode/DataOutput.hpp"
+#include "geode/internal/DataSerializablePrimitive.hpp"
+
+// C client public headers
+#include "data_serializable_raw.hpp"
+
+// C client private headers
+
+using apache::geode::client::DataInput;
+using apache::geode::client::DataOutput;
+
+namespace apache {
+namespace geode {
+namespace client {
+namespace internal {
+
+DataSerializableRaw::DataSerializableRaw(const int8_t* data, size_t size) {
Review comment:
Any way to use `std::vector`? In other places where we needed arrays of
bytes we have used `std::vector` to encapsulate the length and lifecycle
management of the array. While in this method the `const` makes it very clear
that the caller is the owner often times it isn't so clear.
##
File path: c-bindings/src/data_serializable_raw.hpp
##
@@ -0,0 +1,53 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See
[jira] [Updated] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9973: - Labels: needsTriage (was: ) > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Priority: Major > Labels: needsTriage > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
Alberto Gomez created GEODE-9973: Summary: Documentation: socket-lease-time is not used to return sockets to a pool but to close them Key: GEODE-9973 URL: https://issues.apache.org/jira/browse/GEODE-9973 Project: Geode Issue Type: Bug Components: docs Reporter: Alberto Gomez The "Making sure you have enough sockets" Geode documentation section says the following about socket-lease-time (check underlined sentence): Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use the socket-lease-time to make sure that no socket sits idle for too long. +When a socket that belongs to an individual thread remains unused for this time period, the system automatically returns it to the pool.+ The next time the thread needs a socket, it creates a new socket. Actually, the system automatically closes the connection in the situation described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9785) CI Failure: RedundancyLevelPart2DUnitTest.testRedundancySpecifiedEPFails FAILED
[
https://issues.apache.org/jira/browse/GEODE-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478221#comment-17478221
]
Geode Integration commented on GEODE-9785:
--
Seen in [distributed-test-openjdk8
#648|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/648]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642247272/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642247272/distributedtestfiles-openjdk8-1.15.0-build.0789.tgz].
> CI Failure: RedundancyLevelPart2DUnitTest.testRedundancySpecifiedEPFails
> FAILED
> ---
>
> Key: GEODE-9785
> URL: https://issues.apache.org/jira/browse/GEODE-9785
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Eric Shu
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> {noformat}
> org.junit.ComparisonFailure: expected:<[2]> but was:<[0]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart2DUnitTest.testRedundancySpecifiedEPFails(RedundancyLevelPart2DUnitTest.java:215)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> 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.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> 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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
>
[jira] [Commented] (GEODE-9372) DistributionStats needs a stat for create sender time to help diagnose data replication spikes
[ https://issues.apache.org/jira/browse/GEODE-9372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478217#comment-17478217 ] ASF subversion and git services commented on GEODE-9372: Commit 16ecb0121d98723a19dcb8d082ec1c41fcaf2f85 in geode's branch refs/heads/support/1.12 from Barry Oglesby [ https://gitbox.apache.org/repos/asf?p=geode.git;h=16ecb01 ] GEODE-9372: Added createSenderTime and createSenderInProgress stats (#6608) (cherry picked from commit f0e6e0d9c2b299e31fd20dea47703b019fc66f31) (cherry picked from commit 5644b85c65e136d65cfe92f8dd3888a148cd925c) (cherry picked from commit aa106eee0d33767d57279855873d592b73b19fc7) > DistributionStats needs a stat for create sender time to help diagnose data > replication spikes > -- > > Key: GEODE-9372 > URL: https://issues.apache.org/jira/browse/GEODE-9372 > Project: Geode > Issue Type: Improvement > Components: statistics >Reporter: Barrett Oglesby >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > Attachments: > PartitionedRegionStats_sendReplicationTime_DistributionStats_sendersTO.gif > > > While debugging an issue with sendReplicationTime, we realized it was all due > to sender creation time. > A statistic for that time would have been very useful. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9372) DistributionStats needs a stat for create sender time to help diagnose data replication spikes
[ https://issues.apache.org/jira/browse/GEODE-9372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478212#comment-17478212 ] ASF subversion and git services commented on GEODE-9372: Commit aa106eee0d33767d57279855873d592b73b19fc7 in geode's branch refs/heads/support/1.13 from Barry Oglesby [ https://gitbox.apache.org/repos/asf?p=geode.git;h=aa106ee ] GEODE-9372: Added createSenderTime and createSenderInProgress stats (#6608) (cherry picked from commit f0e6e0d9c2b299e31fd20dea47703b019fc66f31) (cherry picked from commit 5644b85c65e136d65cfe92f8dd3888a148cd925c) > DistributionStats needs a stat for create sender time to help diagnose data > replication spikes > -- > > Key: GEODE-9372 > URL: https://issues.apache.org/jira/browse/GEODE-9372 > Project: Geode > Issue Type: Improvement > Components: statistics >Reporter: Barrett Oglesby >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > Attachments: > PartitionedRegionStats_sendReplicationTime_DistributionStats_sendersTO.gif > > > While debugging an issue with sendReplicationTime, we realized it was all due > to sender creation time. > A statistic for that time would have been very useful. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9372) DistributionStats needs a stat for create sender time to help diagnose data replication spikes
[ https://issues.apache.org/jira/browse/GEODE-9372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478209#comment-17478209 ] ASF subversion and git services commented on GEODE-9372: Commit 5644b85c65e136d65cfe92f8dd3888a148cd925c in geode's branch refs/heads/support/1.14 from Barry Oglesby [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5644b85 ] GEODE-9372: Added createSenderTime and createSenderInProgress stats (#6608) (cherry picked from commit f0e6e0d9c2b299e31fd20dea47703b019fc66f31) > DistributionStats needs a stat for create sender time to help diagnose data > replication spikes > -- > > Key: GEODE-9372 > URL: https://issues.apache.org/jira/browse/GEODE-9372 > Project: Geode > Issue Type: Improvement > Components: statistics >Reporter: Barrett Oglesby >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > Attachments: > PartitionedRegionStats_sendReplicationTime_DistributionStats_sendersTO.gif > > > While debugging an issue with sendReplicationTime, we realized it was all due > to sender creation time. > A statistic for that time would have been very useful. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (GEODE-9571) Radish REMRANGE* DUnit tests may fail in stress-test
[
https://issues.apache.org/jira/browse/GEODE-9571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristen reopened GEODE-9571:
> Radish REMRANGE* DUnit tests may fail in stress-test
>
>
> Key: GEODE-9571
> URL: https://issues.apache.org/jira/browse/GEODE-9571
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Fix For: 1.15.0
>
>
> Failures were seen in pre-checkin stress-new-test for
> ZRemRangeByScoreDUnitTest, ZRemRangeByRankDUnitTest and
> ZRemRangeByLexDUnitTest, all of which use similar test methods. The failures
> were seen in the *RemovesMembersFromSortedSetAfterPrimaryShutsDown() test and
> the *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() test in a few
> different runs.
> The failures in *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() were
> seen when the tests for both ZRemRangeByScoreDUnitTest and
> ZRemRangeByRankDUnitTest were being run at the same time due to both classes
> being changed. It's possibly relevant that the difference in the second
> assertion (expected:<[999]L> but was:<[498]L>) is exactly the incorrect
> number of members removed in the first assertion (expected:<[499]L> but
> was:<[501]L>):
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[499]L> but was:<[501]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByScoreDUnitTest.java:159)
> Caused by:
> org.junit.ComparisonFailure: expected:<[499]L> but was:<[501]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.removeAllButFirstEntry(ZRemRangeByScoreDUnitTest.java:213)
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest >
> zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[999]L> but was:<[498]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByRankDUnitTest.java:144)
> Caused by:
> org.junit.ComparisonFailure: expected:<[999]L> but was:<[498]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.removeAllButFirstEntry(ZRemRangeByRankDUnitTest.java:206)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-results/repeatTest/1630442126/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-artifacts/1630442126/stressnewtestfiles-geode-pr-6803.tgz]
> The same failure was also seen in this second run, along with a failure in
> ZRemRangeByScoreDUnitTest >
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown due to the
> remove command not finding any members to remove:
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown FAILED
> org.junit.ComparisonFailure: expected:<[50]0L> but was:<[]0L>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
>
[jira] [Commented] (GEODE-9712) Genericize All .NET Core Classes
[ https://issues.apache.org/jira/browse/GEODE-9712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478191#comment-17478191 ] ASF GitHub Bot commented on GEODE-9712: --- lgtm-com[bot] commented on pull request #909: URL: https://github.com/apache/geode-native/pull/909#issuecomment-1015816463 This pull request **introduces 10 alerts** when merging 0197951911cd3b86f556920fbb14c2672f8d1c52 into 0550b0ff4d4040500cc52baef9297c01691011a8 - [view on LGTM.com](https://lgtm.com/projects/g/apache/geode-native/rev/pr-a6b3342ad72ded4afd2a579216a6799d5c6120b6) **new alerts:** * 7 for Useless assignment to local variable * 2 for Empty branch of conditional, or empty loop body * 1 for Dereferenced variable may be null -- 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 > Genericize All .NET Core Classes > > > Key: GEODE-9712 > URL: https://issues.apache.org/jira/browse/GEODE-9712 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > > We need to implement IRegion in .NET Core. This will require > writing generic versions of RegionFactory, Region, and Cache. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9712) Genericize All .NET Core Classes
[ https://issues.apache.org/jira/browse/GEODE-9712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478171#comment-17478171 ] ASF GitHub Bot commented on GEODE-9712: --- pivotal-jbarrett commented on a change in pull request #909: URL: https://github.com/apache/geode-native/pull/909#discussion_r787112789 ## File path: c-bindings/include/geode/region.h ## @@ -40,18 +40,41 @@ APACHE_GEODE_C_EXPORT void apache_geode_Region_PutString( apache_geode_region_t* region, const char* key, const char* value); APACHE_GEODE_C_EXPORT void apache_geode_Region_PutByteArray( -apache_geode_region_t* region, const char* key, const char* value, size_t size); +apache_geode_region_t* region, const char* key, size_t keyLength, Review comment: We should really require length parameters for all array pointers, it's not safe to rely on `NULL` termination. -- 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 > Genericize All .NET Core Classes > > > Key: GEODE-9712 > URL: https://issues.apache.org/jira/browse/GEODE-9712 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > > We need to implement IRegion in .NET Core. This will require > writing generic versions of RegionFactory, Region, and Cache. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9972) remove 'wait overnight' step from release process
Owen Nichols created GEODE-9972: --- Summary: remove 'wait overnight' step from release process Key: GEODE-9972 URL: https://issues.apache.org/jira/browse/GEODE-9972 Project: Geode Issue Type: Improvement Components: release Reporter: Owen Nichols now that maven central syncs within 1 hour and closer.cgi mirrors use the new dlcdn which syncs within 15 minutes, we can eliminate the overnight step in the release steps -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9528:
Fix Version/s: 1.14.4
(was: 1.14.3)
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0
>
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9528:
Fix Version/s: 1.13.8
(was: 1.13.7)
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.9, 1.13.8, 1.14.3, 1.15.0
>
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9971) Fix ping distributed test case after switching from docker-compose to testcontainers
[ https://issues.apache.org/jira/browse/GEODE-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9971: -- Labels: needsTriage pull-request-available (was: needsTriage) > Fix ping distributed test case after switching from docker-compose to > testcontainers > > > Key: GEODE-9971 > URL: https://issues.apache.org/jira/browse/GEODE-9971 > Project: Geode > Issue Type: Bug >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: needsTriage, pull-request-available > > Due to the changes done by GEODE-9156 to switch from docker-compose to > testcontainers test case > testPingsToReceiversWithSamePortAndHostnameForSendersReachTheRightReceivers > from > SeveralGatewayReceiversWithSamePortAndHostnameForSendersTest was not working > properly even though it was failing. > The test must be enhanced to check that entries are wan replicated to the > other site (for example by checking that entries added locally do not leave > events in the gateway sender queues). > After that, the code of the test must be fixed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9971) Fix ping distributed test case after switching from docker-compose to testcontainers
[ https://issues.apache.org/jira/browse/GEODE-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9971: - Labels: needsTriage (was: ) > Fix ping distributed test case after switching from docker-compose to > testcontainers > > > Key: GEODE-9971 > URL: https://issues.apache.org/jira/browse/GEODE-9971 > Project: Geode > Issue Type: Bug >Reporter: Alberto Gomez >Priority: Major > Labels: needsTriage > > Due to the changes done by GEODE-9156 to switch from docker-compose to > testcontainers test case > testPingsToReceiversWithSamePortAndHostnameForSendersReachTheRightReceivers > from > SeveralGatewayReceiversWithSamePortAndHostnameForSendersTest was not working > properly even though it was failing. > The test must be enhanced to check that entries are wan replicated to the > other site (for example by checking that entries added locally do not leave > events in the gateway sender queues). > After that, the code of the test must be fixed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9971) Fix ping distributed test case after switching from docker-compose to testcontainers
Alberto Gomez created GEODE-9971: Summary: Fix ping distributed test case after switching from docker-compose to testcontainers Key: GEODE-9971 URL: https://issues.apache.org/jira/browse/GEODE-9971 Project: Geode Issue Type: Bug Reporter: Alberto Gomez Due to the changes done by GEODE-9156 to switch from docker-compose to testcontainers test case testPingsToReceiversWithSamePortAndHostnameForSendersReachTheRightReceivers from SeveralGatewayReceiversWithSamePortAndHostnameForSendersTest was not working properly even though it was failing. The test must be enhanced to check that entries are wan replicated to the other site (for example by checking that entries added locally do not leave events in the gateway sender queues). After that, the code of the test must be fixed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9970) Decouple Redis Module From Geode Core
Wayne created GEODE-9970: Summary: Decouple Redis Module From Geode Core Key: GEODE-9970 URL: https://issues.apache.org/jira/browse/GEODE-9970 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne Decouple the Redis module from Geode Core to allow for the Redis module to evolve and be released independently from Geode Core. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9971) Fix ping distributed test case after switching from docker-compose to testcontainers
[ https://issues.apache.org/jira/browse/GEODE-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Gomez reassigned GEODE-9971: Assignee: Alberto Gomez > Fix ping distributed test case after switching from docker-compose to > testcontainers > > > Key: GEODE-9971 > URL: https://issues.apache.org/jira/browse/GEODE-9971 > Project: Geode > Issue Type: Bug >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: needsTriage > > Due to the changes done by GEODE-9156 to switch from docker-compose to > testcontainers test case > testPingsToReceiversWithSamePortAndHostnameForSendersReachTheRightReceivers > from > SeveralGatewayReceiversWithSamePortAndHostnameForSendersTest was not working > properly even though it was failing. > The test must be enhanced to check that entries are wan replicated to the > other site (for example by checking that entries added locally do not leave > events in the gateway sender queues). > After that, the code of the test must be fixed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-1891) Potential region inconsistency with bulk operations and non-replicant regions
[ https://issues.apache.org/jira/browse/GEODE-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478150#comment-17478150 ] Geode Integration commented on GEODE-1891: -- Seen on support/1.12 in [distributed-test-openjdk8 #26|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/26] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.9-build.0336/test-results/distributedTest/1642215117/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.9-build.0336/test-artifacts/1642215117/distributedtestfiles-openjdk8-1.12.9-build.0336.tgz]. > Potential region inconsistency with bulk operations and non-replicant regions > - > > Key: GEODE-1891 > URL: https://issues.apache.org/jira/browse/GEODE-1891 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Scott Jewell >Priority: Major > > There is a possible region inconsistency when performing bulk operations with > non-replicant regions. > The LocalRegion.lockRVVForBulkOp and unlockRVVForBulkOp methods > only take cache modification lock if region attribute withReplication() is > true. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9758) Configure locator serialization filtering by default on Java 8
[ https://issues.apache.org/jira/browse/GEODE-9758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478140#comment-17478140 ] ASF subversion and git services commented on GEODE-9758: Commit 7978abf34707d11da45cff0b7cb7445f18d21438 in geode's branch refs/heads/develop from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7978abf ] GEODE-9758: Add internal serial filter API (#7217) GEODE-9758: Add internal serial filter API #7217 Expand ObjectInputStreamFilterWrapper to be an internal API which supports all of Geode's uses of Java's ObjectInputFilter. Introduce a new system property, geode.enableGlobalSerialFilter, to enable a process-wide filter with all serializable Geode classes on the classpath and the value of serializable-object-filter accept-listed. To enable the process-wide filter with GFSH start commands, add: * --J=-Dgeode.enableGlobalSerialFilter=true Functional Capabilities The internal API lives in geode-serialization and works on OpenJDK based JREs providing a facade for Java's ObjectInputFilter in Java 8 and Java 9 or greater using reflection. The API provides the following capabilities: * creating an ObjectInputFilter * setting an ObjectInputFilter on an ObjectInputStream * getting an ObjectInputFilter from a ObjectInputStream * setting a process-wide ObjectInputFilter * getting a process-wide ObjectInputFilter Design Notes The API defines the following primary interface types: * factory interfaces for creating instances of types within the API * filter interfaces to split out single ops from Java's ObjectInputFilter * configuration interfaces for handling system properties, logging, and config validation The concrete classes in the API receive parameters injected via a constructor for any collaborators that are not specified by the interfaces. This is intentional even when the instance is only used once before de-referencing it. All collaborators that are defined in the interface are passed in as parameters to the implementing method; all others are passed in via the constructor and stored as fields. > Configure locator serialization filtering by default on Java 8 > -- > > Key: GEODE-9758 > URL: https://issues.apache.org/jira/browse/GEODE-9758 > Project: Geode > Issue Type: Improvement >Affects Versions: 1.12.7 >Reporter: Jianxia Chen >Assignee: Jianxia Chen >Priority: Major > Labels: pull-request-available > > When Geode locator is running on Java 8 JVM, the serialization filter should > be configured by default to accept only JDK classes and Geode classes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[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=17478134#comment-17478134
]
Geode Integration commented on GEODE-8616:
--
Seen in [distributed-test-openjdk8
#607|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/607]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642215852/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642215852/distributedtestfiles-openjdk8-1.15.0-build.0789.tgz].
> ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException fails with
> ServerConnectivityException : Pool unexpected socket timed out on client
> --
>
> Key: GEODE-8616
> URL: https://issues.apache.org/jira/browse/GEODE-8616
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.1, 1.13.7, 1.14.3, 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: GeodeOperationAPI, flaky-test
> Attachments: hansonm-findfailures-11-10-2021-23-52-38-logs.tgz,
> hansonm-findfailures-11-10-2021-23-52-45-logs.tgz
>
>
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$177/0x000100b52040.run
> in VM 2 running on Host c1346ab7b3e3 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.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:117)
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Pool
> unexpected socket timed out on client connection=Pooled Connection to
> c1346ab7b3e3:35437: Connection[DESTROYED]). Server unreachable: could not
> connect after 1 attempts
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:774)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:116)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2795)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1472)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1445)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:196)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1382)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1321)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1306)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:436)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:120)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-results/distributedTest/1601514101/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-artifacts/1601514101/distributedtestfiles-OpenJDK11-1.12.1-build.0106.tgz
> This is a flaky failure.
--
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=17478128#comment-17478128
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#617|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/617]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642223326/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642223326/distributedtestfiles-openjdk8-1.15.0-build.0789.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-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=17478127#comment-17478127
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#622|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/622]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642230976/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642230976/distributedtestfiles-openjdk8-1.15.0-build.0789.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-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=17478126#comment-17478126
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#629|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/629]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642231907/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642231907/distributedtestfiles-openjdk8-1.15.0-build.0789.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-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=17478125#comment-17478125
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#652|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/652]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642254028/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642254028/distributedtestfiles-openjdk8-1.15.0-build.0789.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-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=17478124#comment-17478124
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#662|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/662]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642262504/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642262504/distributedtestfiles-openjdk8-1.15.0-build.0789.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] [Reopened] (GEODE-9716) ZRemRangeByScoreDUnitTest.zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-9716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristen reopened GEODE-9716:
> ZRemRangeByScoreDUnitTest.zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown
> fails intermittently
> ---
>
> Key: GEODE-9716
> URL: https://issues.apache.org/jira/browse/GEODE-9716
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Assignee: Ray Ingles
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown fails rarely
> with the following stack trace:
> {code:java}
> ZRemRangeByScoreDUnitTest >
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown FAILED
> org.opentest4j.AssertionFailedError:
> expected: 500L
> but was: 0L
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreWithRetries(ZRemRangeByScoreDUnitTest.java:253)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.doZRemRangeByScoreWithRetries(ZRemRangeByScoreDUnitTest.java:237)
> {code}
--
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=17478118#comment-17478118
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#674|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/674]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642270697/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642270697/distributedtestfiles-openjdk8-1.15.0-build.0789.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-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=17478117#comment-17478117
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#687|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/687]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642278875/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642278875/distributedtestfiles-openjdk8-1.15.0-build.0789.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-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=17478114#comment-17478114
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#689|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/689]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642279284/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642279284/distributedtestfiles-openjdk8-1.15.0-build.0789.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] (GEODE-9571) Radish REMRANGE* DUnit tests may fail in stress-test
[ https://issues.apache.org/jira/browse/GEODE-9571 ]
Kristen deleted comment on GEODE-9571:
was (Author: JIRAUSER280260):
Duplicate of
https://issues.apache.org/jira/browse/GEODE-9716?jql=text%20~%20%22ZRemRangeByScoreDUnitTest%22
> Radish REMRANGE* DUnit tests may fail in stress-test
>
>
> Key: GEODE-9571
> URL: https://issues.apache.org/jira/browse/GEODE-9571
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Fix For: 1.15.0
>
>
> Failures were seen in pre-checkin stress-new-test for
> ZRemRangeByScoreDUnitTest, ZRemRangeByRankDUnitTest and
> ZRemRangeByLexDUnitTest, all of which use similar test methods. The failures
> were seen in the *RemovesMembersFromSortedSetAfterPrimaryShutsDown() test and
> the *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() test in a few
> different runs.
> The failures in *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() were
> seen when the tests for both ZRemRangeByScoreDUnitTest and
> ZRemRangeByRankDUnitTest were being run at the same time due to both classes
> being changed. It's possibly relevant that the difference in the second
> assertion (expected:<[999]L> but was:<[498]L>) is exactly the incorrect
> number of members removed in the first assertion (expected:<[499]L> but
> was:<[501]L>):
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[499]L> but was:<[501]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByScoreDUnitTest.java:159)
> Caused by:
> org.junit.ComparisonFailure: expected:<[499]L> but was:<[501]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.removeAllButFirstEntry(ZRemRangeByScoreDUnitTest.java:213)
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest >
> zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[999]L> but was:<[498]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByRankDUnitTest.java:144)
> Caused by:
> org.junit.ComparisonFailure: expected:<[999]L> but was:<[498]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.removeAllButFirstEntry(ZRemRangeByRankDUnitTest.java:206)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-results/repeatTest/1630442126/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-artifacts/1630442126/stressnewtestfiles-geode-pr-6803.tgz]
> The same failure was also seen in this second run, along with a failure in
> ZRemRangeByScoreDUnitTest >
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown due to the
> remove command not finding any members to remove:
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown FAILED
> org.junit.ComparisonFailure: expected:<[50]0L> but was:<[]0L>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>
[jira] [Resolved] (GEODE-9571) Radish REMRANGE* DUnit tests may fail in stress-test
[
https://issues.apache.org/jira/browse/GEODE-9571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristen resolved GEODE-9571.
Resolution: Duplicate
> Radish REMRANGE* DUnit tests may fail in stress-test
>
>
> Key: GEODE-9571
> URL: https://issues.apache.org/jira/browse/GEODE-9571
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Fix For: 1.15.0
>
>
> Failures were seen in pre-checkin stress-new-test for
> ZRemRangeByScoreDUnitTest, ZRemRangeByRankDUnitTest and
> ZRemRangeByLexDUnitTest, all of which use similar test methods. The failures
> were seen in the *RemovesMembersFromSortedSetAfterPrimaryShutsDown() test and
> the *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() test in a few
> different runs.
> The failures in *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() were
> seen when the tests for both ZRemRangeByScoreDUnitTest and
> ZRemRangeByRankDUnitTest were being run at the same time due to both classes
> being changed. It's possibly relevant that the difference in the second
> assertion (expected:<[999]L> but was:<[498]L>) is exactly the incorrect
> number of members removed in the first assertion (expected:<[499]L> but
> was:<[501]L>):
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[499]L> but was:<[501]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByScoreDUnitTest.java:159)
> Caused by:
> org.junit.ComparisonFailure: expected:<[499]L> but was:<[501]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.removeAllButFirstEntry(ZRemRangeByScoreDUnitTest.java:213)
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest >
> zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[999]L> but was:<[498]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByRankDUnitTest.java:144)
> Caused by:
> org.junit.ComparisonFailure: expected:<[999]L> but was:<[498]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.removeAllButFirstEntry(ZRemRangeByRankDUnitTest.java:206)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-results/repeatTest/1630442126/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-artifacts/1630442126/stressnewtestfiles-geode-pr-6803.tgz]
> The same failure was also seen in this second run, along with a failure in
> ZRemRangeByScoreDUnitTest >
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown due to the
> remove command not finding any members to remove:
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown FAILED
> org.junit.ComparisonFailure: expected:<[50]0L> but was:<[]0L>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
>
[jira] [Resolved] (GEODE-9571) Radish REMRANGE* DUnit tests may fail in stress-test
[
https://issues.apache.org/jira/browse/GEODE-9571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristen resolved GEODE-9571.
Fix Version/s: 1.15.0
Resolution: Duplicate
> Radish REMRANGE* DUnit tests may fail in stress-test
>
>
> Key: GEODE-9571
> URL: https://issues.apache.org/jira/browse/GEODE-9571
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Fix For: 1.15.0
>
>
> Failures were seen in pre-checkin stress-new-test for
> ZRemRangeByScoreDUnitTest, ZRemRangeByRankDUnitTest and
> ZRemRangeByLexDUnitTest, all of which use similar test methods. The failures
> were seen in the *RemovesMembersFromSortedSetAfterPrimaryShutsDown() test and
> the *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() test in a few
> different runs.
> The failures in *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() were
> seen when the tests for both ZRemRangeByScoreDUnitTest and
> ZRemRangeByRankDUnitTest were being run at the same time due to both classes
> being changed. It's possibly relevant that the difference in the second
> assertion (expected:<[999]L> but was:<[498]L>) is exactly the incorrect
> number of members removed in the first assertion (expected:<[499]L> but
> was:<[501]L>):
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[499]L> but was:<[501]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByScoreDUnitTest.java:159)
> Caused by:
> org.junit.ComparisonFailure: expected:<[499]L> but was:<[501]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.removeAllButFirstEntry(ZRemRangeByScoreDUnitTest.java:213)
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest >
> zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[999]L> but was:<[498]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByRankDUnitTest.java:144)
> Caused by:
> org.junit.ComparisonFailure: expected:<[999]L> but was:<[498]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.removeAllButFirstEntry(ZRemRangeByRankDUnitTest.java:206)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-results/repeatTest/1630442126/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-artifacts/1630442126/stressnewtestfiles-geode-pr-6803.tgz]
> The same failure was also seen in this second run, along with a failure in
> ZRemRangeByScoreDUnitTest >
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown due to the
> remove command not finding any members to remove:
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown FAILED
> org.junit.ComparisonFailure: expected:<[50]0L> but was:<[]0L>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
>
[jira] [Reopened] (GEODE-9571) Radish REMRANGE* DUnit tests may fail in stress-test
[
https://issues.apache.org/jira/browse/GEODE-9571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristen reopened GEODE-9571:
> Radish REMRANGE* DUnit tests may fail in stress-test
>
>
> Key: GEODE-9571
> URL: https://issues.apache.org/jira/browse/GEODE-9571
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Fix For: 1.15.0
>
>
> Failures were seen in pre-checkin stress-new-test for
> ZRemRangeByScoreDUnitTest, ZRemRangeByRankDUnitTest and
> ZRemRangeByLexDUnitTest, all of which use similar test methods. The failures
> were seen in the *RemovesMembersFromSortedSetAfterPrimaryShutsDown() test and
> the *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() test in a few
> different runs.
> The failures in *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() were
> seen when the tests for both ZRemRangeByScoreDUnitTest and
> ZRemRangeByRankDUnitTest were being run at the same time due to both classes
> being changed. It's possibly relevant that the difference in the second
> assertion (expected:<[999]L> but was:<[498]L>) is exactly the incorrect
> number of members removed in the first assertion (expected:<[499]L> but
> was:<[501]L>):
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[499]L> but was:<[501]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByScoreDUnitTest.java:159)
> Caused by:
> org.junit.ComparisonFailure: expected:<[499]L> but was:<[501]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.removeAllButFirstEntry(ZRemRangeByScoreDUnitTest.java:213)
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest >
> zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[999]L> but was:<[498]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByRankDUnitTest.java:144)
> Caused by:
> org.junit.ComparisonFailure: expected:<[999]L> but was:<[498]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.removeAllButFirstEntry(ZRemRangeByRankDUnitTest.java:206)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-results/repeatTest/1630442126/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-artifacts/1630442126/stressnewtestfiles-geode-pr-6803.tgz]
> The same failure was also seen in this second run, along with a failure in
> ZRemRangeByScoreDUnitTest >
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown due to the
> remove command not finding any members to remove:
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown FAILED
> org.junit.ComparisonFailure: expected:<[50]0L> but was:<[]0L>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
>
[jira] [Commented] (GEODE-9571) Radish REMRANGE* DUnit tests may fail in stress-test
[
https://issues.apache.org/jira/browse/GEODE-9571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478112#comment-17478112
]
Kristen commented on GEODE-9571:
Duplicate of
https://issues.apache.org/jira/browse/GEODE-9716?jql=text%20~%20%22ZRemRangeByScoreDUnitTest%22
> Radish REMRANGE* DUnit tests may fail in stress-test
>
>
> Key: GEODE-9571
> URL: https://issues.apache.org/jira/browse/GEODE-9571
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Fix For: 1.15.0
>
>
> Failures were seen in pre-checkin stress-new-test for
> ZRemRangeByScoreDUnitTest, ZRemRangeByRankDUnitTest and
> ZRemRangeByLexDUnitTest, all of which use similar test methods. The failures
> were seen in the *RemovesMembersFromSortedSetAfterPrimaryShutsDown() test and
> the *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() test in a few
> different runs.
> The failures in *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() were
> seen when the tests for both ZRemRangeByScoreDUnitTest and
> ZRemRangeByRankDUnitTest were being run at the same time due to both classes
> being changed. It's possibly relevant that the difference in the second
> assertion (expected:<[999]L> but was:<[498]L>) is exactly the incorrect
> number of members removed in the first assertion (expected:<[499]L> but
> was:<[501]L>):
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[499]L> but was:<[501]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByScoreDUnitTest.java:159)
> Caused by:
> org.junit.ComparisonFailure: expected:<[499]L> but was:<[501]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.removeAllButFirstEntry(ZRemRangeByScoreDUnitTest.java:213)
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest >
> zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[999]L> but was:<[498]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByRankDUnitTest.java:144)
> Caused by:
> org.junit.ComparisonFailure: expected:<[999]L> but was:<[498]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.removeAllButFirstEntry(ZRemRangeByRankDUnitTest.java:206)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-results/repeatTest/1630442126/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-artifacts/1630442126/stressnewtestfiles-geode-pr-6803.tgz]
> The same failure was also seen in this second run, along with a failure in
> ZRemRangeByScoreDUnitTest >
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown due to the
> remove command not finding any members to remove:
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown FAILED
> org.junit.ComparisonFailure: expected:<[50]0L> but was:<[]0L>
> at
>
[jira] [Commented] (GEODE-9716) ZRemRangeByScoreDUnitTest.zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-9716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478111#comment-17478111
]
Geode Integration commented on GEODE-9716:
--
Seen in [distributed-test-openjdk8
#632|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/632]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642239162/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642239162/distributedtestfiles-openjdk8-1.15.0-build.0789.tgz].
> ZRemRangeByScoreDUnitTest.zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown
> fails intermittently
> ---
>
> Key: GEODE-9716
> URL: https://issues.apache.org/jira/browse/GEODE-9716
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Assignee: Ray Ingles
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown fails rarely
> with the following stack trace:
> {code:java}
> ZRemRangeByScoreDUnitTest >
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown FAILED
> org.opentest4j.AssertionFailedError:
> expected: 500L
> but was: 0L
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreWithRetries(ZRemRangeByScoreDUnitTest.java:253)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.doZRemRangeByScoreWithRetries(ZRemRangeByScoreDUnitTest.java:237)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9571) Radish REMRANGE* DUnit tests may fail in stress-test
[
https://issues.apache.org/jira/browse/GEODE-9571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478108#comment-17478108
]
Geode Integration commented on GEODE-9571:
--
Seen in [distributed-test-openjdk8
#632|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/632]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642239162/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642239162/distributedtestfiles-openjdk8-1.15.0-build.0789.tgz].
> Radish REMRANGE* DUnit tests may fail in stress-test
>
>
> Key: GEODE-9571
> URL: https://issues.apache.org/jira/browse/GEODE-9571
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
>
> Failures were seen in pre-checkin stress-new-test for
> ZRemRangeByScoreDUnitTest, ZRemRangeByRankDUnitTest and
> ZRemRangeByLexDUnitTest, all of which use similar test methods. The failures
> were seen in the *RemovesMembersFromSortedSetAfterPrimaryShutsDown() test and
> the *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() test in a few
> different runs.
> The failures in *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() were
> seen when the tests for both ZRemRangeByScoreDUnitTest and
> ZRemRangeByRankDUnitTest were being run at the same time due to both classes
> being changed. It's possibly relevant that the difference in the second
> assertion (expected:<[999]L> but was:<[498]L>) is exactly the incorrect
> number of members removed in the first assertion (expected:<[499]L> but
> was:<[501]L>):
> {noformat}
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest
> > zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[499]L> but was:<[501]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByScoreDUnitTest.java:159)
> Caused by:
> org.junit.ComparisonFailure: expected:<[499]L> but was:<[501]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.removeAllButFirstEntry(ZRemRangeByScoreDUnitTest.java:213)
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest >
> zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
> java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
> expected:<[999]L> but was:<[498]L>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByRankDUnitTest.java:144)
> Caused by:
> org.junit.ComparisonFailure: expected:<[999]L> but was:<[498]L>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.removeAllButFirstEntry(ZRemRangeByRankDUnitTest.java:206)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-results/repeatTest/1630442126/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-artifacts/1630442126/stressnewtestfiles-geode-pr-6803.tgz]
> The same failure was also seen in this second run, along with a failure in
> ZRemRangeByScoreDUnitTest >
>
[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=17478097#comment-17478097
]
Geode Integration commented on GEODE-9885:
--
Seen in [distributed-test-openjdk8
#659|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/659]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642256136/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642256136/distributedtestfiles-openjdk8-1.15.0-build.0789.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
>Assignee: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> 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.
> Additional to this failure, the test should be modified to produce a more
> useful failure message. The current assertion prints the entire String upon
> failure, which can contain upwards of 50,000 repeats of the
> "\{append0}-key-3*" String, making the output large and unreadable. Consider
> using an assertion with {{.withFailureMessage()}} to produce a more useful
> error message rather than the currently used {{Assert.fail().}}
--
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=17478096#comment-17478096
]
Geode Integration commented on GEODE-9885:
--
Seen in [distributed-test-openjdk8
#700|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/700]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642287575/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642287575/distributedtestfiles-openjdk8-1.15.0-build.0789.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
>Assignee: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> 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.
> Additional to this failure, the test should be modified to produce a more
> useful failure message. The current assertion prints the entire String upon
> failure, which can contain upwards of 50,000 repeats of the
> "\{append0}-key-3*" String, making the output large and unreadable. Consider
> using an assertion with {{.withFailureMessage()}} to produce a more useful
> error message rather than the currently used {{Assert.fail().}}
--
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=17478098#comment-17478098
]
Geode Integration commented on GEODE-9885:
--
Seen in [distributed-test-openjdk8
#639|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/639]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642239672/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642239672/distributedtestfiles-openjdk8-1.15.0-build.0789.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
>Assignee: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> 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.
> Additional to this failure, the test should be modified to produce a more
> useful failure message. The current assertion prints the entire String upon
> failure, which can contain upwards of 50,000 repeats of the
> "\{append0}-key-3*" String, making the output large and unreadable. Consider
> using an assertion with {{.withFailureMessage()}} to produce a more useful
> error message rather than the currently used {{Assert.fail().}}
--
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=17478094#comment-17478094
]
Geode Integration commented on GEODE-9885:
--
Seen in [distributed-test-openjdk8
#698|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/698]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642287550/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642287550/distributedtestfiles-openjdk8-1.15.0-build.0789.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
>Assignee: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> 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.
> Additional to this failure, the test should be modified to produce a more
> useful failure message. The current assertion prints the entire String upon
> failure, which can contain upwards of 50,000 repeats of the
> "\{append0}-key-3*" String, making the output large and unreadable. Consider
> using an assertion with {{.withFailureMessage()}} to produce a more useful
> error message rather than the currently used {{Assert.fail().}}
--
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=17478092#comment-17478092
]
Geode Integration commented on GEODE-9885:
--
Seen in [distributed-test-openjdk8
#696|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/696]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-results/distributedTest/1642287635/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0789/test-artifacts/1642287635/distributedtestfiles-openjdk8-1.15.0-build.0789.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
>Assignee: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> 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.
> Additional to this failure, the test should be modified to produce a more
> useful failure message. The current assertion prints the entire String upon
> failure, which can contain upwards of 50,000 repeats of the
> "\{append0}-key-3*" String, making the output large and unreadable. Consider
> using an assertion with {{.withFailureMessage()}} to produce a more useful
> error message rather than the currently used {{Assert.fail().}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-6801) CI: AutoConnectionSourceImplJUnitTest.test_DiscoverLocators_whenOneLocatorWasShutdown failed on Windows
[ https://issues.apache.org/jira/browse/GEODE-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478090#comment-17478090 ] Geode Integration commented on GEODE-6801: -- Seen in [integration-test-openjdk8 #104|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/integration-test-openjdk8/builds/104] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0788/test-results/integrationTest/1642204530/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0788/test-artifacts/1642204530/integrationtestfiles-openjdk8-1.15.0-build.0788.tgz]. > CI: > AutoConnectionSourceImplJUnitTest.test_DiscoverLocators_whenOneLocatorWasShutdown > failed on Windows > > > Key: GEODE-6801 > URL: https://issues.apache.org/jira/browse/GEODE-6801 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Jinmei Liao >Priority: Major > Labels: flaky > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/455 > org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to connect > to any locators in the list [LocatorAddress > [socketInetAddress=packer-5cd4b68b-ea62-1633-a97a-d526ad1b88a1/10.0.0.135:29249, > hostname=packer-5cd4b68b-ea62-1633-a97a-d526ad1b88a1, isIpString=false], > LocatorAddress > [socketInetAddress=packer-5cd4b68b-ea62-1633-a97a-d526ad1b88a1/10.0.0.135:29250, > hostname=packer-5cd4b68b-ea62-1633-a97a-d526ad1b88a1, isIpString=false]] > at > org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:159) > at > org.apache.geode.cache.client.internal.AutoConnectionSourceImplJUnitTest.test_DiscoverLocators_whenOneLocatorWasShutdown(AutoConnectionSourceImplJUnitTest.java:339) > 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.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > 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.java:566) > at >
[jira] [Resolved] (GEODE-9913) A retried event can fail if the original event is still being processed and a new event for that same key occurs at the same time
[ https://issues.apache.org/jira/browse/GEODE-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrett Oglesby resolved GEODE-9913. Fix Version/s: 1.15.0 Resolution: Fixed > A retried event can fail if the original event is still being processed and a > new event for that same key occurs at the same time > - > > Key: GEODE-9913 > URL: https://issues.apache.org/jira/browse/GEODE-9913 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Barrett Oglesby >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-7059) CI Failure: Tomcat8ClientServerRollingUpgradeTest.canDoARollingUpgradeOfGeodeServersWithSessionModules[170]
[
https://issues.apache.org/jira/browse/GEODE-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478089#comment-17478089
]
Geode Integration commented on GEODE-7059:
--
Seen in [upgrade-test-openjdk8
#102|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk8/builds/102]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0788/test-results/upgradeTest/1642207859/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0788/test-artifacts/1642207859/upgradetestfiles-openjdk8-1.15.0-build.0788.tgz].
> CI Failure:
> Tomcat8ClientServerRollingUpgradeTest.canDoARollingUpgradeOfGeodeServersWithSessionModules[170]
> ---
>
> Key: GEODE-7059
> URL: https://issues.apache.org/jira/browse/GEODE-7059
> Project: Geode
> Issue Type: Bug
>Reporter: Hale Bales
>Priority: Major
>
> Tomcat8ClientServerRollingUpgradeTest failed in CI:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK8/builds/954
> Results available here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0008/test-results/upgradeTest/1565134781/
> Archive here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0008/test-artifacts/1565134781/upgradetestfiles-OpenJDK8-1.11.0-SNAPSHOT.0008.tgz
> The issue appears to be a port conflict, however a connection through GFSH
> does not seem like it should be triggering JMX startup.
> {noformat}
> Executing db801bc9548a20f6: gfsh -e connect --locator=localhost[25018] -e
> create region --type=PARTITION_REDUNDANT --name=gemfire_modules_sessions
> --enable-statistics=true
> --entry-idle-time-custom-expiry=org.apache.geode.modules.util.SessionCustomExpiry
> [INFO 23:03:02.978 GMT] (db801bc9548a20f6):
> [INFO 23:03:02.978 GMT] (db801bc9548a20f6): (1) Executing - connect
> --locator=localhost[25018]
> [INFO 23:03:02.979 GMT] (db801bc9548a20f6):
> [INFO 23:03:03.017 GMT] (db801bc9548a20f6): Connecting to Locator at
> [host=localhost, port=25018] ..
> [ERROR 23:03:05.075 GMT] (db801bc9548a20f6): Exception caused JMX Manager
> startup to fail because: 'java.rmi.server.ExportException: Port already in
> use: 25019; nested exception is:
> [ERROR 23:03:05.075 GMT] (db801bc9548a20f6): java.net.BindException:
> Failed to create server socket on null[25,019]'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9935) CI Failure: RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment
[
https://issues.apache.org/jira/browse/GEODE-9935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao reassigned GEODE-9935:
--
Assignee: Jinmei Liao
> CI Failure: RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment
> --
>
> Key: GEODE-9935
> URL: https://issues.apache.org/jira/browse/GEODE-9935
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Assignee: Jinmei Liao
>Priority: Major
> Labels: GeodeOperationAPI, needsTriage
>
> CI Failure in upgrade tests in RollingUpgradeWithGfshDUnitTest >
> testRollingUpgradeWithDeployment. starting locator exits with status of 1,
> not the expected 0.
> {code:java}
> > Task :geode-assembly:upgradeTest
> RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment[1.10.0]
> FAILED
> org.opentest4j.AssertionFailedError: [Exit value from process started by
> [e35c359d41713de9: gfsh -e start locator --name=loc2 --port=24585
> --http-service-port=0 --locators=localhost[24583]
> --J=-Dgemfire.jmx-manager-port=24586]]
> expected: 0
> but was: 1
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:152)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:153)
> at
> org.apache.geode.management.RollingUpgradeWithGfshDUnitTest.testRollingUpgradeWithDeployment(RollingUpgradeWithGfshDUnitTest.java:107)
> 134 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-results/upgradeTest/1641589807/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-artifacts/1641589807/upgradetestfiles-openjdk8-1.15.0-build.0767.tgz
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9935) CI Failure: RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment
[
https://issues.apache.org/jira/browse/GEODE-9935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao updated GEODE-9935:
---
Labels: GeodeOperationAPI needsTriage (was: needsTriage)
> CI Failure: RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment
> --
>
> Key: GEODE-9935
> URL: https://issues.apache.org/jira/browse/GEODE-9935
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Priority: Major
> Labels: GeodeOperationAPI, needsTriage
>
> CI Failure in upgrade tests in RollingUpgradeWithGfshDUnitTest >
> testRollingUpgradeWithDeployment. starting locator exits with status of 1,
> not the expected 0.
> {code:java}
> > Task :geode-assembly:upgradeTest
> RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment[1.10.0]
> FAILED
> org.opentest4j.AssertionFailedError: [Exit value from process started by
> [e35c359d41713de9: gfsh -e start locator --name=loc2 --port=24585
> --http-service-port=0 --locators=localhost[24583]
> --J=-Dgemfire.jmx-manager-port=24586]]
> expected: 0
> but was: 1
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:152)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:153)
> at
> org.apache.geode.management.RollingUpgradeWithGfshDUnitTest.testRollingUpgradeWithDeployment(RollingUpgradeWithGfshDUnitTest.java:107)
> 134 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-results/upgradeTest/1641589807/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0767/test-artifacts/1641589807/upgradetestfiles-openjdk8-1.15.0-build.0767.tgz
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (GEODE-9836) SUNION Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen resolved GEODE-9836. Resolution: Fixed > SUNION Command Supported > > > Key: GEODE-9836 > URL: https://issues.apache.org/jira/browse/GEODE-9836 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Kristen >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The SUNION command has been implemented but lacks sufficient testing to > ensure that the implementation is robust and does not regress in the future. > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers. > > +Acceptance Criteria+ > > Passing Unit/integration tests for both Geode and native Redis. The > RedisCommandType class and > README/redis_api_for_[geode.html.md.erb|http://geode.html.md.erb/] updated to > make command "supported". Stories in the backlog to fix the identified issues > (with JIRA tickets) and problem tests that are ignored should be fixed and > enabled. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9302) Benchmark instability in PartitionedPutStringBenchmark
[
https://issues.apache.org/jira/browse/GEODE-9302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478085#comment-17478085
]
Geode Integration commented on GEODE-9302:
--
Seen in [benchmark-base
#97|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/97].
> Benchmark instability in PartitionedPutStringBenchmark
> --
>
> Key: GEODE-9302
> URL: https://issues.apache.org/jira/browse/GEODE-9302
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
>
> A benchmark failure due to the recently-introduced
> PartitionedPutStringBenchmark was observed:
> {noformat}
> This is ITERATION 1 of benchmarking against baseline.
> P2pPartitionedGetBenchmark avg ops/sec
> Baseline:853001.60 Test:867151.67 Difference: +1.7%
> avg latency
> Baseline:842007.55 Test:828545.06 Difference: -1.6%
> P2pPartitionedPutBenchmark avg ops/sec
> Baseline:128283.47 Test:126510.92 Difference: -1.4%
> avg latency
> Baseline: 5785619.62 Test: 5915913.49 Difference: +2.3%
> P2pPartitionedPutBytesBenchmark avg ops/sec
> Baseline:175658.08 Test:174865.97 Difference: -0.5%
> avg latency
> Baseline: 4130071.43 Test: 4130753.09 Difference: +0.0%
>PartitionedFunctionExecutionBenchmark avg ops/sec
> Baseline:254788.26 Test:268132.99 Difference: +5.2%
> avg latency
> Baseline:846158.41 Test:804199.42 Difference: -5.0%
> PartitionedFunctionExecutionWithArgumentsBenchmark avg ops/sec
> Baseline:278669.87 Test:281504.58 Difference: +1.0%
> avg latency
> Baseline: 1031826.82 Test: 1021314.54 Difference: -1.0%
> PartitionedFunctionExecutionWithFiltersBenchmark avg ops/sec
> Baseline:372204.82 Test:348815.81 Difference: -6.3%
> avg latency
> Baseline: 1545217.38 Test: 1649706.37 Difference: +6.8%
> PartitionedGetBenchmark avg ops/sec
> Baseline:823740.09 Test:819044.99 Difference: -0.6%
> avg latency
> Baseline:872172.75 Test:877580.02 Difference: +0.6%
> PartitionedGetLongBenchmark avg ops/sec
> Baseline: 1047221.43 Test: 1045565.89 Difference: -0.2%
> avg latency
> Baseline:685757.55 Test:687005.43 Difference: +0.2%
>PartitionedGetStringBenchmark avg ops/sec
> Baseline: 1055904.14 Test: 1045420.73 Difference: -1.0%
> avg latency
> Baseline:680031.44 Test:687045.15 Difference: +1.0%
> PartitionedIndexedQueryBenchmark avg ops/sec
> Baseline: 31596.35 Test: 31653.48 Difference: +0.2%
> avg latency
> Baseline: 18221302.10 Test: 18216097.86 Difference: -0.0%
> PartitionedNonIndexedQueryBenchmark avg ops/sec
> Baseline:95.78 Test: 100.35 Difference: +4.8%
> avg latency
> Baseline: 750871203.78 Test: 716853923.95 Difference: -4.5%
> PartitionedPutAllBenchmark avg ops/sec
> Baseline: 8675.75 Test: 8628.10 Difference: -0.5%
> avg latency
> Baseline: 16595044.73 Test: 16685258.91 Difference: +0.5%
> PartitionedPutAllLongBenchmark avg ops/sec
> Baseline: 1382.38 Test: 1380.50 Difference: -0.1%
> avg latency
> Baseline: 104866853.92 Test: 104775538.34 Difference: -0.1%
> PartitionedPutBenchmark avg ops/sec
> Baseline:491790.40 Test:479926.75 Difference: -2.4%
> avg latency
> Baseline: 1461947.23 Test: 1497519.77 Difference: +2.4%
>
[jira] [Updated] (GEODE-9836) SUNION Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9836: --- Fix Version/s: 1.15.0 > SUNION Command Supported > > > Key: GEODE-9836 > URL: https://issues.apache.org/jira/browse/GEODE-9836 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Kristen >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The SUNION command has been implemented but lacks sufficient testing to > ensure that the implementation is robust and does not regress in the future. > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers. > > +Acceptance Criteria+ > > Passing Unit/integration tests for both Geode and native Redis. The > RedisCommandType class and > README/redis_api_for_[geode.html.md.erb|http://geode.html.md.erb/] updated to > make command "supported". Stories in the backlog to fix the identified issues > (with JIRA tickets) and problem tests that are ignored should be fixed and > enabled. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-7572) BENCHMARK FAILED: org.apache.geode.benchmark.tests.PartitionedPutAllLongBenchmark average latency is 5% worse than baseline.
[ https://issues.apache.org/jira/browse/GEODE-7572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478084#comment-17478084 ] Geode Integration commented on GEODE-7572: -- Seen in [benchmark-base #93|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/93]. > BENCHMARK FAILED: > org.apache.geode.benchmark.tests.PartitionedPutAllLongBenchmark average > latency is 5% worse than baseline. > > > Key: GEODE-7572 > URL: https://issues.apache.org/jira/browse/GEODE-7572 > Project: Geode > Issue Type: Bug > Components: benchmarks, ci >Reporter: Ernest Burghardt >Priority: Major > > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/7] > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/8] > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/9 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9644) ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects FAILED
[
https://issues.apache.org/jira/browse/GEODE-9644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478076#comment-17478076
]
ASF subversion and git services commented on GEODE-9644:
Commit a240351b17efb7419b3bb3e122618ff6a9e26817 in geode's branch
refs/heads/develop from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a240351 ]
GEODE-9644: Remove use of ephemeral ports for tests (#7264)
> ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects
> FAILED
> --
>
> Key: GEODE-9644
> URL: https://issues.apache.org/jira/browse/GEODE-9644
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jinmei Liao
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> There is sequence of cascading exceptions that occur in the VMs and we need a
> more detailed investigation: Possible culprit may be the bind address in use
> exeception:
> [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0513/test-results/distributedTest/1632566050/*]
>
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
> > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest$$Lambda$163/1450009752.run
> in VM 0 running on Host
> heavy-lifter-2c03c48d-8a0c-58ae-bad6-31f64bb5400a.c.apachegeode-ci.internal
> with 5 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.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> at
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.waitForLocatorToReconnect(ClusterConfigLocatorRestartDUnitTest.java:225)
> at
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:90)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
> was not fulfilled within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:166)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:908)
> at
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.lambda$waitForLocatorToReconnect$f182e747$2(ClusterConfigLocatorRestartDUnitTest.java:226)
> 8300 tests completed, 1 failed, 413 skipped{noformat}
> VM2 mentions that cluster membership has failed.
> {noformat}
> [vm2] [info 2021/09/25 09:36:44.487 UTC server-2
> tid=0x153] cluster membership failed due to
> [vm2]
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> for testing
> [vm2] at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1787)
> [vm2] at
> org.apache.geode.distributed.internal.membership.api.MembershipManagerHelper.crashDistributedSystem(MembershipManagerHelper.java:139)
> [vm2] at
> org.apache.geode.test.junit.rules.MemberStarterRule.forceDisconnectMember(MemberStarterRule.java:568)
> [vm2] at
> org.apache.geode.test.dunit.rules.MemberVM.lambda$forceDisconnect$bb17a952$1(MemberVM.java:90)
> [vm2] at
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run(IdentifiableRunnable.java:41)
> [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm2] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm2] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm2] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm2] at
> org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> [vm2] at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
> [vm2] at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
> [vm2] at
>
[jira] [Comment Edited] (GEODE-9644) ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects FAILED
[
https://issues.apache.org/jira/browse/GEODE-9644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478073#comment-17478073
]
Jinmei Liao edited comment on GEODE-9644 at 1/18/22, 5:40 PM:
--
have the rule not to use ephemeral port
was (Author: jinmeiliao):
have the rule not to use empheral port
> ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects
> FAILED
> --
>
> Key: GEODE-9644
> URL: https://issues.apache.org/jira/browse/GEODE-9644
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jinmei Liao
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> There is sequence of cascading exceptions that occur in the VMs and we need a
> more detailed investigation: Possible culprit may be the bind address in use
> exeception:
> [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0513/test-results/distributedTest/1632566050/*]
>
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
> > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest$$Lambda$163/1450009752.run
> in VM 0 running on Host
> heavy-lifter-2c03c48d-8a0c-58ae-bad6-31f64bb5400a.c.apachegeode-ci.internal
> with 5 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.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> at
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.waitForLocatorToReconnect(ClusterConfigLocatorRestartDUnitTest.java:225)
> at
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:90)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
> was not fulfilled within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:166)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:908)
> at
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.lambda$waitForLocatorToReconnect$f182e747$2(ClusterConfigLocatorRestartDUnitTest.java:226)
> 8300 tests completed, 1 failed, 413 skipped{noformat}
> VM2 mentions that cluster membership has failed.
> {noformat}
> [vm2] [info 2021/09/25 09:36:44.487 UTC server-2
> tid=0x153] cluster membership failed due to
> [vm2]
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> for testing
> [vm2] at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1787)
> [vm2] at
> org.apache.geode.distributed.internal.membership.api.MembershipManagerHelper.crashDistributedSystem(MembershipManagerHelper.java:139)
> [vm2] at
> org.apache.geode.test.junit.rules.MemberStarterRule.forceDisconnectMember(MemberStarterRule.java:568)
> [vm2] at
> org.apache.geode.test.dunit.rules.MemberVM.lambda$forceDisconnect$bb17a952$1(MemberVM.java:90)
> [vm2] at
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run(IdentifiableRunnable.java:41)
> [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm2] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm2] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm2] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm2] at
> org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> [vm2] at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
> [vm2] at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
> [vm2] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm2] at
[jira] [Resolved] (GEODE-9644) ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects FAILED
[
https://issues.apache.org/jira/browse/GEODE-9644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-9644.
Fix Version/s: 1.15.0
Resolution: Fixed
have the rule not to use empheral port
> ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects
> FAILED
> --
>
> Key: GEODE-9644
> URL: https://issues.apache.org/jira/browse/GEODE-9644
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jinmei Liao
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> There is sequence of cascading exceptions that occur in the VMs and we need a
> more detailed investigation: Possible culprit may be the bind address in use
> exeception:
> [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0513/test-results/distributedTest/1632566050/*]
>
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
> > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest$$Lambda$163/1450009752.run
> in VM 0 running on Host
> heavy-lifter-2c03c48d-8a0c-58ae-bad6-31f64bb5400a.c.apachegeode-ci.internal
> with 5 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.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> at
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.waitForLocatorToReconnect(ClusterConfigLocatorRestartDUnitTest.java:225)
> at
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:90)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
> was not fulfilled within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:166)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:908)
> at
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.lambda$waitForLocatorToReconnect$f182e747$2(ClusterConfigLocatorRestartDUnitTest.java:226)
> 8300 tests completed, 1 failed, 413 skipped{noformat}
> VM2 mentions that cluster membership has failed.
> {noformat}
> [vm2] [info 2021/09/25 09:36:44.487 UTC server-2
> tid=0x153] cluster membership failed due to
> [vm2]
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> for testing
> [vm2] at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1787)
> [vm2] at
> org.apache.geode.distributed.internal.membership.api.MembershipManagerHelper.crashDistributedSystem(MembershipManagerHelper.java:139)
> [vm2] at
> org.apache.geode.test.junit.rules.MemberStarterRule.forceDisconnectMember(MemberStarterRule.java:568)
> [vm2] at
> org.apache.geode.test.dunit.rules.MemberVM.lambda$forceDisconnect$bb17a952$1(MemberVM.java:90)
> [vm2] at
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run(IdentifiableRunnable.java:41)
> [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm2] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm2] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm2] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm2] at
> org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> [vm2] at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
> [vm2] at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
> [vm2] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm2] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm2] at
>
[jira] [Commented] (GEODE-9836) SUNION Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478069#comment-17478069 ] ASF subversion and git services commented on GEODE-9836: Commit f78fd7334131be4c99421c666879cfb857f8d7c5 in geode's branch refs/heads/develop from Kris10 [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f78fd73 ] GEODE-9836: SUNION Command Support > SUNION Command Supported > > > Key: GEODE-9836 > URL: https://issues.apache.org/jira/browse/GEODE-9836 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Kristen >Priority: Major > Labels: pull-request-available > > The SUNION command has been implemented but lacks sufficient testing to > ensure that the implementation is robust and does not regress in the future. > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers. > > +Acceptance Criteria+ > > Passing Unit/integration tests for both Geode and native Redis. The > RedisCommandType class and > README/redis_api_for_[geode.html.md.erb|http://geode.html.md.erb/] updated to > make command "supported". Stories in the backlog to fix the identified issues > (with JIRA tickets) and problem tests that are ignored should be fixed and > enabled. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478057#comment-17478057
]
Barrett Oglesby commented on GEODE-9528:
I backported this change to support/1.14, support/1.13 and support/1.12.
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.9, 1.13.7, 1.14.3, 1.15.0
>
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrett Oglesby updated GEODE-9528:
---
Fix Version/s: 1.12.9
1.13.7
1.14.3
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.9, 1.13.7, 1.14.3, 1.15.0
>
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478056#comment-17478056
]
ASF subversion and git services commented on GEODE-9528:
Commit 1c043ff51a6c5eb77b0a83b10b83e071aad0 in geode's branch
refs/heads/support/1.12 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1c0 ]
GEODE-9528: Updated test to await until asserted (#6798)
(cherry picked from commit ed816c55406131b95d4db8571558ed1fcecc53e7)
(cherry picked from commit aecbdb2d327cb4dfdf27e669092c7889414a7e7f)
(cherry picked from commit fa1f753b38c8b8a1985b712751411e94654ca49e)
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478052#comment-17478052
]
ASF subversion and git services commented on GEODE-9528:
Commit fa1f753b38c8b8a1985b712751411e94654ca49e in geode's branch
refs/heads/support/1.13 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=fa1f753 ]
GEODE-9528: Updated test to await until asserted (#6798)
(cherry picked from commit ed816c55406131b95d4db8571558ed1fcecc53e7)
(cherry picked from commit aecbdb2d327cb4dfdf27e669092c7889414a7e7f)
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478045#comment-17478045
]
ASF subversion and git services commented on GEODE-9528:
Commit aecbdb2d327cb4dfdf27e669092c7889414a7e7f in geode's branch
refs/heads/support/1.14 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=aecbdb2 ]
GEODE-9528: Updated test to await until asserted (#6798)
(cherry picked from commit ed816c55406131b95d4db8571558ed1fcecc53e7)
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9964) ExplicitMoveDirector incorrectly compares Member with InternalDistributedMember.
[
https://issues.apache.org/jira/browse/GEODE-9964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478004#comment-17478004
]
Alexander Murmann commented on GEODE-9964:
--
What's the customer-visible impact of this?
> ExplicitMoveDirector incorrectly compares Member with
> InternalDistributedMember.
>
>
> Key: GEODE-9964
> URL: https://issues.apache.org/jira/browse/GEODE-9964
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.14.2, 1.15.0
>Reporter: Jacob Barrett
>Priority: Major
> Labels: needsTriage
>
> {{ExplicitMoveDirector}} incorrectly compares {{Member}} with
> {{InternalDistributedMember}} due use of raw types rather than generics. It
> is also likely there is either no testing for this failure case or the test
> is passing for the wrong reasons.
> See
> [here|https://github.com/apache/geode/blob/2b032440eb9d0f3c68a94602289cc41435c68fad/geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/rebalance/ExplicitMoveDirector.java#L93]
> See
> [here|https://github.com/apache/geode/blob/2b032440eb9d0f3c68a94602289cc41435c68fad/geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/rebalance/ExplicitMoveDirector.java#L99]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9848) Duplicate and Unnecessary REGISTER_INTEREST Message Sent to Server
[ https://issues.apache.org/jira/browse/GEODE-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17477962#comment-17477962 ] ASF GitHub Bot commented on GEODE-9848: --- mmartell merged pull request #906: URL: https://github.com/apache/geode-native/pull/906 -- 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 > Duplicate and Unnecessary REGISTER_INTEREST Message Sent to Server > -- > > Key: GEODE-9848 > URL: https://issues.apache.org/jira/browse/GEODE-9848 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > > In the course of debugging a RegisterAllKeys bug (GEMNC-508), it was > discovered that a second REGISTER_INTEREST message is being sent to the same > server. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9829) SINTER Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bala Tripura Sundari Kaza Venkata resolved GEODE-9829. -- Resolution: Fixed > SINTER Command Supported > > > Key: GEODE-9829 > URL: https://issues.apache.org/jira/browse/GEODE-9829 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Bala Tripura Sundari Kaza Venkata >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The SINTER command has been implemented but lacks sufficient testing to > ensure that the implementation is robust and does not regress in the future. > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers. > > +Acceptance Criteria+ > > Passing Unit/integration tests for both Geode and native Redis. The > RedisCommandType class and > README/redis_api_for_[geode.html.md.erb|http://geode.html.md.erb/] updated to > make command "supported". Stories in the backlog to fix the identified issues > (with JIRA tickets) and problem tests that are ignored should be fixed and > enabled. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9835) SSCAN Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9835: -- Labels: pull-request-available (was: ) > SSCAN Command Supported > --- > > Key: GEODE-9835 > URL: https://issues.apache.org/jira/browse/GEODE-9835 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Priority: Major > Labels: pull-request-available > > The SSCAN command has been implemented but lacks sufficient testing to ensure > that the implementation is robust and does not regress in the future. > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers. > > +Acceptance Criteria+ > > Passing Unit/integration tests for both Geode and native Redis. The > RedisCommandType class and > README/redis_api_for_[geode.html.md.erb|http://geode.html.md.erb/] updated to > make command "supported". Stories in the backlog to fix the identified issues > (with JIRA tickets) and problem tests that are ignored should be fixed and > enabled. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9969) The region name starting with underscore lead to missing disk store after restart
Mario Kevo created GEODE-9969:
-
Summary: The region name starting with underscore lead to missing
disk store after restart
Key: GEODE-9969
URL: https://issues.apache.org/jira/browse/GEODE-9969
Project: Geode
Issue Type: Bug
Components: regions
Affects Versions: 1.14.2, 1.13.6, 1.12.8, 1.15.0
Reporter: Mario Kevo
The problem is when using the region with a name starting with an
underscore(allowed by documentation
[region_naming|https://geode.apache.org/docs/guide/114/basic_config/data_regions/region_naming.html]).
If we stop one of the members and then rename the working dir(include disk
store dir) to some new name and start the server with the name like renamed
working dir, it will lead that we have the same disk-store-id in the listed
disk-stores and in the missing disk store.
This happens only if we are using the region with an underscore at the
beginning.
Steps to reproduce:
Run locator and 4 servers, create region with name starting by underscore
# start locator --name=locator
# start server --name=server1 --server-port=40401
# start server --name=server2 --server-port=40402
# start server --name=server3 --server-port=40403
# start server --name=server4 --server-port=40404
# create region --name=_test-region --type=PARTITION_REDUNDANT_PERSISTENT
--redundant-copies=1 --total-num-buckets=10 --enable-synchronous-disk=false
# query --query="select * from /_test-region"
>From another terminal (Kill server and rename working dir)
# kill -9 $(cat server4/vf.gf.server.pid)
# mv server4/ server5
{code:java}
gfsh>list disk-stores
Member Name | Member Id | Disk Store Name | Disk
Store ID
--- | -- | --- |
server1 | 192.168.0.145(server1:16916):41001 | DEFAULT |
d5d17b43-4a06-408b-917f-08e5b2533ebe
server2 | 192.168.0.145(server2:17004):41002 | DEFAULT |
31d47cb4-718e-4b58-bde3-ae15b4657910
server3 | 192.168.0.145(server3:17094):41003 | DEFAULT |
f12850c6-a73b-443e-9ee0-87f0819ae6bc
server5 | 192.168.0.145(server5:17428):41004 | DEFAULT |
7a552fb3-e43d-4fa8-baa8-f6dc794cbf74
gfsh>show missing-disk-stores
Missing Disk Stores
Disk Store ID | Host | Directory
| - |
7a552fb3-e43d-4fa8-baa8-f6dc794cbf74 | 192.168.0.145 |
/home/mkevo/apache-geode-1.15.0-build.0/bin/server4/.
No missing colocated region found
{code}
Start a new server with a name like you rename your working dir from the
restarted server.
# start server --name=server5 --server-port=40405
Now we have the following output:
{code:java}
gfsh>list disk-stores
Member Name | Member Id| Disk Store Name | Disk
Store ID
--- | -- | --- |
server1 | 192.168.0.145(server1:16916):41001 | DEFAULT |
d5d17b43-4a06-408b-917f-08e5b2533ebe
server2 | 192.168.0.145(server2:17004):41002 | DEFAULT |
31d47cb4-718e-4b58-bde3-ae15b4657910
server3 | 192.168.0.145(server3:17094):41003 | DEFAULT |
f12850c6-a73b-443e-9ee0-87f0819ae6bc
server5 | 192.168.0.145(server5:17428):41004 | DEFAULT |
7a552fb3-e43d-4fa8-baa8-f6dc794cbf74
gfsh>show missing-disk-stores
Missing Disk Stores
Disk Store ID | Host | Directory
| - |
7a552fb3-e43d-4fa8-baa8-f6dc794cbf74 | 192.168.0.145 |
/home/mkevo/apache-geode-1.15.0-build.0/bin/server4/.
No missing colocated region found
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9969) The region name starting with underscore lead to missing disk store after restart
[
https://issues.apache.org/jira/browse/GEODE-9969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Kevo reassigned GEODE-9969:
-
Assignee: Mario Kevo
> The region name starting with underscore lead to missing disk store after
> restart
> -
>
> Key: GEODE-9969
> URL: https://issues.apache.org/jira/browse/GEODE-9969
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.12.8, 1.13.6, 1.14.2, 1.15.0
>Reporter: Mario Kevo
>Assignee: Mario Kevo
>Priority: Major
> Labels: needsTriage
>
> The problem is when using the region with a name starting with an
> underscore(allowed by documentation
> [region_naming|https://geode.apache.org/docs/guide/114/basic_config/data_regions/region_naming.html]).
> If we stop one of the members and then rename the working dir(include disk
> store dir) to some new name and start the server with the name like renamed
> working dir, it will lead that we have the same disk-store-id in the listed
> disk-stores and in the missing disk store.
> This happens only if we are using the region with an underscore at the
> beginning.
> Steps to reproduce:
> Run locator and 4 servers, create region with name starting by underscore
> # start locator --name=locator
> # start server --name=server1 --server-port=40401
> # start server --name=server2 --server-port=40402
> # start server --name=server3 --server-port=40403
> # start server --name=server4 --server-port=40404
> # create region --name=_test-region --type=PARTITION_REDUNDANT_PERSISTENT
> --redundant-copies=1 --total-num-buckets=10 --enable-synchronous-disk=false
> # query --query="select * from /_test-region"
> From another terminal (Kill server and rename working dir)
> # kill -9 $(cat server4/vf.gf.server.pid)
> # mv server4/ server5
> {code:java}
> gfsh>list disk-stores
> Member Name | Member Id | Disk Store Name | Disk
> Store ID
> --- | -- | --- |
>
> server1 | 192.168.0.145(server1:16916):41001 | DEFAULT |
> d5d17b43-4a06-408b-917f-08e5b2533ebe
> server2 | 192.168.0.145(server2:17004):41002 | DEFAULT |
> 31d47cb4-718e-4b58-bde3-ae15b4657910
> server3 | 192.168.0.145(server3:17094):41003 | DEFAULT |
> f12850c6-a73b-443e-9ee0-87f0819ae6bc
> server5 | 192.168.0.145(server5:17428):41004 | DEFAULT |
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74
> gfsh>show missing-disk-stores
> Missing Disk Stores
> Disk Store ID | Host | Directory
> | - |
>
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74 | 192.168.0.145 |
> /home/mkevo/apache-geode-1.15.0-build.0/bin/server4/.
> No missing colocated region found
> {code}
> Start a new server with a name like you rename your working dir from the
> restarted server.
> # start server --name=server5 --server-port=40405
> Now we have the following output:
> {code:java}
> gfsh>list disk-stores
> Member Name | Member Id| Disk Store Name | Disk
> Store ID
> --- | -- | --- |
>
> server1 | 192.168.0.145(server1:16916):41001 | DEFAULT |
> d5d17b43-4a06-408b-917f-08e5b2533ebe
> server2 | 192.168.0.145(server2:17004):41002 | DEFAULT |
> 31d47cb4-718e-4b58-bde3-ae15b4657910
> server3 | 192.168.0.145(server3:17094):41003 | DEFAULT |
> f12850c6-a73b-443e-9ee0-87f0819ae6bc
> server5 | 192.168.0.145(server5:17428):41004 | DEFAULT |
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74
> gfsh>show missing-disk-stores
> Missing Disk Stores
>Disk Store ID | Host | Directory
> | - |
>
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74 | 192.168.0.145 |
> /home/mkevo/apache-geode-1.15.0-build.0/bin/server4/.
> No missing colocated region found
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9969) The region name starting with underscore lead to missing disk store after restart
[
https://issues.apache.org/jira/browse/GEODE-9969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-9969:
-
Labels: needsTriage (was: )
> The region name starting with underscore lead to missing disk store after
> restart
> -
>
> Key: GEODE-9969
> URL: https://issues.apache.org/jira/browse/GEODE-9969
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.12.8, 1.13.6, 1.14.2, 1.15.0
>Reporter: Mario Kevo
>Priority: Major
> Labels: needsTriage
>
> The problem is when using the region with a name starting with an
> underscore(allowed by documentation
> [region_naming|https://geode.apache.org/docs/guide/114/basic_config/data_regions/region_naming.html]).
> If we stop one of the members and then rename the working dir(include disk
> store dir) to some new name and start the server with the name like renamed
> working dir, it will lead that we have the same disk-store-id in the listed
> disk-stores and in the missing disk store.
> This happens only if we are using the region with an underscore at the
> beginning.
> Steps to reproduce:
> Run locator and 4 servers, create region with name starting by underscore
> # start locator --name=locator
> # start server --name=server1 --server-port=40401
> # start server --name=server2 --server-port=40402
> # start server --name=server3 --server-port=40403
> # start server --name=server4 --server-port=40404
> # create region --name=_test-region --type=PARTITION_REDUNDANT_PERSISTENT
> --redundant-copies=1 --total-num-buckets=10 --enable-synchronous-disk=false
> # query --query="select * from /_test-region"
> From another terminal (Kill server and rename working dir)
> # kill -9 $(cat server4/vf.gf.server.pid)
> # mv server4/ server5
> {code:java}
> gfsh>list disk-stores
> Member Name | Member Id | Disk Store Name | Disk
> Store ID
> --- | -- | --- |
>
> server1 | 192.168.0.145(server1:16916):41001 | DEFAULT |
> d5d17b43-4a06-408b-917f-08e5b2533ebe
> server2 | 192.168.0.145(server2:17004):41002 | DEFAULT |
> 31d47cb4-718e-4b58-bde3-ae15b4657910
> server3 | 192.168.0.145(server3:17094):41003 | DEFAULT |
> f12850c6-a73b-443e-9ee0-87f0819ae6bc
> server5 | 192.168.0.145(server5:17428):41004 | DEFAULT |
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74
> gfsh>show missing-disk-stores
> Missing Disk Stores
> Disk Store ID | Host | Directory
> | - |
>
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74 | 192.168.0.145 |
> /home/mkevo/apache-geode-1.15.0-build.0/bin/server4/.
> No missing colocated region found
> {code}
> Start a new server with a name like you rename your working dir from the
> restarted server.
> # start server --name=server5 --server-port=40405
> Now we have the following output:
> {code:java}
> gfsh>list disk-stores
> Member Name | Member Id| Disk Store Name | Disk
> Store ID
> --- | -- | --- |
>
> server1 | 192.168.0.145(server1:16916):41001 | DEFAULT |
> d5d17b43-4a06-408b-917f-08e5b2533ebe
> server2 | 192.168.0.145(server2:17004):41002 | DEFAULT |
> 31d47cb4-718e-4b58-bde3-ae15b4657910
> server3 | 192.168.0.145(server3:17094):41003 | DEFAULT |
> f12850c6-a73b-443e-9ee0-87f0819ae6bc
> server5 | 192.168.0.145(server5:17428):41004 | DEFAULT |
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74
> gfsh>show missing-disk-stores
> Missing Disk Stores
>Disk Store ID | Host | Directory
> | - |
>
> 7a552fb3-e43d-4fa8-baa8-f6dc794cbf74 | 192.168.0.145 |
> /home/mkevo/apache-geode-1.15.0-build.0/bin/server4/.
> No missing colocated region found
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
