[jira] [Commented] (GEODE-10089) release 1.15.0
[ https://issues.apache.org/jira/browse/GEODE-10089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562451#comment-17562451 ] ASF GitHub Bot commented on GEODE-10089: gaussianrecurrence commented on PR #976: URL: https://github.com/apache/geode-native/pull/976#issuecomment-1174754568 Hi :) Is there any plans to get this merged? I thought this needed to be merged before releasing 1.15.0 :S > release 1.15.0 > -- > > Key: GEODE-10089 > URL: https://issues.apache.org/jira/browse/GEODE-10089 > Project: Geode > Issue Type: Task > Components: release >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: pull-request-available > > As per [Jan 25 dev list > discussion|https://lists.apache.org/thread/s9mpd207h40crcr76fpdfmohdchgdqog], > support/1.15 was cut with the intention of stabilizing and releasing a new > Geode minor. > UPDATE: As per [Mar 16 dev list > discussion|https://lists.apache.org/thread/twlwzcvmx2kqw15whpmxkh2h8bmrok21], > support/1.15 was retracted. Work will continue on develop with an eye toward > re-cutting support/1.15 in ~June > UPDATE: support/1.15 was re-cut on May 9 with an eye toward shipping in mid > to late June (2022). > Release status information is also updated in the Geode [Release > Schedule|https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10089) release 1.15.0
[ https://issues.apache.org/jira/browse/GEODE-10089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562455#comment-17562455 ] ASF GitHub Bot commented on GEODE-10089: onichols-pivotal merged PR #976: URL: https://github.com/apache/geode-native/pull/976 > release 1.15.0 > -- > > Key: GEODE-10089 > URL: https://issues.apache.org/jira/browse/GEODE-10089 > Project: Geode > Issue Type: Task > Components: release >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: pull-request-available > > As per [Jan 25 dev list > discussion|https://lists.apache.org/thread/s9mpd207h40crcr76fpdfmohdchgdqog], > support/1.15 was cut with the intention of stabilizing and releasing a new > Geode minor. > UPDATE: As per [Mar 16 dev list > discussion|https://lists.apache.org/thread/twlwzcvmx2kqw15whpmxkh2h8bmrok21], > support/1.15 was retracted. Work will continue on develop with an eye toward > re-cutting support/1.15 in ~June > UPDATE: support/1.15 was re-cut on May 9 with an eye toward shipping in mid > to late June (2022). > Release status information is also updated in the Geode [Release > Schedule|https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10089) release 1.15.0
[ https://issues.apache.org/jira/browse/GEODE-10089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562456#comment-17562456 ] ASF subversion and git services commented on GEODE-10089: - Commit e28693188546e56f2b4e9f89ebf4105629a9c758 in geode-native's branch refs/heads/develop from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=e28693188 ] GEODE-10089: Bump Geode version to 1.15.0 (#976) Native client hardcodes Geode version to test with in several places. Update those variables to latest-and-greatest apache-geode 1.15.0 > release 1.15.0 > -- > > Key: GEODE-10089 > URL: https://issues.apache.org/jira/browse/GEODE-10089 > Project: Geode > Issue Type: Task > Components: release >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: pull-request-available > > As per [Jan 25 dev list > discussion|https://lists.apache.org/thread/s9mpd207h40crcr76fpdfmohdchgdqog], > support/1.15 was cut with the intention of stabilizing and releasing a new > Geode minor. > UPDATE: As per [Mar 16 dev list > discussion|https://lists.apache.org/thread/twlwzcvmx2kqw15whpmxkh2h8bmrok21], > support/1.15 was retracted. Work will continue on develop with an eye toward > re-cutting support/1.15 in ~June > UPDATE: support/1.15 was re-cut on May 9 with an eye toward shipping in mid > to late June (2022). > Release status information is also updated in the Geode [Release > Schedule|https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10396) IllegalStateException wrapped within FunctionException triggers endpoint disconnection
[ https://issues.apache.org/jira/browse/GEODE-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10396: --- Labels: needsTriage pull-request-available (was: needsTriage) > 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=17562504#comment-17562504 ] ASF GitHub Bot commented on GEODE-10396: gaussianrecurrence opened a new pull request, #977: URL: https://github.com/apache/geode-native/pull/977 - Currently whenever a server function is executed on a region with no filter, if an IllegalStateException wrapped within a FunctionException is thrown inside the server fuction body, then the endpoint's connections are closed, given the client considers the endpoint is failing. - In order to solve this, now it's checked if the exception is wrapped into a FunctionException before triggering the endpoint disconnection mechanism. - A new IT has been added to verify the behavior. > 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 > > *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-10392) Faulty statistics when parallel gateway sender is started with clean queue, on restarted member
[ https://issues.apache.org/jira/browse/GEODE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562611#comment-17562611 ] ASF subversion and git services commented on GEODE-10392: - Commit d6261cc3cce1b661714fb136c732addb8c11a33e in geode's branch refs/heads/develop from Mario Ivanac [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d6261cc3cc ] GEODE-10392: When gw sender started with cleanqueue remove EvictionController from diskstore (#7817) > Faulty statistics when parallel gateway sender is started with clean queue, > on restarted member > --- > > Key: GEODE-10392 > URL: https://issues.apache.org/jira/browse/GEODE-10392 > Project: Geode > Issue Type: Bug > Components: statistics, wan >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: needsTriage, pull-request-available > > we have following scenario: > we fill parallel gateway-sender queue with some events, restart one server, > and after it is recovered, execute stop gw sender, and then start gw sender > with clean queue option. > At this moment, queue is cleared, and all stats are zero. > After this moment, if we put any data in queue, you can see that stats > getTotalQueueSizeBytesInUse is 0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10392) Faulty statistics when parallel gateway sender is started with clean queue, on restarted member
[ https://issues.apache.org/jira/browse/GEODE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Ivanac resolved GEODE-10392. -- Fix Version/s: 1.16.0 Resolution: Fixed > Faulty statistics when parallel gateway sender is started with clean queue, > on restarted member > --- > > Key: GEODE-10392 > URL: https://issues.apache.org/jira/browse/GEODE-10392 > Project: Geode > Issue Type: Bug > Components: statistics, wan >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.16.0 > > > we have following scenario: > we fill parallel gateway-sender queue with some events, restart one server, > and after it is recovered, execute stop gw sender, and then start gw sender > with clean queue option. > At this moment, queue is cleared, and all stats are zero. > After this moment, if we put any data in queue, you can see that stats > getTotalQueueSizeBytesInUse is 0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10371) C++ Native client: Improve dispersion on connections expiration
[ https://issues.apache.org/jira/browse/GEODE-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562996#comment-17562996 ] ASF subversion and git services commented on GEODE-10371: - Commit e2ebf323a0c3f072a9256419c20b4313540219cf in geode-native's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=e2ebf323a ] GEODE-10371: C++ client: Improve dispersion on connections expiration > C++ Native client: Improve dispersion on connections expiration > --- > > Key: GEODE-10371 > URL: https://issues.apache.org/jira/browse/GEODE-10371 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > > The dispersion on connections expirations in the C++ native client works in > such a way that it adds a dispersion (variance) between -9% and 9% over the > time for a connection to expire due to load-conditioning so that, in the > event of having many connections being created at the same, they do not > expire at the right exact time. > Nevertheless, the current implementation has two problems: > - The randomness of the variance depends on the current time in seconds. As a > result, for connections created in the same second, the variance will be the > same and, therefore, the expiration time too. > - The randomness is created using the C standard's library "rand()" function > which is considered not secure. > It is recommended to change the library used to generate the random variance > to a secure one and also to make sure that for the time in seconds it does > not return the same variance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10371) C++ Native client: Improve dispersion on connections expiration
[ https://issues.apache.org/jira/browse/GEODE-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562997#comment-17562997 ] ASF subversion and git services commented on GEODE-10371: - Commit 6160f974ec7e88bba04bdaa58195d7de84fcd108 in geode-native's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=6160f974e ] GEODE-10371: Changes after review > C++ Native client: Improve dispersion on connections expiration > --- > > Key: GEODE-10371 > URL: https://issues.apache.org/jira/browse/GEODE-10371 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > > The dispersion on connections expirations in the C++ native client works in > such a way that it adds a dispersion (variance) between -9% and 9% over the > time for a connection to expire due to load-conditioning so that, in the > event of having many connections being created at the same, they do not > expire at the right exact time. > Nevertheless, the current implementation has two problems: > - The randomness of the variance depends on the current time in seconds. As a > result, for connections created in the same second, the variance will be the > same and, therefore, the expiration time too. > - The randomness is created using the C standard's library "rand()" function > which is considered not secure. > It is recommended to change the library used to generate the random variance > to a secure one and also to make sure that for the time in seconds it does > not return the same variance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10371) C++ Native client: Improve dispersion on connections expiration
[ https://issues.apache.org/jira/browse/GEODE-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562998#comment-17562998 ] ASF subversion and git services commented on GEODE-10371: - Commit d4d09908d49fb7748cd7141a01016fc4b298b4ca in geode-native's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=d4d09908d ] Merge pull request #974 from Nordix/feature/GEODE-10371 GEODE-10371: C++ client: Improve dispersion on connections expiration > C++ Native client: Improve dispersion on connections expiration > --- > > Key: GEODE-10371 > URL: https://issues.apache.org/jira/browse/GEODE-10371 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > > The dispersion on connections expirations in the C++ native client works in > such a way that it adds a dispersion (variance) between -9% and 9% over the > time for a connection to expire due to load-conditioning so that, in the > event of having many connections being created at the same, they do not > expire at the right exact time. > Nevertheless, the current implementation has two problems: > - The randomness of the variance depends on the current time in seconds. As a > result, for connections created in the same second, the variance will be the > same and, therefore, the expiration time too. > - The randomness is created using the C standard's library "rand()" function > which is considered not secure. > It is recommended to change the library used to generate the random variance > to a secure one and also to make sure that for the time in seconds it does > not return the same variance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10371) C++ Native client: Improve dispersion on connections expiration
[ https://issues.apache.org/jira/browse/GEODE-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562995#comment-17562995 ] ASF GitHub Bot commented on GEODE-10371: albertogpz merged PR #974: URL: https://github.com/apache/geode-native/pull/974 > C++ Native client: Improve dispersion on connections expiration > --- > > Key: GEODE-10371 > URL: https://issues.apache.org/jira/browse/GEODE-10371 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > > The dispersion on connections expirations in the C++ native client works in > such a way that it adds a dispersion (variance) between -9% and 9% over the > time for a connection to expire due to load-conditioning so that, in the > event of having many connections being created at the same, they do not > expire at the right exact time. > Nevertheless, the current implementation has two problems: > - The randomness of the variance depends on the current time in seconds. As a > result, for connections created in the same second, the variance will be the > same and, therefore, the expiration time too. > - The randomness is created using the C standard's library "rand()" function > which is considered not secure. > It is recommended to change the library used to generate the random variance > to a secure one and also to make sure that for the time in seconds it does > not return the same variance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
