[jira] [Updated] (GEODE-9456) Create AuthenticationExpiredException and have the client handle that exception for re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9456: -- Labels: GeodeOperationAPI pull-request-available (was: GeodeOperationAPI) > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > - > > Key: GEODE-9456 > URL: https://issues.apache.org/jira/browse/GEODE-9456 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9460) add tests for multi-user mode when one user expires
[ https://issues.apache.org/jira/browse/GEODE-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9460: --- Labels: GeodeOperationAPI (was: ) > add tests for multi-user mode when one user expires > --- > > Key: GEODE-9460 > URL: https://issues.apache.org/jira/browse/GEODE-9460 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > make sure the behavior matches expections -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9460) add tests for multi-user mode when one user expires
Jinmei Liao created GEODE-9460: -- Summary: add tests for multi-user mode when one user expires Key: GEODE-9460 URL: https://issues.apache.org/jira/browse/GEODE-9460 Project: Geode Issue Type: Sub-task Reporter: Jinmei Liao make sure the behavior matches expections -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9459) add tests for wan connection when authentication expires
Jinmei Liao created GEODE-9459: -- Summary: add tests for wan connection when authentication expires Key: GEODE-9459 URL: https://issues.apache.org/jira/browse/GEODE-9459 Project: Geode Issue Type: Sub-task Reporter: Jinmei Liao make sure the behavior matches expections. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9459) add tests for wan connection when authentication expires
[ https://issues.apache.org/jira/browse/GEODE-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9459: --- Labels: GeodeOperationAPI (was: ) > add tests for wan connection when authentication expires > > > Key: GEODE-9459 > URL: https://issues.apache.org/jira/browse/GEODE-9459 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > make sure the behavior matches expections. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8200) Rebalance operations stuck in "IN_PROGRESS" state forever
[
https://issues.apache.org/jira/browse/GEODE-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386578#comment-17386578
]
Aaron Lindsey commented on GEODE-8200:
--
The only difference is that now it's happening for restore redundancy instead
of rebalance, but it's pretty much the same scenario where we see the issue.
(We switched to using restore redundancy instead of rebalance after that
operation was added to Geode.)
> Rebalance operations stuck in "IN_PROGRESS" state forever
> -
>
> Key: GEODE-8200
> URL: https://issues.apache.org/jira/browse/GEODE-8200
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Aaron Lindsey
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI
> Fix For: 1.13.1, 1.14.0
>
> Attachments: GEODE-8200-exportedLogs.zip
>
>
> We use the management REST API to call rebalance immediately before stopping
> a server to limit the possibility of data loss. In a cluster with 3 locators,
> 3 servers, and no regions, we noticed that sometimes the rebalance operation
> never ends if one of the locators is restarting concurrently with the
> rebalance operation.
> More specifically, the scenario where we see this issue crop up is during an
> automated "rolling restart" operation in a Kubernetes environment which
> proceeds as follows:
> * At most one locator and one server are restarting at any point in time
> * Each locator/server waits until the previous locator/server is fully online
> before restarting
> * Immediately before stopping a server, a rebalance operation is performed
> and the server is not stopped until the rebalance operation is completed
> The impact of this issue is that the "rolling restart" operation will never
> complete, because it cannot proceed with stopping a server until the
> rebalance operation is completed. A human is then required to intervene and
> manually trigger a rebalance and stop the server. This type of "rolling
> restart" operation is triggered fairly often in Kubernetes — any time part of
> the configuration of the locators or servers changes.
> The following JSON is a sample response from the management REST API that
> shows the rebalance operation stuck in "IN_PROGRESS".
> {code}
> {
> "statusCode": "IN_PROGRESS",
> "links": {
> "self":
> "http://geodecluster-sample-locator.default/management/v1/operations/rebalances/a47f23c8-02b3-443c-a367-636fd6921ea7;,
> "list":
> "http://geodecluster-sample-locator.default/management/v1/operations/rebalances;
> },
> "operationStart": "2020-05-27T22:38:30.619Z",
> "operationId": "a47f23c8-02b3-443c-a367-636fd6921ea7",
> "operation": {
> "simulate": false
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9458) Add tests for functions executions on servers when authentication expires
[ https://issues.apache.org/jira/browse/GEODE-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9458: --- Labels: GeodeOperationAPI (was: ) > Add tests for functions executions on servers when authentication expires > - > > Key: GEODE-9458 > URL: https://issues.apache.org/jira/browse/GEODE-9458 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > and make sure the behavior matches expection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9458) Add tests for functions executions on servers when authentication expires
Jinmei Liao created GEODE-9458: -- Summary: Add tests for functions executions on servers when authentication expires Key: GEODE-9458 URL: https://issues.apache.org/jira/browse/GEODE-9458 Project: Geode Issue Type: Sub-task Reporter: Jinmei Liao and make sure the behavior matches expection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9457) Investigate the behavior of CQ and registered interests when authentication expires.
[ https://issues.apache.org/jira/browse/GEODE-9457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9457: --- Labels: GeodeOperationAPI (was: ) > Investigate the behavior of CQ and registered interests when authentication > expires. > > > Key: GEODE-9457 > URL: https://issues.apache.org/jira/browse/GEODE-9457 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > We need to find out what's the current behavior of cq and registered > interests when authentication expires and see if the behavior matches the > expectation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9457) Investigate the behavior of CQ and registered interests when authentication expires.
Jinmei Liao created GEODE-9457: -- Summary: Investigate the behavior of CQ and registered interests when authentication expires. Key: GEODE-9457 URL: https://issues.apache.org/jira/browse/GEODE-9457 Project: Geode Issue Type: Sub-task Components: core, security Reporter: Jinmei Liao We need to find out what's the current behavior of cq and registered interests when authentication expires and see if the behavior matches the expectation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9456) Create AuthenticationExpiredException and have the client handle that exception for re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9456: --- Labels: GeodeOperationAPI (was: ) > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > - > > Key: GEODE-9456 > URL: https://issues.apache.org/jira/browse/GEODE-9456 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9456) Create AuthenticationExpiredException and have the client handle that exception for re-authentication
Jinmei Liao created GEODE-9456: -- Summary: Create AuthenticationExpiredException and have the client handle that exception for re-authentication Key: GEODE-9456 URL: https://issues.apache.org/jira/browse/GEODE-9456 Project: Geode Issue Type: Sub-task Components: core, security Reporter: Jinmei Liao Create AuthenticationExpiredException and have the client handle that exception for re-authentication -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9377) Revert deploymentName on Deployment configuration object.
[ https://issues.apache.org/jira/browse/GEODE-9377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Johnsn resolved GEODE-9377. --- Fix Version/s: 1.15.0 Resolution: Fixed > Revert deploymentName on Deployment configuration object. > - > > Key: GEODE-9377 > URL: https://issues.apache.org/jira/browse/GEODE-9377 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh, management >Reporter: Patrick Johnsn >Assignee: Patrick Johnsn >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Revert the addition of deploymentName to Deployment to avoid serialization > issues with older versions that use fileName. Deployment name was added as > part of ticket GEODE-8705, to support a dropped feature. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9289) Configuration Class cannot be deserialized in old locators
[ https://issues.apache.org/jira/browse/GEODE-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-9289: Fix Version/s: 1.15.0 > Configuration Class cannot be deserialized in old locators > -- > > Key: GEODE-9289 > URL: https://issues.apache.org/jira/browse/GEODE-9289 > Project: Geode > Issue Type: Bug > Components: serialization >Reporter: Nabarun Nag >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.12.3, 1.13.3, 1.14.0, 1.15.0 > > > * Locators post version 1.12.0 when send out the Configuration to old version > locators > * Old locators are not able to interpret the null jarNames sent by the new > locators > * This causes a lot of NPEs in the old locators > * This clears out the jarNames in the configuration and if a server joins > the cluster and requests the cluster configuration from the oldest locator, > then it does not the jars deployed in the cluster. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9289) Configuration Class cannot be deserialized in old locators
[ https://issues.apache.org/jira/browse/GEODE-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-9289. - Resolution: Fixed > Configuration Class cannot be deserialized in old locators > -- > > Key: GEODE-9289 > URL: https://issues.apache.org/jira/browse/GEODE-9289 > Project: Geode > Issue Type: Bug > Components: serialization >Reporter: Nabarun Nag >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.14.0, 1.15.0, 1.13.3, 1.12.3 > > > * Locators post version 1.12.0 when send out the Configuration to old version > locators > * Old locators are not able to interpret the null jarNames sent by the new > locators > * This causes a lot of NPEs in the old locators > * This clears out the jarNames in the configuration and if a server joins > the cluster and requests the cluster configuration from the oldest locator, > then it does not the jars deployed in the cluster. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9050) Redis test fails with Netty 4.1.60 and later
[
https://issues.apache.org/jira/browse/GEODE-9050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols resolved GEODE-9050.
-
Resolution: Duplicate
> Redis test fails with Netty 4.1.60 and later
>
>
> Key: GEODE-9050
> URL: https://issues.apache.org/jira/browse/GEODE-9050
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> {{PubSubIntegrationTest > ensureOrderingOfPublishedMessages}}
> [fails|http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6153/test-results/integrationTest/1616031328/index.html]
> reliably, on both Linux and Windows, if I [bump
> Netty|https://github.com/apache/geode/pull/6153/commits/03b81f93b011377a5021a4b87acecacfa02b93a4]
> from 4.1.59.Final to 4.1.60.Final. It's important to keep up to date with
> latest versions of our 3rd-party dependencies but breaking this out
> separately so someone with redis knowledge can tackle it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8200) Rebalance operations stuck in "IN_PROGRESS" state forever
[
https://issues.apache.org/jira/browse/GEODE-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386570#comment-17386570
]
Aaron Lindsey commented on GEODE-8200:
--
Re-opened because this issue has started reproducing again on develop.
> Rebalance operations stuck in "IN_PROGRESS" state forever
> -
>
> Key: GEODE-8200
> URL: https://issues.apache.org/jira/browse/GEODE-8200
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Aaron Lindsey
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI
> Fix For: 1.13.1, 1.14.0
>
> Attachments: GEODE-8200-exportedLogs.zip
>
>
> We use the management REST API to call rebalance immediately before stopping
> a server to limit the possibility of data loss. In a cluster with 3 locators,
> 3 servers, and no regions, we noticed that sometimes the rebalance operation
> never ends if one of the locators is restarting concurrently with the
> rebalance operation.
> More specifically, the scenario where we see this issue crop up is during an
> automated "rolling restart" operation in a Kubernetes environment which
> proceeds as follows:
> * At most one locator and one server are restarting at any point in time
> * Each locator/server waits until the previous locator/server is fully online
> before restarting
> * Immediately before stopping a server, a rebalance operation is performed
> and the server is not stopped until the rebalance operation is completed
> The impact of this issue is that the "rolling restart" operation will never
> complete, because it cannot proceed with stopping a server until the
> rebalance operation is completed. A human is then required to intervene and
> manually trigger a rebalance and stop the server. This type of "rolling
> restart" operation is triggered fairly often in Kubernetes — any time part of
> the configuration of the locators or servers changes.
> The following JSON is a sample response from the management REST API that
> shows the rebalance operation stuck in "IN_PROGRESS".
> {code}
> {
> "statusCode": "IN_PROGRESS",
> "links": {
> "self":
> "http://geodecluster-sample-locator.default/management/v1/operations/rebalances/a47f23c8-02b3-443c-a367-636fd6921ea7;,
> "list":
> "http://geodecluster-sample-locator.default/management/v1/operations/rebalances;
> },
> "operationStart": "2020-05-27T22:38:30.619Z",
> "operationId": "a47f23c8-02b3-443c-a367-636fd6921ea7",
> "operation": {
> "simulate": false
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9455) remove workaround for JDK-7078465 in HeapMemoryMonitor
[ https://issues.apache.org/jira/browse/GEODE-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-9455: Priority: Trivial (was: Major) > remove workaround for JDK-7078465 in HeapMemoryMonitor > -- > > Key: GEODE-9455 > URL: https://issues.apache.org/jira/browse/GEODE-9455 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Darrel Schneider >Priority: Trivial > > The HeapMemoryMonitor was a workaround for JDK-7078465 which was fixed in all > versions of java 8. See: > [https://bugs.java.com/bugdatabase/view_bug.do?bug_id=7078465] > So the workaround can be removed. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9455) remove workaround for JDK-7078465 in HeapMemoryMonitor
Darrel Schneider created GEODE-9455: --- Summary: remove workaround for JDK-7078465 in HeapMemoryMonitor Key: GEODE-9455 URL: https://issues.apache.org/jira/browse/GEODE-9455 Project: Geode Issue Type: Improvement Components: core Reporter: Darrel Schneider The HeapMemoryMonitor was a workaround for JDK-7078465 which was fixed in all versions of java 8. See: [https://bugs.java.com/bugdatabase/view_bug.do?bug_id=7078465] So the workaround can be removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9289) Configuration Class cannot be deserialized in old locators
[ https://issues.apache.org/jira/browse/GEODE-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386532#comment-17386532 ] ASF subversion and git services commented on GEODE-9289: Commit 4e70bfcb1949b8399cf20a72d21ac556d0835cf2 in geode's branch refs/heads/develop from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e70bfc ] GEODE-9289: Configuration class modified into VersionedDataSerializable * This was suppose to be a part of the initial commit for GEODE-9289 * However we had to wait for a revert in the deployement data structure in GEODE-9377 * This commit is already a part of the previous releases of Apache Geode > Configuration Class cannot be deserialized in old locators > -- > > Key: GEODE-9289 > URL: https://issues.apache.org/jira/browse/GEODE-9289 > Project: Geode > Issue Type: Bug > Components: serialization >Reporter: Nabarun Nag >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.12.3, 1.13.3, 1.14.0 > > > * Locators post version 1.12.0 when send out the Configuration to old version > locators > * Old locators are not able to interpret the null jarNames sent by the new > locators > * This causes a lot of NPEs in the old locators > * This clears out the jarNames in the configuration and if a server joins > the cluster and requests the cluster configuration from the oldest locator, > then it does not the jars deployed in the cluster. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9377) Revert deploymentName on Deployment configuration object.
[ https://issues.apache.org/jira/browse/GEODE-9377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386533#comment-17386533 ] ASF subversion and git services commented on GEODE-9377: Commit 4e70bfcb1949b8399cf20a72d21ac556d0835cf2 in geode's branch refs/heads/develop from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e70bfc ] GEODE-9289: Configuration class modified into VersionedDataSerializable * This was suppose to be a part of the initial commit for GEODE-9289 * However we had to wait for a revert in the deployement data structure in GEODE-9377 * This commit is already a part of the previous releases of Apache Geode > Revert deploymentName on Deployment configuration object. > - > > Key: GEODE-9377 > URL: https://issues.apache.org/jira/browse/GEODE-9377 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh, management >Reporter: Patrick Johnsn >Assignee: Patrick Johnsn >Priority: Major > Labels: pull-request-available > > Revert the addition of deploymentName to Deployment to avoid serialization > issues with older versions that use fileName. Deployment name was added as > part of ticket GEODE-8705, to support a dropped feature. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9289) Configuration Class cannot be deserialized in old locators
[ https://issues.apache.org/jira/browse/GEODE-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386531#comment-17386531 ] ASF subversion and git services commented on GEODE-9289: Commit 4e70bfcb1949b8399cf20a72d21ac556d0835cf2 in geode's branch refs/heads/develop from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e70bfc ] GEODE-9289: Configuration class modified into VersionedDataSerializable * This was suppose to be a part of the initial commit for GEODE-9289 * However we had to wait for a revert in the deployement data structure in GEODE-9377 * This commit is already a part of the previous releases of Apache Geode > Configuration Class cannot be deserialized in old locators > -- > > Key: GEODE-9289 > URL: https://issues.apache.org/jira/browse/GEODE-9289 > Project: Geode > Issue Type: Bug > Components: serialization >Reporter: Nabarun Nag >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.12.3, 1.13.3, 1.14.0 > > > * Locators post version 1.12.0 when send out the Configuration to old version > locators > * Old locators are not able to interpret the null jarNames sent by the new > locators > * This causes a lot of NPEs in the old locators > * This clears out the jarNames in the configuration and if a server joins > the cluster and requests the cluster configuration from the oldest locator, > then it does not the jars deployed in the cluster. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9334) Geode Native User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-9334: --- Fix Version/s: 1.14.0 1.13.5 1.12.5 > Geode Native User Guide: update dockerfile to use newer ruby & gems > --- > > Key: GEODE-9334 > URL: https://issues.apache.org/jira/browse/GEODE-9334 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0 > > > Update the Geode Native docker-based scripts to generate the user guides, > following the same process done for Geode User Guide (GEODE-9042) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9334) Geode Native User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386513#comment-17386513 ] Dave Barnes commented on GEODE-9334: Back-ported to v1.12.5, 1.13.5, 1.14 > Geode Native User Guide: update dockerfile to use newer ruby & gems > --- > > Key: GEODE-9334 > URL: https://issues.apache.org/jira/browse/GEODE-9334 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Update the Geode Native docker-based scripts to generate the user guides, > following the same process done for Geode User Guide (GEODE-9042) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9360) Initial revision of .net core support
[ https://issues.apache.org/jira/browse/GEODE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386487#comment-17386487 ] ASF subversion and git services commented on GEODE-9360: Commit d7445864c29d3b5e0152e7cad0dbd98278912436 in geode-native's branch refs/heads/develop from Blake Bender [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=d744586 ] GEODE-9360: Initial checkin of .net core support (#823) * GEODE-9360: Initial revision of Geode .net core library and tests Co-authored-by: Matthew Reddington Co-authored-by: Mike Martell > Initial revision of .net core support > - > > Key: GEODE-9360 > URL: https://issues.apache.org/jira/browse/GEODE-9360 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > > As a .net core developer, I would like to be able to access the geode-native > API. To facilitate this, we need to implement a minimal set of C# classes > that use p/invoke to access geode-native via C bindings (GEODE-9358). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9360) Initial revision of .net core support
[ https://issues.apache.org/jira/browse/GEODE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386486#comment-17386486 ] ASF subversion and git services commented on GEODE-9360: Commit d7445864c29d3b5e0152e7cad0dbd98278912436 in geode-native's branch refs/heads/develop from Blake Bender [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=d744586 ] GEODE-9360: Initial checkin of .net core support (#823) * GEODE-9360: Initial revision of Geode .net core library and tests Co-authored-by: Matthew Reddington Co-authored-by: Mike Martell > Initial revision of .net core support > - > > Key: GEODE-9360 > URL: https://issues.apache.org/jira/browse/GEODE-9360 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > > As a .net core developer, I would like to be able to access the geode-native > API. To facilitate this, we need to implement a minimal set of C# classes > that use p/invoke to access geode-native via C bindings (GEODE-9358). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9360) Initial revision of .net core support
[ https://issues.apache.org/jira/browse/GEODE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386488#comment-17386488 ] ASF GitHub Bot commented on GEODE-9360: --- pdxcodemonkey merged pull request #823: URL: https://github.com/apache/geode-native/pull/823 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Initial revision of .net core support > - > > Key: GEODE-9360 > URL: https://issues.apache.org/jira/browse/GEODE-9360 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > > As a .net core developer, I would like to be able to access the geode-native > API. To facilitate this, we need to implement a minimal set of C# classes > that use p/invoke to access geode-native via C bindings (GEODE-9358). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9334) Geode Native User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386484#comment-17386484 ] ASF subversion and git services commented on GEODE-9334: Commit 4017c327ca6f28b74019c8a86444d88bce5428a4 in geode-native's branch refs/heads/support/1.14 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=4017c32 ] GEODE-9334: Update UG generation scripts > Geode Native User Guide: update dockerfile to use newer ruby & gems > --- > > Key: GEODE-9334 > URL: https://issues.apache.org/jira/browse/GEODE-9334 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Update the Geode Native docker-based scripts to generate the user guides, > following the same process done for Geode User Guide (GEODE-9042) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9454) The client, if multiple operations are in flight, should not flood the authentication server with re-authentication requests.
[ https://issues.apache.org/jira/browse/GEODE-9454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9454: --- Description: the blocking should only be for one client only Having a test with multiple clients with multiple thread doing cache operations The test should also cover the multi-user authentication mode was: the blocking should only be for one client only Having a test with multiple clients with multiple thread doing cache operations > The client, if multiple operations are in flight, should not flood the > authentication server with re-authentication requests. > - > > Key: GEODE-9454 > URL: https://issues.apache.org/jira/browse/GEODE-9454 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > > the blocking should only be for one client only > Having a test with multiple clients with multiple thread doing cache > operations > The test should also cover the multi-user authentication mode -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9454) The client, if multiple operations are in flight, should not flood the authentication server with re-authentication requests.
Jinmei Liao created GEODE-9454: -- Summary: The client, if multiple operations are in flight, should not flood the authentication server with re-authentication requests. Key: GEODE-9454 URL: https://issues.apache.org/jira/browse/GEODE-9454 Project: Geode Issue Type: Sub-task Components: core, security Reporter: Jinmei Liao the blocking should only be for one client only Having a test with multiple clients with multiple thread doing cache operations -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9453) The server, once a user expires, should clean the user attributes from the server.
Jinmei Liao created GEODE-9453: -- Summary: The server, once a user expires, should clean the user attributes from the server. Key: GEODE-9453 URL: https://issues.apache.org/jira/browse/GEODE-9453 Project: Geode Issue Type: Sub-task Components: core, security Reporter: Jinmei Liao ClientUserAuths maintains a map of clientID to its user attributes (the logged in shiro subject etc), when user expires, we need to remove that entry from that map and log the shiro subject out to avoid resource leak. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9452) The older version client should receive the AuthenticationRequiredException when authentication expires
Jinmei Liao created GEODE-9452: -- Summary: The older version client should receive the AuthenticationRequiredException when authentication expires Key: GEODE-9452 URL: https://issues.apache.org/jira/browse/GEODE-9452 Project: Geode Issue Type: Sub-task Components: core, security Reporter: Jinmei Liao Currently, for older client, it's receiving a ClassNotFoundException, we need to add the serialization code to convert the AuthenticationExpiredException into this old exception type that the older clients can understand. Note: when converting the exception, if we have the message to match what the older client expects, it can do re-authentication automatically, but we lost the original message that server has thrown. (Need to consult the PM on what kind of behavior they want). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9451) On demand authentication expiration and re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9451: --- Labels: GeodeOperationAPI (was: ) > On demand authentication expiration and re-authentication > - > > Key: GEODE-9451 > URL: https://issues.apache.org/jira/browse/GEODE-9451 > Project: Geode > Issue Type: New Feature > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9451) On demand authentication expiration and re-authentication
Jinmei Liao created GEODE-9451: -- Summary: On demand authentication expiration and re-authentication Key: GEODE-9451 URL: https://issues.apache.org/jira/browse/GEODE-9451 Project: Geode Issue Type: New Feature Components: core, security Reporter: Jinmei Liao -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8674) CLI DataInput object leaks internal buffer when allocating ctor is called
[
https://issues.apache.org/jira/browse/GEODE-8674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386425#comment-17386425
]
Blake Bender commented on GEODE-8674:
-
https://github.com/apache/geode-native/pull/682
> CLI DataInput object leaks internal buffer when allocating ctor is called
> -
>
> Key: GEODE-8674
> URL: https://issues.apache.org/jira/browse/GEODE-8674
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Blake Bender
>Assignee: Blake Bender
>Priority: Major
> Fix For: 1.14.0
>
>
> The CLI DataInput object has two ctors, one of which copies the passed-in
> buffer parameter via new[] and one of which doesn't. In the event that the
> former is called, the buffer is leaked when the object is deleted/Disposed.
> Here's the current code for CLI `DataInput::~DataInput`:
> ```
> ~DataInput( ) \{ Cleanup(); }
> ```
> And the code for `DataInput::Cleanup`:
> ```
> void DataInput::Cleanup()
> {
> //TODO:
> //GF_SAFE_DELETE_ARRAY(m_buffer);
> }
> ```
> So apparently this bug has been known for some time (?!?), but has never been
> fixed.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9450) StringBytesGlossary has a large number of MakeImmutable annotations
Darrel Schneider created GEODE-9450: --- Summary: StringBytesGlossary has a large number of MakeImmutable annotations Key: GEODE-9450 URL: https://issues.apache.org/jira/browse/GEODE-9450 Project: Geode Issue Type: Improvement Components: redis Reporter: Darrel Schneider All of the byte array constants in StringBytesGlossary are annotated with MakeImmutable. This annotation indicates that changes need to be made. We could just change the annotation to Immutable but then we would still have static fields that could actually be mutated. In the case of StringBytesGlossary it seems like some of the byte array constants in it could be encapsulated into an Enum constant. The Enum constructor would take a byte array and store it the instance. But it would not have methods that allow other classes to get a reference to the byte array. Instead it could just have a "boolean equalsIgnoreCaseBytes(byte[])" and any other comparison methods needed and only those methods would need to be coded correctly to not modify the array. This would work fine for all the redis keywords we need to identify. Instead of passing a byte array to the constructor we could probably just use Enum.getName() in the constructor and call stringToBytes on it. But other constants in StringBytesGlossary are used for output to be sent back the the client (for example see bPING_RESPONSE). For those we probably should just mark the as Immutable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9450) StringBytesGlossary has a large number of MakeImmutable annotations
[ https://issues.apache.org/jira/browse/GEODE-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-9450: Priority: Minor (was: Major) > StringBytesGlossary has a large number of MakeImmutable annotations > --- > > Key: GEODE-9450 > URL: https://issues.apache.org/jira/browse/GEODE-9450 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Darrel Schneider >Priority: Minor > > All of the byte array constants in StringBytesGlossary are annotated with > MakeImmutable. This annotation indicates that changes need to be made. > We could just change the annotation to Immutable but then we would still have > static fields that could actually be mutated. > In the case of StringBytesGlossary it seems like some of the byte array > constants in it could be encapsulated into an Enum constant. The Enum > constructor would take a byte array and store it the instance. But it would > not have methods that allow other classes to get a reference to the byte > array. Instead it could just have a "boolean equalsIgnoreCaseBytes(byte[])" > and any other comparison methods needed and only those methods would need to > be coded correctly to not modify the array. This would work fine for all the > redis keywords we need to identify. Instead of passing a byte array to the > constructor we could probably just use Enum.getName() in the constructor and > call stringToBytes on it. > But other constants in StringBytesGlossary are used for output to be sent > back the the client (for example see bPING_RESPONSE). For those we probably > should just mark the as Immutable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9449) remove 'b' prefix from constants
[ https://issues.apache.org/jira/browse/GEODE-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-9449: Priority: Minor (was: Major) > remove 'b' prefix from constants > > > Key: GEODE-9449 > URL: https://issues.apache.org/jira/browse/GEODE-9449 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Darrel Schneider >Priority: Minor > > I number of constants in the redis packages have a 'b' prefix on their name. > This might have been a use of Hungarian notation but that is not clear. The > convention for constant names in geode is all upper case with underscore > between words. So the 'b' prefix should be removed. See StringBytesGlossary > for the location of many of these constants. Most of the constants in > StringBytesGlossary contains bytes, one or more, but if a few of the > constants in it are actually String instances. Consider renaming them to have > _STRING suffix or moving them to another class like StringGlossary. > The byte array constants in this class are marked with the MakeImmutable > annotation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9449) remove 'b' prefix from constants
Darrel Schneider created GEODE-9449: --- Summary: remove 'b' prefix from constants Key: GEODE-9449 URL: https://issues.apache.org/jira/browse/GEODE-9449 Project: Geode Issue Type: Improvement Components: redis Reporter: Darrel Schneider I number of constants in the redis packages have a 'b' prefix on their name. This might have been a use of Hungarian notation but that is not clear. The convention for constant names in geode is all upper case with underscore between words. So the 'b' prefix should be removed. See StringBytesGlossary for the location of many of these constants. Most of the constants in StringBytesGlossary contains bytes, one or more, but if a few of the constants in it are actually String instances. Consider renaming them to have _STRING suffix or moving them to another class like StringGlossary. The byte array constants in this class are marked with the MakeImmutable annotation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9334) Geode Native User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386382#comment-17386382 ] ASF subversion and git services commented on GEODE-9334: Commit d2598b291f2d3362c01f94f41e1c44c359bb87ff in geode-native's branch refs/heads/support/1.13 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=d2598b2 ] GEODE-9334: Update UG generation scripts > Geode Native User Guide: update dockerfile to use newer ruby & gems > --- > > Key: GEODE-9334 > URL: https://issues.apache.org/jira/browse/GEODE-9334 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Update the Geode Native docker-based scripts to generate the user guides, > following the same process done for Geode User Guide (GEODE-9042) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9334) Geode Native User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386355#comment-17386355 ] ASF subversion and git services commented on GEODE-9334: Commit c7800a39b91b9d98b1dc51ba7873010515737825 in geode-native's branch refs/heads/support/1.12 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=c7800a3 ] GEODE-9334: Update UG generation scripts > Geode Native User Guide: update dockerfile to use newer ruby & gems > --- > > Key: GEODE-9334 > URL: https://issues.apache.org/jira/browse/GEODE-9334 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Update the Geode Native docker-based scripts to generate the user guides, > following the same process done for Geode User Guide (GEODE-9042) -- This message was sent by Atlassian Jira (v8.3.4#803005)
