[jira] [Commented] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17504004#comment-17504004 ] ASF subversion and git services commented on GEODE-10099: - Commit 82a57a9fd146472b1704652753e68b55a8b9cfd9 in geode's branch refs/heads/support/1.14 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode.git;h=82a57a9 ] GEODE-10099: Add 1.12.9 as old version Adds 1.12.9 to old versions on develop (cherry picked from commit 5243f68505eaca5758c990473b3df527635b25f7) (cherry picked from commit 75145f3347eb3a081f9675de01d63527ba90263f) > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > Labels: pull-request-available > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17504005#comment-17504005 ] ASF subversion and git services commented on GEODE-10099: - Commit 161e612780859283546d56a94006a6d89b8a35d6 in geode's branch refs/heads/support/1.13 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode.git;h=161e612 ] GEODE-10099: Add 1.12.9 as old version Adds 1.12.9 to old versions on develop (cherry picked from commit 5243f68505eaca5758c990473b3df527635b25f7) (cherry picked from commit 75145f3347eb3a081f9675de01d63527ba90263f) > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > Labels: pull-request-available > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17504002#comment-17504002 ] ASF subversion and git services commented on GEODE-10099: - Commit 75145f3347eb3a081f9675de01d63527ba90263f in geode's branch refs/heads/support/1.15 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode.git;h=75145f3 ] GEODE-10099: Add 1.12.9 as old version Adds 1.12.9 to old versions on develop (cherry picked from commit 5243f68505eaca5758c990473b3df527635b25f7) > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > Labels: pull-request-available > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10099: --- Labels: pull-request-available (was: ) > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > Labels: pull-request-available > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503949#comment-17503949 ] ASF subversion and git services commented on GEODE-10099: - Commit b03e9f6e105dbdaebbc7f64ecf173cd3937ff961 in geode's branch refs/heads/support/1.12 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b03e9f6 ] GEODE-10099: Bump version to 1.12.10 As part of the Geode Release Process, the build number must be rolled forward so work can begin on the next release > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503950#comment-17503950 ] ASF subversion and git services commented on GEODE-10099: - Commit 2ed0119fd809d45a1520908009527db8cb0d166a in geode-benchmarks's branch refs/heads/support/1.12 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode-benchmarks.git;h=2ed0119 ] GEODE-10099: Bump version to 1.12.10 As part of the Geode Release Process, the geode-benchmarks build number must be rolled forward as work begins on the next release > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503948#comment-17503948 ] ASF subversion and git services commented on GEODE-10099: - Commit 6388d6170d93d52782a0f831944e54c5cb2f741f in geode's branch refs/heads/support/1.12 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6388d61 ] GEODE-10099: Add 1.12.9 as old version Adds 1.12.9 to old versions on support/1.12 > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503946#comment-17503946 ] ASF subversion and git services commented on GEODE-10099: - Commit 4fd65928a9eeceff51ab856391cdba1edf628ad4 in geode-examples's branch refs/heads/support/1.12 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=4fd6592 ] Revert "GEODE-10099: Set temporary staging repo" The staging repo no longest exists, so set this back to search the default location (mavencentral) > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503947#comment-17503947 ] ASF subversion and git services commented on GEODE-10099: - Commit a68077bc33e874456d42accbd96dea18d31e9b0d in geode-examples's branch refs/heads/support/1.12 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=a68077b ] GEODE-10099: Bump version to 1.12.10 As part of the Geode Release Process, the geode-examples build number must be rolled forward as work begins on the next release > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503942#comment-17503942 ] ASF subversion and git services commented on GEODE-10099: - Commit 7ca174cc4d93dc4099ebba888e538ba90bc3cd5a in geode's branch refs/heads/support/1.12 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7ca174c ] GEODE-10099: update Dockerfile to apache-geode 1.12.9 > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503944#comment-17503944 ] ASF subversion and git services commented on GEODE-10099: - Commit 4b0d9a2e8b4802b8cb856451ab64de0bfa30cc3a in geode-native's branch refs/heads/support/1.12 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=4b0d9a2 ] GEODE-10099: Update Dockerfile and vars Native client hardcodes Geode version to test with in several places. Update native Dockerfile and other variables to apache-geode 1.12.9 > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10080) Upgrade Jedis client in benchmark tests to 4.1.1
[ https://issues.apache.org/jira/browse/GEODE-10080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Zoerner reassigned GEODE-10080: Assignee: Eric Zoerner > Upgrade Jedis client in benchmark tests to 4.1.1 > > > Key: GEODE-10080 > URL: https://issues.apache.org/jira/browse/GEODE-10080 > Project: Geode > Issue Type: Task > Components: benchmarks, redis >Reporter: Eric Zoerner >Assignee: Eric Zoerner >Priority: Major > > Upgrade Jedis client in benchmark tests to 4.1.1. This is necessary in order > to benchmark support for Redis 6.0 in Geode for Redis. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[
https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-10045:
--
Labels: Micrometer blocks-1.15.0 (was: Micrometer)
> Upgrade to Micrometer 2.0
> -
>
> Key: GEODE-10045
> URL: https://issues.apache.org/jira/browse/GEODE-10045
> Project: Geode
> Issue Type: Sub-task
> Components: core
>Affects Versions: 1.14.3
>Reporter: John Blum
>Priority: Blocker
> Labels: Micrometer, blocks-1.15.0
>
> As part of the ongoing story and themes in Spring Framework 6, Spring Data
> 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and
> major topics is Observability (Monitoring with Metrics, Tracing, and so on).
> As part of that effort, Micrometer is undergoing a major revision change from
> 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode
> no longer runs (or even will build) with Micrometer 2.0.
> Either Micrometer should be upgraded to 2.0 (most likely in the next major
> version of Geode, i.e. 2.0) or Micrometer should be an optional dependency,
> perhaps only enabled when Micrometer is on the classpath.
> Still a cleaner separation is needed if [Spring] Apache Geode users require
> and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on
> Micrometer 1.x (currently
> [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231]
> in Apache Geode {{1.14.3}}).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-6183) CI Failure: LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed with ConditionTimeoutException
[ https://issues.apache.org/jira/browse/GEODE-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503926#comment-17503926 ] Geode Integration commented on GEODE-6183: -- Seen in [windows-core-integration-test-openjdk11 #189|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-core-integration-test-openjdk11/builds/189] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0128/test-results/integrationTest/1646864635/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0128/test-artifacts/1646864635/windows-coreintegrationtestfiles-openjdk11-1.16.0-build.0128.tgz]. > CI Failure: > LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed > with ConditionTimeoutException > > > Key: GEODE-6183 > URL: https://issues.apache.org/jira/browse/GEODE-6183 > Project: Geode > Issue Type: Bug > Components: build >Affects Versions: 1.14.0, 1.15.0 >Reporter: Eric Shu >Assignee: Kirk Lund >Priority: Major > Time Spent: 5h 50m > Remaining Estimate: 0h > > Test failed in > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/223 > org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > > startDeletesStaleControlFiles FAILED > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase that > uses org.apache.geode.distributed.LocatorLauncher expected:<[online]> but > was:<[not responding]> within 300 seconds. > Caused by: > org.junit.ComparisonFailure: expected:<[online]> but was:<[not > responding]> -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9880) Cluster with multiple locators in an environment with no host name resolution, leads to null pointer exception
[
https://issues.apache.org/jira/browse/GEODE-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-9880:
-
Labels: blocks-1.12.10 blocks-1.15.0 membership (was: blocks-1.12.10
membership)
> Cluster with multiple locators in an environment with no host name
> resolution, leads to null pointer exception
> --
>
> Key: GEODE-9880
> URL: https://issues.apache.org/jira/browse/GEODE-9880
> Project: Geode
> Issue Type: Bug
> Components: locator, membership
>Affects Versions: 1.12.5
>Reporter: Tigran Ghahramanyan
>Priority: Major
> Labels: blocks-1.12.10, blocks-1.15.0, membership
>
> In our use case we have two locators that are initially configured with IP
> addresses, but _AutoConnectionSourceImpl.UpdateLocatorList()_ flow keeps on
> adding their corresponding host names to the locators list, while these host
> names are not resolvable.
> Later in {_}AutoConnectionSourceImpl.queryLocators(){_}, whenever a client
> tries to use such non resolvable host name to connect to a locator it tries
> to establish a connection to {_}socketaddr=0.0.0.0{_}, as written in
> {_}SocketCreator.connect(){_}. Which seems strange.
> Then, if there is no locator running on the same host, the next locator in
> the list is contacted, until reaching a locator contact configured with IP
> address - which succeeds eventually.
> But, when there happens to be a locator listening on the same host, then we
> have a null pointer exception in the second line below, because _inetadd=null_
> _socket.connect(sockaddr, Math.max(timeout, 0)); // sockaddr=0.0.0.0,
> connects to a locator listening on the same host_
> _configureClientSSLSocket(socket, inetadd.getHostName(), timeout); // inetadd
> = null_
>
> As a result, the cluster comes to a failed state, unable to recover.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (GEODE-10113) CI: AutoConnectionSourceImplTest.queryLocatorsTriesNextLocatorOnSSLExceptions() FAILED
[ https://issues.apache.org/jira/browse/GEODE-10113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Barrett closed GEODE-10113. - > CI: > AutoConnectionSourceImplTest.queryLocatorsTriesNextLocatorOnSSLExceptions() > FAILED > -- > > Key: GEODE-10113 > URL: https://issues.apache.org/jira/browse/GEODE-10113 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Priority: Major > Labels: needsTriage > > > Task :geode-core:test > AutoConnectionSourceImplTest > queryLocatorsTriesNextLocatorOnSSLExceptions() > FAILED > java.lang.AssertionError: > Expecting actual: > Mock for ServerLocationResponse, hashCode: 186159903 > and actual: > null > to refer to the same object > at > org.apache.geode.cache.client.internal.AutoConnectionSourceImplTest.queryLocatorsTriesNextLocatorOnSSLExceptions(AutoConnectionSourceImplTest.java:91) > 7320 tests completed, 1 failed, 11 skipped > It's found in > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-unit-test-openjdk11/builds/187 > It's said to be similar to GEODE-10066 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10113) CI: AutoConnectionSourceImplTest.queryLocatorsTriesNextLocatorOnSSLExceptions() FAILED
[ https://issues.apache.org/jira/browse/GEODE-10113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Barrett resolved GEODE-10113. --- Resolution: Fixed > CI: > AutoConnectionSourceImplTest.queryLocatorsTriesNextLocatorOnSSLExceptions() > FAILED > -- > > Key: GEODE-10113 > URL: https://issues.apache.org/jira/browse/GEODE-10113 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Priority: Major > Labels: needsTriage > > > Task :geode-core:test > AutoConnectionSourceImplTest > queryLocatorsTriesNextLocatorOnSSLExceptions() > FAILED > java.lang.AssertionError: > Expecting actual: > Mock for ServerLocationResponse, hashCode: 186159903 > and actual: > null > to refer to the same object > at > org.apache.geode.cache.client.internal.AutoConnectionSourceImplTest.queryLocatorsTriesNextLocatorOnSSLExceptions(AutoConnectionSourceImplTest.java:91) > 7320 tests completed, 1 failed, 11 skipped > It's found in > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-unit-test-openjdk11/builds/187 > It's said to be similar to GEODE-10066 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10108) Duplicate Ops During GII/Delta Updates
[ https://issues.apache.org/jira/browse/GEODE-10108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503866#comment-17503866 ] ASF subversion and git services commented on GEODE-10108: - Commit 09cd1927a9fe047b222f05075db5247301736710 in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=09cd192 ] GEODE-10108: Add version field to AbstractRedisData and deltas (#7429) This change is necessary because GII can retrieve a value that is currently being updated. This can result in corruption if a Delta change is subsequently applied. - Convert DeltaInfo to an abstract class and add a version field - DeltaTypes indicate whether the type is versioned - Versioning needs to be added to any operations where the application of a Delta is not idempotent. In such cases, the version and data change MUST happen under synchronization. - Update the String APPEND command to use these changes - Other commands will be updated separately. - For subsequent use of versioning, take care that the version is not inadvertently updated as a result of applying a delta change. > Duplicate Ops During GII/Delta Updates > --- > > Key: GEODE-10108 > URL: https://issues.apache.org/jira/browse/GEODE-10108 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Wayne >Assignee: Jens Deppe >Priority: Major > Labels: blocks-1.15.0, pull-request-available > > When Redis commands are ongoing and a server that was previously not hosting > a bucket becomes the host of the primary bucket for a key, there exists a > time window where that server is performing GII but also receiving delta > updates from the previous primary bucket. This can lead to the delta being > applied to a data structure that is already in the “correct” state, resulting > in the command being applied twice. This can result in duplicated appends, > increments/decrements, and in the case of LTRIP and RPOP especially, > IndexOutOfBoundsException on the member applying the delta, as the index to > which the delta refers has already been removed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10055) AbstractLauncher print info and debug with stderr instead of stdout
[
https://issues.apache.org/jira/browse/GEODE-10055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-10055:
--
Labels: pull-request-available (was: needsTriage pull-request-available)
> AbstractLauncher print info and debug with stderr instead of stdout
> ---
>
> Key: GEODE-10055
> URL: https://issues.apache.org/jira/browse/GEODE-10055
> Project: Geode
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.12.8, 1.13.7, 1.14.3
>Reporter: Mario Kevo
>Assignee: Mario Kevo
>Priority: Major
> Labels: pull-request-available
>
> The problem happened with locator/server launcher logs which are printed with
> stderr in both cases, for info and debug.
> {code:java}
> protected void info(final Object message, final Object... args) {
> if (args != null && args.length > 0) {
> System.err.printf(message.toString(), args);
> } else {
> System.err.print(message);
> }
> }
> {code}
> And when it is redirected to some tools it represents it like an error as it
> is printed with stderr, instead of stdout.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10066) SSL handshake failures on 1 locator prevents connection pool from trying other locators
[
https://issues.apache.org/jira/browse/GEODE-10066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-10066:
--
Labels: pull-request-available (was: needsTriage pull-request-available)
> SSL handshake failures on 1 locator prevents connection pool from trying
> other locators
> ---
>
> Key: GEODE-10066
> URL: https://issues.apache.org/jira/browse/GEODE-10066
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.12.9, 1.13.8, 1.14.4, 1.15.0, 1.16.0
>Reporter: Jacob Barrett
>Assignee: Jacob Barrett
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> If an {{SSLException}} is thrown when handshaking with a locator the
> exception is wrapped in an {{IllegalStateException}} that is not caught by
> the connection pool, the stack is blown, and no connections can be
> established. If not wrapped the connection pool will properly try the next
> locator.
> The {{SSLExceptions}} are wrapped in at least
> {{TcpClient.getServerVersion()}} but other locations may exist in this path.
> This method throws {{IOException}} and the {{SSLExceptions}} extend
> {{IOExceptions}} so they should not be wrapped. It probably makes sense to
> split the concern of socket connection from determining the server version in
> {{TcpClient.getServerVersion()}}.
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative names matching IP address 10.2.8.12 found
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1946)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:316)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:310)
> at
> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1639)
> at
> sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:965)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
> at
> org.apache.geode.internal.net.SocketCreator.configureClientSSLSocket(SocketCreator.java:594)
> at
> org.apache.geode.internal.net.SCAdvancedSocketCreator.connect(SCAdvancedSocketCreator.java:83)
> at
> org.apache.geode.distributed.internal.tcpserver.ClusterSocketCreatorImpl.connect(ClusterSocketCreatorImpl.java:96)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpClient.getServerVersion(TcpClient.java:246)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:151)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocatorUsingConnection(AutoConnectionSourceImpl.java:227)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocator(AutoConnectionSourceImpl.java:217)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryLocators(AutoConnectionSourceImpl.java:264)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:176)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:211)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:196)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:190)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:282)
> at
> org.apache.geode.cache.client.internal.PoolImpl.acquireConnection(PoolImpl.java:940)
> at
> org.apache.geode.cache.wan.internal.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:464)
> at
> org.apache.geode.cache.wan.internal.GatewaySenderEventRemoteDispatcher.(GatewaySenderEventRemoteDispatcher.java:105)
> at
> org.apache.geode.cache.wan.internal.parallel.RemoteParallelGatewaySenderEventProcessor.initializeEventDispatcher(RemoteParallelGatewaySenderEventProcessor.java:66)
> at
>
[jira] [Resolved] (GEODE-9967) The Geode wiki page about the "Redis Adaptor" should be updated
[ https://issues.apache.org/jira/browse/GEODE-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne resolved GEODE-9967. -- Resolution: Won't Fix > The Geode wiki page about the "Redis Adaptor" should be updated > --- > > Key: GEODE-9967 > URL: https://issues.apache.org/jira/browse/GEODE-9967 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Eric Zoerner >Assignee: Ray Ingles >Priority: Major > > This wiki page is out of date for the 1.15 release and should be updated: > https://cwiki.apache.org/confluence/display/GEODE/Geode+Redis+Adapter -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9967) The Geode wiki page about the "Redis Adaptor" should be updated
[ https://issues.apache.org/jira/browse/GEODE-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Ingles reassigned GEODE-9967: - Assignee: Ray Ingles > The Geode wiki page about the "Redis Adaptor" should be updated > --- > > Key: GEODE-9967 > URL: https://issues.apache.org/jira/browse/GEODE-9967 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Eric Zoerner >Assignee: Ray Ingles >Priority: Major > > This wiki page is out of date for the 1.15 release and should be updated: > https://cwiki.apache.org/confluence/display/GEODE/Geode+Redis+Adapter -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (GEODE-10092) IllegalArgumentException: Illegal Capacity (with a negative value) thrown from EntriesSet.toArray() in client
[ https://issues.apache.org/jira/browse/GEODE-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503802#comment-17503802 ] Jinmei Liao edited comment on GEODE-10092 at 3/9/22, 7:43 PM: -- The test that failed with the invalid region size log is: RenameDunitTest.givenCrashDuringRename_thenDoesNotLeaveInconsistencies, Note in this test, the negative region size is reported on a server, but the the original ticket is on the client, so this may not be the same code path that caused this problem. was (Author: jinmeiliao): The test that failed with the invalid region size log is: RenameDunitTest.givenCrashDuringRename_thenDoesNotLeaveInconsistencies, > IllegalArgumentException: Illegal Capacity (with a negative value) thrown > from EntriesSet.toArray() in client > - > > Key: GEODE-10092 > URL: https://issues.apache.org/jira/browse/GEODE-10092 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Priority: Major > Labels: needsTriage, pull-request-available > > In some case, we see the following stack trace when executing > entriesSet.toArray() call: Exception java.lang.IllegalArgumentException: > Illegal Capacity: -40 > at java.util.ArrayList.(ArrayList.java:157) > at > org.apache.geode.internal.cache.EntriesSet.toArray(EntriesSet.java:251) > at > org.apache.geode.internal.cache.EntriesSet.toArray(EntriesSet.java:245) > looks like the entriesSet.size() call will sometimes returns a negative value. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (GEODE-10092) IllegalArgumentException: Illegal Capacity (with a negative value) thrown from EntriesSet.toArray() in client
[ https://issues.apache.org/jira/browse/GEODE-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503802#comment-17503802 ] Jinmei Liao edited comment on GEODE-10092 at 3/9/22, 7:42 PM: -- The test that failed with the invalid region size log is: RenameDunitTest.givenCrashDuringRename_thenDoesNotLeaveInconsistencies, was (Author: jinmeiliao): The test that failed with the invalid region size report is: RenameDunitTest.givenCrashDuringRename_thenDoesNotLeaveInconsistencies, > IllegalArgumentException: Illegal Capacity (with a negative value) thrown > from EntriesSet.toArray() in client > - > > Key: GEODE-10092 > URL: https://issues.apache.org/jira/browse/GEODE-10092 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Priority: Major > Labels: needsTriage, pull-request-available > > In some case, we see the following stack trace when executing > entriesSet.toArray() call: Exception java.lang.IllegalArgumentException: > Illegal Capacity: -40 > at java.util.ArrayList.(ArrayList.java:157) > at > org.apache.geode.internal.cache.EntriesSet.toArray(EntriesSet.java:251) > at > org.apache.geode.internal.cache.EntriesSet.toArray(EntriesSet.java:245) > looks like the entriesSet.size() call will sometimes returns a negative value. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10092) IllegalArgumentException: Illegal Capacity (with a negative value) thrown from EntriesSet.toArray() in client
[ https://issues.apache.org/jira/browse/GEODE-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503802#comment-17503802 ] Jinmei Liao commented on GEODE-10092: - The test that failed with the invalid region size report is: RenameDunitTest.givenCrashDuringRename_thenDoesNotLeaveInconsistencies, > IllegalArgumentException: Illegal Capacity (with a negative value) thrown > from EntriesSet.toArray() in client > - > > Key: GEODE-10092 > URL: https://issues.apache.org/jira/browse/GEODE-10092 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Priority: Major > Labels: needsTriage, pull-request-available > > In some case, we see the following stack trace when executing > entriesSet.toArray() call: Exception java.lang.IllegalArgumentException: > Illegal Capacity: -40 > at java.util.ArrayList.(ArrayList.java:157) > at > org.apache.geode.internal.cache.EntriesSet.toArray(EntriesSet.java:251) > at > org.apache.geode.internal.cache.EntriesSet.toArray(EntriesSet.java:245) > looks like the entriesSet.size() call will sometimes returns a negative value. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0
[
https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Blum updated GEODE-10045:
--
Description:
As part of the ongoing story and themes in Spring Framework 6, Spring Data 3.0,
Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and major
topics is Observability (Monitoring with Metrics, Tracing, and so on).
As part of that effort, Micrometer is undergoing a major revision change from
1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode no
longer runs (or even will build) with Micrometer 2.0.
Either Micrometer should be upgraded to 2.0 (most likely in the next major
version of Geode, i.e. 2.0) or Micrometer should be an optional dependency,
perhaps only enabled when Micrometer is on the classpath.
Still a cleaner separation is needed if [Spring] Apache Geode users require and
use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on
Micrometer 1.x (currently
[1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231]
in Apache Geode {{1.14.3}}).
was:
As part of the ongoing story and themes in Spring Framework 6, Spring Data 3.0
and the rest of the Spring portfolio, 1 of the new and major topics is
Observability (Monitoring with Metrics, Tracing, and so on).
As part of that effort, Micrometer is undergoing a major revision change from
1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode no
longer runs (or even will build) with Micrometer 2.0.
Either Micrometer should be upgraded to 2.0 (most likely in the next major
version of Geode, i.e. 2.0) or Micrometer should be an optional dependency,
perhaps only enabled when Micrometer is on the classpath.
Still a cleaner separation is needed if [Spring] Apache Geode users require and
use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on
Micrometer 1.x (currently
[1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231]
in Apache Geode {{1.14.3}}).
> Upgrade to Micrometer 2.0
> -
>
> Key: GEODE-10045
> URL: https://issues.apache.org/jira/browse/GEODE-10045
> Project: Geode
> Issue Type: Sub-task
> Components: core
>Affects Versions: 1.14.3
>Reporter: John Blum
>Priority: Blocker
> Labels: Micrometer
>
> As part of the ongoing story and themes in Spring Framework 6, Spring Data
> 3.0, Spring Boot 3.0 and the rest of the Spring portfolio, 1 of the new and
> major topics is Observability (Monitoring with Metrics, Tracing, and so on).
> As part of that effort, Micrometer is undergoing a major revision change from
> 1.x to 2.0. Many of their APIs have changed, and as a result, Apache Geode
> no longer runs (or even will build) with Micrometer 2.0.
> Either Micrometer should be upgraded to 2.0 (most likely in the next major
> version of Geode, i.e. 2.0) or Micrometer should be an optional dependency,
> perhaps only enabled when Micrometer is on the classpath.
> Still a cleaner separation is needed if [Spring] Apache Geode users require
> and use a newer version of Micrometer (e.g. 2.0) and Apache Geode remains on
> Micrometer 1.x (currently
> [1.6.3|https://github.com/apache/geode/blob/rel/v1.14.3/boms/geode-all-bom/src/test/resources/expected-pom.xml#L226-L231]
> in Apache Geode {{1.14.3}}).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10008) Avoid possible EntryDestroyedException error in wan-copy region command when entry destroyed in partitioned region
[ https://issues.apache.org/jira/browse/GEODE-10008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503751#comment-17503751 ] Geode Integration commented on GEODE-10008: --- Seen on support/1.15 in [distributed-test-openjdk11 #25|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-15-main/jobs/distributed-test-openjdk11/builds/25] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-15-main/1.15.0-build.0913/test-results/distributedTest/1646775199/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-15-main/1.15.0-build.0913/test-artifacts/1646775199/distributedtestfiles-openjdk11-1.15.0-build.0913.tgz]. > Avoid possible EntryDestroyedException error in wan-copy region command when > entry destroyed in partitioned region > -- > > Key: GEODE-10008 > URL: https://issues.apache.org/jira/browse/GEODE-10008 > Project: Geode > Issue Type: Bug > Components: gfsh, wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: blocks-1.15.0, needsTriage, pull-request-available > Fix For: 1.16.0 > > > When the wan-copy region command is executed over a partitioned region, it is > possible that sometimes an EntryDestroyedException error is found if, while > reading the entries from the region, one of them is destroyed. > The error has been seen sometimes when running the following test: > WanCopyRegionCommandDUnitTest. > testSuccessfulExecutionWhileRunningOpsOnRegion(true, true). > > Log of the error: > Multiple Failures (2 failures) > org.opentest4j.AssertionFailedError: [ Member | > Status | Message > -- | -- | > --- > alberto-dell(421543):41010 | ERROR | Execution failed. Error: > org.apache.geode.cache.EntryDestroyedException: 26 > alberto-dell(421504):41009 | OK | Entries copied: 2,977 > alberto-dell(421598):41011 | OK | Entries copied: 3,042 > ] > expected: OK > but was: ERROR > 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-vm6.log' at line 1883 > [error 2022/02/01 08:58:59.046 CET tid=99] > Exception occurred attempting to wan-copy region > java.util.concurrent.ExecutionException: > org.apache.geode.cache.EntryDestroyedException: 26 > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:192) > at > org.apache.geode.cache.wan.internal.WanCopyRegionFunctionService.execute(WanCopyRegionFunctionService.java:90) > at > org.apache.geode.management.internal.cli.functions.WanCopyRegionFunction.executeFunctionInService(WanCopyRegionFunction.java:163) > at > org.apache.geode.management.internal.cli.functions.WanCopyRegionFunction.executeFunction(WanCopyRegionFunction.java:157) > at > org.apache.geode.management.cli.CliFunction.execute(CliFunction.java:37) > at > org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201) > at > org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382) > at > org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:447) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:444) > at > org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:379) > at > org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.apache.geode.cache.EntryDestroyedException: 26 > at > org.apache.geode.internal.cache.NonTXEntry.basicGetEntry(NonTXEntry.java:62) > at > org.apache.geode.internal.cache.NonTXEntry.getRegion(NonTXEntry.java:119) > at > org.apache.geode.internal.cache.NonTXEntry.hashCode(NonTXEntry.java:157) > at java.util.HashMap.hash(HashMap.java:340) > at java.util.HashMap.put(HashMap.java:613) > at java.util.HashSet.add(HashSet.java:220) > at
[jira] [Commented] (GEODE-10103) Rebalance with no setting for include-region doesn't work for subregions
[
https://issues.apache.org/jira/browse/GEODE-10103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503739#comment-17503739
]
ASF subversion and git services commented on GEODE-10103:
-
Commit 8610ee70d470a8b30ab067db912bd0ac345d9df0 in geode's branch
refs/heads/develop from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8610ee7 ]
GEODE-10103: Retrieve full region path names (#7419)
* GEODE-10103: Retrieve full region path names
This commit modifies RebalanceOperationPerformer getMemberRegionList
to invoke listAllRegionPaths instead of listNames.
> Rebalance with no setting for include-region doesn't work for subregions
>
>
> Key: GEODE-10103
> URL: https://issues.apache.org/jira/browse/GEODE-10103
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> Executing a command like this produces no output for the rebalance command
> even though a region exists to rebalance:
> {noformat}
> gfsh -e "connect --locator=localhost[23456]" -e "rebalance"{noformat}
> Output:
> {noformat}
> ./rebalance.sh
> (1) Executing - connect --locator=localhost[23456]
> Connecting to Locator at [host=localhost, port=23456] ..
> Connecting to Manager at [host=192.168.1.5, port=1099] ..
> Successfully connected to: [host=192.168.1.5, port=1099]
> You are connected to a cluster of version: 1.16.0-build.0
> (2) Executing - rebalance{noformat}
> Running from gfsh directly does:
> {noformat}
> gfsh>rebalance
> gfsh> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10116) Enable native Redis TCL tests for List data type
Ray Ingles created GEODE-10116: -- Summary: Enable native Redis TCL tests for List data type Key: GEODE-10116 URL: https://issues.apache.org/jira/browse/GEODE-10116 Project: Geode Issue Type: Improvement Reporter: Ray Ingles The native redis TCL-based test suite has several tests for the List data type, which should be enabled when Geode-for-Redis support is sufficient to support them. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10105) restarting of gateway sender during dispatching of events, causes duplication of events without indication of possibleduplicate
[ https://issues.apache.org/jira/browse/GEODE-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Ivanac reassigned GEODE-10105: Assignee: Mario Ivanac > restarting of gateway sender during dispatching of events, causes duplication > of events without indication of possibleduplicate > --- > > Key: GEODE-10105 > URL: https://issues.apache.org/jira/browse/GEODE-10105 > Project: Geode > Issue Type: Bug > Components: wan >Affects Versions: 1.14.0 >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: needsTriage, pull-request-available > > During dispatching events in parallel gateway sender, if we stop dispatching, > and after some time restart dispatching, multiple duplicate events are > observed on receiving side (without indication possible duplicate). -- This message was sent by Atlassian Jira (v8.20.1#820001)
