[jira] [Commented] (GEODE-10291) Support Jammy (ubuntu 22.04)
[ https://issues.apache.org/jira/browse/GEODE-10291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871523#comment-17871523 ] ASF GitHub Bot commented on GEODE-10291: moleske closed pull request #972: GEODE-10291: Use clang 12 in all dockerfiles URL: https://github.com/apache/geode-native/pull/972 > Support Jammy (ubuntu 22.04) > > > Key: GEODE-10291 > URL: https://issues.apache.org/jira/browse/GEODE-10291 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Labels: pull-request-available > Fix For: 1.15.1, 1.16.0 > > > Native client should compile on the latest (ubuntu 22.04) operating system. > Consider including a new pipeline as part of this -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10291) Support Jammy (ubuntu 22.04)
[ https://issues.apache.org/jira/browse/GEODE-10291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871522#comment-17871522 ] ASF GitHub Bot commented on GEODE-10291: moleske closed pull request #968: GEODE-10291: Add ubuntu 22.04 (jammy) to CI URL: https://github.com/apache/geode-native/pull/968 > Support Jammy (ubuntu 22.04) > > > Key: GEODE-10291 > URL: https://issues.apache.org/jira/browse/GEODE-10291 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Labels: pull-request-available > Fix For: 1.15.1, 1.16.0 > > > Native client should compile on the latest (ubuntu 22.04) operating system. > Consider including a new pipeline as part of this -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10454) Update to Develocity Gradle Plugin
[ https://issues.apache.org/jira/browse/GEODE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clay Johnson updated GEODE-10454: - Description: Currently, Geode publishes build scans to the Develocity instance at ge.apache.org. To accomplish this, the Gradle Enterprise Gradle Plugin is applied. As of Develocity 2024.3, expected later this year, the Gradle Enterprise Gradle Plugin will no longer be supported. Migration to the Develocity Gradle Plugin will be necessary. was: Currently, Fineract publishes build scans to the Develocity instance at ge.apache.org. To accomplish this, the Gradle Enterprise Gradle Plugin is applied. As of Develocity 2024.3, expected later this year, the Gradle Enterprise Gradle Plugin will no longer be supported. Migration to the Develocity Gradle Plugin will be necessary. > Update to Develocity Gradle Plugin > -- > > Key: GEODE-10454 > URL: https://issues.apache.org/jira/browse/GEODE-10454 > Project: Geode > Issue Type: Improvement >Reporter: Clay Johnson >Priority: Major > Labels: pull-request-available > > Currently, Geode publishes build scans to the Develocity instance at > ge.apache.org. To accomplish this, the Gradle Enterprise Gradle Plugin is > applied. > As of Develocity 2024.3, expected later this year, the Gradle Enterprise > Gradle Plugin will no longer be supported. Migration to the Develocity Gradle > Plugin will be necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10454) Update to Develocity Gradle Plugin
Clay Johnson created GEODE-10454: Summary: Update to Develocity Gradle Plugin Key: GEODE-10454 URL: https://issues.apache.org/jira/browse/GEODE-10454 Project: Geode Issue Type: Improvement Reporter: Clay Johnson Currently, Fineract publishes build scans to the Develocity instance at ge.apache.org. To accomplish this, the Gradle Enterprise Gradle Plugin is applied. As of Develocity 2024.3, expected later this year, the Gradle Enterprise Gradle Plugin will no longer be supported. Migration to the Develocity Gradle Plugin will be necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10454) Update to Develocity Gradle Plugin
[ https://issues.apache.org/jira/browse/GEODE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10454: --- Labels: pull-request-available (was: ) > Update to Develocity Gradle Plugin > -- > > Key: GEODE-10454 > URL: https://issues.apache.org/jira/browse/GEODE-10454 > Project: Geode > Issue Type: Improvement >Reporter: Clay Johnson >Priority: Major > Labels: pull-request-available > > Currently, Fineract publishes build scans to the Develocity instance at > ge.apache.org. To accomplish this, the Gradle Enterprise Gradle Plugin is > applied. > As of Develocity 2024.3, expected later this year, the Gradle Enterprise > Gradle Plugin will no longer be supported. Migration to the Develocity Gradle > Plugin will be necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10453) Infinite/slow indexing on reconnect and register interest replay
Leon Finker created GEODE-10453:
---
Summary: Infinite/slow indexing on reconnect and register interest
replay
Key: GEODE-10453
URL: https://issues.apache.org/jira/browse/GEODE-10453
Project: Geode
Issue Type: Bug
Affects Versions: 1.15.1
Reporter: Leon Finker
Cache server was restarted. Client side upon reconnect went into infinite/slow
indexing loop. This has not recovered even after multiple days. The thread
stack for thread taking 100% CPU was:
{code}
Thread Name state
Waiting on
Owned By with ID <140>
Executor Group
Monitored metric
Thread stack for "poolTimer-Server-21659" (0x128275):
java.lang.ThreadState: BLOCKED
at
app//org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:283)
at
app//org.apache.geode.cache.client.internal.QueueConnectionImpl.execute(QueueConnectionImpl.java:191)
at
app//org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:760)
at
app//org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:343)
at
app//org.apache.geode.cache.client.internal.OpExecutorImpl.executeOn(OpExecutorImpl.java:312)
at
app//org.apache.geode.cache.client.internal.PoolImpl.executeOn(PoolImpl.java:848)
at app//org.apache.geode.cache.client.internal.PingOp.execute(PingOp.java:40)
at
app//org.apache.geode.cache.client.internal.LiveServerPinger$PingTask.run2(LiveServerPinger.java:128)
at
app//org.apache.geode.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1340)
at
java.base@17.0.6/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at
java.base@17.0.6/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at
app//org.apache.geode.internal.ScheduledThreadPoolExecutorWithKeepAlive$DelegatingScheduledFuture.run(ScheduledThreadPoolExecutorWithKeepAlive.java:285)
at
java.base@17.0.6/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base@17.0.6/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base@17.0.6/java.lang.Thread.run(Thread.java:833)
Locked ownable synchronizers:
- None
Lock owner thread stack for "queueTimer-Server1" (0x6a):
java.lang.ThreadState: RUNNABLE
at
app//org.apache.geode.cache.query.internal.types.TypeUtils$ComparisonStrategy$4.execute(TypeUtils.java:90)
at
app//org.apache.geode.cache.query.internal.types.TypeUtils.compare(TypeUtils.java:499)
at
app//org.apache.geode.cache.query.internal.index.MemoryIndexStore.getOldKey(MemoryIndexStore.java:275)
at
app//org.apache.geode.cache.query.internal.index.MemoryIndexStore.updateMapping(MemoryIndexStore.java:122)
at
app//org.apache.geode.cache.query.internal.index.CompactRangeIndex$IMQEvaluator.applyProjection(CompactRangeIndex.java:1563)
at
app//org.apache.geode.cache.query.internal.index.CompactRangeIndex$IMQEvaluator.doNestedIterations(CompactRangeIndex.java:1519)
at
app//org.apache.geode.cache.query.internal.index.CompactRangeIndex$IMQEvaluator.evaluate(CompactRangeIndex.java:1372)
at
app//org.apache.geode.cache.query.internal.index.CompactRangeIndex.addMapping(CompactRangeIndex.java:143)
at
app//org.apache.geode.cache.query.internal.index.AbstractIndex.addIndexMapping(AbstractIndex.java:488)
at
app//org.apache.geode.cache.query.internal.index.IndexManager.addIndexMapping(IndexManager.java:1143)
at
app//org.apache.geode.cache.query.internal.index.IndexManager.processAction(IndexManager.java:1089)
at
app//org.apache.geode.cache.query.internal.index.IndexManager.updateIndexes(IndexManager.java:982)
at
app//org.apache.geode.cache.query.internal.index.IndexManager.updateIndexes(IndexManager.java:956)
at
app//org.apache.geode.internal.cache.AbstractRegionMap.initialImagePut(AbstractRegionMap.java:839)
at
app//org.apache.geode.internal.cache.LocalRegion.refreshEntriesFromServerKeys(LocalRegion.java:4348)
at
app//org.apache.geode.cache.client.internal.RegisterInterestOp$RegisterInterestOpImpl.processResponse(RegisterInterestOp.java:217)
at
app//org.apache.geode.cache.client.internal.RegisterInterestOp$RegisterInterestOpImpl.processResponse(RegisterInterestOp.java:121)
at
app//org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:209)
at
app//org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:394)
at
app//org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:284)
at
app//org.apache.geode.cache.client.internal.QueueConnectionImpl.execute(QueueConnectionImpl.java:191)
at
app//org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:760)
at
app//org.apache.geode.cache.client.internal.OpExecutorImpl.executeOn(OpExecut
[jira] [Updated] (GEODE-10452) geode-kafka-connector uses log4shell affected log4j-core
[ https://issues.apache.org/jira/browse/GEODE-10452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PJ Fanning updated GEODE-10452: --- Description: See https://github.com/apache/geode-kafka-connector/pull/20 Is geode-kafka-connector maintained? If not, could it be archived? It feels wrong for an ASF project to have source that is using log4shell affected jars in 2024. was: See https://github.com/apache/geode-kafka-connector/pull/20 Is geode-kafka-connector maintained? If not, could it be archived. It feels wrong for an ASF project to have source that is using log4shell affected jars in 2024. > geode-kafka-connector uses log4shell affected log4j-core > > > Key: GEODE-10452 > URL: https://issues.apache.org/jira/browse/GEODE-10452 > Project: Geode > Issue Type: Bug >Reporter: PJ Fanning >Priority: Major > Labels: needsTriage > > See https://github.com/apache/geode-kafka-connector/pull/20 > Is geode-kafka-connector maintained? If not, could it be archived? > It feels wrong for an ASF project to have source that is using log4shell > affected jars in 2024. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10452) geode-kafka-connector uses log4shell affected log4j-core
[ https://issues.apache.org/jira/browse/GEODE-10452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10452: -- Labels: needsTriage (was: ) > geode-kafka-connector uses log4shell affected log4j-core > > > Key: GEODE-10452 > URL: https://issues.apache.org/jira/browse/GEODE-10452 > Project: Geode > Issue Type: Bug >Reporter: PJ Fanning >Priority: Major > Labels: needsTriage > > See https://github.com/apache/geode-kafka-connector/pull/20 > Is geode-kafka-connector maintained? If not, could it be archived. > It feels wrong for an ASF project to have source that is using log4shell > affected jars in 2024. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10452) geode-kafka-connector uses log4shell affected log4j-core
PJ Fanning created GEODE-10452: -- Summary: geode-kafka-connector uses log4shell affected log4j-core Key: GEODE-10452 URL: https://issues.apache.org/jira/browse/GEODE-10452 Project: Geode Issue Type: Bug Reporter: PJ Fanning See https://github.com/apache/geode-kafka-connector/pull/20 Is geode-kafka-connector maintained? If not, could it be archived. It feels wrong for an ASF project to have source that is using log4shell affected jars in 2024. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10451) insecure confluent http url used in geode-kafka-connector build
[ https://issues.apache.org/jira/browse/GEODE-10451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821871#comment-17821871 ] PJ Fanning commented on GEODE-10451: https://github.com/apache/geode-kafka-connector/pull/23 is open for this - https://github.com/apache/geode-kafka-connector/pull/21 is a duplicate (I think) > insecure confluent http url used in geode-kafka-connector build > > > Key: GEODE-10451 > URL: https://issues.apache.org/jira/browse/GEODE-10451 > Project: Geode > Issue Type: Bug >Reporter: PJ Fanning >Priority: Major > Labels: needsTriage > > https://github.com/apache/geode-kafka-connector/blob/37992b8d7331cd8d131e5c8ce971763a2f7eb8ca/pom.xml#L55 > Please use https only - otherwise, we are at risk of someone spoofing the > HTTP address and injecting dangerous code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10451) insecure confluent http url used in geode-kafka-connector build
PJ Fanning created GEODE-10451: -- Summary: insecure confluent http url used in geode-kafka-connector build Key: GEODE-10451 URL: https://issues.apache.org/jira/browse/GEODE-10451 Project: Geode Issue Type: Bug Reporter: PJ Fanning https://github.com/apache/geode-kafka-connector/blob/37992b8d7331cd8d131e5c8ce971763a2f7eb8ca/pom.xml#L55 Please use https only - otherwise, we are at risk of someone spoofing the HTTP address and injecting dangerous code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10451) insecure confluent http url used in geode-kafka-connector build
[ https://issues.apache.org/jira/browse/GEODE-10451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10451: -- Labels: needsTriage (was: ) > insecure confluent http url used in geode-kafka-connector build > > > Key: GEODE-10451 > URL: https://issues.apache.org/jira/browse/GEODE-10451 > Project: Geode > Issue Type: Bug >Reporter: PJ Fanning >Priority: Major > Labels: needsTriage > > https://github.com/apache/geode-kafka-connector/blob/37992b8d7331cd8d131e5c8ce971763a2f7eb8ca/pom.xml#L55 > Please use https only - otherwise, we are at risk of someone spoofing the > HTTP address and injecting dangerous code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10450) Update spring version for CVE-2023-20861
[
https://issues.apache.org/jira/browse/GEODE-10450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10450:
--
Labels: needsTriage (was: )
> Update spring version for CVE-2023-20861
>
>
> Key: GEODE-10450
> URL: https://issues.apache.org/jira/browse/GEODE-10450
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.1
>Reporter: Ankush Mittal
>Priority: Major
> Labels: needsTriage
>
> As per [https://nvd.nist.gov/vuln/detail/CVE-2023-20861],
> "{_}In Spring Framework versions 6.0.0 - 6.0.6, 5.3.0 - 5.3.25, 5.2.0.RELEASE
> - 5.2.22.RELEASE, and older unsupported versions, it is possible for a user
> to provide a specially crafted SpEL expression that may cause a
> denial-of-service (DoS) condition.{_}"
>
> Geode bundles version 5.3.20 which is vulnerable as per the CVE.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (GEODE-10450) Update spring version for CVE-2023-20861
Ankush Mittal created GEODE-10450:
-
Summary: Update spring version for CVE-2023-20861
Key: GEODE-10450
URL: https://issues.apache.org/jira/browse/GEODE-10450
Project: Geode
Issue Type: Bug
Affects Versions: 1.15.1
Reporter: Ankush Mittal
As per [https://nvd.nist.gov/vuln/detail/CVE-2023-20861],
"{_}In Spring Framework versions 6.0.0 - 6.0.6, 5.3.0 - 5.3.25, 5.2.0.RELEASE -
5.2.22.RELEASE, and older unsupported versions, it is possible for a user to
provide a specially crafted SpEL expression that may cause a denial-of-service
(DoS) condition.{_}"
Geode bundles version 5.3.20 which is vulnerable as per the CVE.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (GEODE-10449) Update shiro-core to version 1.12.0 for CVE-2023-34478
[ https://issues.apache.org/jira/browse/GEODE-10449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10449: -- Labels: needsTriage (was: ) > Update shiro-core to version 1.12.0 for CVE-2023-34478 > -- > > Key: GEODE-10449 > URL: https://issues.apache.org/jira/browse/GEODE-10449 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.1 >Reporter: Ankush Mittal >Priority: Major > Labels: needsTriage > > As per [https://nvd.nist.gov/vuln/detail/CVE-2023-34478] , > _"Apache Shiro, before 1.12.0 or 2.0.0-alpha-3, may be susceptible to a path > traversal attack that results in an authentication bypass when used together > with APIs or other web frameworks that route requests based on non-normalized > requests. Mitigation: Update to Apache Shiro 1.12.0+ or 2.0.0-alpha-3+"_ > Geode 1.15.1 bundles version 1.9.1 of shiro-core jar which is vulnerable as > per the CVE. > > There is another CVE related to shiro-core 1.9.1, > [https://nvd.nist.gov/vuln/detail/CVE-2023-22602] , > which states > "When using Apache Shiro before 1.11.0 together with Spring Boot 2.6+, a > specially crafted HTTP request may cause an authentication bypass. The > authentication bypass occurs when Shiro and Spring Boot are using different > pattern-matching techniques. Both Shiro and Spring Boot < 2.6 default to Ant > style pattern matching. Mitigation: Update to Apache Shiro 1.11.0, or set the > following Spring Boot configuration value: > `spring.mvc.pathmatch.matching-strategy = ant_path_matcher`" > > Fix for the mentioned vulnerabilities seems to be merged in "develop" branch > via commit > [https://github.com/apache/geode/commit/d1958146c12affb1fe3eabc5823bb4eeb6c0badc] > Logging this Jira to update the same in 1.15.1 branch as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10449) Update shiro-core to version 1.12.0 for CVE-2023-34478
Ankush Mittal created GEODE-10449: - Summary: Update shiro-core to version 1.12.0 for CVE-2023-34478 Key: GEODE-10449 URL: https://issues.apache.org/jira/browse/GEODE-10449 Project: Geode Issue Type: Bug Affects Versions: 1.15.1 Reporter: Ankush Mittal As per [https://nvd.nist.gov/vuln/detail/CVE-2023-34478] , _"Apache Shiro, before 1.12.0 or 2.0.0-alpha-3, may be susceptible to a path traversal attack that results in an authentication bypass when used together with APIs or other web frameworks that route requests based on non-normalized requests. Mitigation: Update to Apache Shiro 1.12.0+ or 2.0.0-alpha-3+"_ Geode 1.15.1 bundles version 1.9.1 of shiro-core jar which is vulnerable as per the CVE. There is another CVE related to shiro-core 1.9.1, [https://nvd.nist.gov/vuln/detail/CVE-2023-22602] , which states "When using Apache Shiro before 1.11.0 together with Spring Boot 2.6+, a specially crafted HTTP request may cause an authentication bypass. The authentication bypass occurs when Shiro and Spring Boot are using different pattern-matching techniques. Both Shiro and Spring Boot < 2.6 default to Ant style pattern matching. Mitigation: Update to Apache Shiro 1.11.0, or set the following Spring Boot configuration value: `spring.mvc.pathmatch.matching-strategy = ant_path_matcher`" Fix for the mentioned vulnerabilities seems to be merged in "develop" branch via commit [https://github.com/apache/geode/commit/d1958146c12affb1fe3eabc5823bb4eeb6c0badc] Logging this Jira to update the same in 1.15.1 branch as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10400) Function execution triggering internal exception
[ https://issues.apache.org/jira/browse/GEODE-10400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787318#comment-17787318 ] ASF GitHub Bot commented on GEODE-10400: gaussianrecurrence commented on PR #982: URL: https://github.com/apache/geode-native/pull/982#issuecomment-1816770813 I haven't had the time to work on this for a long time or I think I'll have the opportunity to in the near future, hence I am closing this PR, if anyone wants to tackle this issue can take it up from its latest state. > Function execution triggering internal exception > > > Key: GEODE-10400 > URL: https://issues.apache.org/jira/browse/GEODE-10400 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: needsTriage, pull-request-available > > *GIVEN* a cluster with at least 3 members > *AND* a partitioned region with 1 redundant-copy > *AND* a server function called *JustAFunction* with isHA=false, > hasResult=true, optimizeForWrite=true > *AND* a native client configured to connect to the above cluster with a pool > using PR-Single-Hop=true > *WHEN* *JustAFunction* is executed with onRegion and no filters > *IF* the client has partial metadata due to the cluster starting up or a > rebalance occurring > *THEN* and exception of type > *"org.apache.geode.internal.cache.execute.InternalFunctionInvocationTargetException: > Multiple target nodes found for single hop operation"* is thrown by one of > the servers > --- > *Additional information.* Currently, in geode-native whenever the metadata > information is incomplete, and the user tries to execute the server function > with onRegion and no filters, a request of type > EXECUTE_REGION_FUNCTION_SINGLE_HOP is sent to each node. > But the issue is that bucket partition used by the client is incorrect, > leading consequently to the mentioned exception. > *Potential solution.* The potential solution would be to detect that the > metadata is incomplete before actually executing the function and send a > EXECUTE_REGION_FUNCTION request to one of the cluster nodes instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10400) Function execution triggering internal exception
[ https://issues.apache.org/jira/browse/GEODE-10400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787317#comment-17787317 ] ASF GitHub Bot commented on GEODE-10400: gaussianrecurrence closed pull request #982: GEODE-10400: Fix metadata completion detection URL: https://github.com/apache/geode-native/pull/982 > Function execution triggering internal exception > > > Key: GEODE-10400 > URL: https://issues.apache.org/jira/browse/GEODE-10400 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: needsTriage, pull-request-available > > *GIVEN* a cluster with at least 3 members > *AND* a partitioned region with 1 redundant-copy > *AND* a server function called *JustAFunction* with isHA=false, > hasResult=true, optimizeForWrite=true > *AND* a native client configured to connect to the above cluster with a pool > using PR-Single-Hop=true > *WHEN* *JustAFunction* is executed with onRegion and no filters > *IF* the client has partial metadata due to the cluster starting up or a > rebalance occurring > *THEN* and exception of type > *"org.apache.geode.internal.cache.execute.InternalFunctionInvocationTargetException: > Multiple target nodes found for single hop operation"* is thrown by one of > the servers > --- > *Additional information.* Currently, in geode-native whenever the metadata > information is incomplete, and the user tries to execute the server function > with onRegion and no filters, a request of type > EXECUTE_REGION_FUNCTION_SINGLE_HOP is sent to each node. > But the issue is that bucket partition used by the client is incorrect, > leading consequently to the mentioned exception. > *Potential solution.* The potential solution would be to detect that the > metadata is incomplete before actually executing the function and send a > EXECUTE_REGION_FUNCTION request to one of the cluster nodes instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10414) Add putIfAbsent method to region interfaces
[ https://issues.apache.org/jira/browse/GEODE-10414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787319#comment-17787319 ] ASF GitHub Bot commented on GEODE-10414: gaussianrecurrence closed pull request #984: GEODE-10414: Implement Region::putIfAbsent method URL: https://github.com/apache/geode-native/pull/984 > Add putIfAbsent method to region interfaces > --- > > Key: GEODE-10414 > URL: https://issues.apache.org/jira/browse/GEODE-10414 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > *AS A* geode-native contributor > *I WANT TO* have putIfAbsent region method implemented > *SO THAT* I can atomically put entries only if they don't previously, exist > and also, to align it with the Java API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10276) Refactor PDX (de)serialziation code to align it with Java client
[ https://issues.apache.org/jira/browse/GEODE-10276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787312#comment-17787312 ] ASF GitHub Bot commented on GEODE-10276: gaussianrecurrence commented on PR #969: URL: https://github.com/apache/geode-native/pull/969#issuecomment-1816770033 I haven't had the time to work on this for a long time or I think I'll have the opportunity to in the near future, hence I am closing this PR, if anyone wants to tackle this issue can take it up from its latest state. > Refactor PDX (de)serialziation code to align it with Java client > > > Key: GEODE-10276 > URL: https://issues.apache.org/jira/browse/GEODE-10276 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > Currently there are the following open issues regarding PDX (de)serialization: > * [GEODE-9968 - Fix deserialization for new fields in PdxSerializable > class|https://issues.apache.org/jira/browse/GEODE-9968] > * [GEODE-9753 - Coredump during PdxSerializable object > serialization|https://issues.apache.org/jira/browse/GEODE-9753] > * [GEODE-10220 - Coredump while initializing PdxType > remoteToLocal|https://issues.apache.org/jira/browse/GEODE-10220] > * [GEODE-10255 - PdxSerializable not working correctly for multiple versions > of the same class|https://issues.apache.org/jira/browse/GEODE-10255] > Also, the implementation on this ticket ([GEODE-8212: Reduce connections to > server to get type id|https://issues.apache.org/jira/browse/GEODE-8212]) > poses some issues with PDX entries which fields are a permutation. Thing is > that PdxTypes which fields are a permutation might use the wrong offsets, > leading to a corrupt serialization. This is something that was not taken into > account at the time of getting this PR merged. > So this ticket should be reverted and possibly an alternative solution > proposed. > In order to tackle these issues, a code refactoring is needed to introduce > the following implementations: > * Single type of PdxWriter > * An implementation PdxReader that tracks unread data, and other that don't. > * An implementation for PdxInstances that guarantees that fields are > actually written in alphabetical order, independently of the writeFields call > order. This should tackle the issue described above regarding GEODE-8212. > * Also, it'd be ideal to make it so PDX code is cleaner and easier to > understand, though that's a complex matter, and also, subjective. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10396) IllegalStateException wrapped within FunctionException triggers endpoint disconnection
[ https://issues.apache.org/jira/browse/GEODE-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787316#comment-17787316 ] ASF GitHub Bot commented on GEODE-10396: gaussianrecurrence commented on PR #977: URL: https://github.com/apache/geode-native/pull/977#issuecomment-1816770656 I haven't had the time to work on this for a long time or I think I'll have the opportunity to in the near future, hence I am closing this PR, if anyone wants to tackle this issue can take it up from its latest state. > IllegalStateException wrapped within FunctionException triggers endpoint > disconnection > -- > > Key: GEODE-10396 > URL: https://issues.apache.org/jira/browse/GEODE-10396 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: needsTriage, pull-request-available > > *GIVEN* A cluster of 3 servers and a client with a pool pointing to those 3 > servers >*AND* configured with PR-Singl-Hop = true > *WHEN* A server function is executed with onRegion and with a filter >*AND* it throws an IllegalServerException wrapped within a > FunctionExceution in the body > *THEN* the native client thinks there is an isue with the node and closes all > the endpoint's connections. > --- > *IT IS TO BE EXPECTED* That given that the exception is wrapped inside a > FunctionException this should be ignored by the endpoint failure detection > mechanism that native client has into place. > *AS ADDITIONAL INFO* Currently, the exception chain relationship info is not > read by the native client, as it's serialized using Java serialization format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10396) IllegalStateException wrapped within FunctionException triggers endpoint disconnection
[ https://issues.apache.org/jira/browse/GEODE-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787315#comment-17787315 ] ASF GitHub Bot commented on GEODE-10396: gaussianrecurrence closed pull request #977: GEODE-10396: Avoid endpoint closure upon exception URL: https://github.com/apache/geode-native/pull/977 > IllegalStateException wrapped within FunctionException triggers endpoint > disconnection > -- > > Key: GEODE-10396 > URL: https://issues.apache.org/jira/browse/GEODE-10396 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: needsTriage, pull-request-available > > *GIVEN* A cluster of 3 servers and a client with a pool pointing to those 3 > servers >*AND* configured with PR-Singl-Hop = true > *WHEN* A server function is executed with onRegion and with a filter >*AND* it throws an IllegalServerException wrapped within a > FunctionExceution in the body > *THEN* the native client thinks there is an isue with the node and closes all > the endpoint's connections. > --- > *IT IS TO BE EXPECTED* That given that the exception is wrapped inside a > FunctionException this should be ignored by the endpoint failure detection > mechanism that native client has into place. > *AS ADDITIONAL INFO* Currently, the exception chain relationship info is not > read by the native client, as it's serialized using Java serialization format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10276) Refactor PDX (de)serialziation code to align it with Java client
[ https://issues.apache.org/jira/browse/GEODE-10276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787313#comment-17787313 ] ASF GitHub Bot commented on GEODE-10276: gaussianrecurrence closed pull request #969: GEODE-10276: Refactor PDX (de)serialization code URL: https://github.com/apache/geode-native/pull/969 > Refactor PDX (de)serialziation code to align it with Java client > > > Key: GEODE-10276 > URL: https://issues.apache.org/jira/browse/GEODE-10276 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > Currently there are the following open issues regarding PDX (de)serialization: > * [GEODE-9968 - Fix deserialization for new fields in PdxSerializable > class|https://issues.apache.org/jira/browse/GEODE-9968] > * [GEODE-9753 - Coredump during PdxSerializable object > serialization|https://issues.apache.org/jira/browse/GEODE-9753] > * [GEODE-10220 - Coredump while initializing PdxType > remoteToLocal|https://issues.apache.org/jira/browse/GEODE-10220] > * [GEODE-10255 - PdxSerializable not working correctly for multiple versions > of the same class|https://issues.apache.org/jira/browse/GEODE-10255] > Also, the implementation on this ticket ([GEODE-8212: Reduce connections to > server to get type id|https://issues.apache.org/jira/browse/GEODE-8212]) > poses some issues with PDX entries which fields are a permutation. Thing is > that PdxTypes which fields are a permutation might use the wrong offsets, > leading to a corrupt serialization. This is something that was not taken into > account at the time of getting this PR merged. > So this ticket should be reverted and possibly an alternative solution > proposed. > In order to tackle these issues, a code refactoring is needed to introduce > the following implementations: > * Single type of PdxWriter > * An implementation PdxReader that tracks unread data, and other that don't. > * An implementation for PdxInstances that guarantees that fields are > actually written in alphabetical order, independently of the writeFields call > order. This should tackle the issue described above regarding GEODE-8212. > * Also, it'd be ideal to make it so PDX code is cleaner and easier to > understand, though that's a complex matter, and also, subjective. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10414) Add putIfAbsent method to region interfaces
[ https://issues.apache.org/jira/browse/GEODE-10414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787320#comment-17787320 ] ASF GitHub Bot commented on GEODE-10414: gaussianrecurrence commented on PR #984: URL: https://github.com/apache/geode-native/pull/984#issuecomment-1816770978 I haven't had the time to work on this for a long time or I think I'll have the opportunity to in the near future, hence I am closing this PR, if anyone wants to tackle this issue can take it up from its latest state. > Add putIfAbsent method to region interfaces > --- > > Key: GEODE-10414 > URL: https://issues.apache.org/jira/browse/GEODE-10414 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > *AS A* geode-native contributor > *I WANT TO* have putIfAbsent region method implemented > *SO THAT* I can atomically put entries only if they don't previously, exist > and also, to align it with the Java API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10044) Allow for FunctionAttributes to be updated
[ https://issues.apache.org/jira/browse/GEODE-10044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787310#comment-17787310 ] ASF GitHub Bot commented on GEODE-10044: gaussianrecurrence commented on PR #930: URL: https://github.com/apache/geode-native/pull/930#issuecomment-1816768908 I haven't had the time to work on this for a long time or I think I'll have the opportunity to in the near future, hence I am closing this PR, if anyone wants to tackle this issue can take it up from its latest state. > Allow for FunctionAttributes to be updated > --- > > Key: GEODE-10044 > URL: https://issues.apache.org/jira/browse/GEODE-10044 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Minor > Labels: pull-request-available > > *AS A* geode-native contributor > *I WANT TO* to reset function attributes on-the-fly whenever a function > attributes mismatch is detected on the client > *SO THAT* FunctionAttributes can be changed during an upgrade scenario > > *Additional information.* Currently there is no exception being thrown from > the server whenever a function attributes missmatch is detected. Instead, a > function execution error is send to the client. So it remains to be tackled > how the mismatch is going to be detected on the client side. > *Also, for additional context,* this feature is designed in order to fulfill > the following upgrade scenario: > # A server function called ExampleFunction is deployed inside a cluster. > This server function is defined with isHA=false > # Function is executed several times from the client. > # After some time, a new version of ExampleFunction jar is deployed. The new > version of the server function is defined with isHA=true > # After updating the server function, executions for this function inside > the client should fail at most once, and after that, execute smoothly with > the new function attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10044) Allow for FunctionAttributes to be updated
[ https://issues.apache.org/jira/browse/GEODE-10044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787311#comment-17787311 ] ASF GitHub Bot commented on GEODE-10044: gaussianrecurrence closed pull request #930: GEODE-10044: Allow FunctionAttributes update URL: https://github.com/apache/geode-native/pull/930 > Allow for FunctionAttributes to be updated > --- > > Key: GEODE-10044 > URL: https://issues.apache.org/jira/browse/GEODE-10044 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Minor > Labels: pull-request-available > > *AS A* geode-native contributor > *I WANT TO* to reset function attributes on-the-fly whenever a function > attributes mismatch is detected on the client > *SO THAT* FunctionAttributes can be changed during an upgrade scenario > > *Additional information.* Currently there is no exception being thrown from > the server whenever a function attributes missmatch is detected. Instead, a > function execution error is send to the client. So it remains to be tackled > how the mismatch is going to be detected on the client side. > *Also, for additional context,* this feature is designed in order to fulfill > the following upgrade scenario: > # A server function called ExampleFunction is deployed inside a cluster. > This server function is defined with isHA=false > # Function is executed several times from the client. > # After some time, a new version of ExampleFunction jar is deployed. The new > version of the server function is defined with isHA=true > # After updating the server function, executions for this function inside > the client should fail at most once, and after that, execute smoothly with > the new function attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10012) Avoid retries for non-HA function execution
[
https://issues.apache.org/jira/browse/GEODE-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787309#comment-17787309
]
ASF GitHub Bot commented on GEODE-10012:
gaussianrecurrence commented on PR #920:
URL: https://github.com/apache/geode-native/pull/920#issuecomment-1816767907
I haven't had the time to work on this for a long time or I think I'll have
the opportunity to in the near future, hence I am closing this PR, if anyone
wants to tackle this issue can take it up from its latest state.
> Avoid retries for non-HA function execution
> ---
>
> Key: GEODE-10012
> URL: https://issues.apache.org/jira/browse/GEODE-10012
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Major
> Labels: pull-request-available
>
> *GIVEN* a cluster with 3 servers and 1 locator
> *AND* a PartitionedRegion with redundant-copies="1"
> *AND* a user-defined Function with isHA=false
> *AND* a geode-native client with a pool with single-hop enabled and retry
> attempts set to 2
> *WHEN* execution fails due to a connectivity issue/connection
> timeout/internal cluster error
> *THEN* function is retried twice
>
> *Additional information.* The function is retried at the network code layer,
> and given whenever there is a timeout/connectivity error, the BSL is removed
> from the ClientMetadataService, whenever retries happen, you might get a
> *InternalFunctionInvocationTargetException* exception thrown indicating:
> {code:java}
> Multiple target nodes found for single hop operation {code}
> Also, have into account that Java client API behaviour never retries a
> Function Execution if isHA=false for that function, and whenever isHA=true,
> the function is retried but on the function execution logic and not at the
> networking layer.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (GEODE-10012) Avoid retries for non-HA function execution
[
https://issues.apache.org/jira/browse/GEODE-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787308#comment-17787308
]
ASF GitHub Bot commented on GEODE-10012:
gaussianrecurrence closed pull request #920: GEODE-10012: Avoid non-HA
function retries
URL: https://github.com/apache/geode-native/pull/920
> Avoid retries for non-HA function execution
> ---
>
> Key: GEODE-10012
> URL: https://issues.apache.org/jira/browse/GEODE-10012
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Major
> Labels: pull-request-available
>
> *GIVEN* a cluster with 3 servers and 1 locator
> *AND* a PartitionedRegion with redundant-copies="1"
> *AND* a user-defined Function with isHA=false
> *AND* a geode-native client with a pool with single-hop enabled and retry
> attempts set to 2
> *WHEN* execution fails due to a connectivity issue/connection
> timeout/internal cluster error
> *THEN* function is retried twice
>
> *Additional information.* The function is retried at the network code layer,
> and given whenever there is a timeout/connectivity error, the BSL is removed
> from the ClientMetadataService, whenever retries happen, you might get a
> *InternalFunctionInvocationTargetException* exception thrown indicating:
> {code:java}
> Multiple target nodes found for single hop operation {code}
> Also, have into account that Java client API behaviour never retries a
> Function Execution if isHA=false for that function, and whenever isHA=true,
> the function is retried but on the function execution logic and not at the
> networking layer.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (GEODE-10017) Fix new ITs unstability for TCs that involve members restart
[
https://issues.apache.org/jira/browse/GEODE-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787307#comment-17787307
]
ASF GitHub Bot commented on GEODE-10017:
gaussianrecurrence commented on PR #919:
URL: https://github.com/apache/geode-native/pull/919#issuecomment-1816767172
I haven't had the time to work on this for a long time or I think I'll have
the opportunity to in the near future, hence I am closing this PR, if anyone
wants to tackle this issue can take it up from its latest state.
> Fix new ITs unstability for TCs that involve members restart
>
>
> Key: GEODE-10017
> URL: https://issues.apache.org/jira/browse/GEODE-10017
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Major
> Labels: pull-request-available
>
> *GIVEN* an integration TC on which a server restart needs to be restarted
> *WHEN* the server is starting up again
> *THEN* +{color:#172b4d}it might{color}+{color:#172b4d} happen that the TC
> gets stuck{color}
>
> *Additional information.* This issue does not always happens, and I've seen
> it happening more frequently with the latest version of Geode server (1.15.0)
> Some examples of this TC are:
> * RegisterKeysTest.RegisterKeySetAndClusterRestart
> * PartitionRegionWithRedundancyTest.putgetWithSingleHop
> * ···
> Also, this is normally the exec flow for the TCs that get stuck:
> # Setup cluster
> # Do TC specific ops
> # Stop server(s)/Cluster shutdown
> # Start server(s)
> In all cases, the server gets stuck at step 4
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (GEODE-10017) Fix new ITs unstability for TCs that involve members restart
[
https://issues.apache.org/jira/browse/GEODE-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787306#comment-17787306
]
ASF GitHub Bot commented on GEODE-10017:
gaussianrecurrence closed pull request #919: GEODE-10017: Fix servers restart
within new ITs
URL: https://github.com/apache/geode-native/pull/919
> Fix new ITs unstability for TCs that involve members restart
>
>
> Key: GEODE-10017
> URL: https://issues.apache.org/jira/browse/GEODE-10017
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Major
> Labels: pull-request-available
>
> *GIVEN* an integration TC on which a server restart needs to be restarted
> *WHEN* the server is starting up again
> *THEN* +{color:#172b4d}it might{color}+{color:#172b4d} happen that the TC
> gets stuck{color}
>
> *Additional information.* This issue does not always happens, and I've seen
> it happening more frequently with the latest version of Geode server (1.15.0)
> Some examples of this TC are:
> * RegisterKeysTest.RegisterKeySetAndClusterRestart
> * PartitionRegionWithRedundancyTest.putgetWithSingleHop
> * ···
> Also, this is normally the exec flow for the TCs that get stuck:
> # Setup cluster
> # Do TC specific ops
> # Stop server(s)/Cluster shutdown
> # Start server(s)
> In all cases, the server gets stuck at step 4
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (GEODE-7251) Incorrect/incomplete instructions on download page
[
https://issues.apache.org/jira/browse/GEODE-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved GEODE-7251.
-
Resolution: Fixed
Looks OK now
> Incorrect/incomplete instructions on download page
> --
>
> Key: GEODE-7251
> URL: https://issues.apache.org/jira/browse/GEODE-7251
> Project: Geode
> Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> There are some issues with the download page instructions.
> It still refers to checking MD5 hashes, but there are none.
> Also the gpg sig check needs a second parameter:
> gpg --verify ${filename}.tar.gz.asc ${filename}.tar.gz
> See https://www.apache.org/info/verification.html#specify_both
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (GEODE-7251) Incorrect/incomplete instructions on download page
[
https://issues.apache.org/jira/browse/GEODE-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker reassigned GEODE-7251:
Assignee: (was: Anthony Baker)
> Incorrect/incomplete instructions on download page
> --
>
> Key: GEODE-7251
> URL: https://issues.apache.org/jira/browse/GEODE-7251
> Project: Geode
> Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> There are some issues with the download page instructions.
> It still refers to checking MD5 hashes, but there are none.
> Also the gpg sig check needs a second parameter:
> gpg --verify ${filename}.tar.gz.asc ${filename}.tar.gz
> See https://www.apache.org/info/verification.html#specify_both
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (GEODE-7053) PREntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpiration fails intermittently in CI
[
https://issues.apache.org/jira/browse/GEODE-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker reassigned GEODE-7053:
Assignee: (was: Anthony Baker)
> PREntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpiration
> fails intermittently in CI
> -
>
> Key: GEODE-7053
> URL: https://issues.apache.org/jira/browse/GEODE-7053
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.13.0, 1.15.0
>Reporter: Kirk Lund
>Priority: Major
>
> This test appears to be flaky and fails intermittently with:
> {noformat}
> org.apache.geode.internal.cache.PREntryIdleExpirationDistributedTest >
> readsInOtherMemberShouldPreventExpiration FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.PREntryIdleExpirationDistributedTest$$Lambda$29/458121042.run
> in VM 0 running on Host 40e899358944 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.PREntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpiration(PREntryIdleExpirationDistributedTest.java:114)
> Caused by:
> org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.PREntryIdleExpirationDistributedTest.lambda$readsInOtherMemberShouldPreventExpiration$bb17a952$2(PREntryIdleExpirationDistributedTest.java:124)
> {noformat}
> This test depends on a background thread waking up every 10 ms to perform a
> GET which prevents another thread from expiring an entry. I think that would
> be very prone to failing if the thread loses CPU for any reason.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (GEODE-1168) geode-dependencies manifest is missing jars that are present in the lib directory
[
https://issues.apache.org/jira/browse/GEODE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker reassigned GEODE-1168:
Assignee: (was: Anthony Baker)
> geode-dependencies manifest is missing jars that are present in the lib
> directory
> -
>
> Key: GEODE-1168
> URL: https://issues.apache.org/jira/browse/GEODE-1168
> Project: Geode
> Issue Type: Bug
> Components: build
>Reporter: Dan Smith
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> While looking into GEODE-1025, I discovered that we have a number of jars in
> the geode-assembly/build/install/apache-geode/lib directory that do not
> appear in geode-dependencies.jar or gfsh-dependencies.jar.
> I believe that means that these are not actually on the classpath for any
> geode process, which means they either shouldn't be shipped with geode at
> all, or they are supposed to be on the classpath but I getting skipped for
> some reason.
> These are the jars present in the lib directory, but not on the classpath,
> excluding the spring jars (I'm cleaning those up as part of GEODE-1025)
> {noformat}
> activation-1.1.jar
> commons-modeler-2.0.jar
> findbugs-annotations-1.3.9-1.jar
> geode-jca-1.0.0-incubating.M2-SNAPSHOT.rar
> geode-web-1.0.0-incubating.M2-SNAPSHOT.jar
> geode-web-api-1.0.0-incubating.M2-SNAPSHOT.jar
> guava-15.0.jar
> javax.mail-api-1.4.5.jar
> mx4j-3.0.1.jar
> mx4j-remote-3.0.1.jar
> mx4j-tools-3.0.1.jar
> ra.jar
> {noformat}
> Most of these jars appear to be coming from compile dependencies of
> geode-core.
> The jars in the lib directory are controlled by the distributions section of
> geode-assembly/build.gradle. The jars in the geode-dependencies.jar manifest
> are coming from the cp() method in geode-assembly/build.gradle.
> It seems like these two lists ought to be unified - we should only ship jars
> that appear in one of the two manifests, and what goes into the manifest
> should probably be controlled by the configurations of the other projects -
> In other words, if it's part of the runtime configuration of geode-core it
> should be part of the geode-dependencies.jar; it shouldn't be filtered by
> this cp() method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (GEODE-2160) gfsh stop server/locator exits with code 0 before server/locator actually stops
[
https://issues.apache.org/jira/browse/GEODE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker reassigned GEODE-2160:
Assignee: (was: Anthony Baker)
> gfsh stop server/locator exits with code 0 before server/locator actually
> stops
> ---
>
> Key: GEODE-2160
> URL: https://issues.apache.org/jira/browse/GEODE-2160
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.0.0-incubating
>Reporter: Jacob Barrett
>Priority: Major
>
> Executing
> {code}
> gfsh stop server --name=server1
> {code}
> {{gfsh}} exits, with code 0, prior to the server actually being stopped.
> This behavior isn't documented and makes scripting with gfsh difficult. One
> can't assume that the server has stopped after gfsh exits. To verify you must
> parse the server pid and check the status of the proc.
> Simple test:
> {code}
> gfsh start server --name=s2 && sleep 10 && gfsh stop server --dir=s2; echo
> $?; while (kill -0 `cat s2/vf.gf.server.pid`); do date +%s.%N; done
> {code}
> Starts server, waits 10s, stops server, prints exit code, loops until process
> is gone while printing the time since epoch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (GEODE-10448) CVE-2022-42889 Apache Commons Text security vulnerability in Apache Geode
[ https://issues.apache.org/jira/browse/GEODE-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli updated GEODE-10448: Description: I have encountered the security vulnerability [CVE-2022-42889|https://lists.apache.org/thread/n2bd4vdsgkqh2tm14l1wyc3jyol7s1om] related to Apache Commons Text. It is mentioned that the mitigation is to "Upgrade to [Apache Commons Text 1.10.0|https://commons.apache.org/proper/commons-text/download_text.cgi]."; because the following jar files are present. /locator01/GemFire_gemfire/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar /locator01/GemFire_root/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar The latest official [Apache Geode version 1.15.1|https://apache.org/dyn/closer.cgi/geode/1.15.1/apache-geode-1.15.1.tgz] has the vulnerable file commons-text-1.9.jar, which falls under the affected range “version 1.5 and continuing through 1.9”. Inside the folder /tools/Pulse, there is the file geode-pulse-1.15.1.war. Inside that war file, there is the file geode-pulse-1.15.1.war/WEB-INF/lib/commons-text-1.9.jar. As a temporary workaround, I replaced the file commons-text-1.9.jar with commons-text-1.10.0.jar, updated the MANIFEST.MF file under geode-pulse-1.15.1.war/META-INF, and created a new geode-pulse-1.15.1.war file including the 2 updated files mentioned. Unfortunately, I’m not a developer. I’m not familiar with Github, so as much as I would like to help in contributing in the code, there is a more appropriate person to perform the update to commons-text 1.10.0. I have sent a mail to ASF Security Team, and I was given this [link|#L144] that shows the dependency on the vulnerable commons-text version 1.9. Can somebody assist in fixing this security vulnerability? Any help is very much appreciated. Thank you in advance! was: I have encountered the security vulnerability [CVE-2022-42889|https://lists.apache.org/thread/n2bd4vdsgkqh2tm14l1wyc3jyol7s1om] related to Apache Commons Text. It is mentioned that the mitigation is to "Upgrade to [Apache Commons Text 1.10.0|https://commons.apache.org/proper/commons-text/download_text.cgi]."; because the following jar files are present. /locator01/GemFire_gemfire/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar /locator01/GemFire_root/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar The latest official [Apache Geode version 1.15.1|[https://apache.org/dyn/closer.cgi/geode/1.15.1/apache-geode-1.15.1.tgz|https://urldefense.com/v3/__https:/apache.org/dyn/closer.cgi/geode/1.15.1/apache-geode-1.15.1.tgz__;!!OrxsNty6D4my!7476fkBhS9dRAajU_LNsgk5KeehflkDwT1rsdOg5_lmW9F-rnt-zPr7K5J66Ylc8jzr9eR10QsOBYlTmJR0Y8tDl8ik$]] has the vulnerable file commons-text-1.9.jar, which falls under the affected range “version 1.5 and continuing through 1.9”. Inside the folder /tools/Pulse, there is the file geode-pulse-1.15.1.war. Inside that war file, there is the file geode-pulse-1.15.1.war/WEB-INF/lib/commons-text-1.9.jar. As a temporary workaround, I replaced the file commons-text-1.9.jar with commons-text-1.10.0.jar, updated the MANIFEST.MF file under geode-pulse-1.15.1.war/META-INF, and created a new geode-pulse-1.15.1.war file including the 2 updated files mentioned. Unfortunately, I’m not a developer. I’m not familiar with Github, so as much as I would like to help in contributing in the code, there is a more appropriate person to perform the update to commons-text 1.10.0. I have sent a mail to ASF Security Team, and I was given this [link|#L144] that shows the dependency on the vulnerable commons-text version 1.9. Can somebody assist in fixing this security vulnerability? Any help is very much appreciated. Thank you in advance! > CVE-2022-42889 Apache Commons Text security vulnerability in Apache Geode > - > > Key: GEODE-10448 > URL: https://issues.apache.org/jira/browse/GEODE-10448 > Project: Geode > Issue Type: Bug > Components: pulse, tools >Affects Versions: 1.15.1 >Reporter: Eli >Priority: Major > Labels: needsTriage > > I have encountered the security vulnerability > [CVE-2022-42889|https://lists.apache.org/thread/n2bd4vdsgkqh2tm14l1wyc3jyol7s1om] > related to Apache Commons Text. It is mentioned that the mitigation is to > "Upgrade to [Apache Commons Text > 1.10.0|https://commons.apache.org/proper/commons-text/download_text.cgi]."; > because the following jar files are present. > /locator01/GemFire_gemfire/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar > > /locator01/GemFire_root/services/http/0
[jira] [Updated] (GEODE-10448) CVE-2022-42889 Apache Commons Text security vulnerability in Apache Geode
[ https://issues.apache.org/jira/browse/GEODE-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli updated GEODE-10448: Description: I have encountered the security vulnerability [CVE-2022-42889|https://lists.apache.org/thread/n2bd4vdsgkqh2tm14l1wyc3jyol7s1om] related to Apache Commons Text. It is mentioned that the mitigation is to "Upgrade to [Apache Commons Text 1.10.0|https://commons.apache.org/proper/commons-text/download_text.cgi]."; because the following jar files are present. /locator01/GemFire_gemfire/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar /locator01/GemFire_root/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar The latest official [Apache Geode version 1.15.1|[https://apache.org/dyn/closer.cgi/geode/1.15.1/apache-geode-1.15.1.tgz|https://urldefense.com/v3/__https:/apache.org/dyn/closer.cgi/geode/1.15.1/apache-geode-1.15.1.tgz__;!!OrxsNty6D4my!7476fkBhS9dRAajU_LNsgk5KeehflkDwT1rsdOg5_lmW9F-rnt-zPr7K5J66Ylc8jzr9eR10QsOBYlTmJR0Y8tDl8ik$]] has the vulnerable file commons-text-1.9.jar, which falls under the affected range “version 1.5 and continuing through 1.9”. Inside the folder /tools/Pulse, there is the file geode-pulse-1.15.1.war. Inside that war file, there is the file geode-pulse-1.15.1.war/WEB-INF/lib/commons-text-1.9.jar. As a temporary workaround, I replaced the file commons-text-1.9.jar with commons-text-1.10.0.jar, updated the MANIFEST.MF file under geode-pulse-1.15.1.war/META-INF, and created a new geode-pulse-1.15.1.war file including the 2 updated files mentioned. Unfortunately, I’m not a developer. I’m not familiar with Github, so as much as I would like to help in contributing in the code, there is a more appropriate person to perform the update to commons-text 1.10.0. I have sent a mail to ASF Security Team, and I was given this [link|#L144] that shows the dependency on the vulnerable commons-text version 1.9. Can somebody assist in fixing this security vulnerability? Any help is very much appreciated. Thank you in advance! was: I have encountered the security vulnerability [CVE-2022-42889|https://lists.apache.org/thread/n2bd4vdsgkqh2tm14l1wyc3jyol7s1om] related to Apache Commons Text. It is mentioned that the mitigation is to "Upgrade to [Apache Commons Text 1.10.0|https://commons.apache.org/proper/commons-text/download_text.cgi]."; because the following jar files are present. /locator01/GemFire_gemfire/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar /locator01/GemFire_root/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar The latest official [Apache Geode version 1.15.1|[https://apache.org/dyn/closer.cgi/geode/1.15.1/apache-geode-1.15.1.tgz|https://urldefense.com/v3/__https:/apache.org/dyn/closer.cgi/geode/1.15.1/apache-geode-1.15.1.tgz__;!!OrxsNty6D4my!7476fkBhS9dRAajU_LNsgk5KeehflkDwT1rsdOg5_lmW9F-rnt-zPr7K5J66Ylc8jzr9eR10QsOBYlTmJR0Y8tDl8ik$]] has the vulnerable file commons-text-1.9.jar, which falls under the affected range “version 1.5 and continuing through 1.9”. Inside the folder /tools/Pulse, there is the file geode-pulse-1.15.1.war. Inside that war file, there is the file geode-pulse-1.15.1.war/WEB-INF/lib/commons-text-1.9.jar. As a temporary workaround, I replaced the file commons-text-1.9.jar with commons-text-1.10.0.jar, updated the MANIFEST.MF file under geode-pulse-1.15.1.war/META-INF, and created a new geode-pulse-1.15.1.war file including the 2 updated files mentioned. Unfortunately, I’m not a developer. I’m not familiar with Github, so as much as I would like to help in contributing in the code, there is a more appropriate person to perform the update to commons-text 1.10.0. I have sent a mail to ASF Security Team, and I was given this [link|[https://github.com/apache/geode/blob/master/build-tools/geode-dependency-management/src/main/groovy/org/apache/geode/gradle/plugins/DependencyConstraints.groovy#L144|https://urldefense.com/v3/__https:/github.com/apache/geode/blob/master/build-tools/geode-dependency-management/src/main/groovy/org/apache/geode/gradle/plugins/DependencyConstraints.groovy*L144__;Iw!!OrxsNty6D4my!6EKoN5DUPbSrn9BPavV5jC0T1h5U4Ih1aqdG5cHGJt2a0fqw2jCVoWL4Nl1lCC4hkzC3buVr9YC30Y_jxCSk43yE-FU$]] that shows the dependency on the vulnerable commons-text version 1.9. Can somebody assist in fixing this security vulnerability? Thank you in advance! > CVE-2022-42889 Apache Commons Text security vulnerability in Apache Geode > - > > Key: GEODE-10448 > URL: https://issues.apache.org/jira/browse/GEODE-10448 > Project: Geode > Issue Type: Bug > Components: pulse, tools >Affects Versions: 1.15.1 >
[jira] [Created] (GEODE-10448) CVE-2022-42889 Apache Commons Text security vulnerability in Apache Geode
Eli created GEODE-10448: --- Summary: CVE-2022-42889 Apache Commons Text security vulnerability in Apache Geode Key: GEODE-10448 URL: https://issues.apache.org/jira/browse/GEODE-10448 Project: Geode Issue Type: Bug Components: pulse, tools Affects Versions: 1.15.1 Reporter: Eli I have encountered the security vulnerability [CVE-2022-42889|https://lists.apache.org/thread/n2bd4vdsgkqh2tm14l1wyc3jyol7s1om] related to Apache Commons Text. It is mentioned that the mitigation is to "Upgrade to [Apache Commons Text 1.10.0|https://commons.apache.org/proper/commons-text/download_text.cgi]."; because the following jar files are present. /locator01/GemFire_gemfire/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar /locator01/GemFire_root/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar The latest official [Apache Geode version 1.15.1|[https://apache.org/dyn/closer.cgi/geode/1.15.1/apache-geode-1.15.1.tgz|https://urldefense.com/v3/__https:/apache.org/dyn/closer.cgi/geode/1.15.1/apache-geode-1.15.1.tgz__;!!OrxsNty6D4my!7476fkBhS9dRAajU_LNsgk5KeehflkDwT1rsdOg5_lmW9F-rnt-zPr7K5J66Ylc8jzr9eR10QsOBYlTmJR0Y8tDl8ik$]] has the vulnerable file commons-text-1.9.jar, which falls under the affected range “version 1.5 and continuing through 1.9”. Inside the folder /tools/Pulse, there is the file geode-pulse-1.15.1.war. Inside that war file, there is the file geode-pulse-1.15.1.war/WEB-INF/lib/commons-text-1.9.jar. As a temporary workaround, I replaced the file commons-text-1.9.jar with commons-text-1.10.0.jar, updated the MANIFEST.MF file under geode-pulse-1.15.1.war/META-INF, and created a new geode-pulse-1.15.1.war file including the 2 updated files mentioned. Unfortunately, I’m not a developer. I’m not familiar with Github, so as much as I would like to help in contributing in the code, there is a more appropriate person to perform the update to commons-text 1.10.0. I have sent a mail to ASF Security Team, and I was given this [link|[https://github.com/apache/geode/blob/master/build-tools/geode-dependency-management/src/main/groovy/org/apache/geode/gradle/plugins/DependencyConstraints.groovy#L144|https://urldefense.com/v3/__https:/github.com/apache/geode/blob/master/build-tools/geode-dependency-management/src/main/groovy/org/apache/geode/gradle/plugins/DependencyConstraints.groovy*L144__;Iw!!OrxsNty6D4my!6EKoN5DUPbSrn9BPavV5jC0T1h5U4Ih1aqdG5cHGJt2a0fqw2jCVoWL4Nl1lCC4hkzC3buVr9YC30Y_jxCSk43yE-FU$]] that shows the dependency on the vulnerable commons-text version 1.9. Can somebody assist in fixing this security vulnerability? Thank you in advance! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10448) CVE-2022-42889 Apache Commons Text security vulnerability in Apache Geode
[ https://issues.apache.org/jira/browse/GEODE-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10448: -- Labels: needsTriage (was: ) > CVE-2022-42889 Apache Commons Text security vulnerability in Apache Geode > - > > Key: GEODE-10448 > URL: https://issues.apache.org/jira/browse/GEODE-10448 > Project: Geode > Issue Type: Bug > Components: pulse, tools >Affects Versions: 1.15.1 >Reporter: Eli >Priority: Major > Labels: needsTriage > > I have encountered the security vulnerability > [CVE-2022-42889|https://lists.apache.org/thread/n2bd4vdsgkqh2tm14l1wyc3jyol7s1om] > related to Apache Commons Text. It is mentioned that the mitigation is to > "Upgrade to [Apache Commons Text > 1.10.0|https://commons.apache.org/proper/commons-text/download_text.cgi]."; > because the following jar files are present. > /locator01/GemFire_gemfire/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar > > /locator01/GemFire_root/services/http/0.0.0.0_7070_pulse_/webapp/WEB-INF/lib/commons-text-1.9.jar > The latest official [Apache Geode version > 1.15.1|[https://apache.org/dyn/closer.cgi/geode/1.15.1/apache-geode-1.15.1.tgz|https://urldefense.com/v3/__https:/apache.org/dyn/closer.cgi/geode/1.15.1/apache-geode-1.15.1.tgz__;!!OrxsNty6D4my!7476fkBhS9dRAajU_LNsgk5KeehflkDwT1rsdOg5_lmW9F-rnt-zPr7K5J66Ylc8jzr9eR10QsOBYlTmJR0Y8tDl8ik$]] > has the vulnerable file commons-text-1.9.jar, which falls under the affected > range “version 1.5 and continuing through 1.9”. Inside the folder > /tools/Pulse, there is the file geode-pulse-1.15.1.war. Inside > that war file, there is the file > geode-pulse-1.15.1.war/WEB-INF/lib/commons-text-1.9.jar. > As a temporary workaround, I replaced the file commons-text-1.9.jar with > commons-text-1.10.0.jar, updated the MANIFEST.MF file under > geode-pulse-1.15.1.war/META-INF, and created a new geode-pulse-1.15.1.war > file including the 2 updated files mentioned. > Unfortunately, I’m not a developer. I’m not familiar with Github, so as much > as I would like to help in contributing in the code, there is a more > appropriate person to perform the update to commons-text 1.10.0. I have sent > a mail to ASF Security Team, and I was given this > [link|[https://github.com/apache/geode/blob/master/build-tools/geode-dependency-management/src/main/groovy/org/apache/geode/gradle/plugins/DependencyConstraints.groovy#L144|https://urldefense.com/v3/__https:/github.com/apache/geode/blob/master/build-tools/geode-dependency-management/src/main/groovy/org/apache/geode/gradle/plugins/DependencyConstraints.groovy*L144__;Iw!!OrxsNty6D4my!6EKoN5DUPbSrn9BPavV5jC0T1h5U4Ih1aqdG5cHGJt2a0fqw2jCVoWL4Nl1lCC4hkzC3buVr9YC30Y_jxCSk43yE-FU$]] > that shows the dependency on the vulnerable commons-text version 1.9. > Can somebody assist in fixing this security vulnerability? Thank you in > advance! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10401) Oplog recovery takes too long due to fault in fastutil library
[
https://issues.apache.org/jira/browse/GEODE-10401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737102#comment-17737102
]
ASF subversion and git services commented on GEODE-10401:
-
Commit b828c9ff38a369bc5a4814e0ad2f0ddf7827 in geode's branch
refs/heads/develop from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b828c9ff38 ]
GEODE-10401: Replace 1.15.0 with 1.15.1 as old version (#7868)
Replace 1.15.0 with 1.15.1 in old versions and set as default Benchmarks
baseline on develop
to enable rolling upgrade tests from 1.15.1
The serialization version has not changed between 1.15.0 and 1.15.1,
so there should be no need to keep both
> Oplog recovery takes too long due to fault in fastutil library
> --
>
> Key: GEODE-10401
> URL: https://issues.apache.org/jira/browse/GEODE-10401
> Project: Geode
> Issue Type: Bug
>Reporter: Jakov Varenina
>Assignee: Jakov Varenina
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.1, 1.16.0
>
>
> {color:#0e101a}As we already know, the .drf file delete operations only
> contain OplogEntryID. During recovery, the server reads (byte by byte) each
> OplogEntryID and stores it in a HashSet to use later when recovering .crf
> files. There are two types of HashSets: IntOpenHashSet and LongOpenHashSet.
> The OplogEntryID of type
> {color}_{color:#0e101a}integer{color}_{color:#0e101a} will be stored in
> IntOpenHashSet, and {color}_{color:#0e101a}long
> integer{color}_{color:#0e101a} in LongOpenHashSet, probably due to memory
> optimization and performance factors. OplogEntryID starts with a zero and
> increments throughout time.
> {color}
> {color:#0e101a}We have observed in logs that between exception (There is a
> large number of deleted entries) and the previous log have passed more than 4
> minutes (sometimes even more).{color}
> {code:java}
> {"timestamp":"2022-06-14T21:41:43.772+08:00","severity":"info","message":"Recovering
> oplog#271 /opt/dbservice/data/datastore/BACKUPdataDiskStore_271.drf for disk
> store dataDiskStore.","metadata":
> {"timestamp":"2022-06-14T21:46:02.152+08:00","severity":"warning","message":"There
> is a large number of deleted entries within the disk-store, please execute
> an offline
> compaction.","metadata":
> {code}
> {color:#0e101a}When the above exception occurs, that means that the limit of
> {color}_{color:#0e101a}805306401{color}_{color:#0e101a} entries in
> IntOpenHashSet has been reached. In that case, the server rolls to the new
> IntOpenHashSet, where an exception and the delay could happen again.{color}
> {color:#0e101a}The problem is that due to the fault in FastUtil dependency
> (IntOpenHashSet and LongOpenHashSet), the unnecessary rehashing happens
> multiple times before the max size is reached. The{color}
> _{color:#0e101a}rehashing starts from{color}_ {color:#0e101a}805306368
> onwards for each new entry until the max size. This rehashing adds several
> minutes to .drf Oplog recovery, but does nothing as max is already
> reached.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (GEODE-10447) Support JDK11 for Geode
[ https://issues.apache.org/jira/browse/GEODE-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17734007#comment-17734007 ] ASF subversion and git services commented on GEODE-10447: - Commit b81e9d486a2ba160e245575c95d3b483d73ee360 in geode's branch refs/heads/develop from jakevin [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b81e9d486a ] GEODE-10447: improve code for supporting JDK11 (#7882) > Support JDK11 for Geode > --- > > Key: GEODE-10447 > URL: https://issues.apache.org/jira/browse/GEODE-10447 > Project: Geode > Issue Type: Improvement >Reporter: Jie Wen >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10447) Support JDK11 for Geode
[ https://issues.apache.org/jira/browse/GEODE-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10447: --- Labels: pull-request-available (was: ) > Support JDK11 for Geode > --- > > Key: GEODE-10447 > URL: https://issues.apache.org/jira/browse/GEODE-10447 > Project: Geode > Issue Type: Improvement >Reporter: Jie Wen >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10447) Support JDK11 for Geode
Jie Wen created GEODE-10447: --- Summary: Support JDK11 for Geode Key: GEODE-10447 URL: https://issues.apache.org/jira/browse/GEODE-10447 Project: Geode Issue Type: Improvement Reporter: Jie Wen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10443) Update shiro-core to version 1.11.0 for CVE-2022-40664
[ https://issues.apache.org/jira/browse/GEODE-10443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733786#comment-17733786 ] ASF subversion and git services commented on GEODE-10443: - Commit 55d92bb9683bf2c145219f22a122078d53f35364 in geode's branch refs/heads/develop from jakevin [ https://gitbox.apache.org/repos/asf?p=geode.git;h=55d92bb968 ] GEODE-10443: Update shiro-core to version 1.11.0 for CVE-2022-40664 (#7881) > Update shiro-core to version 1.11.0 for CVE-2022-40664 > -- > > Key: GEODE-10443 > URL: https://issues.apache.org/jira/browse/GEODE-10443 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.1 >Reporter: Ankush Mittal >Priority: Major > Labels: needsTriage, pull-request-available > > As per [https://nvd.nist.gov/vuln/detail/CVE-2022-40664] , > _"Apache Shiro before 1.10.0, Authentication Bypass Vulnerability in Shiro > when forwarding or including via RequestDispatcher."_ > Geode 1.15.1 bundles version 1.9.1 of shiro-core jar which is vulnerable as > per the CVE. > Also although the CVE doesn't include "1.10.0", but since more latest version > "1.11.0" is available, logged ticket to bundle the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10443) Update shiro-core to version 1.11.0 for CVE-2022-40664
[ https://issues.apache.org/jira/browse/GEODE-10443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10443: --- Labels: needsTriage pull-request-available (was: needsTriage) > Update shiro-core to version 1.11.0 for CVE-2022-40664 > -- > > Key: GEODE-10443 > URL: https://issues.apache.org/jira/browse/GEODE-10443 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.1 >Reporter: Ankush Mittal >Priority: Major > Labels: needsTriage, pull-request-available > > As per [https://nvd.nist.gov/vuln/detail/CVE-2022-40664] , > _"Apache Shiro before 1.10.0, Authentication Bypass Vulnerability in Shiro > when forwarding or including via RequestDispatcher."_ > Geode 1.15.1 bundles version 1.9.1 of shiro-core jar which is vulnerable as > per the CVE. > Also although the CVE doesn't include "1.10.0", but since more latest version > "1.11.0" is available, logged ticket to bundle the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10446) Capture build scans on ge.apache.org to benefit from deep build insights
[ https://issues.apache.org/jira/browse/GEODE-10446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10446: --- Labels: pull-request-available (was: ) > Capture build scans on ge.apache.org to benefit from deep build insights > -- > > Key: GEODE-10446 > URL: https://issues.apache.org/jira/browse/GEODE-10446 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Clay Johnson >Priority: Major > Labels: pull-request-available > > This improvement will enhance the functionality of the Geode build by > publishing build scans to [ge.apache.org|https://ge.apache.org/], hosted by > the Apache Software Foundation and run in partnership between the ASF and > Gradle. This Gradle Enterprise instance has all features and extensions > enabled and is freely available for use by the Apache Geode project and all > other Apache projects. > On this Gradle Enterprise instance, Apache Geode will have access not only to > all of the published build scans but other aggregate data features such as: > * Dashboards to view all historical build scans, along with performance > trends over time > * Build failure analytics for enhanced investigation and diagnosis of build > failures > * Test failure analytics to better understand trends and causes around slow, > failing, and flaky tests > If interested in exploring a fully populated Gradle Enterprise instance, > please explore the Maven builds already connected to > [ge.apache.org|https://ge.apache.org/], the [Spring project’s > instance|https://ge.spring.io/scans?search.relativeStartTime=P28D&search.timeZoneId=Europe/Zurich], > or any number of other [OSS > projects|https://gradle.com/enterprise-customers/oss-projects/] for which we > sponsor instances of Gradle Enterprise. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10446) Capture build scans on ge.apache.org to benefit from deep build insights
[ https://issues.apache.org/jira/browse/GEODE-10446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731616#comment-17731616 ] ASF subversion and git services commented on GEODE-10446: - Commit 77f1afdbac9208511be14553d5f110d9445faa3b in geode's branch refs/heads/develop from Clay Johnson [ https://gitbox.apache.org/repos/asf?p=geode.git;h=77f1afdbac ] GEODE-10446: Capture build scans on ge.apache.org to benefit from deep build insights (#7879) > Capture build scans on ge.apache.org to benefit from deep build insights > -- > > Key: GEODE-10446 > URL: https://issues.apache.org/jira/browse/GEODE-10446 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Clay Johnson >Priority: Major > Labels: pull-request-available > > This improvement will enhance the functionality of the Geode build by > publishing build scans to [ge.apache.org|https://ge.apache.org/], hosted by > the Apache Software Foundation and run in partnership between the ASF and > Gradle. This Gradle Enterprise instance has all features and extensions > enabled and is freely available for use by the Apache Geode project and all > other Apache projects. > On this Gradle Enterprise instance, Apache Geode will have access not only to > all of the published build scans but other aggregate data features such as: > * Dashboards to view all historical build scans, along with performance > trends over time > * Build failure analytics for enhanced investigation and diagnosis of build > failures > * Test failure analytics to better understand trends and causes around slow, > failing, and flaky tests > If interested in exploring a fully populated Gradle Enterprise instance, > please explore the Maven builds already connected to > [ge.apache.org|https://ge.apache.org/], the [Spring project’s > instance|https://ge.spring.io/scans?search.relativeStartTime=P28D&search.timeZoneId=Europe/Zurich], > or any number of other [OSS > projects|https://gradle.com/enterprise-customers/oss-projects/] for which we > sponsor instances of Gradle Enterprise. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10446) Capture build scans on ge.apache.org to benefit from deep build insights
Clay Johnson created GEODE-10446: Summary: Capture build scans on ge.apache.org to benefit from deep build insights Key: GEODE-10446 URL: https://issues.apache.org/jira/browse/GEODE-10446 Project: Geode Issue Type: Improvement Components: build Reporter: Clay Johnson This improvement will enhance the functionality of the Geode build by publishing build scans to [ge.apache.org|https://ge.apache.org/], hosted by the Apache Software Foundation and run in partnership between the ASF and Gradle. This Gradle Enterprise instance has all features and extensions enabled and is freely available for use by the Apache Geode project and all other Apache projects. On this Gradle Enterprise instance, Apache Geode will have access not only to all of the published build scans but other aggregate data features such as: * Dashboards to view all historical build scans, along with performance trends over time * Build failure analytics for enhanced investigation and diagnosis of build failures * Test failure analytics to better understand trends and causes around slow, failing, and flaky tests If interested in exploring a fully populated Gradle Enterprise instance, please explore the Maven builds already connected to [ge.apache.org|https://ge.apache.org/], the [Spring project’s instance|https://ge.spring.io/scans?search.relativeStartTime=P28D&search.timeZoneId=Europe/Zurich], or any number of other [OSS projects|https://gradle.com/enterprise-customers/oss-projects/] for which we sponsor instances of Gradle Enterprise. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10445) [Geode Main] Migrate distributedTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713369#comment-17713369 ] ASF subversion and git services commented on GEODE-10445: - Commit 268e1a1e932c8095c5ae125114692f4e2d7a522f in geode's branch refs/heads/feature/gha-windows-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=268e1a1e93 ] GEODE-10445: Add distributed tests to pipeline (#7877) Included wan, cq, lucene, assembly and management DUnit test jobs as individual steps in the pipeline to deal with 6hr max timeout. > [Geode Main] Migrate distributedTest to GHA > --- > > Key: GEODE-10445 > URL: https://issues.apache.org/jira/browse/GEODE-10445 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10445) [Geode Main] Migrate distributedTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712884#comment-17712884 ] ASF subversion and git services commented on GEODE-10445: - Commit 268e1a1e932c8095c5ae125114692f4e2d7a522f in geode's branch refs/heads/develop from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=268e1a1e93 ] GEODE-10445: Add distributed tests to pipeline (#7877) Included wan, cq, lucene, assembly and management DUnit test jobs as individual steps in the pipeline to deal with 6hr max timeout. > [Geode Main] Migrate distributedTest to GHA > --- > > Key: GEODE-10445 > URL: https://issues.apache.org/jira/browse/GEODE-10445 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10445) [Geode Main] Migrate distributedTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10445: --- Labels: pull-request-available (was: ) > [Geode Main] Migrate distributedTest to GHA > --- > > Key: GEODE-10445 > URL: https://issues.apache.org/jira/browse/GEODE-10445 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GEODE-10445) [Geode Main] Migrate distributedTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-10445: --- Assignee: Sai Boorlagadda > [Geode Main] Migrate distributedTest to GHA > --- > > Key: GEODE-10445 > URL: https://issues.apache.org/jira/browse/GEODE-10445 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10445) [Geode Main] Migrate distributedTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712671#comment-17712671 ] ASF subversion and git services commented on GEODE-10445: - Commit 18728686401ab00e5be04a9317c548ba5b2f01cb in geode's branch refs/heads/feature/gha-distributed-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1872868640 ] GEODE-10445: Add distributed tests to pipeline Included wan, cq, lucene, assembly and management DUnit test jobs as individual steps in the pipeline to deal with 6hr max timeout. > [Geode Main] Migrate distributedTest to GHA > --- > > Key: GEODE-10445 > URL: https://issues.apache.org/jira/browse/GEODE-10445 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10445) [Geode Main] Migrate distributedTest to GHA
Sai Boorlagadda created GEODE-10445: --- Summary: [Geode Main] Migrate distributedTest to GHA Key: GEODE-10445 URL: https://issues.apache.org/jira/browse/GEODE-10445 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-10442. - Resolution: Fixed > [Geode Main] Migrate acceptanceTest to GHA > -- > > Key: GEODE-10442 > URL: https://issues.apache.org/jira/browse/GEODE-10442 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706656#comment-17706656 ] ASF subversion and git services commented on GEODE-10442: - Commit e05ecbe5ae8bf7cad5b941dfcebed18a2c34f9ff in geode's branch refs/heads/develop from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e05ecbe5ae ] GEODE-10442: Add acceptanceTest step to GHA pipeline (#7876) Upgraded testcontainers dependency to newer version as newer version fixed a requirement of needing 2GB disk available for docker. Moved MsgStreamerTest and PartitionRegionRebalanceOpTest into integration test suite as they are creating distribution system > [Geode Main] Migrate acceptanceTest to GHA > -- > > Key: GEODE-10442 > URL: https://issues.apache.org/jira/browse/GEODE-10442 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10444) Difference Between Pivotal Gemfire and Apache Geode
[ https://issues.apache.org/jira/browse/GEODE-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bretl resolved GEODE-10444. Assignee: Mark Bretl Resolution: Done Hi [~rhajvijay] , excellent question, however, I do not think a Jira is the right place to answer this. I would highly recommend emailing the Geode User group, u...@geode.apache.org, this question so it can be seen by all and archived on the list for later viewing. Please let me know if you have any issues emailing the distribution list. --Mark > Difference Between Pivotal Gemfire and Apache Geode > --- > > Key: GEODE-10444 > URL: https://issues.apache.org/jira/browse/GEODE-10444 > Project: Geode > Issue Type: New Feature >Reporter: Rhajvijay Manoharan >Assignee: Mark Bretl >Priority: Major > > Hi Team, > I had worked on Pivotal Gemfire. And I'm convinced to use Apache Geode as its > open source. I would like to know the differences between the both. And want > to know the features which are in Gemfire that are not available with Geode. > Thanks, > Rhaj Vijay Manoharan -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10444) Difference Between Pivotal Gemfire and Apache Geode
Rhajvijay Manoharan created GEODE-10444: --- Summary: Difference Between Pivotal Gemfire and Apache Geode Key: GEODE-10444 URL: https://issues.apache.org/jira/browse/GEODE-10444 Project: Geode Issue Type: New Feature Reporter: Rhajvijay Manoharan Hi Team, I had worked on Pivotal Gemfire. And I'm convinced to use Apache Geode as its open source. I would like to know the differences between the both. And want to know the features which are in Gemfire that are not available with Geode. Thanks, Rhaj Vijay Manoharan -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706194#comment-17706194 ] ASF subversion and git services commented on GEODE-10442: - Commit da2ef9803149f86bb3bebbfacc46659b6dc9faf2 in geode's branch refs/heads/feature/gha-acceptance-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=da2ef98031 ] GEODE-10442: Add acceptanceTest step to GHA pipeline Upgraded testcontainers dependency to newer version as newer version fixed a requirement of needing 2GB disk available for docker. Moved MsgStreamerTest and PartitionRegionRebalanceOpTest into integration test suite as they are creating distribution system > [Geode Main] Migrate acceptanceTest to GHA > -- > > Key: GEODE-10442 > URL: https://issues.apache.org/jira/browse/GEODE-10442 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10442: --- Labels: pull-request-available (was: ) > [Geode Main] Migrate acceptanceTest to GHA > -- > > Key: GEODE-10442 > URL: https://issues.apache.org/jira/browse/GEODE-10442 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705997#comment-17705997 ] ASF subversion and git services commented on GEODE-10442: - Commit 2752f41bfbea0eefdba872494d733d480cac40cd in geode's branch refs/heads/feature/gha-acceptance-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2752f41bfb ] GEODE-10442: Add acceptanceTest step to GHA pipeline Upgraded testcontainers dependency to newer version as newer version fixed a requirement of needing 2GB disk available for docker. Moved MsgStreamerTest and PartitionRegionRebalanceOpTest into integration test suite as they are creating distribution system > [Geode Main] Migrate acceptanceTest to GHA > -- > > Key: GEODE-10442 > URL: https://issues.apache.org/jira/browse/GEODE-10442 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10440) Add support for Micrometer Observation
[ https://issues.apache.org/jira/browse/GEODE-10440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705779#comment-17705779 ] Sai Boorlagadda commented on GEODE-10440: - [~marcingrzejszczak] thanks for reaching out. The community is kind of a reset since both supported companies have recently withdrawn their support. But I am more than happy to learn about this new feature from micrometer and would be willing to review the PR and merge it. > Add support for Micrometer Observation > -- > > Key: GEODE-10440 > URL: https://issues.apache.org/jira/browse/GEODE-10440 > Project: Geode > Issue Type: New Feature >Reporter: Marcin Grzejszczak >Priority: Major > > I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together > with Tommy Ludwig and Jonatan Ivanov). > [Micrometer Observation|https://micrometer.io/docs/observation] is coming as > part of the Micrometer 1.10 release and [Micrometer > Tracing|https://micrometer.io/docs/tracing] is a new project. The idea of > Micrometer Observation is that you instrument code once but you get multiple > benefits out of it - e.g. you can get tracing, metrics, logging or whatever > you see fit). > Since this project already supports Micrometer I was curious if there's > interest in adding Micrometer Observation support so that automatically (when > on classpath) except for metrics, spans could be created and tracing context > propagation could happen too. In other words metrics and tracing of this > project could be created + if there are Micrometer Observation compatible > projects, then they will join the whole graph (e.g. whole Spring Framework 6 > is, Apache Dubbo, Resilience4j etc.). > If there's interest in adding that feature, I can provide a PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705676#comment-17705676 ] ASF subversion and git services commented on GEODE-10442: - Commit de5178508418ef5afb966c02b513221325fa696e in geode's branch refs/heads/feature/gha-acceptance-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=de51785084 ] GEODE-10442: Add acceptanceTest step to GHA pipeline Upgraded testcontainers dependency to newer version as newer version fixed a requirement of needing 2GB disk available for docker. > [Geode Main] Migrate acceptanceTest to GHA > -- > > Key: GEODE-10442 > URL: https://issues.apache.org/jira/browse/GEODE-10442 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10443) Update shiro-core to version 1.11.0 for CVE-2022-40664
[ https://issues.apache.org/jira/browse/GEODE-10443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankush Mittal updated GEODE-10443: -- Description: As per [https://nvd.nist.gov/vuln/detail/CVE-2022-40664] , _"Apache Shiro before 1.10.0, Authentication Bypass Vulnerability in Shiro when forwarding or including via RequestDispatcher."_ Geode 1.15.1 bundles version 1.9.1 of shiro-core jar which is vulnerable as per the CVE. Also although the CVE doesn't include "1.10.0", but since more latest version "1.11.0" is available, logged ticket to bundle the same. was: As per [https://nvd.nist.gov/vuln/detail/CVE-2022-40664] , _"Apache Shiro before 1.10.0, Authentication Bypass Vulnerability in Shiro when forwarding or including via RequestDispatcher."_ Geode 1.15.1 bundles version 1.9.1 of shiro-core jar which is vulnerable as per the CVE. Also although the CVE doesn't include "1.10.0", but since more latest version "1.11.0" is available, logged ticket to bundle the same. > Update shiro-core to version 1.11.0 for CVE-2022-40664 > -- > > Key: GEODE-10443 > URL: https://issues.apache.org/jira/browse/GEODE-10443 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.1 >Reporter: Ankush Mittal >Priority: Major > Labels: needsTriage > > As per [https://nvd.nist.gov/vuln/detail/CVE-2022-40664] , > _"Apache Shiro before 1.10.0, Authentication Bypass Vulnerability in Shiro > when forwarding or including via RequestDispatcher."_ > Geode 1.15.1 bundles version 1.9.1 of shiro-core jar which is vulnerable as > per the CVE. > Also although the CVE doesn't include "1.10.0", but since more latest version > "1.11.0" is available, logged ticket to bundle the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10443) Update shiro-core to version 1.11.0 for CVE-2022-40664
Ankush Mittal created GEODE-10443: - Summary: Update shiro-core to version 1.11.0 for CVE-2022-40664 Key: GEODE-10443 URL: https://issues.apache.org/jira/browse/GEODE-10443 Project: Geode Issue Type: Bug Affects Versions: 1.15.1 Reporter: Ankush Mittal As per [https://nvd.nist.gov/vuln/detail/CVE-2022-40664] , _"Apache Shiro before 1.10.0, Authentication Bypass Vulnerability in Shiro when forwarding or including via RequestDispatcher."_ Geode 1.15.1 bundles version 1.9.1 of shiro-core jar which is vulnerable as per the CVE. Also although the CVE doesn't include "1.10.0", but since more latest version "1.11.0" is available, logged ticket to bundle the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10443) Update shiro-core to version 1.11.0 for CVE-2022-40664
[ https://issues.apache.org/jira/browse/GEODE-10443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10443: -- Labels: needsTriage (was: ) > Update shiro-core to version 1.11.0 for CVE-2022-40664 > -- > > Key: GEODE-10443 > URL: https://issues.apache.org/jira/browse/GEODE-10443 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.1 >Reporter: Ankush Mittal >Priority: Major > Labels: needsTriage > > As per [https://nvd.nist.gov/vuln/detail/CVE-2022-40664] , > _"Apache Shiro before 1.10.0, Authentication Bypass Vulnerability in Shiro > when forwarding or including via RequestDispatcher."_ > > Geode 1.15.1 bundles version 1.9.1 of shiro-core jar which is vulnerable as > per the CVE. > > Also although the CVE doesn't include "1.10.0", but since more latest version > "1.11.0" is available, logged ticket to bundle the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688600#comment-17688600 ] ASF subversion and git services commented on GEODE-10442: - Commit 341e8ffac8360887e9bfa01429589411b7bfa7d9 in geode's branch refs/heads/feature/gha-acceptance-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=341e8ffac8 ] GEODE-10442: Add acceptanceTest step to GHA pipeline Added .testcontainers.properties to disable checks, in order for test containers not to check for atleast 2GB disk available for docker. > [Geode Main] Migrate acceptanceTest to GHA > -- > > Key: GEODE-10442 > URL: https://issues.apache.org/jira/browse/GEODE-10442 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-10442: --- Assignee: Sai Boorlagadda > [Geode Main] Migrate acceptanceTest to GHA > -- > > Key: GEODE-10442 > URL: https://issues.apache.org/jira/browse/GEODE-10442 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
Sai Boorlagadda created GEODE-10442: --- Summary: [Geode Main] Migrate acceptanceTest to GHA Key: GEODE-10442 URL: https://issues.apache.org/jira/browse/GEODE-10442 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10441) [Geode Main] Migrate integrationTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688312#comment-17688312 ] ASF subversion and git services commented on GEODE-10441: - Commit faa6fe4571c8335f36107862d6423fc460c0b8e7 in geode's branch refs/heads/feature/gha-acceptance-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=faa6fe4571 ] GEODE-10441: Migrate integrationTest to Github Action (#7872) * Added integrationTest job that depends on both apiCheck and unitTest * Made unitTest depend on build so it can be parallel to apiCheck > [Geode Main] Migrate integrationTest to GHA > --- > > Key: GEODE-10441 > URL: https://issues.apache.org/jira/browse/GEODE-10441 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10441) [Geode Main] Migrate integrationTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-10441. - Resolution: Fixed > [Geode Main] Migrate integrationTest to GHA > --- > > Key: GEODE-10441 > URL: https://issues.apache.org/jira/browse/GEODE-10441 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10441) [Geode Main] Migrate integrationTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688277#comment-17688277 ] ASF subversion and git services commented on GEODE-10441: - Commit faa6fe4571c8335f36107862d6423fc460c0b8e7 in geode's branch refs/heads/develop from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=faa6fe4571 ] GEODE-10441: Migrate integrationTest to Github Action (#7872) * Added integrationTest job that depends on both apiCheck and unitTest * Made unitTest depend on build so it can be parallel to apiCheck > [Geode Main] Migrate integrationTest to GHA > --- > > Key: GEODE-10441 > URL: https://issues.apache.org/jira/browse/GEODE-10441 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10441) [Geode Main] Migrate integrationTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10441: --- Labels: pull-request-available (was: ) > [Geode Main] Migrate integrationTest to GHA > --- > > Key: GEODE-10441 > URL: https://issues.apache.org/jira/browse/GEODE-10441 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10441) [Geode Main] Migrate integrationTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686138#comment-17686138 ] ASF subversion and git services commented on GEODE-10441: - Commit e87067de766400f95c3ffdea1aa3eb4fba2b7e7f in geode's branch refs/heads/feature/gha-integration-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e87067de76 ] GEODE-10441: Migrate integrationTest to Github Action * Added integrationTest job that depends on both apiCheck and unitTest * Made unitTest depend on build so it can be parallel to apiCheck > [Geode Main] Migrate integrationTest to GHA > --- > > Key: GEODE-10441 > URL: https://issues.apache.org/jira/browse/GEODE-10441 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GEODE-10441) [Geode Main] Migrate integrationTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-10441: --- Assignee: Sai Boorlagadda > [Geode Main] Migrate integrationTest to GHA > --- > > Key: GEODE-10441 > URL: https://issues.apache.org/jira/browse/GEODE-10441 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10441) [Geode Main] Migrate integrationTest to GHA
Sai Boorlagadda created GEODE-10441: --- Summary: [Geode Main] Migrate integrationTest to GHA Key: GEODE-10441 URL: https://issues.apache.org/jira/browse/GEODE-10441 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-10434. - Resolution: Fixed > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686076#comment-17686076 ] ASF subversion and git services commented on GEODE-10434: - Commit d7cd8143506e173e1998ef1bfd6ee355a84a213d in geode's branch refs/heads/feature/gha-integration-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d7cd814350 ] GEODE-10434: Migrate to Github Action * Added integrationTest job that depends on both apiCheck and unitTest * Made unitTest depend on build so it can be parallel to apiCheck > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10440) Add support for Micrometer Observation
[ https://issues.apache.org/jira/browse/GEODE-10440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcin Grzejszczak updated GEODE-10440: --- Description: I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together with Tommy Ludwig and Jonatan Ivanov). [Micrometer Observation|https://micrometer.io/docs/observation] is coming as part of the Micrometer 1.10 release and [Micrometer Tracing|https://micrometer.io/docs/tracing] is a new project. The idea of Micrometer Observation is that you instrument code once but you get multiple benefits out of it - e.g. you can get tracing, metrics, logging or whatever you see fit). Since this project already supports Micrometer I was curious if there's interest in adding Micrometer Observation support so that automatically (when on classpath) except for metrics, spans could be created and tracing context propagation could happen too. In other words metrics and tracing of this project could be created + if there are Micrometer Observation compatible projects, then they will join the whole graph (e.g. whole Spring Framework 6 is, Apache Dubbo, Resilience4j etc.). If there's interest in adding that feature, I can provide a PR. was: I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together with Tommy Ludwig and Jonatan Ivanov). [Micrometer Observation|micrometer.io/docs/observation] is coming as part of the Micrometer 1.10 release and [Micrometer Tracing|micrometer.io/docs/tracing] is a new project. The idea of Micrometer Observation is that you instrument code once but you get multiple benefits out of it - e.g. you can get tracing, metrics, logging or whatever you see fit). Since this project already supports Micrometer I was curious if there's interest in adding Micrometer Observation support so that automatically (when on classpath) except for metrics, spans could be created and tracing context propagation could happen too. In other words metrics and tracing of this project could be created + if there are Micrometer Observation compatible projects, then they will join the whole graph (e.g. whole Spring Framework 6 is, Apache Dubbo, Resilience4j etc.). If there's interest in adding that feature, I can provide a PR. > Add support for Micrometer Observation > -- > > Key: GEODE-10440 > URL: https://issues.apache.org/jira/browse/GEODE-10440 > Project: Geode > Issue Type: New Feature >Reporter: Marcin Grzejszczak >Priority: Major > > I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together > with Tommy Ludwig and Jonatan Ivanov). > [Micrometer Observation|https://micrometer.io/docs/observation] is coming as > part of the Micrometer 1.10 release and [Micrometer > Tracing|https://micrometer.io/docs/tracing] is a new project. The idea of > Micrometer Observation is that you instrument code once but you get multiple > benefits out of it - e.g. you can get tracing, metrics, logging or whatever > you see fit). > Since this project already supports Micrometer I was curious if there's > interest in adding Micrometer Observation support so that automatically (when > on classpath) except for metrics, spans could be created and tracing context > propagation could happen too. In other words metrics and tracing of this > project could be created + if there are Micrometer Observation compatible > projects, then they will join the whole graph (e.g. whole Spring Framework 6 > is, Apache Dubbo, Resilience4j etc.). > If there's interest in adding that feature, I can provide a PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10440) Add support for Micrometer Observation
Marcin Grzejszczak created GEODE-10440: -- Summary: Add support for Micrometer Observation Key: GEODE-10440 URL: https://issues.apache.org/jira/browse/GEODE-10440 Project: Geode Issue Type: New Feature Reporter: Marcin Grzejszczak I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together with Tommy Ludwig and Jonatan Ivanov). [Micrometer Observation|micrometer.io/docs/observation] is coming as part of the Micrometer 1.10 release and [Micrometer Tracing|micrometer.io/docs/tracing] is a new project. The idea of Micrometer Observation is that you instrument code once but you get multiple benefits out of it - e.g. you can get tracing, metrics, logging or whatever you see fit). Since this project already supports Micrometer I was curious if there's interest in adding Micrometer Observation support so that automatically (when on classpath) except for metrics, spans could be created and tracing context propagation could happen too. In other words metrics and tracing of this project could be created + if there are Micrometer Observation compatible projects, then they will join the whole graph (e.g. whole Spring Framework 6 is, Apache Dubbo, Resilience4j etc.). If there's interest in adding that feature, I can provide a PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681664#comment-17681664 ] ASF subversion and git services commented on GEODE-10434: - Commit af430d39e2f610bb887d0cfa500f0e4d61a46f18 in geode's branch refs/heads/feature/gha-integration-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=af430d39e2 ] GEODE-10434: Migrate to Github action (#7870) * GEODE-10434: Migrate to Github Action * Added a build step for java 8 on ubuntu * Added a unit-test step for ubuntu that runs - using JDK 8 for build and tests using 8, 11 and 17 * Added apiCheck step > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681665#comment-17681665 ] ASF subversion and git services commented on GEODE-10434: - Commit ef12f211342d5d0acaefa61549b5de37e8682026 in geode's branch refs/heads/feature/gha-integration-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ef12f21134 ] GEODE-10434: Migrate to Github Action * Added a build step for java 8 on ubuntu * Added a unit-test step for ubuntu that runs - using JDK 8 for build and tests using 8, 11 and 17 > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681666#comment-17681666 ] ASF subversion and git services commented on GEODE-10434: - Commit bf57e06ebfeccdf6dff28e39cdbcd17884c3e81d in geode's branch refs/heads/feature/gha-integration-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bf57e06ebf ] GEODE-10434: Migrate to Github Action, added apiCheck * Added apiCheck step > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681662#comment-17681662 ] ASF subversion and git services commented on GEODE-10434: - Commit af430d39e2f610bb887d0cfa500f0e4d61a46f18 in geode's branch refs/heads/develop from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=af430d39e2 ] GEODE-10434: Migrate to Github action (#7870) * GEODE-10434: Migrate to Github Action * Added a build step for java 8 on ubuntu * Added a unit-test step for ubuntu that runs - using JDK 8 for build and tests using 8, 11 and 17 * Added apiCheck step > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10433) Migrate to new CI
[ https://issues.apache.org/jira/browse/GEODE-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681648#comment-17681648 ] ASF subversion and git services commented on GEODE-10433: - Commit d1bed0a4bf134286abd7114a743b587e2f75da66 in geode's branch refs/heads/master from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d1bed0a4bf ] GEODE-10433: remove concourse ci checks (#7875) > Migrate to new CI > - > > Key: GEODE-10433 > URL: https://issues.apache.org/jira/browse/GEODE-10433 > Project: Geode > Issue Type: New Feature > Components: build, ci >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > > Migrating Geode CI onto Apache Infra Jenkins from sponsored Concourse infra. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10433) Migrate to new CI
[ https://issues.apache.org/jira/browse/GEODE-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681615#comment-17681615 ] ASF subversion and git services commented on GEODE-10433: - Commit 124d16d9411ac56e8377fe2e121b065c7b82c533 in geode's branch refs/heads/feature/remove-concourse-required-checks from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=124d16d941 ] GEODE-10433: remove concourse ci checks > Migrate to new CI > - > > Key: GEODE-10433 > URL: https://issues.apache.org/jira/browse/GEODE-10433 > Project: Geode > Issue Type: New Feature > Components: build, ci >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > > Migrating Geode CI onto Apache Infra Jenkins from sponsored Concourse infra. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10433) Migrate to new CI
[ https://issues.apache.org/jira/browse/GEODE-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10433: --- Labels: pull-request-available (was: ) > Migrate to new CI > - > > Key: GEODE-10433 > URL: https://issues.apache.org/jira/browse/GEODE-10433 > Project: Geode > Issue Type: New Feature > Components: build, ci >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > > Migrating Geode CI onto Apache Infra Jenkins from sponsored Concourse infra. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10433) Migrate to new CI
[ https://issues.apache.org/jira/browse/GEODE-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681613#comment-17681613 ] ASF subversion and git services commented on GEODE-10433: - Commit b2d90d09d0afaa0a4caaf5aa9b18e2a652174001 in geode's branch refs/heads/feature/remove-concourse-required-checks from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b2d90d09d0 ] GEODE-10433: remove concourse ci checks > Migrate to new CI > - > > Key: GEODE-10433 > URL: https://issues.apache.org/jira/browse/GEODE-10433 > Project: Geode > Issue Type: New Feature > Components: build, ci >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > > Migrating Geode CI onto Apache Infra Jenkins from sponsored Concourse infra. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10434: --- Labels: pull-request-available (was: ) > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679679#comment-17679679 ] ASF subversion and git services commented on GEODE-10434: - Commit 2a76c983e7a9e5be4f8ddfc43c01ac4bdfc91475 in geode's branch refs/heads/feature/gha-integration-tests from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2a76c983e7 ] GEODE-10434: Migrate to Github Action, added apiCheck * Added apiCheck step > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679677#comment-17679677 ] ASF subversion and git services commented on GEODE-10434: - Commit 2a76c983e7a9e5be4f8ddfc43c01ac4bdfc91475 in geode's branch refs/heads/feature/gha from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2a76c983e7 ] GEODE-10434: Migrate to Github Action, added apiCheck * Added apiCheck step > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10439) [Geode Kafka Connector] Upgrade Github actions to latest versions
[ https://issues.apache.org/jira/browse/GEODE-10439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679676#comment-17679676 ] ASF subversion and git services commented on GEODE-10439: - Commit 2d99d0798f36e86b40805b21241ec4cc741530f6 in geode-kafka-connector's branch refs/heads/feature/gha-update from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode-kafka-connector.git;h=2d99d07 ] GEODE-10439: Upgrade github actions to newer versions * upgraded setup java and checkout actions to latest versions * limit to run on latest OS versions * uses liberica jdk 8 > [Geode Kafka Connector] Upgrade Github actions to latest versions > - > > Key: GEODE-10439 > URL: https://issues.apache.org/jira/browse/GEODE-10439 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GEODE-10439) [Geode Kafka Connector] Upgrade Github actions to latest versions
[ https://issues.apache.org/jira/browse/GEODE-10439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-10439: --- Assignee: Sai Boorlagadda > [Geode Kafka Connector] Upgrade Github actions to latest versions > - > > Key: GEODE-10439 > URL: https://issues.apache.org/jira/browse/GEODE-10439 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10439) [Geode Kafka Connector] Upgrade Github actions to latest versions
Sai Boorlagadda created GEODE-10439: --- Summary: [Geode Kafka Connector] Upgrade Github actions to latest versions Key: GEODE-10439 URL: https://issues.apache.org/jira/browse/GEODE-10439 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10438) [Geode Benchmarks] Migrate to GH Actions
[ https://issues.apache.org/jira/browse/GEODE-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-10438. - Resolution: Fixed > [Geode Benchmarks] Migrate to GH Actions > > > Key: GEODE-10438 > URL: https://issues.apache.org/jira/browse/GEODE-10438 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10438) [Geode Benchmarks] Migrate to GH Actions
[ https://issues.apache.org/jira/browse/GEODE-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679674#comment-17679674 ] ASF GitHub Bot commented on GEODE-10438: sboorlagadda merged PR #170: URL: https://github.com/apache/geode-benchmarks/pull/170 > [Geode Benchmarks] Migrate to GH Actions > > > Key: GEODE-10438 > URL: https://issues.apache.org/jira/browse/GEODE-10438 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10438) [Geode Benchmarks] Migrate to GH Actions
[ https://issues.apache.org/jira/browse/GEODE-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679675#comment-17679675 ] ASF subversion and git services commented on GEODE-10438: - Commit 60d0d831667eef964f1bed7afe26f6ef5a1298b4 in geode-benchmarks's branch refs/heads/develop from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode-benchmarks.git;h=60d0d831 ] GEODE-10438: Migrate to GH Actions (#170) * removed Travis CI configuration * added GH actions workflow > [Geode Benchmarks] Migrate to GH Actions > > > Key: GEODE-10438 > URL: https://issues.apache.org/jira/browse/GEODE-10438 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679656#comment-17679656 ] ASF subversion and git services commented on GEODE-10434: - Commit 7219156d6e00531d3b453ca80151f9a64aa843ec in geode's branch refs/heads/feature/gha-api-check from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7219156d6e ] GEODE-10434: Migrate to Github Action, added apiCheck * Added apiCheck step > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679652#comment-17679652 ] ASF subversion and git services commented on GEODE-10434: - Commit 0b795f1cd9ddb810201ecfa48445a0aa15919a9d in geode's branch refs/heads/feature/gha-api-check from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0b795f1cd9 ] GEODE-10434: Migrate to Github Action * Added apiCheck step > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679614#comment-17679614 ] ASF subversion and git services commented on GEODE-10434: - Commit 80a66524eaa1277dec55201d7b8e4a6f8087f007 in geode's branch refs/heads/feature/gha from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=80a66524ea ] GEODE-10434: Migrate to Github Action * Added a build step for java 8 on ubuntu * Added a unit-test step for ubuntu that runs - using JDK 8 for build and tests using 8, 11 and 17 > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
