[jira] [Updated] (GEODE-10355) bump spring-security to recommended version
[ https://issues.apache.org/jira/browse/GEODE-10355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-10355: - Fix Version/s: 1.12.10 1.14.5 > bump spring-security to recommended version > --- > > Key: GEODE-10355 > URL: https://issues.apache.org/jira/browse/GEODE-10355 > Project: Geode > Issue Type: Improvement >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.12.10, 1.14.5, 1.15.0, 1.16.0 > > > latest (5.5.8 or 5.6.5) is recommended -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10355) bump spring-security to recommended version
[ https://issues.apache.org/jira/browse/GEODE-10355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553800#comment-17553800 ] ASF subversion and git services commented on GEODE-10355: - Commit ed47063062b3d93c6c65f2be9ce6b58b731d4048 in geode's branch refs/heads/support/1.12 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ed47063062 ] GEODE-10355: Bump spring-security from 5.2.12 to 5.5.8 (#7770) Geode endeavors to update to the latest version of 3rd-party dependencies on develop wherever possible. Doing so increases the shelf life of releases and increases security and reliability. Doing so regularly makes the occasional hiccups this can cause easier to pinpoint and address. Dependency bumps in this batch: * Bump spring-security from 5.2.12.RELEASE to 5.5.8 > bump spring-security to recommended version > --- > > Key: GEODE-10355 > URL: https://issues.apache.org/jira/browse/GEODE-10355 > Project: Geode > Issue Type: Improvement >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0, 1.16.0 > > > latest (5.5.8 or 5.6.5) is recommended -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10355) bump spring-security to recommended version
[ https://issues.apache.org/jira/browse/GEODE-10355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553799#comment-17553799 ] ASF subversion and git services commented on GEODE-10355: - Commit 06cdd2658949213386ab56d2d077b50f0db9d023 in geode's branch refs/heads/support/1.14 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=06cdd26589 ] GEODE-10355: Bump spring-security from 5.4.8 to 5.6.5 (#7769) Geode endeavors to update to the latest version of 3rd-party dependencies on develop wherever possible. Doing so increases the shelf life of releases and increases security and reliability. Doing so regularly makes the occasional hiccups this can cause easier to pinpoint and address. Dependency bumps in this batch: * Bump spring-security from 5.4.8 to 5.6.5 > bump spring-security to recommended version > --- > > Key: GEODE-10355 > URL: https://issues.apache.org/jira/browse/GEODE-10355 > Project: Geode > Issue Type: Improvement >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0, 1.16.0 > > > latest (5.5.8 or 5.6.5) is recommended -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10369) Change heavy lifter instances types to E2
[ https://issues.apache.org/jira/browse/GEODE-10369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553768#comment-17553768 ] Geode Integration commented on GEODE-10369: --- Seen in [windows-unit-test-openjdk11 #413.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-unit-test-openjdk11/builds/413.1]. > Change heavy lifter instances types to E2 > - > > Key: GEODE-10369 > URL: https://issues.apache.org/jira/browse/GEODE-10369 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > To reduce CI costs, we should be using E2 instances. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10377) Add getter for CacheServiceProfile list to CacheDistributionAdvisor
[ https://issues.apache.org/jira/browse/GEODE-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Ingles resolved GEODE-10377. Resolution: Won't Do Instead of using a getter, extensions will use reflection. > Add getter for CacheServiceProfile list to CacheDistributionAdvisor > --- > > Key: GEODE-10377 > URL: https://issues.apache.org/jira/browse/GEODE-10377 > Project: Geode > Issue Type: New Feature > Components: core >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > > Clients of CacheDistributionAdvisor could use this feature to determine > features of members of the cluster. For example, the version of extensions on > other members could be determined, enhancing forward and backward > compatibility to simplify rolling upgrades of extensions. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10369) Change heavy lifter instances types to E2
[ https://issues.apache.org/jira/browse/GEODE-10369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553760#comment-17553760 ] ASF subversion and git services commented on GEODE-10369: - Commit e2ac1113f8f6819095785be556bef8e080ab6988 in geode's branch refs/heads/develop from Sean Goller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e2ac1113f8 ] GEODE-10369 part 2 Fix hardcoded gcp project reference and adjust windows unit test cpu/ram usage. (#7798) * Fix hardcoded reference to gcp project. * Fix windows unit test ram and cpu settings. > Change heavy lifter instances types to E2 > - > > Key: GEODE-10369 > URL: https://issues.apache.org/jira/browse/GEODE-10369 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > To reduce CI costs, we should be using E2 instances. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10377) Add getter for CacheServiceProfile list to CacheDistributionAdvisor
[ https://issues.apache.org/jira/browse/GEODE-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-10377: -- Labels: (was: blocks-1.15.0 needsTriage) > Add getter for CacheServiceProfile list to CacheDistributionAdvisor > --- > > Key: GEODE-10377 > URL: https://issues.apache.org/jira/browse/GEODE-10377 > Project: Geode > Issue Type: New Feature > Components: core >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > > Clients of CacheDistributionAdvisor could use this feature to determine > features of members of the cluster. For example, the version of extensions on > other members could be determined, enhancing forward and backward > compatibility to simplify rolling upgrades of extensions. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (GEODE-8745) Closing the region backing the queue when the serial gateway sender is stopped.
[
https://issues.apache.org/jira/browse/GEODE-8745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553608#comment-17553608
]
Jakov Varenina edited comment on GEODE-8745 at 6/13/22 2:25 PM:
Hi [~nnag] ,
When serial gateways senders are stopped and one server is forcefully
restarted, then the restarted server is stuck at the startup, indicating the
following:
{code:java}
[info 2022/06/13 11:37:22.550 CEST server-ln-3 tid=0x1] Region
/ny.0_SERIAL_GATEWAY_SENDER_QUEUE has potentially stale data. It is waiting for
another member to recover the latest data.{code}
Before this fix was introduced, the server would normally start with a running
serial gateway sender. Did you intentionally change this design base behavior?
was (Author: jvarenina):
Hi [~nnag] ,
When serial gateways senders are stopped and one server is restarted, then the
restarted server is stuck at the startup, indicating the following:
{code:java}
[info 2022/06/13 11:37:22.550 CEST server-ln-3 tid=0x1] Region
/ny.0_SERIAL_GATEWAY_SENDER_QUEUE has potentially stale data. It is waiting for
another member to recover the latest data.{code}
Before this fix was introduced, the server would normally start with a running
serial gateway sender. Did you intentionally change this design base behavior?
> Closing the region backing the queue when the serial gateway sender is
> stopped.
> ---
>
> Key: GEODE-8745
> URL: https://issues.apache.org/jira/browse/GEODE-8745
> Project: Geode
> Issue Type: Task
> Components: wan
>Reporter: Nabarun Nag
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> In the commit for GEODE-7458, when the sender is stopped, the region backing
> the queues are no more closed, but just remove the cache listeners.
> This is causing a problem, as the regions continue to exist, it keeps on
> storing entry events and hence the queue size never gets to zero.
> Also, as the region exists but before attaching the cache listener when
> restarting the sender leads to entries being never removed from the
> unprocessed event map.
>
> As mention in the PR for GEODE-7458 - "This option is only applicable for
> Gateway Senders with enabled persistence."
> Hence believe that it is ok to close the region as the disk files will still
> be maintained. so when we restart the values can be obtained back from the
> disk stores.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (GEODE-8745) Closing the region backing the queue when the serial gateway sender is stopped.
[
https://issues.apache.org/jira/browse/GEODE-8745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553608#comment-17553608
]
Jakov Varenina commented on GEODE-8745:
---
Hi [~nnag] ,
When serial gateways senders are stopped and one server is restarted, then the
restarted server is stuck at the startup, indicating the following:
{code:java}
[info 2022/06/13 11:37:22.550 CEST server-ln-3 tid=0x1] Region
/ny.0_SERIAL_GATEWAY_SENDER_QUEUE has potentially stale data. It is waiting for
another member to recover the latest data.{code}
Before this fix was introduced, the server would normally start with a running
serial gateway sender. Did you intentionally change this design base behavior?
> Closing the region backing the queue when the serial gateway sender is
> stopped.
> ---
>
> Key: GEODE-8745
> URL: https://issues.apache.org/jira/browse/GEODE-8745
> Project: Geode
> Issue Type: Task
> Components: wan
>Reporter: Nabarun Nag
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> In the commit for GEODE-7458, when the sender is stopped, the region backing
> the queues are no more closed, but just remove the cache listeners.
> This is causing a problem, as the regions continue to exist, it keeps on
> storing entry events and hence the queue size never gets to zero.
> Also, as the region exists but before attaching the cache listener when
> restarting the sender leads to entries being never removed from the
> unprocessed event map.
>
> As mention in the PR for GEODE-7458 - "This option is only applicable for
> Gateway Senders with enabled persistence."
> Hence believe that it is ok to close the region as the disk files will still
> be maintained. so when we restart the values can be obtained back from the
> disk stores.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (GEODE-10377) Add getter for CacheServiceProfile list to CacheDistributionAdvisor
[ https://issues.apache.org/jira/browse/GEODE-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Ingles reassigned GEODE-10377: -- Assignee: Ray Ingles > Add getter for CacheServiceProfile list to CacheDistributionAdvisor > --- > > Key: GEODE-10377 > URL: https://issues.apache.org/jira/browse/GEODE-10377 > Project: Geode > Issue Type: New Feature > Components: core >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > Labels: blocks-1.15.0, needsTriage > > Clients of CacheDistributionAdvisor could use this feature to determine > features of members of the cluster. For example, the version of extensions on > other members could be determined, enhancing forward and backward > compatibility to simplify rolling upgrades of extensions. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10267) Create gw sender with non-existent disk store does not fail
[
https://issues.apache.org/jira/browse/GEODE-10267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Kevo resolved GEODE-10267.
Fix Version/s: 1.16.0
Resolution: Fixed
> Create gw sender with non-existent disk store does not fail
> ---
>
> Key: GEODE-10267
> URL: https://issues.apache.org/jira/browse/GEODE-10267
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.14.4
>Reporter: Mario Kevo
>Assignee: Mario Kevo
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> While creating a parallel gw sender with a non-existing disk store, the
> command passed successfully but shouldn't.
> {code:java}
> gfsh>create gateway-sender --id=ln --remote-distributed-system-id=2
> --parallel=true --disk-store-name=nonExistingDiskStore
> Member | Status | Message
> --- | -- | ---
> server1 | OK | GatewaySender "ln" created on "server1"
> server2 | OK | GatewaySender "ln" created on "server2"
> Cluster configuration for group 'cluster' is updated.
> gfsh>list disk-stores
> No Disk Stores Found
> {code}
> For the serial gw sender, it throws that disk-store is not found as expected.
> {code:java}
> gfsh>create gateway-sender --id=ln-serial --remote-distributed-system-id=2
> --parallel=false --disk-store-name=nonExistingDiskStore
> Member | Status | Message
> --- | -- |
> ---
> server1 | ERROR | java.lang.IllegalStateException: Disk store
> nonExistingDiskStore not found
> server2 | ERROR | java.lang.IllegalStateException: Disk store
> nonExistingDiskStore not found
> {code}
> But after the above command for the serial gw sender is failed, execute list
> gateways and got that the serial gw sender is created.
> {code:java}
> gfsh>list gateways
> GatewaySender Section
> GatewaySender Id | Member | Remote Cluster Id
> | Type | Status| Queued Events | Receiver Location
> | -- | -
> | -- | --- | - | -
> ln2 | 192.168.0.145(server1:10868):41001 | 2
> | Serial | Not Running | 0 |
> ln2 | 192.168.0.145(server2:10963):41002 | 2
> | Serial | Not Running | 0 |
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (GEODE-10267) Create gw sender with non-existent disk store does not fail
[
https://issues.apache.org/jira/browse/GEODE-10267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553427#comment-17553427
]
ASF subversion and git services commented on GEODE-10267:
-
Commit d7ff22cd18bb3e08a73035e950e6e5523ff99bec in geode's branch
refs/heads/develop from Mario Kevo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d7ff22cd18 ]
GEODE-10267: fix creating gw sender with non-existent disk store (#7643)
* GEODE-10267: fix creating gw sender with non-existent disk store
> Create gw sender with non-existent disk store does not fail
> ---
>
> Key: GEODE-10267
> URL: https://issues.apache.org/jira/browse/GEODE-10267
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.14.4
>Reporter: Mario Kevo
>Assignee: Mario Kevo
>Priority: Major
> Labels: pull-request-available
>
> While creating a parallel gw sender with a non-existing disk store, the
> command passed successfully but shouldn't.
> {code:java}
> gfsh>create gateway-sender --id=ln --remote-distributed-system-id=2
> --parallel=true --disk-store-name=nonExistingDiskStore
> Member | Status | Message
> --- | -- | ---
> server1 | OK | GatewaySender "ln" created on "server1"
> server2 | OK | GatewaySender "ln" created on "server2"
> Cluster configuration for group 'cluster' is updated.
> gfsh>list disk-stores
> No Disk Stores Found
> {code}
> For the serial gw sender, it throws that disk-store is not found as expected.
> {code:java}
> gfsh>create gateway-sender --id=ln-serial --remote-distributed-system-id=2
> --parallel=false --disk-store-name=nonExistingDiskStore
> Member | Status | Message
> --- | -- |
> ---
> server1 | ERROR | java.lang.IllegalStateException: Disk store
> nonExistingDiskStore not found
> server2 | ERROR | java.lang.IllegalStateException: Disk store
> nonExistingDiskStore not found
> {code}
> But after the above command for the serial gw sender is failed, execute list
> gateways and got that the serial gw sender is created.
> {code:java}
> gfsh>list gateways
> GatewaySender Section
> GatewaySender Id | Member | Remote Cluster Id
> | Type | Status| Queued Events | Receiver Location
> | -- | -
> | -- | --- | - | -
> ln2 | 192.168.0.145(server1:10868):41001 | 2
> | Serial | Not Running | 0 |
> ln2 | 192.168.0.145(server2:10963):41002 | 2
> | Serial | Not Running | 0 |
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
