[jira] [Created] (GEODE-9591) Native client re-execute function even Function.isHA() is set to false and redundancy in not used on partition region
Jakov Varenina created GEODE-9591: - Summary: Native client re-execute function even Function.isHA() is set to false and redundancy in not used on partition region Key: GEODE-9591 URL: https://issues.apache.org/jira/browse/GEODE-9591 Project: Geode Issue Type: Bug Components: native client Reporter: Jakov Varenina This behavior of native client should be aligned with java client. Java client in this case doesn't re-execute the function, but it trows the exception from the server. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9591) Native client re-execute function even Function.isHA() is set to false and redundancy in not used on partition region
[ https://issues.apache.org/jira/browse/GEODE-9591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakov Varenina reassigned GEODE-9591: - Assignee: Jakov Varenina > Native client re-execute function even Function.isHA() is set to false and > redundancy in not used on partition region > - > > Key: GEODE-9591 > URL: https://issues.apache.org/jira/browse/GEODE-9591 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jakov Varenina >Assignee: Jakov Varenina >Priority: Major > > This behavior of native client should be aligned with java client. Java > client in this case doesn't re-execute the function, but it trows the > exception from the server. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9591) Native client re-execute function even Function.isHA() is set to false and redundancy in not used on partition region
[ https://issues.apache.org/jira/browse/GEODE-9591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakov Varenina updated GEODE-9591: -- Description: This behavior of native client should be aligned with java client. Java client in this case doesn't re-execute the function, but it trows the exception that received from the server. was:This behavior of native client should be aligned with java client. Java client in this case doesn't re-execute the function, but it trows the exception from the server. > Native client re-execute function even Function.isHA() is set to false and > redundancy in not used on partition region > - > > Key: GEODE-9591 > URL: https://issues.apache.org/jira/browse/GEODE-9591 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jakov Varenina >Assignee: Jakov Varenina >Priority: Major > > This behavior of native client should be aligned with java client. Java > client in this case doesn't re-execute the function, but it trows the > exception that received > from the server. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-5782) LauncherMemberMXBeanIntegrationTest can fail intermittently
[
https://issues.apache.org/jira/browse/GEODE-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412673#comment-17412673
]
Geode Integration commented on GEODE-5782:
--
Seen on support/1.12 in [windows-core-integration-test-openjdk8
#34|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-core-integration-test-openjdk8/builds/34]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0280/test-results/integrationTest/1631149143/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0280/test-artifacts/1631149143/windows-coreintegrationtestfiles-openjdk8-1.12.5-build.0280.tgz].
> LauncherMemberMXBeanIntegrationTest can fail intermittently
> ---
>
> Key: GEODE-5782
> URL: https://issues.apache.org/jira/browse/GEODE-5782
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Affects Versions: 1.9.0
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Noticed this failure:
> {noformat}
> org.apache.geode.distributed.LauncherMemberMXBeanIntegrationTest >
> showOSMetrics_reconstructsOSMetricsFromCompositeDataType FAILED
> org.junit.ComparisonFailure: expected:<204.[68]> but was:<204.[55]>
> 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.distributed.LauncherMemberMXBeanIntegrationTest.showOSMetrics_reconstructsOSMetricsFromCompositeDataType(LauncherMemberMXBeanIntegrationTest.java:143)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9576) InternalFunctionInvocationTargetException when executing single hop function all buckets
[
https://issues.apache.org/jira/browse/GEODE-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412706#comment-17412706
]
ASF GitHub Bot commented on GEODE-9576:
---
echobravopapa commented on a change in pull request #864:
URL: https://github.com/apache/geode-native/pull/864#discussion_r705531306
##
File path: cppcache/src/ClientMetadataService.cpp
##
@@ -578,12 +579,10 @@ ClientMetadataService::pruneNodes(
const auto locations = metadata->adviseServerLocations(bucketId);
if (locations.size() == 0) {
LOGDEBUG(
- "ClientMetadataService::pruneNodes Since no server location "
- "available for bucketId = %d putting it into "
- "bucketSetWithoutServer ",
+ "ClientMetadataService::pruneNodes Use non single-hop path "
+ "since no server location is available for bucketId = %d",
bucketId);
- bucketSetWithoutServer.insert(bucketId);
- continue;
+ return nullptr;
Review comment:
I'd like to see an integration test that exposes the issue being fixed...
--
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
> InternalFunctionInvocationTargetException when executing single hop function
> all buckets
>
>
> Key: GEODE-9576
> URL: https://issues.apache.org/jira/browse/GEODE-9576
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Jakov Varenina
>Assignee: Jakov Varenina
>Priority: Major
> Labels: pull-request-available
>
> *InternalFunctionInvocationTargetException: Multiple target nodes found for
> single hop operation* occurs on native client when executing function in a
> single hop manner for all buckets during the period when client bucket
> metadata doesn't contain all buckets locations.
> Java client in this case executes functions in non single hop manner until it
> receives locations of all buckets on servers. The solution in native client
> would be to implement the same handling as in java client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9576) InternalFunctionInvocationTargetException when executing single hop function all buckets
[
https://issues.apache.org/jira/browse/GEODE-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412718#comment-17412718
]
ASF GitHub Bot commented on GEODE-9576:
---
pivotal-jbarrett commented on a change in pull request #864:
URL: https://github.com/apache/geode-native/pull/864#discussion_r705544017
##
File path: cppcache/integration/test/FunctionExecutionTest.cpp
##
@@ -175,6 +181,58 @@ TEST(FunctionExecutionTest,
cache.close();
}
+void populateRegion(const std::shared_ptr ®ion) {
+ for (int i = 0; i < 113; i++) {
+region->put("KEY--" + std::to_string(i), "VALUE--" + std::to_string(i));
+ }
+}
+
+TEST(FunctionExecutionTest, FunctionExecutionSingleHopNonHA) {
+ Cluster cluster{
+ LocatorCount{1}, ServerCount{3},
+ CacheXMLFiles(
+ {std::string(getFrameworkString(FrameworkVariable::TestCacheXmlDir))
+
+ "/func_cacheserver1_pool_nonHA.xml",
+ std::string(getFrameworkString(FrameworkVariable::TestCacheXmlDir))
+
+ "/func_cacheserver2_pool_nonHA.xml",
+ std::string(getFrameworkString(FrameworkVariable::TestCacheXmlDir))
+
+ "/func_cacheserver3_pool_nonHA.xml"})};
+
+ cluster.start([&]() {
+cluster.getGfsh()
+.deploy()
+.jar(getFrameworkString(FrameworkVariable::JavaObjectJarPath))
+.execute();
+ });
+
+ auto cache = CacheFactory().create();
+ auto poolFactory = cache.getPoolManager().createFactory();
+
+ cluster.applyLocators(poolFactory);
+
+ auto pool =
+ poolFactory.setPRSingleHopEnabled(true).setRetryAttempts(0).create(
+ "pool");
+
+ auto region = cache.createRegionFactory(RegionShortcut::PROXY)
+.setPoolName("pool")
+.create("partition_region");
+
+ populateRegion(region);
+
+ for (int i = 0; i < 30; i++) {
+auto functionService = FunctionService::onRegion(region);
+auto rc =
+functionService.withCollector(std::make_shared())
Review comment:
Unfortunately this is notoriously hard to test. PR metadata updates are
asynchronous and there isn't any hooks to trigger when an update is complete.
You may want to start with adding that function. The downside to that is to use
them in an integration tests we would have to export those functions and we try
not to export internal/test symbols if we can. Perhaps it might be easier to
create a unit test that asserts this part of the function execution logic does
the correct thing when the metadata is incomplete. It should be easier to tease
out a function that is given the metadata and makes this decisions and then
write a test to verify the expected behaviors.
--
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
> InternalFunctionInvocationTargetException when executing single hop function
> all buckets
>
>
> Key: GEODE-9576
> URL: https://issues.apache.org/jira/browse/GEODE-9576
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Jakov Varenina
>Assignee: Jakov Varenina
>Priority: Major
> Labels: pull-request-available
>
> *InternalFunctionInvocationTargetException: Multiple target nodes found for
> single hop operation* occurs on native client when executing function in a
> single hop manner for all buckets during the period when client bucket
> metadata doesn't contain all buckets locations.
> Java client in this case executes functions in non single hop manner until it
> receives locations of all buckets on servers. The solution in native client
> would be to implement the same handling as in java client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9576) InternalFunctionInvocationTargetException when executing single hop function all buckets
[
https://issues.apache.org/jira/browse/GEODE-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412733#comment-17412733
]
ASF GitHub Bot commented on GEODE-9576:
---
echobravopapa commented on a change in pull request #864:
URL: https://github.com/apache/geode-native/pull/864#discussion_r705553536
##
File path: cppcache/integration/test/FunctionExecutionTest.cpp
##
@@ -175,6 +181,58 @@ TEST(FunctionExecutionTest,
cache.close();
}
+void populateRegion(const std::shared_ptr ®ion) {
+ for (int i = 0; i < 113; i++) {
+region->put("KEY--" + std::to_string(i), "VALUE--" + std::to_string(i));
+ }
+}
+
+TEST(FunctionExecutionTest, FunctionExecutionSingleHopNonHA) {
+ Cluster cluster{
+ LocatorCount{1}, ServerCount{3},
+ CacheXMLFiles(
+ {std::string(getFrameworkString(FrameworkVariable::TestCacheXmlDir))
+
+ "/func_cacheserver1_pool_nonHA.xml",
+ std::string(getFrameworkString(FrameworkVariable::TestCacheXmlDir))
+
+ "/func_cacheserver2_pool_nonHA.xml",
+ std::string(getFrameworkString(FrameworkVariable::TestCacheXmlDir))
+
+ "/func_cacheserver3_pool_nonHA.xml"})};
+
+ cluster.start([&]() {
+cluster.getGfsh()
+.deploy()
+.jar(getFrameworkString(FrameworkVariable::JavaObjectJarPath))
+.execute();
+ });
+
+ auto cache = CacheFactory().create();
+ auto poolFactory = cache.getPoolManager().createFactory();
+
+ cluster.applyLocators(poolFactory);
+
+ auto pool =
+ poolFactory.setPRSingleHopEnabled(true).setRetryAttempts(0).create(
+ "pool");
+
+ auto region = cache.createRegionFactory(RegionShortcut::PROXY)
+.setPoolName("pool")
+.create("partition_region");
+
+ populateRegion(region);
+
+ for (int i = 0; i < 30; i++) {
+auto functionService = FunctionService::onRegion(region);
+auto rc =
+functionService.withCollector(std::make_shared())
Review comment:
A similarly difficult issue was tested and fixed in recent months,
regarding incorrect EventIds etc... which fixed a "fix" that was making native
operate at parity with java client, but the initial fix was incomplete...
I'm sure @pdxcodemonkey has more to say about this...
--
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
> InternalFunctionInvocationTargetException when executing single hop function
> all buckets
>
>
> Key: GEODE-9576
> URL: https://issues.apache.org/jira/browse/GEODE-9576
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Jakov Varenina
>Assignee: Jakov Varenina
>Priority: Major
> Labels: pull-request-available
>
> *InternalFunctionInvocationTargetException: Multiple target nodes found for
> single hop operation* occurs on native client when executing function in a
> single hop manner for all buckets during the period when client bucket
> metadata doesn't contain all buckets locations.
> Java client in this case executes functions in non single hop manner until it
> receives locations of all buckets on servers. The solution in native client
> would be to implement the same handling as in java client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9592) CI Failure: FixedPartitioningDUnitTest > testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed
Jens Deppe created GEODE-9592:
-
Summary: CI Failure: FixedPartitioningDUnitTest >
testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed
Key: GEODE-9592
URL: https://issues.apache.org/jira/browse/GEODE-9592
Project: Geode
Issue Type: Test
Components: core
Affects Versions: 1.12.4
Reporter: Jens Deppe
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/37.1
{noformat}
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest >
testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$468/1983677783.run
in VM 1 running on Host 00080b53bda3 with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed(FixedPartitioningDUnitTest.java:1496)
Caused by:
java.lang.AssertionError: expected:<1> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningTestBase.checkStartingBucketIDs_Nodeup(FixedPartitioningTestBase.java:1182)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.lambda$testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed$bb17a952$13(FixedPartitioningDUnitTest.java:1496)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0279/test-results/distributedTest/1631145014/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0279/test-artifacts/1631145014/distributedtestfiles-openjdk8-1.12.5-build.0279.tgz
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9592) CI Failure: FixedPartitioningDUnitTest > testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed
[
https://issues.apache.org/jira/browse/GEODE-9592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe updated GEODE-9592:
--
Description:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/37.1
{noformat}
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest >
testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$468/1983677783.run
in VM 1 running on Host 00080b53bda3 with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed(FixedPartitioningDUnitTest.java:1496)
Caused by:
java.lang.AssertionError: expected:<1> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningTestBase.checkStartingBucketIDs_Nodeup(FixedPartitioningTestBase.java:1182)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.lambda$testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed$bb17a952$13(FixedPartitioningDUnitTest.java:1496)
{noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0279/test-results/distributedTest/1631145014/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0279/test-artifacts/1631145014/distributedtestfiles-openjdk8-1.12.5-build.0279.tgz
was:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/37.1
{noformat}
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest >
testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$468/1983677783.run
in VM 1 running on Host 00080b53bda3 with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed(FixedPartitioningDUnitTest.java:1496)
Caused by:
java.lang.AssertionError: expected:<1> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningTestBase.checkStartingBucketIDs_Nodeup(FixedPartitioningTestBase.java:1182)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.lambda$testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed$bb17a952$13(FixedPartitioningDUnitTest.java:1496)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0279/test-results/distributedTest/1631145014/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0279/test-artifacts/1631145014/distributedtestfiles-openjdk8-1.12.5-build.0279.tgz
{noformat}
> CI Failure: FixedPartitioningDUnitTest >
> testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed
> -
>
> Key: GEODE-9592
> URL: https://issues.apache.org/jira/browse/GEODE-9592
> Project: Geode
> Issue Type: Test
> Components: core
>Affects Versions: 1.12.4
>Reporter: Jens Deppe
>Priority: Major
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/37.1
> {noformat}
[jira] [Commented] (GEODE-9592) CI Failure: FixedPartitioningDUnitTest > testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed
[
https://issues.apache.org/jira/browse/GEODE-9592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412745#comment-17412745
]
Geode Integration commented on GEODE-9592:
--
Seen on support/1.12 in [distributed-test-openjdk8
#37.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/37.1]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0279/test-results/distributedTest/1631145014/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0279/test-artifacts/1631145014/distributedtestfiles-openjdk8-1.12.5-build.0279.tgz].
> CI Failure: FixedPartitioningDUnitTest >
> testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed
> -
>
> Key: GEODE-9592
> URL: https://issues.apache.org/jira/browse/GEODE-9592
> Project: Geode
> Issue Type: Test
> Components: core
>Affects Versions: 1.12.4
>Reporter: Jens Deppe
>Priority: Major
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/37.1
> {noformat}
> org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest
> > testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$468/1983677783.run
> in VM 1 running on Host 00080b53bda3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at
> org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed(FixedPartitioningDUnitTest.java:1496)
> Caused by:
> java.lang.AssertionError: expected:<1> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at
> org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningTestBase.checkStartingBucketIDs_Nodeup(FixedPartitioningTestBase.java:1182)
> at
> org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.lambda$testPut_ValidateDataOnMember_MultiplePrimaries_Datastore_CacheClosed$bb17a952$13(FixedPartitioningDUnitTest.java:1496)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0279/test-results/distributedTest/1631145014/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0279/test-artifacts/1631145014/distributedtestfiles-openjdk8-1.12.5-build.0279.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9593) CI Failure: TxCommitMessageBCServerToServerViaPoolTxBothTest > test[11]
[
https://issues.apache.org/jira/browse/GEODE-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412750#comment-17412750
]
Geode Integration commented on GEODE-9593:
--
Seen on support/1.13 in [upgrade-test-openjdk11
#48|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/48]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0592/test-results/upgradeTest/1631146868/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0592/test-artifacts/1631146868/upgradetestfiles-openjdk11-1.13.5-build.0592.tgz].
> CI Failure: TxCommitMessageBCServerToServerViaPoolTxBothTest > test[11]
> ---
>
> Key: GEODE-9593
> URL: https://issues.apache.org/jira/browse/GEODE-9593
> Project: Geode
> Issue Type: Test
> Components: transactions
>Reporter: Jens Deppe
>Priority: Major
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/48
> {noformat}
> org.apache.geode.internal.cache.TxCommitMessageBCServerToServerViaPoolTxBothTest
> > test[11] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.TxCommitMessageBCTestBase$$Lambda$178/0x000100876c40.call
> in VM 1 running on Host d7d5657db523 with 5 VMs
> Caused by:
> org.apache.geode.GemFireConfigException: Unable to join the
> distributed system. Operation either timed out, was stopped or Locator does
> not exist.
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0592/test-results/upgradeTest/1631146868/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0592/test-artifacts/1631146868/upgradetestfiles-openjdk11-1.13.5-build.0592.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9593) CI Failure: TxCommitMessageBCServerToServerViaPoolTxBothTest > test[11]
Jens Deppe created GEODE-9593:
-
Summary: CI Failure:
TxCommitMessageBCServerToServerViaPoolTxBothTest > test[11]
Key: GEODE-9593
URL: https://issues.apache.org/jira/browse/GEODE-9593
Project: Geode
Issue Type: Test
Components: transactions
Reporter: Jens Deppe
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/48
{noformat}
org.apache.geode.internal.cache.TxCommitMessageBCServerToServerViaPoolTxBothTest
> test[11] FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.TxCommitMessageBCTestBase$$Lambda$178/0x000100876c40.call
in VM 1 running on Host d7d5657db523 with 5 VMs
Caused by:
org.apache.geode.GemFireConfigException: Unable to join the distributed
system. Operation either timed out, was stopped or Locator does not exist.
{noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0592/test-results/upgradeTest/1631146868/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0592/test-artifacts/1631146868/upgradetestfiles-openjdk11-1.13.5-build.0592.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9576) InternalFunctionInvocationTargetException when executing single hop function all buckets
[
https://issues.apache.org/jira/browse/GEODE-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412758#comment-17412758
]
ASF GitHub Bot commented on GEODE-9576:
---
pdxcodemonkey commented on a change in pull request #864:
URL: https://github.com/apache/geode-native/pull/864#discussion_r705589383
##
File path: cppcache/integration/test/FunctionExecutionTest.cpp
##
@@ -175,6 +181,58 @@ TEST(FunctionExecutionTest,
cache.close();
}
+void populateRegion(const std::shared_ptr ®ion) {
+ for (int i = 0; i < 113; i++) {
+region->put("KEY--" + std::to_string(i), "VALUE--" + std::to_string(i));
+ }
+}
+
+TEST(FunctionExecutionTest, FunctionExecutionSingleHopNonHA) {
+ Cluster cluster{
+ LocatorCount{1}, ServerCount{3},
+ CacheXMLFiles(
+ {std::string(getFrameworkString(FrameworkVariable::TestCacheXmlDir))
+
+ "/func_cacheserver1_pool_nonHA.xml",
+ std::string(getFrameworkString(FrameworkVariable::TestCacheXmlDir))
+
+ "/func_cacheserver2_pool_nonHA.xml",
+ std::string(getFrameworkString(FrameworkVariable::TestCacheXmlDir))
+
+ "/func_cacheserver3_pool_nonHA.xml"})};
+
+ cluster.start([&]() {
+cluster.getGfsh()
+.deploy()
+.jar(getFrameworkString(FrameworkVariable::JavaObjectJarPath))
+.execute();
+ });
+
+ auto cache = CacheFactory().create();
+ auto poolFactory = cache.getPoolManager().createFactory();
+
+ cluster.applyLocators(poolFactory);
+
+ auto pool =
+ poolFactory.setPRSingleHopEnabled(true).setRetryAttempts(0).create(
+ "pool");
+
+ auto region = cache.createRegionFactory(RegionShortcut::PROXY)
+.setPoolName("pool")
+.create("partition_region");
+
+ populateRegion(region);
+
+ for (int i = 0; i < 30; i++) {
+auto functionService = FunctionService::onRegion(region);
+auto rc =
+functionService.withCollector(std::make_shared())
Review comment:
The `putAllAndVerifyKeysExist` test, added in this PR:
https://github.com/apache/geode-native/pull/784/files
(very nearly?) guarantees a state in which not all metadata buckets are
present on the client, so I kind of expect executing a single-hop function
instead of the `putAll` call in this test code would reproduce. This test has
been _very_ reliable, so I wouldn't expect to have a lot of issues with flaky
behavior with respect to metadata updates.
--
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
> InternalFunctionInvocationTargetException when executing single hop function
> all buckets
>
>
> Key: GEODE-9576
> URL: https://issues.apache.org/jira/browse/GEODE-9576
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Jakov Varenina
>Assignee: Jakov Varenina
>Priority: Major
> Labels: pull-request-available
>
> *InternalFunctionInvocationTargetException: Multiple target nodes found for
> single hop operation* occurs on native client when executing function in a
> single hop manner for all buckets during the period when client bucket
> metadata doesn't contain all buckets locations.
> Java client in this case executes functions in non single hop manner until it
> receives locations of all buckets on servers. The solution in native client
> would be to implement the same handling as in java client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9402) Automatic Reconnect Failure: Address already in use
[
https://issues.apache.org/jira/browse/GEODE-9402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernest Burghardt reassigned GEODE-9402:
---
Assignee: (was: Nabarun Nag)
> Automatic Reconnect Failure: Address already in use
> ---
>
> Key: GEODE-9402
> URL: https://issues.apache.org/jira/browse/GEODE-9402
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Juan Ramos
>Priority: Major
> Attachments: cluster_logs_gke_latest_54.zip, cluster_logs_pks_121.zip
>
>
> There are 2 locators and 4 servers during the test, once they're all up and
> running the test drops the network connectivity between all members to
> generate a full network partition and cause all members to shutdown and go
> into reconnect mode. Upon reaching the mentioned state, the test
> automatically restores the network connectivity and expects all members to
> automatically go up again and re-form the distributed system.
> This works fine most of the time, and we see every member successfully
> reconnecting to the distributed system:
> {noformat}
> [info 2021/06/23 15:58:12.981 GMT gemfire-cluster-locator-0
> tid=0x87] Reconnect completed.
> [info 2021/06/23 15:58:14.726 GMT gemfire-cluster-locator-1
> tid=0x86] Reconnect completed.
> [info 2021/06/23 15:58:46.702 GMT gemfire-cluster-server-0
> tid=0x94] Reconnect completed.
> [info 2021/06/23 15:58:46.485 GMT gemfire-cluster-server-1
> tid=0x96] Reconnect completed.
> [info 2021/06/23 15:58:46.273 GMT gemfire-cluster-server-2
> tid=0x97] Reconnect completed.
> [info 2021/06/23 15:58:46.902 GMT gemfire-cluster-server-3
> tid=0x95] Reconnect completed.
> {noformat}
> In some rare occasions, though, one of the servers fails during the reconnect
> phase with the following exception:
> {noformat}
> [error 2021/06/09 18:48:52.872 GMT gemfire-cluster-server-1
> tid=0x91] Cache initialization for GemFireCache[id = 575310555; isClosing =
> false; isShutDownAll = false; created = Wed Jun 09 18:46:49 GMT 2021; server
> = false; copyOnRead = false; lockLease = 120; lockTimeout = 60] failed
> because:
> org.apache.geode.GemFireIOException: While starting cache server CacheServer
> on port=40404 client subscription config policy=none client subscription
> config capacity=1 client subscription config overflow directory=.
> at
> org.apache.geode.internal.cache.xmlcache.CacheCreation.startCacheServers(CacheCreation.java:800)
> at
> org.apache.geode.internal.cache.xmlcache.CacheCreation.create(CacheCreation.java:599)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.create(CacheXmlParser.java:339)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.loadCacheXml(GemFireCacheImpl.java:4207)
> at
> org.apache.geode.internal.cache.ClusterConfigurationLoader.applyClusterXmlConfiguration(ClusterConfigurationLoader.java:197)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.applyJarAndXmlFromClusterConfig(GemFireCacheImpl.java:1497)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1449)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2668)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2426)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1277)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:2315)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership.uncleanShutdown(GMSMembership.java:1183)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$forceDisconnect$0(GMSMembership.java:1807)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.net.BindException: Address already in use (Bind failed)
> at java.base/java.net.PlainSocketImpl.socketBind(Native Method)
> at
> java.base/java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:436)
> at java.base/java.net.ServerSocket.bind(ServerSocket.java:395)
> at
> org.apache.geode.internal.net.SCClusterSocketCreator.createServerSocket(SCClusterSocketCreator.java:70)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:529)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.(AcceptorImpl.java:573)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorBuilder.create(AcceptorBuilder.java:291)
>
[jira] [Commented] (GEODE-9554) Rebalancing a region with multiple redundancy zones can fail
[ https://issues.apache.org/jira/browse/GEODE-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412776#comment-17412776 ] ASF subversion and git services commented on GEODE-9554: Commit d1d605b24787698c5d8f47b8538808d6b990c0a4 in geode's branch refs/heads/develop from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d1d605b ] GEODE-9554: Change up the rebalance calls to use new canDelete call (#6845) GEODE-9554: Change up the rebalance calls to use new canDelete call If there is no redundancy zone, exit and allow delete Adding xml files to git Adding xml files to git Added new tests > Rebalancing a region with multiple redundancy zones can fail > > > Key: GEODE-9554 > URL: https://issues.apache.org/jira/browse/GEODE-9554 > Project: Geode > Issue Type: Bug > Components: core >Affects Versions: 1.12.4, 1.13.4, 1.14.0, 1.15.0 >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Labels: pull-request-available > > When attempting to rebalance a region with multiple redundancy zones, the > code does not distinguish between zones when deleting redundant bucket > copies. This can mean that a bucket from a different zone gets deleted > leaving the servers in a state of reduced redundancy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9139) SSLException in starting up a Locator
[
https://issues.apache.org/jira/browse/GEODE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernest Burghardt resolved GEODE-9139.
-
Assignee: Kamilla Aslami (was: Ernest Burghardt)
Resolution: Fixed
> SSLException in starting up a Locator
> -
>
> Key: GEODE-9139
> URL: https://issues.apache.org/jira/browse/GEODE-9139
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Reporter: Bruce J Schuchardt
>Assignee: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> If you start up a locator using its host name, without a domain name, as a
> bind address you may get an SSLException in the form
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative DNS name matching hostname.domainname found
> {noformat}
> The LocatorLauncher and InternalLocator throw away the bind address string
> and later do a reverse lookup to find the fully qualified hostname to use in
> endpoint identification matching.If the locator's own TLS certificate
> doesn't have the fully qualified name in it as a Subject Alternate Name the
> connection that the Locator makes to its own location service will fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9577) **PSETEX** and **SETEX** Commands Supported
[ https://issues.apache.org/jira/browse/GEODE-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9577: -- Labels: pull-request-available redis (was: redis) > **PSETEX** and **SETEX** Commands Supported > --- > > Key: GEODE-9577 > URL: https://issues.apache.org/jira/browse/GEODE-9577 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Eric Zoerner >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available, redis > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers for the following commands: > PSETEX and SETEX > A.C. > Unit/integration tests for both Geode and native Redis passing > DUNIT tests passing > README/redis_api_for_geode.html.md.erb updated to make command "supported" > or > 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.3.4#803005)
[jira] [Commented] (GEODE-9577) **PSETEX** and **SETEX** Commands Supported
[ https://issues.apache.org/jira/browse/GEODE-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412782#comment-17412782 ] ASF subversion and git services commented on GEODE-9577: Commit 9242a1fde07e01f942b714de6625733726023b23 in geode's branch refs/heads/develop from Eric Zoerner [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9242a1f ] GEODE-9577: Make PSETEX and SETEX supported commands (#6841) > **PSETEX** and **SETEX** Commands Supported > --- > > Key: GEODE-9577 > URL: https://issues.apache.org/jira/browse/GEODE-9577 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Eric Zoerner >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available, redis > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers for the following commands: > PSETEX and SETEX > A.C. > Unit/integration tests for both Geode and native Redis passing > DUNIT tests passing > README/redis_api_for_geode.html.md.erb updated to make command "supported" > or > 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.3.4#803005)
[jira] [Updated] (GEODE-9396) Upgrades using SSL fail with mismatch of hostname in certificates
[ https://issues.apache.org/jira/browse/GEODE-9396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Burghardt updated GEODE-9396: Labels: pull-request-available release-blocker (was: pull-request-available) > Upgrades using SSL fail with mismatch of hostname in certificates > - > > Key: GEODE-9396 > URL: https://issues.apache.org/jira/browse/GEODE-9396 > Project: Geode > Issue Type: Bug > Components: membership >Affects Versions: 1.15.0 >Reporter: Ernest Burghardt >Assignee: Kamilla Aslami >Priority: Major > Labels: pull-request-available, release-blocker > > When upgrading from a previous version (prior to 1.14) the ssl handshake will > fail to complete in cases where the Certificate contains a symbolic name that > doesn't match the hostname used by the sslengine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9170) Support ZGC
[ https://issues.apache.org/jira/browse/GEODE-9170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-9170: - Labels: (was: blocks-1.15.0) > Support ZGC > --- > > Key: GEODE-9170 > URL: https://issues.apache.org/jira/browse/GEODE-9170 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Priority: Major > > Our performance research indicated that throughput improved by 13% by using > the Z Garbage Collector. > In addition to use of ZGC, we also need to rework the ResourceManager. > The ResourceManager is monitoring the MBeans related to GC and trying to > guestimate how much memory is being used. Based upon heap usage, and user > configured thresholds, the user can configure eviction. > Exceeding the Critical threshold will stop puts. When can add support for > ZGC by looking at the correct MBeans for ZGC. Alternatively, we can stop > using the ResourceManager and find a new way of monitoring heap. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9170) Support ZGC
[ https://issues.apache.org/jira/browse/GEODE-9170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412826#comment-17412826 ] Wayne commented on GEODE-9170: -- We will not be able to deliver this feature until Geode can render under JDK 16 or later. > Support ZGC > --- > > Key: GEODE-9170 > URL: https://issues.apache.org/jira/browse/GEODE-9170 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Priority: Major > > Our performance research indicated that throughput improved by 13% by using > the Z Garbage Collector. > In addition to use of ZGC, we also need to rework the ResourceManager. > The ResourceManager is monitoring the MBeans related to GC and trying to > guestimate how much memory is being used. Based upon heap usage, and user > configured thresholds, the user can configure eviction. > Exceeding the Critical threshold will stop puts. When can add support for > ZGC by looking at the correct MBeans for ZGC. Alternatively, we can stop > using the ResourceManager and find a new way of monitoring heap. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9038) CI Failure: ShutdownAllDUnitTest > testShutdownAllWithMembersWaiting fails with suspect strings
[ https://issues.apache.org/jira/browse/GEODE-9038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412864#comment-17412864 ] Geode Integration commented on GEODE-9038: -- Seen in [distributed-test-openjdk8 #175|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk8/builds/175] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0473/test-results/distributedTest/1631222909/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0473/test-artifacts/1631222909/distributedtestfiles-openjdk8-1.15.0-build.0473.tgz]. > CI Failure: ShutdownAllDUnitTest > testShutdownAllWithMembersWaiting fails > with suspect strings > --- > > Key: GEODE-9038 > URL: https://issues.apache.org/jira/browse/GEODE-9038 > Project: Geode > Issue Type: Bug >Reporter: John Hutchison >Priority: Major > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/78 > org.apache.geode.internal.cache.partitioned.ShutdownAllDUnitTest > > testShutdownAllWithMembersWaiting 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-vm0.log' at line 1246 > [fatal 2021/03/15 19:27:44.311 GMT > tid=1461] While pushing message unexpected exception during data cleanup" level WARNING> to recipients: > <172.17.0.7(179):41003> > org.apache.geode.alerting.internal.spi.AlertingIOException: > java.io.IOException: Cannot form connection to alert listener > 172.17.0.7(179):41003 > at > org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:884) > at > org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:464) > at > org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:280) > at > org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:187) > at > org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:523) > at > org.apache.geode.distributed.internal.DistributionImpl.directChannelSend(DistributionImpl.java:346) > at > org.apache.geode.distributed.internal.DistributionImpl.send(DistributionImpl.java:291) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2053) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1981) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2018) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1083) > at > org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$null$0(ClusterAlertMessaging.java:103) > at > org.apache.geode.alerting.internal.spi.AlertingAction.execute(AlertingAction.java:34) > at > org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$sendAlert$1(ClusterAlertMessaging.java:81) > at > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: java.io.IOException: Cannot form connection to alert listener > 172.17.0.7(179):41003 > at > org.apache.geode.internal.tcp.ConnectionTable.getSharedConnection(ConnectionTable.java:406) > at > org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:574) > at > org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:803) > ... 18 more -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9340) Benchmark instability in PartitionedPutLongBenchmark
[
https://issues.apache.org/jira/browse/GEODE-9340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412867#comment-17412867
]
Geode Integration commented on GEODE-9340:
--
Seen in [benchmark-base
#174|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/174].
> Benchmark instability in PartitionedPutLongBenchmark
>
>
> Key: GEODE-9340
> URL: https://issues.apache.org/jira/browse/GEODE-9340
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.15.0
>Reporter: Sarah Abbey
>Assignee: Hale Bales
>Priority: Major
> Labels: pull-request-available
>
> PartitionedPutLongBenchmark failed in CI
> (https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/6):
> {code:java}
> This is ITERATION 1 of benchmarking against baseline.
> P2pPartitionedGetBenchmark avg ops/sec
> Baseline:825011.38 Test:835847.67 Difference: +1.3%
> avg latency
> Baseline:871392.31 Test:859444.66 Difference: -1.4%
> P2pPartitionedPutBenchmark avg ops/sec
> Baseline:123838.43 Test:122686.30 Difference: -0.9%
> avg latency
> Baseline: 6015719.73 Test: 6119472.19 Difference: +1.7%
> P2pPartitionedPutBytesBenchmark avg ops/sec
> Baseline:174887.77 Test:171040.93 Difference: -2.2%
> avg latency
> Baseline: 4145337.60 Test: 4236159.60 Difference: +2.2%
> PartitionedFunctionExecutionBenchmark avg ops/sec
> Baseline:248635.36 Test:261498.94 Difference: +5.2%
> avg latency
> Baseline:867122.63 Test:824550.34 Difference: -4.9%
> PartitionedFunctionExecutionWithArgumentsBenchmark avg ops/sec
> Baseline:280071.19 Test:275305.31 Difference: -1.7%
> avg latency
> Baseline: 1026643.12 Test: 1044307.43 Difference: +1.7%
> PartitionedFunctionExecutionWithFiltersBenchmark avg ops/sec
> Baseline:301416.23 Test:304317.30 Difference: +1.0%
> avg latency
> Baseline: 1908390.88 Test: 1890040.46 Difference: -1.0%
> PartitionedGetBenchmark avg ops/sec
> Baseline:790800.52 Test:784514.74 Difference: -0.8%
> avg latency
> Baseline:908357.58 Test:915790.96 Difference: +0.8%
> PartitionedGetLongBenchmark avg ops/sec
> Baseline: 1020821.32 Test:996529.93 Difference: -2.4%
> avg latency
> Baseline:703761.09 Test:720744.36 Difference: +2.4%
> PartitionedGetStringBenchmark avg ops/sec
> Baseline: 1028992.93 Test: 1010447.47 Difference: -1.8%
> avg latency
> Baseline:698009.55 Test:710765.29 Difference: +1.8%
> PartitionedIndexedQueryBenchmark avg ops/sec
> Baseline: 30868.78 Test: 31478.90 Difference: +2.0%
> avg latency
> Baseline: 18670093.21 Test: 18278083.16 Difference: -2.1%
> PartitionedNonIndexedQueryBenchmark avg ops/sec
> Baseline:99.45 Test: 101.97 Difference: +2.5%
> avg latency
> Baseline: 723415530.75 Test: 705653061.86 Difference: -2.5%
> PartitionedPutAllBenchmark avg ops/sec
> Baseline: 7921.61 Test: 7816.66 Difference: -1.3%
> avg latency
> Baseline: 18172638.37 Test: 18416169.28 Difference: +1.3%
> PartitionedPutAllLongBenchmark avg ops/sec
> Baseline: 1379.53 Test: 1169.16 Difference: -15.2%
> avg latency
> Baseline: 105140260.44 Test: 123722914.94 Difference: +17.7%
> PartitionedPutBenchmark avg ops/sec
> Baseline:474986.11 Test:467924.19 Difference: -1.5%
>
[jira] [Commented] (GEODE-9340) Benchmark instability in PartitionedPutLongBenchmark
[
https://issues.apache.org/jira/browse/GEODE-9340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412868#comment-17412868
]
Geode Integration commented on GEODE-9340:
--
Seen in [benchmark-base
#172|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/172].
> Benchmark instability in PartitionedPutLongBenchmark
>
>
> Key: GEODE-9340
> URL: https://issues.apache.org/jira/browse/GEODE-9340
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.15.0
>Reporter: Sarah Abbey
>Assignee: Hale Bales
>Priority: Major
> Labels: pull-request-available
>
> PartitionedPutLongBenchmark failed in CI
> (https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/6):
> {code:java}
> This is ITERATION 1 of benchmarking against baseline.
> P2pPartitionedGetBenchmark avg ops/sec
> Baseline:825011.38 Test:835847.67 Difference: +1.3%
> avg latency
> Baseline:871392.31 Test:859444.66 Difference: -1.4%
> P2pPartitionedPutBenchmark avg ops/sec
> Baseline:123838.43 Test:122686.30 Difference: -0.9%
> avg latency
> Baseline: 6015719.73 Test: 6119472.19 Difference: +1.7%
> P2pPartitionedPutBytesBenchmark avg ops/sec
> Baseline:174887.77 Test:171040.93 Difference: -2.2%
> avg latency
> Baseline: 4145337.60 Test: 4236159.60 Difference: +2.2%
> PartitionedFunctionExecutionBenchmark avg ops/sec
> Baseline:248635.36 Test:261498.94 Difference: +5.2%
> avg latency
> Baseline:867122.63 Test:824550.34 Difference: -4.9%
> PartitionedFunctionExecutionWithArgumentsBenchmark avg ops/sec
> Baseline:280071.19 Test:275305.31 Difference: -1.7%
> avg latency
> Baseline: 1026643.12 Test: 1044307.43 Difference: +1.7%
> PartitionedFunctionExecutionWithFiltersBenchmark avg ops/sec
> Baseline:301416.23 Test:304317.30 Difference: +1.0%
> avg latency
> Baseline: 1908390.88 Test: 1890040.46 Difference: -1.0%
> PartitionedGetBenchmark avg ops/sec
> Baseline:790800.52 Test:784514.74 Difference: -0.8%
> avg latency
> Baseline:908357.58 Test:915790.96 Difference: +0.8%
> PartitionedGetLongBenchmark avg ops/sec
> Baseline: 1020821.32 Test:996529.93 Difference: -2.4%
> avg latency
> Baseline:703761.09 Test:720744.36 Difference: +2.4%
> PartitionedGetStringBenchmark avg ops/sec
> Baseline: 1028992.93 Test: 1010447.47 Difference: -1.8%
> avg latency
> Baseline:698009.55 Test:710765.29 Difference: +1.8%
> PartitionedIndexedQueryBenchmark avg ops/sec
> Baseline: 30868.78 Test: 31478.90 Difference: +2.0%
> avg latency
> Baseline: 18670093.21 Test: 18278083.16 Difference: -2.1%
> PartitionedNonIndexedQueryBenchmark avg ops/sec
> Baseline:99.45 Test: 101.97 Difference: +2.5%
> avg latency
> Baseline: 723415530.75 Test: 705653061.86 Difference: -2.5%
> PartitionedPutAllBenchmark avg ops/sec
> Baseline: 7921.61 Test: 7816.66 Difference: -1.3%
> avg latency
> Baseline: 18172638.37 Test: 18416169.28 Difference: +1.3%
> PartitionedPutAllLongBenchmark avg ops/sec
> Baseline: 1379.53 Test: 1169.16 Difference: -15.2%
> avg latency
> Baseline: 105140260.44 Test: 123722914.94 Difference: +17.7%
> PartitionedPutBenchmark avg ops/sec
> Baseline:474986.11 Test:467924.19 Difference: -1.5%
>
[jira] [Commented] (GEODE-9583) CI Failure: DiskDistributedNoAckAsyncOverflowRegionDUnitTest > testNoDataSerializer fails with NotSerializableException
[
https://issues.apache.org/jira/browse/GEODE-9583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412875#comment-17412875
]
Jianxia Chen commented on GEODE-9583:
-
>From the logs
>[http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0466/test-results/distributedTest/1630758210/classes/org.apache.geode.cache30.DiskDistributedNoAckAsyncOverflowRegionDUnitTest.html#testNoDataSerializer]
It shows that the test `unregisterAllSerializers()` on all vms including vm2,
before vm2 `FlusherThread.doAsyncFlush()`. So the `FlusherThread` throws
`NotSerializableException`. Because it still need the `LongWrapperSerializer`
at this time.
> CI Failure: DiskDistributedNoAckAsyncOverflowRegionDUnitTest >
> testNoDataSerializer fails with NotSerializableException
> ---
>
> Key: GEODE-9583
> URL: https://issues.apache.org/jira/browse/GEODE-9583
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI
>
> This test run
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1549
> failed with:
> {code:java}
> org.apache.geode.cache30.DiskDistributedNoAckAsyncOverflowRegionDUnitTest >
> testNoDataSerializer 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-vm2.log' at line 493
> [error 2021/09/04 11:19:51.404 UTC DiskDistributedNoAckAsyncOverflowRegionDUnitTest_testNoDataSerializer>
> tid=1025] A DiskAccessException has occurred while writing to the disk for
> disk store
> DiskDistributedNoAckAsyncOverflowRegionDUnitTest_testNoDataSerializer. The
> cache will be closed.
> org.apache.geode.cache.DiskAccessException: For DiskStore:
> DiskDistributedNoAckAsyncOverflowRegionDUnitTest_testNoDataSerializer: Fatal
> error from asynchronous flusher thread, caused by
> org.apache.geode.SerializationException: An IOException was thrown while
> serializing.
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.doAsyncFlush(DiskStoreImpl.java:1796)
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.run(DiskStoreImpl.java:1710)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.geode.SerializationException: An IOException was
> thrown while serializing.
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2107)
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2090)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.createValueWrapper(DiskEntry.java:755)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.createValueWrapperFromEntry(DiskEntry.java:791)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeToDisk(DiskEntry.java:809)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeToDisk(DiskEntry.java:799)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeEntryToDisk(DiskEntry.java:1465)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.doAsyncFlush(DiskEntry.java:1417)
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.doAsyncFlush(DiskStoreImpl.java:1752)
> ... 2 more
> Caused by: java.io.NotSerializableException:
> org.apache.geode.cache30.MultiVMRegionTestCase$LongWrapper
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at
> org.apache.geode.internal.InternalDataSerializer.writeSerializableObject(InternalDataSerializer.java:2187)
> at
> org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2056)
> at org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2839)
> at
> org.apache.geode.internal.util.BlobHelper.serializeToBlob(BlobHelper.java:54)
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2105)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9583) CI Failure: DiskDistributedNoAckAsyncOverflowRegionDUnitTest > testNoDataSerializer fails with NotSerializableException
[
https://issues.apache.org/jira/browse/GEODE-9583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9583:
--
Labels: GeodeOperationAPI pull-request-available (was: GeodeOperationAPI)
> CI Failure: DiskDistributedNoAckAsyncOverflowRegionDUnitTest >
> testNoDataSerializer fails with NotSerializableException
> ---
>
> Key: GEODE-9583
> URL: https://issues.apache.org/jira/browse/GEODE-9583
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> This test run
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1549
> failed with:
> {code:java}
> org.apache.geode.cache30.DiskDistributedNoAckAsyncOverflowRegionDUnitTest >
> testNoDataSerializer 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-vm2.log' at line 493
> [error 2021/09/04 11:19:51.404 UTC DiskDistributedNoAckAsyncOverflowRegionDUnitTest_testNoDataSerializer>
> tid=1025] A DiskAccessException has occurred while writing to the disk for
> disk store
> DiskDistributedNoAckAsyncOverflowRegionDUnitTest_testNoDataSerializer. The
> cache will be closed.
> org.apache.geode.cache.DiskAccessException: For DiskStore:
> DiskDistributedNoAckAsyncOverflowRegionDUnitTest_testNoDataSerializer: Fatal
> error from asynchronous flusher thread, caused by
> org.apache.geode.SerializationException: An IOException was thrown while
> serializing.
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.doAsyncFlush(DiskStoreImpl.java:1796)
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.run(DiskStoreImpl.java:1710)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.geode.SerializationException: An IOException was
> thrown while serializing.
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2107)
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2090)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.createValueWrapper(DiskEntry.java:755)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.createValueWrapperFromEntry(DiskEntry.java:791)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeToDisk(DiskEntry.java:809)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeToDisk(DiskEntry.java:799)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeEntryToDisk(DiskEntry.java:1465)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.doAsyncFlush(DiskEntry.java:1417)
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.doAsyncFlush(DiskStoreImpl.java:1752)
> ... 2 more
> Caused by: java.io.NotSerializableException:
> org.apache.geode.cache30.MultiVMRegionTestCase$LongWrapper
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at
> org.apache.geode.internal.InternalDataSerializer.writeSerializableObject(InternalDataSerializer.java:2187)
> at
> org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2056)
> at org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2839)
> at
> org.apache.geode.internal.util.BlobHelper.serializeToBlob(BlobHelper.java:54)
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2105)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9589) SETRANGE command supported
[ https://issues.apache.org/jira/browse/GEODE-9589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9589: -- Labels: pull-request-available (was: ) > SETRANGE command supported > -- > > Key: GEODE-9589 > URL: https://issues.apache.org/jira/browse/GEODE-9589 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Eric Zoerner >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers for the following command: > - SETRANGE > **A.C.** > - Unit/integration tests for both Geode and native Redis passing > - DUNIT tests passing > - README/redis_api_for_geode.html.md.erb updated to make command "supported" > *or* > - Stories in the backlog to fix the identified issues (with JIRA tickets) > and problem tests ignored -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6588) Cleanup internal use of generics and other static analyzer warnings [PERMANENT]
[ https://issues.apache.org/jira/browse/GEODE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412903#comment-17412903 ] ASF subversion and git services commented on GEODE-6588: Commit 151d8c1afe968196d1ffe1f6ef13182af6697bca in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=151d8c1 ] GEODE-6588: Cleanup Connection * Cleanup Connection and related classes. > Cleanup internal use of generics and other static analyzer warnings > [PERMANENT] > --- > > Key: GEODE-6588 > URL: https://issues.apache.org/jira/browse/GEODE-6588 > Project: Geode > Issue Type: Task >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 8h 40m > Remaining Estimate: 0h > > Use generics where possible. > Cleanup other static analyzer issues along the way. > Generally make the IntelliJ analyzer gutter less cluttered. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-5994) Add a service to contend for CPUs for testing purposes
[ https://issues.apache.org/jira/browse/GEODE-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412923#comment-17412923 ] ASF subversion and git services commented on GEODE-5994: Commit 7b924b5ccef4646f28615bab290447824f9f9f45 in geode's branch refs/heads/develop from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7b924b5 ] GEODE-5994: Cleanup from some additional review comments (#6852) > Add a service to contend for CPUs for testing purposes > -- > > Key: GEODE-5994 > URL: https://issues.apache.org/jira/browse/GEODE-5994 > Project: Geode > Issue Type: Improvement >Reporter: Dale Emery >Assignee: Dale Emery >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Some test failures are easier to reproduce and diagnose when there is heavy > contention for CPUs. > Add a simple utility to contend for CPUs. This can be added to a test while > debugging, and removed after the problem has been diagnosed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9554) Rebalancing a region with multiple redundancy zones can fail
[ https://issues.apache.org/jira/browse/GEODE-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412924#comment-17412924 ] ASF subversion and git services commented on GEODE-9554: Commit 142e06fe001aae428c32ec602992e45bcefa2259 in geode's branch refs/heads/support/1.14 from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=142e06f ] GEODE-9554: Change up the rebalance calls to use new canDelete call (#6845) (#6853) GEODE-9554: Change up the rebalance calls to use new canDelete call If there is no redundancy zone, exit and allow delete Adding xml files to git Adding xml files to git Added new tests (cherry picked from commit d1d605b24787698c5d8f47b8538808d6b990c0a4) > Rebalancing a region with multiple redundancy zones can fail > > > Key: GEODE-9554 > URL: https://issues.apache.org/jira/browse/GEODE-9554 > Project: Geode > Issue Type: Bug > Components: core >Affects Versions: 1.12.4, 1.13.4, 1.14.0, 1.15.0 >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Labels: pull-request-available > > When attempting to rebalance a region with multiple redundancy zones, the > code does not distinguish between zones when deleting redundant bucket > copies. This can mean that a bucket from a different zone gets deleted > leaving the servers in a state of reduced redundancy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-5994) Add a service to contend for CPUs for testing purposes
[ https://issues.apache.org/jira/browse/GEODE-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412925#comment-17412925 ] ASF subversion and git services commented on GEODE-5994: Commit 69ca9cdf75904f70d6272286f4322ba90ee8bfa3 in geode's branch refs/heads/support/1.14 from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=69ca9cd ] GEODE-5994: Cleanup from some additional review comments (#6852) (cherry picked from commit 7b924b5ccef4646f28615bab290447824f9f9f45) > Add a service to contend for CPUs for testing purposes > -- > > Key: GEODE-5994 > URL: https://issues.apache.org/jira/browse/GEODE-5994 > Project: Geode > Issue Type: Improvement >Reporter: Dale Emery >Assignee: Dale Emery >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Some test failures are easier to reproduce and diagnose when there is heavy > contention for CPUs. > Add a simple utility to contend for CPUs. This can be added to a test while > debugging, and removed after the problem has been diagnosed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9554) Rebalancing a region with multiple redundancy zones can fail
[ https://issues.apache.org/jira/browse/GEODE-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412954#comment-17412954 ] ASF subversion and git services commented on GEODE-9554: Commit d94aa6431c4f19167feea417be4739c6746ab4e3 in geode's branch refs/heads/support/1.13 from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d94aa64 ] GEODE-9554 backport (#6856) * GEODE-9554: Change up the rebalance calls to use new canDelete call (#6845) (#6853) GEODE-9554: Change up the rebalance calls to use new canDelete call If there is no redundancy zone, exit and allow delete Adding xml files to git Adding xml files to git Added new tests (cherry picked from commit d1d605b24787698c5d8f47b8538808d6b990c0a4) (cherry picked from commit 142e06fe001aae428c32ec602992e45bcefa2259) * GEODE-5994: Cleanup from some additional review comments (#6852) (cherry picked from commit 7b924b5ccef4646f28615bab290447824f9f9f45) (cherry picked from commit 69ca9cdf75904f70d6272286f4322ba90ee8bfa3) > Rebalancing a region with multiple redundancy zones can fail > > > Key: GEODE-9554 > URL: https://issues.apache.org/jira/browse/GEODE-9554 > Project: Geode > Issue Type: Bug > Components: core >Affects Versions: 1.12.4, 1.13.4, 1.14.0, 1.15.0 >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Labels: pull-request-available > > When attempting to rebalance a region with multiple redundancy zones, the > code does not distinguish between zones when deleting redundant bucket > copies. This can mean that a bucket from a different zone gets deleted > leaving the servers in a state of reduced redundancy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-5994) Add a service to contend for CPUs for testing purposes
[ https://issues.apache.org/jira/browse/GEODE-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412955#comment-17412955 ] ASF subversion and git services commented on GEODE-5994: Commit d94aa6431c4f19167feea417be4739c6746ab4e3 in geode's branch refs/heads/support/1.13 from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d94aa64 ] GEODE-9554 backport (#6856) * GEODE-9554: Change up the rebalance calls to use new canDelete call (#6845) (#6853) GEODE-9554: Change up the rebalance calls to use new canDelete call If there is no redundancy zone, exit and allow delete Adding xml files to git Adding xml files to git Added new tests (cherry picked from commit d1d605b24787698c5d8f47b8538808d6b990c0a4) (cherry picked from commit 142e06fe001aae428c32ec602992e45bcefa2259) * GEODE-5994: Cleanup from some additional review comments (#6852) (cherry picked from commit 7b924b5ccef4646f28615bab290447824f9f9f45) (cherry picked from commit 69ca9cdf75904f70d6272286f4322ba90ee8bfa3) > Add a service to contend for CPUs for testing purposes > -- > > Key: GEODE-5994 > URL: https://issues.apache.org/jira/browse/GEODE-5994 > Project: Geode > Issue Type: Improvement >Reporter: Dale Emery >Assignee: Dale Emery >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Some test failures are easier to reproduce and diagnose when there is heavy > contention for CPUs. > Add a simple utility to contend for CPUs. This can be added to a test while > debugging, and removed after the problem has been diagnosed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
