[jira] [Updated] (GEODE-10378) CI spend optimization
[ https://issues.apache.org/jira/browse/GEODE-10378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10378: --- Labels: pull-request-available (was: ) > CI spend optimization > - > > Key: GEODE-10378 > URL: https://issues.apache.org/jira/browse/GEODE-10378 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Robert Houghton >Priority: Major > Labels: pull-request-available > > Optimize CI/PR spending. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10378) CI spend optimization
Robert Houghton created GEODE-10378: --- Summary: CI spend optimization Key: GEODE-10378 URL: https://issues.apache.org/jira/browse/GEODE-10378 Project: Geode Issue Type: Task Components: ci Reporter: Robert Houghton Optimize CI/PR spending. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10216) Add test for existence of VM stats
[
https://issues.apache.org/jira/browse/GEODE-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hale Bales resolved GEODE-10216.
Resolution: Fixed
> Add test for existence of VM stats
> --
>
> Key: GEODE-10216
> URL: https://issues.apache.org/jira/browse/GEODE-10216
> Project: Geode
> Issue Type: Test
> Components: statistics
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Assignee: Hale Bales
>Priority: Major
> Labels: pull-request-available
>
> When we started running with JDK 11, a couple of stats went missing (fdsOpen
> and fdLimit). This was resolved by adding the following line to test.gradle:
> {code:java}
> "--add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED",
> {code}
> This change was not tested. Add a test so that if something similar happens
> in the future, we will know about it before a customer has an issue.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[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 ssl (was: blocks-1.12.10
pull-request-available ssl)
> 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
>Reporter: Jacob Barrett
>Assignee: Jacob Barrett
>Priority: Major
> Labels: pull-request-available, ssl
> Fix For: 1.15.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] [Updated] (GEODE-10377) Add getter for CacheServiceProfile list to CacheDistributionAdvisor
[ https://issues.apache.org/jira/browse/GEODE-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Ingles updated GEODE-10377: --- Labels: blocks-1.15.0 needsTriage (was: needsTriage) > Add getter for CacheServiceProfile list to CacheDistributionAdvisor > --- > > Key: GEODE-10377 > URL: https://issues.apache.org/jira/browse/GEODE-10377 > Project: Geode > Issue Type: New Feature > Components: core >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Priority: Major > Labels: blocks-1.15.0, needsTriage > > Clients of CacheDistributionAdvisor could use this feature to determine > features of members of the cluster. For example, the version of extensions on > other members could be determined, enhancing forward and backward > compatibility to simplify rolling upgrades of extensions. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10377) Add getter for CacheServiceProfile list to CacheDistributionAdvisor
[ https://issues.apache.org/jira/browse/GEODE-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Ingles updated GEODE-10377: --- Labels: needsTriage (was: ) > Add getter for CacheServiceProfile list to CacheDistributionAdvisor > --- > > Key: GEODE-10377 > URL: https://issues.apache.org/jira/browse/GEODE-10377 > Project: Geode > Issue Type: New Feature > Components: core >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Priority: Major > Labels: needsTriage > > Clients of CacheDistributionAdvisor could use this feature to determine > features of members of the cluster. For example, the version of extensions on > other members could be determined, enhancing forward and backward > compatibility to simplify rolling upgrades of extensions. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10377) Add getter for CacheServiceProfile list to CacheDistributionAdvisor
Ray Ingles created GEODE-10377: -- Summary: Add getter for CacheServiceProfile list to CacheDistributionAdvisor Key: GEODE-10377 URL: https://issues.apache.org/jira/browse/GEODE-10377 Project: Geode Issue Type: New Feature Components: core Affects Versions: 1.15.0 Reporter: Ray Ingles Clients of CacheDistributionAdvisor could use this feature to determine features of members of the cluster. For example, the version of extensions on other members could be determined, enhancing forward and backward compatibility to simplify rolling upgrades of extensions. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10376) Client event processing waits for event registrations to finish.
[
https://issues.apache.org/jira/browse/GEODE-10376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-10376:
--
Labels: (was: needsTriage)
> Client event processing waits for event registrations to finish.
> --
>
> Key: GEODE-10376
> URL: https://issues.apache.org/jira/browse/GEODE-10376
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.16.0
>Reporter: Anilkumar Gingade
>Priority: Major
>
> Currently while processing the events from server the client event processing
> (Cache Client Updater) thread will wait for event registrations to finish;
> this will slowdown the event processing and may cause event build of on
> server.
> The code in question:
> {code:java}
> In CacheClientUpdater.processMessage():
> // Wait for the previously failed cache client updater
> // to finish. This will avoid out of order messages.
> waitForFailedUpdater();
> cache.waitForRegisterInterestsInProgress();
> {code}
> We need to see if "waitForInterestRegistration" needs to be done if there is
> no failure in updater thread.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (GEODE-10376) Client event processing waits for event registrations to finish
[
https://issues.apache.org/jira/browse/GEODE-10376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-10376:
--
Summary: Client event processing waits for event registrations to finish
(was: Client event processing waits for event registrations to finish. )
> Client event processing waits for event registrations to finish
> ---
>
> Key: GEODE-10376
> URL: https://issues.apache.org/jira/browse/GEODE-10376
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.16.0
>Reporter: Anilkumar Gingade
>Priority: Major
>
> Currently while processing the events from server the client event processing
> (Cache Client Updater) thread will wait for event registrations to finish;
> this will slowdown the event processing and may cause event build of on
> server.
> The code in question:
> {code:java}
> In CacheClientUpdater.processMessage():
> // Wait for the previously failed cache client updater
> // to finish. This will avoid out of order messages.
> waitForFailedUpdater();
> cache.waitForRegisterInterestsInProgress();
> {code}
> We need to see if "waitForInterestRegistration" needs to be done if there is
> no failure in updater thread.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (GEODE-10376) Client event processing waits for event registrations to finish.
Anilkumar Gingade created GEODE-10376:
-
Summary: Client event processing waits for event registrations to
finish.
Key: GEODE-10376
URL: https://issues.apache.org/jira/browse/GEODE-10376
Project: Geode
Issue Type: Bug
Components: client/server
Affects Versions: 1.16.0
Reporter: Anilkumar Gingade
Currently while processing the events from server the client event processing
(Cache Client Updater) thread will wait for event registrations to finish; this
will slowdown the event processing and may cause event build of on server.
The code in question:
{code:java}
In CacheClientUpdater.processMessage():
// Wait for the previously failed cache client updater
// to finish. This will avoid out of order messages.
waitForFailedUpdater();
cache.waitForRegisterInterestsInProgress();
{code}
We need to see if "waitForInterestRegistration" needs to be done if there is no
failure in updater thread.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (GEODE-10376) Client event processing waits for event registrations to finish.
[
https://issues.apache.org/jira/browse/GEODE-10376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10376:
--
Labels: needsTriage (was: )
> Client event processing waits for event registrations to finish.
> --
>
> Key: GEODE-10376
> URL: https://issues.apache.org/jira/browse/GEODE-10376
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.16.0
>Reporter: Anilkumar Gingade
>Priority: Major
> Labels: needsTriage
>
> Currently while processing the events from server the client event processing
> (Cache Client Updater) thread will wait for event registrations to finish;
> this will slowdown the event processing and may cause event build of on
> server.
> The code in question:
> {code:java}
> In CacheClientUpdater.processMessage():
> // Wait for the previously failed cache client updater
> // to finish. This will avoid out of order messages.
> waitForFailedUpdater();
> cache.waitForRegisterInterestsInProgress();
> {code}
> We need to see if "waitForInterestRegistration" needs to be done if there is
> no failure in updater thread.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (GEODE-10375) REST management discovery endpoint reports incorrect version
[ https://issues.apache.org/jira/browse/GEODE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-10375. -- Fix Version/s: 1.15.0 1.16.0 Resolution: Fixed > REST management discovery endpoint reports incorrect version > > > Key: GEODE-10375 > URL: https://issues.apache.org/jira/browse/GEODE-10375 > Project: Geode > Issue Type: Bug > Components: rest (admin) >Affects Versions: 1.15.0 >Reporter: Owen Nichols >Assignee: Jinmei Liao >Priority: Major > Labels: blocks-1.15.0, needsTriage, pull-request-available > Fix For: 1.15.0, 1.16.0 > > > prior to GEODE-10312, metadata about the management API url (obtained from > /management) correctly reported /v1/api-docs) > now that we have switched from swagger to springdoc it should now report > /v3/api-docs > see hardcoded value > [here|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/java/org/apache/geode/management/internal/rest/controllers/DocLinksController.java#L38] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10375) REST management discovery endpoint reports incorrect version
[ https://issues.apache.org/jira/browse/GEODE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552925#comment-17552925 ] ASF subversion and git services commented on GEODE-10375: - Commit c30c3ab60e31af26859f474e5200e31c80a23315 in geode's branch refs/heads/support/1.15 from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c30c3ab60e ] GEODE-10375: update supported api docs link (#7794) (cherry picked from commit e0f20a529c8ef961e7038b4f4235a76411ff317e) > REST management discovery endpoint reports incorrect version > > > Key: GEODE-10375 > URL: https://issues.apache.org/jira/browse/GEODE-10375 > Project: Geode > Issue Type: Bug > Components: rest (admin) >Affects Versions: 1.15.0 >Reporter: Owen Nichols >Assignee: Jinmei Liao >Priority: Major > Labels: blocks-1.15.0, needsTriage, pull-request-available > > prior to GEODE-10312, metadata about the management API url (obtained from > /management) correctly reported /v1/api-docs) > now that we have switched from swagger to springdoc it should now report > /v3/api-docs > see hardcoded value > [here|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/java/org/apache/geode/management/internal/rest/controllers/DocLinksController.java#L38] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10375) REST management discovery endpoint reports incorrect version
[ https://issues.apache.org/jira/browse/GEODE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552924#comment-17552924 ] ASF subversion and git services commented on GEODE-10375: - Commit e0f20a529c8ef961e7038b4f4235a76411ff317e in geode's branch refs/heads/develop from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e0f20a529c ] GEODE-10375: update supported api docs link (#7794) > REST management discovery endpoint reports incorrect version > > > Key: GEODE-10375 > URL: https://issues.apache.org/jira/browse/GEODE-10375 > Project: Geode > Issue Type: Bug > Components: rest (admin) >Affects Versions: 1.15.0 >Reporter: Owen Nichols >Assignee: Jinmei Liao >Priority: Major > Labels: blocks-1.15.0, needsTriage, pull-request-available > > prior to GEODE-10312, metadata about the management API url (obtained from > /management) correctly reported /v1/api-docs) > now that we have switched from swagger to springdoc it should now report > /v3/api-docs > see hardcoded value > [here|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/java/org/apache/geode/management/internal/rest/controllers/DocLinksController.java#L38] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-6504) CI: RegionExpirationIntegrationTest > increaseRegionTtl[EMPTY] FAILED
[
https://issues.apache.org/jira/browse/GEODE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552908#comment-17552908
]
ASF subversion and git services commented on GEODE-6504:
Commit 2e7a4fa99ad7bc637e0ba1c5623d8694d2fda341 in geode's branch
refs/heads/develop from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2e7a4fa99a ]
GEODE-6504: Instant class used. (#7779)
* Using instant class instead of nanos.
* Nanos is not updated that often hence not proper resolution.
> CI: RegionExpirationIntegrationTest > increaseRegionTtl[EMPTY] FAILED
> -
>
> Key: GEODE-6504
> URL: https://issues.apache.org/jira/browse/GEODE-6504
> Project: Geode
> Issue Type: Bug
> Components: expiration
>Affects Versions: 1.13.0, 1.14.0, 1.15.0
>Reporter: Mark Hanson
>Assignee: Nabarun Nag
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Attachments: RegionExpirationIntegrationTest.log
>
>
> CI failure: see attached log.
>
> Failed on WindowsIntegrationTestOpenJDK11
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/272]
> {noformat}
> org.apache.geode.cache.RegionExpirationIntegrationTest >
> increaseRegionTtl[EMPTY] FAILED
> java.lang.AssertionError:
> Expecting:
> <7L>
> to be greater than or equal to:
> <8L>
> at
> org.apache.geode.cache.RegionExpirationIntegrationTest.increaseRegionTtl(RegionExpirationIntegrationTest.java:88)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (GEODE-10373) CI Failures: Windows geode-lucene:integrationTest hitting OOM cause CI test run to timeout
[ https://issues.apache.org/jira/browse/GEODE-10373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-10373: -- Labels: (was: needsTriage) > CI Failures: Windows geode-lucene:integrationTest hitting OOM cause CI test > run to timeout > -- > > Key: GEODE-10373 > URL: https://issues.apache.org/jira/browse/GEODE-10373 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Eric Shu >Assignee: Robert Houghton >Priority: Major > > LuceneIndexCommandsWithReindexAllowedIntegrationTest > > whenLuceneReindexingInProgressThenListIndexCommandMustExecuteSuccessfully > FAILED > java.lang.OutOfMemoryError: Java heap space -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (GEODE-10375) REST management discovery endpoint reports incorrect version
[ https://issues.apache.org/jira/browse/GEODE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-10375: --- Assignee: Jinmei Liao (was: Patrick Johnsn) > REST management discovery endpoint reports incorrect version > > > Key: GEODE-10375 > URL: https://issues.apache.org/jira/browse/GEODE-10375 > Project: Geode > Issue Type: Bug > Components: rest (admin) >Affects Versions: 1.15.0 >Reporter: Owen Nichols >Assignee: Jinmei Liao >Priority: Major > Labels: blocks-1.15.0, needsTriage, pull-request-available > > prior to GEODE-10312, metadata about the management API url (obtained from > /management) correctly reported /v1/api-docs) > now that we have switched from swagger to springdoc it should now report > /v3/api-docs > see hardcoded value > [here|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/java/org/apache/geode/management/internal/rest/controllers/DocLinksController.java#L38] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10375) REST management discovery endpoint reports incorrect version
[ https://issues.apache.org/jira/browse/GEODE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10375: --- Labels: blocks-1.15.0 needsTriage pull-request-available (was: blocks-1.15.0 needsTriage) > REST management discovery endpoint reports incorrect version > > > Key: GEODE-10375 > URL: https://issues.apache.org/jira/browse/GEODE-10375 > Project: Geode > Issue Type: Bug > Components: rest (admin) >Affects Versions: 1.15.0 >Reporter: Owen Nichols >Assignee: Patrick Johnsn >Priority: Major > Labels: blocks-1.15.0, needsTriage, pull-request-available > > prior to GEODE-10312, metadata about the management API url (obtained from > /management) correctly reported /v1/api-docs) > now that we have switched from swagger to springdoc it should now report > /v3/api-docs > see hardcoded value > [here|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/java/org/apache/geode/management/internal/rest/controllers/DocLinksController.java#L38] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (GEODE-10375) REST management discovery endpoint reports incorrect version
[ https://issues.apache.org/jira/browse/GEODE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Johnsn reassigned GEODE-10375: -- Assignee: Patrick Johnsn > REST management discovery endpoint reports incorrect version > > > Key: GEODE-10375 > URL: https://issues.apache.org/jira/browse/GEODE-10375 > Project: Geode > Issue Type: Bug > Components: rest (admin) >Affects Versions: 1.15.0 >Reporter: Owen Nichols >Assignee: Patrick Johnsn >Priority: Major > Labels: blocks-1.15.0, needsTriage > > prior to GEODE-10312, metadata about the management API url (obtained from > /management) correctly reported /v1/api-docs) > now that we have switched from swagger to springdoc it should now report > /v3/api-docs > see hardcoded value > [here|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/java/org/apache/geode/management/internal/rest/controllers/DocLinksController.java#L38] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10375) REST management discovery endpoint reports incorrect version
[ https://issues.apache.org/jira/browse/GEODE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-10375: - Labels: blocks-1.15.0 needsTriage (was: needsTriage) > REST management discovery endpoint reports incorrect version > > > Key: GEODE-10375 > URL: https://issues.apache.org/jira/browse/GEODE-10375 > Project: Geode > Issue Type: Bug > Components: rest (admin) >Affects Versions: 1.15.0 >Reporter: Owen Nichols >Priority: Major > Labels: blocks-1.15.0, needsTriage > > prior to GEODE-10312, metadata about the management API url (obtained from > /management) correctly reported /v1/api-docs) > now that we have switched from swagger to springdoc it should now report > /v3/api-docs > see hardcoded value > [here|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/java/org/apache/geode/management/internal/rest/controllers/DocLinksController.java#L38] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10375) REST management discovery endpoint reports incorrect version
[ https://issues.apache.org/jira/browse/GEODE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10375: -- Labels: needsTriage (was: ) > REST management discovery endpoint reports incorrect version > > > Key: GEODE-10375 > URL: https://issues.apache.org/jira/browse/GEODE-10375 > Project: Geode > Issue Type: Bug > Components: rest (admin) >Affects Versions: 1.15.0 >Reporter: Owen Nichols >Priority: Major > Labels: needsTriage > > prior to GEODE-10312, metadata about the management API url (obtained from > /management) correctly reported /v1/api-docs) > now that we have switched from swagger to springdoc it should now report > /v3/api-docs > see hardcoded value > [here|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/java/org/apache/geode/management/internal/rest/controllers/DocLinksController.java#L38] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10375) REST management discovery endpoint reports incorrect version
Owen Nichols created GEODE-10375: Summary: REST management discovery endpoint reports incorrect version Key: GEODE-10375 URL: https://issues.apache.org/jira/browse/GEODE-10375 Project: Geode Issue Type: Bug Components: rest (admin) Affects Versions: 1.15.0 Reporter: Owen Nichols prior to GEODE-10312, metadata about the management API url (obtained from /management) correctly reported /v1/api-docs) now that we have switched from swagger to springdoc it should now report /v3/api-docs see hardcoded value [here|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/java/org/apache/geode/management/internal/rest/controllers/DocLinksController.java#L38] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10329) CI Failure: PersistentPartitionedRegionDistributedTest > testCacheCloseDuringBucketMoveDoesntCauseDataLoss fails due to RejectedExecutionException during member availa
[
https://issues.apache.org/jira/browse/GEODE-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552845#comment-17552845
]
ASF subversion and git services commented on GEODE-10329:
-
Commit b3716d9498dd315ab1509389a92fadd69d8600e5 in geode's branch
refs/heads/develop from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b3716d9498 ]
GEODE-10329: Handle RejectedExecutionException (#7721)
Do not throw RejectedExecutionException if the GMSHealthMonitor is
stopping
Authored-by: Donal Evans
> CI Failure: PersistentPartitionedRegionDistributedTest >
> testCacheCloseDuringBucketMoveDoesntCauseDataLoss fails due to
> RejectedExecutionException during member availability check
> ---
>
> Key: GEODE-10329
> URL: https://issues.apache.org/jira/browse/GEODE-10329
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.16.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: pull-request-available
>
> {code:java}
> > Task :geode-core:distributedTest
> PersistentPartitionedRegionDistributedTest >
> testCacheCloseDuringBucketMoveDoesntCauseDataLoss 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 662
> [fatal 2022/05/23 17:31:45.980 UTC
> tid=257] Uncaught exception in thread Thread[Geode Failure Detection thread
> 4,5,RMI Runtime]
> java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor$$Lambda$604/0x00080119f4f8@2f733640
> rejected from java.util.concurrent.ThreadPoolExecutor@2aaf4890[Shutting
> down, pool size = 6, active threads = 5, queued tasks = 0, completed tasks =
> 7]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2065)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:833)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1365)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.checkIfAvailable(GMSHealthMonitor.java:1241)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.processMessage(GMSHealthMonitor.java:1173)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.sendSuspectRequest(GMSHealthMonitor.java:1425)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.initiateSuspicion(GMSHealthMonitor.java:486)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.lambda$checkMember$1(GMSHealthMonitor.java:470)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:422)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:438)
> at
> org.apache.geode.test.dunit.rules.DistributedRule$TearDown.doTearDown(DistributedRule.java:230)
> at
> org.apache.geode.test.dunit.rules.DistributedRule$TearDown.access$100(DistributedRule.java:211)
> at
> org.apache.geode.test.dunit.rules.DistributedRule.after(DistributedRule.java:151)
> at
> org.apache.geode.test.dunit.rules.AbstractDistributedRule.afterDistributedTest(AbstractDistributedRule.java:81)
> at
> org.apache.geode.test.dunit.rules.AbstractDistributedRule$1.evaluate(AbstractDistributedRule.java:61)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:449)
> at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:393)
> at
[jira] [Resolved] (GEODE-10329) CI Failure: PersistentPartitionedRegionDistributedTest > testCacheCloseDuringBucketMoveDoesntCauseDataLoss fails due to RejectedExecutionException during member availab
[
https://issues.apache.org/jira/browse/GEODE-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans resolved GEODE-10329.
-
Fix Version/s: 1.16.0
Resolution: Fixed
> CI Failure: PersistentPartitionedRegionDistributedTest >
> testCacheCloseDuringBucketMoveDoesntCauseDataLoss fails due to
> RejectedExecutionException during member availability check
> ---
>
> Key: GEODE-10329
> URL: https://issues.apache.org/jira/browse/GEODE-10329
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.16.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> {code:java}
> > Task :geode-core:distributedTest
> PersistentPartitionedRegionDistributedTest >
> testCacheCloseDuringBucketMoveDoesntCauseDataLoss 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 662
> [fatal 2022/05/23 17:31:45.980 UTC
> tid=257] Uncaught exception in thread Thread[Geode Failure Detection thread
> 4,5,RMI Runtime]
> java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor$$Lambda$604/0x00080119f4f8@2f733640
> rejected from java.util.concurrent.ThreadPoolExecutor@2aaf4890[Shutting
> down, pool size = 6, active threads = 5, queued tasks = 0, completed tasks =
> 7]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2065)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:833)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1365)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.checkIfAvailable(GMSHealthMonitor.java:1241)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.processMessage(GMSHealthMonitor.java:1173)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.sendSuspectRequest(GMSHealthMonitor.java:1425)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.initiateSuspicion(GMSHealthMonitor.java:486)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.lambda$checkMember$1(GMSHealthMonitor.java:470)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:422)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:438)
> at
> org.apache.geode.test.dunit.rules.DistributedRule$TearDown.doTearDown(DistributedRule.java:230)
> at
> org.apache.geode.test.dunit.rules.DistributedRule$TearDown.access$100(DistributedRule.java:211)
> at
> org.apache.geode.test.dunit.rules.DistributedRule.after(DistributedRule.java:151)
> at
> org.apache.geode.test.dunit.rules.AbstractDistributedRule.afterDistributedTest(AbstractDistributedRule.java:81)
> at
> org.apache.geode.test.dunit.rules.AbstractDistributedRule$1.evaluate(AbstractDistributedRule.java:61)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:449)
> at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:393)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at
