[jira] [Created] (GEODE-9759) User Guide: gfsh command pages - problem with double-hyphens
Dave Barnes created GEODE-9759: -- Summary: User Guide: gfsh command pages - problem with double-hyphens Key: GEODE-9759 URL: https://issues.apache.org/jira/browse/GEODE-9759 Project: Geode Issue Type: Bug Components: docs Affects Versions: 1.14.0 Reporter: Dave Barnes In the tables of gfsh command options, double-hyphen prefixes are often (but not always) collapsed to a single hyphen. This is a format issue with dozens (possibly hundreds?) of occurrences. See, for example, the `alter` command page, http://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/alter.html. Note the difference between the entry for `--entry-idle-time-expiration-action` and the following entry `-entry-time-to-live-expiration`. The tricky bit is that the source code in both cases uses the same HTML construct: `\-\-entry-time-to-live-expiration`, but the results differ. One likely remedy is to replace the hyphen pair with the code for two non-breaking hyphens: `‑‑`. Behavior may differ depending on whether the entry occurs in an HTML table, a nested HTML table, or a Markdown table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9759) User Guide: gfsh command pages - problem with double-hyphens
[ https://issues.apache.org/jira/browse/GEODE-9759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9759: -- Assignee: Dave Barnes > User Guide: gfsh command pages - problem with double-hyphens > > > Key: GEODE-9759 > URL: https://issues.apache.org/jira/browse/GEODE-9759 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.14.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: needsTriage > > In the tables of gfsh command options, double-hyphen prefixes are often (but > not always) collapsed to a single hyphen. > This is a format issue with dozens (possibly hundreds?) of occurrences. > See, for example, the `alter` command page, > http://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/alter.html. > Note the difference between the entry for > `--entry-idle-time-expiration-action` and the following entry > `-entry-time-to-live-expiration`. The tricky bit is that the source code in > both cases uses the same HTML construct: `\-\-entry-time-to-live-expiration`, but the results > differ. > One likely remedy is to replace the hyphen pair with the code for two > non-breaking hyphens: `‑‑`. > Behavior may differ depending on whether the entry occurs in an HTML table, a > nested HTML table, or a Markdown table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9656) User guide: Document Async disk writer exit behavior
[ https://issues.apache.org/jira/browse/GEODE-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9656: -- Assignee: Dave Barnes > User guide: Document Async disk writer exit behavior > > > Key: GEODE-9656 > URL: https://issues.apache.org/jira/browse/GEODE-9656 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.12.4 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Request from community member Barry Oglesby: > Can the geode docs be updated to document the behavior in the case where the > Async disk writer thread exits? This thread exists in the case where > disk-synchronous=false. If it exits for any reason, the member shuts down if > an operation attempts to update the disk store. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9656) User guide: Document Async disk writer exit behavior
[ https://issues.apache.org/jira/browse/GEODE-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-9656. Fix Version/s: 1.15.0 1.14.1 1.13.5 1.12.6 Resolution: Fixed > User guide: Document Async disk writer exit behavior > > > Key: GEODE-9656 > URL: https://issues.apache.org/jira/browse/GEODE-9656 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.12.4 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.6, 1.13.5, 1.14.1, 1.15.0 > > > Request from community member Barry Oglesby: > Can the geode docs be updated to document the behavior in the case where the > Async disk writer thread exits? This thread exists in the case where > disk-synchronous=false. If it exits for any reason, the member shuts down if > an operation attempts to update the disk store. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9797) User guide typo repairs
[ https://issues.apache.org/jira/browse/GEODE-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9797: -- Assignee: Dave Barnes > User guide typo repairs > --- > > Key: GEODE-9797 > URL: https://issues.apache.org/jira/browse/GEODE-9797 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.12.5, 1.13.4, 1.14.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > Labels: needsTriage > > An eagle-eyed community member reports the following typographical errors: > http://geode.apache.org/docs/guide/114/managing/security/authentication_examples.html > Paragraph 3: "intialization" should be "initialization" > http://geode.apache.org/docs/guide/114/managing/security/implementing_authentication.html > Paragraph 6 (or so): "in the clear" should be "in cleartext" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9797) User guide typo repairs
Dave Barnes created GEODE-9797: -- Summary: User guide typo repairs Key: GEODE-9797 URL: https://issues.apache.org/jira/browse/GEODE-9797 Project: Geode Issue Type: Bug Components: docs Affects Versions: 1.14.0, 1.13.4, 1.12.5 Reporter: Dave Barnes An eagle-eyed community member reports the following typographical errors: http://geode.apache.org/docs/guide/114/managing/security/authentication_examples.html Paragraph 3: "intialization" should be "initialization" http://geode.apache.org/docs/guide/114/managing/security/implementing_authentication.html Paragraph 6 (or so): "in the clear" should be "in cleartext" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9797) User guide typo repairs
[ https://issues.apache.org/jira/browse/GEODE-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-9797: --- Priority: Minor (was: Major) > User guide typo repairs > --- > > Key: GEODE-9797 > URL: https://issues.apache.org/jira/browse/GEODE-9797 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.12.5, 1.13.4, 1.14.0 >Reporter: Dave Barnes >Priority: Minor > Labels: needsTriage > > An eagle-eyed community member reports the following typographical errors: > http://geode.apache.org/docs/guide/114/managing/security/authentication_examples.html > Paragraph 3: "intialization" should be "initialization" > http://geode.apache.org/docs/guide/114/managing/security/implementing_authentication.html > Paragraph 6 (or so): "in the clear" should be "in cleartext" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9797) User guide typo repairs
[ https://issues.apache.org/jira/browse/GEODE-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-9797. Fix Version/s: 1.15.0 1.14.1 1.13.5 1.12.6 Resolution: Fixed > User guide typo repairs > --- > > Key: GEODE-9797 > URL: https://issues.apache.org/jira/browse/GEODE-9797 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.12.5, 1.13.4, 1.14.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > Labels: needsTriage, pull-request-available > Fix For: 1.12.6, 1.13.5, 1.14.1, 1.15.0 > > > An eagle-eyed community member reports the following typographical errors: > http://geode.apache.org/docs/guide/114/managing/security/authentication_examples.html > Paragraph 3: "intialization" should be "initialization" > http://geode.apache.org/docs/guide/114/managing/security/implementing_authentication.html > Paragraph 6 (or so): "in the clear" should be "in cleartext" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9882) User Guide, Micrometer section, fix product_name typo
Dave Barnes created GEODE-9882: -- Summary: User Guide, Micrometer section, fix product_name typo Key: GEODE-9882 URL: https://issues.apache.org/jira/browse/GEODE-9882 Project: Geode Issue Type: Bug Components: docs Reporter: Dave Barnes On page https://geode.apache.org/docs/guide/114/tools_modules/micrometer/micrometer-meters.html, the product name fails to display due to a typo in the variable syntax. Fix it. There are other types of meters available in Micrometer, but they are not currently being used in . Should be "used in Apache Geode." Change `<%vars.product_name%>` to `<%=vars.product_name%>`. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9882) User Guide, Micrometer section, fix product_name typo
[ https://issues.apache.org/jira/browse/GEODE-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9882: -- Assignee: Dave Barnes > User Guide, Micrometer section, fix product_name typo > - > > Key: GEODE-9882 > URL: https://issues.apache.org/jira/browse/GEODE-9882 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > On page > https://geode.apache.org/docs/guide/114/tools_modules/micrometer/micrometer-meters.html, > the product name fails to display due to a typo in the variable syntax. Fix > it. > There are other types of meters available in Micrometer, but they are not > currently being used in . > Should be "used in Apache Geode." > Change `<%vars.product_name%>` to `<%=vars.product_name%>`. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9882) User Guide, Micrometer section, fix product_name typo
[ https://issues.apache.org/jira/browse/GEODE-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-9882. Fix Version/s: 1.12.6 1.13.5 1.14.1 1.15.0 Resolution: Fixed > User Guide, Micrometer section, fix product_name typo > - > > Key: GEODE-9882 > URL: https://issues.apache.org/jira/browse/GEODE-9882 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.6, 1.13.5, 1.14.1, 1.15.0 > > > On page > https://geode.apache.org/docs/guide/114/tools_modules/micrometer/micrometer-meters.html, > the product name fails to display due to a typo in the variable syntax. Fix > it. > There are other types of meters available in Micrometer, but they are not > currently being used in . > Should be "used in Apache Geode." > Change `<%vars.product_name%>` to `<%=vars.product_name%>`. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9921) Rename .NET client to .NET Framework
[ https://issues.apache.org/jira/browse/GEODE-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9921: -- Assignee: Dave Barnes > Rename .NET client to .NET Framework > > > Key: GEODE-9921 > URL: https://issues.apache.org/jira/browse/GEODE-9921 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > The .NET native client docs need to be renamed to .NET Framework to clarify > that it is not .NET Core -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9921) Rename .NET client to .NET Framework
Dave Barnes created GEODE-9921: -- Summary: Rename .NET client to .NET Framework Key: GEODE-9921 URL: https://issues.apache.org/jira/browse/GEODE-9921 Project: Geode Issue Type: Improvement Components: docs, native client Affects Versions: 1.14.2 Reporter: Dave Barnes The .NET native client docs need to be renamed to .NET Framework to clarify that it is not .NET Core -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9923) User Guide: add Log Message troubleshooting section
Dave Barnes created GEODE-9923: -- Summary: User Guide: add Log Message troubleshooting section Key: GEODE-9923 URL: https://issues.apache.org/jira/browse/GEODE-9923 Project: Geode Issue Type: Improvement Components: docs Affects Versions: 1.14.2 Reporter: Dave Barnes GemFire support team (who are also Geode community members) have compiled a troubleshooting guide that maps log messages to suggested solutions. They have contributed this to Geode in the form of a Google doc. Reformat the Google doc and add it to the Geode user guide. There's an existing section under Managing Apache Geode called Troubleshooting and System Recovery that would be a good location for this material. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9923) User Guide: add Log Message troubleshooting section
[ https://issues.apache.org/jira/browse/GEODE-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9923: -- Assignee: Dave Barnes > User Guide: add Log Message troubleshooting section > --- > > Key: GEODE-9923 > URL: https://issues.apache.org/jira/browse/GEODE-9923 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > GemFire support team (who are also Geode community members) have compiled a > troubleshooting guide that maps log messages to suggested solutions. > They have contributed this to Geode in the form of a Google doc. > Reformat the Google doc and add it to the Geode user guide. There's an > existing section under Managing Apache Geode called Troubleshooting and > System Recovery that would be a good location for this material. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9926) User Guide - update log4j version info
[ https://issues.apache.org/jira/browse/GEODE-9926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9926: -- Assignee: Dave Barnes > User Guide - update log4j version info > -- > > Key: GEODE-9926 > URL: https://issues.apache.org/jira/browse/GEODE-9926 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.12.7, 1.13.6, 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > The section "How Geode Logging Works" > (https://geode.apache.org/docs/guide/114/managing/logging/how_logging_works.html) > assures the reader that Geode has been tested with log4j v2.14. > This should be updated to reflect the latest post-CVE version of log4j. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9926) User Guide - update log4j version info
Dave Barnes created GEODE-9926: -- Summary: User Guide - update log4j version info Key: GEODE-9926 URL: https://issues.apache.org/jira/browse/GEODE-9926 Project: Geode Issue Type: Bug Components: docs Affects Versions: 1.14.2, 1.13.6, 1.12.7 Reporter: Dave Barnes The section "How Geode Logging Works" (https://geode.apache.org/docs/guide/114/managing/logging/how_logging_works.html) assures the reader that Geode has been tested with log4j v2.14. This should be updated to reflect the latest post-CVE version of log4j. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9926) User Guide - update log4j version info
[ https://issues.apache.org/jira/browse/GEODE-9926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470188#comment-17470188 ] Dave Barnes commented on GEODE-9926: Doc source code already updated in GEODE-9905 (thank you!). Recompiled Geode User Guides for v1.12, 1.13, and 1.14 and republished to the Apache Geode website. > User Guide - update log4j version info > -- > > Key: GEODE-9926 > URL: https://issues.apache.org/jira/browse/GEODE-9926 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.12.7, 1.13.6, 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > The section "How Geode Logging Works" > (https://geode.apache.org/docs/guide/114/managing/logging/how_logging_works.html) > assures the reader that Geode has been tested with log4j v2.14. > This should be updated to reflect the latest post-CVE version of log4j. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9926) User Guide - update log4j version info
[ https://issues.apache.org/jira/browse/GEODE-9926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-9926. Fix Version/s: 1.14.2 1.13.6 1.12.7 Resolution: Fixed > User Guide - update log4j version info > -- > > Key: GEODE-9926 > URL: https://issues.apache.org/jira/browse/GEODE-9926 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.12.7, 1.13.6, 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Fix For: 1.14.2, 1.13.6, 1.12.7 > > > The section "How Geode Logging Works" > (https://geode.apache.org/docs/guide/114/managing/logging/how_logging_works.html) > assures the reader that Geode has been tested with log4j v2.14. > This should be updated to reflect the latest post-CVE version of log4j. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9883) Review and Cleanup geode_for_redis.html.md.erb
[ https://issues.apache.org/jira/browse/GEODE-9883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-9883: --- Component/s: docs > Review and Cleanup geode_for_redis.html.md.erb > -- > > Key: GEODE-9883 > URL: https://issues.apache.org/jira/browse/GEODE-9883 > Project: Geode > Issue Type: Task > Components: docs, redis >Affects Versions: 1.15.0 >Reporter: Wayne >Assignee: Eric Zoerner >Priority: Major > Labels: blocks-1.15.0 > > Looking at what we have in the geode docs, a few things that are out of date. > * This page still references the geode-for-redis-password, which doesn't > exist any more. It should probably talk about how redis interacts with the > security manager. > * Probably should mention how to configure TLS properties for > geode-for-redis. > * The redis-cli command I think is missing a -c option to use cluster mode. > * The supported redis commands listed in that page is incomplete > * Advantages section doesn't mention synchronous replication -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9939) Typo in error message
Dave Barnes created GEODE-9939: -- Summary: Typo in error message Key: GEODE-9939 URL: https://issues.apache.org/jira/browse/GEODE-9939 Project: Geode Issue Type: Bug Affects Versions: 1.14.2 Reporter: Dave Barnes >From a community member: The spelling “perameterization” is wrong in the codebase [https://github.com/apache/geode/blob/a5bd36f9fa787d3a71c6e6efafed5a7b0fe52d2b/geode-core/src/main/java/org/apache/ge\ ode/internal/cache/xmlcache/CacheXmlPropertyResolver.java#L125](https://github.com/apache/geode/blob/a5bd36f9fa787d3a71c6e6efafed5a7b0fe52d2b/geode-core/src/main/java/org/apache/ge\ ode/internal/cache/xmlcache/CacheXmlPropertyResolver.java#L125). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9956) update website generation tools
Dave Barnes created GEODE-9956:
--
Summary: update website generation tools
Key: GEODE-9956
URL: https://issues.apache.org/jira/browse/GEODE-9956
Project: Geode
Issue Type: Improvement
Components: website
Reporter: Dave Barnes
In the apache/geode-site repository, the gradle compilation command (.gradlew
compile) yields a warning, and the view command (.gradlew view) shows a very
old version of ruby (2.3.1). The script and tools could benefit from an update.
{noformat}
$ ./gradlew compile
Starting a Gradle Daemon (subsequent builds will be faster)
The Task.leftShift(Closure) method has been deprecated and is scheduled to be
removed in Gradle 5.0. Please use Task.doLast(Action) instead.
at
build_1k64csm6uhu150n5tt6rs9fmb.run(/Users/dbarnes/Repo/geode-site/build.gradle:25)
:rat UP-TO-DATE
:compile UP-TO-DATE
BUILD SUCCESSFUL
Total time: 2.936 secs
$ ./gradlew view
The Task.leftShift(Closure) method has been deprecated and is scheduled to be
removed in Gradle 5.0. Please use Task.doLast(Action) instead.
at
build_1k64csm6uhu150n5tt6rs9fmb.run(/Users/dbarnes/Repo/geode-site/build.gradle:25)
:rat UP-TO-DATE
:compile UP-TO-DATE
:view
Loading site… [2022-01-12 18:51:40] INFO WEBrick 1.3.1
[2022-01-12 18:51:40] INFO ruby 2.3.1 (2016-04-26) [x86_64-linux-gnu]
[2022-01-12 18:51:40] INFO WEBrick::HTTPServer#start: pid=1 port=3000
172.17.0.1 - - [12/Jan/2022:18:51:44 +] "GET /releases/ HTTP/1.1" 304 -
0.0048
172.17.0.1 - - [12/Jan/2022:18:51:44 UTC] "GET /releases/ HTTP/1.1" 304 0
http://localhost:3000/ -> /releases/
> Building 66% > :view
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479768#comment-17479768 ] Dave Barnes commented on GEODE-9973: Should this fix be back-ported to earlier versions of the docs? > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: blocks-1.15.0, pull-request-available > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9973: -- Assignee: Dave Barnes (was: Donal Evans) > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480289#comment-17480289 ] Dave Barnes commented on GEODE-9973: In that case, I will back-port this doc fix to Geode 1.12, 1.13, and 1.14. Thanks, [~alberto.gomez] > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9973: -- Assignee: Donal Evans (was: Dave Barnes) > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481305#comment-17481305 ] Dave Barnes commented on GEODE-9973: I approved the PR to modify the docs on the basis of correct format and grammar. I am not qualified to verify that the documented behavior is, in fact, accurate. Reassigning to [~donalevans] to follow-through on the technical verification. > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481425#comment-17481425 ] Dave Barnes commented on GEODE-9973: Apologies if I merged prematurely. I'll hold off on the documentation back-ports until the described behavior has been verified. > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9923) User Guide: add Log Message troubleshooting section
[ https://issues.apache.org/jira/browse/GEODE-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-9923. Fix Version/s: 1.12.9 1.13.8 1.14.4 1.15.0 Resolution: Fixed > User Guide: add Log Message troubleshooting section > --- > > Key: GEODE-9923 > URL: https://issues.apache.org/jira/browse/GEODE-9923 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0 > > > GemFire support team (who are also Geode community members) have compiled a > troubleshooting guide that maps log messages to suggested solutions. > They have contributed this to Geode in the form of a Google doc. > Reformat the Google doc and add it to the Geode user guide. There's an > existing section under Managing Apache Geode called Troubleshooting and > System Recovery that would be a good location for this material. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-9973: --- Fix Version/s: 1.12.9 1.13.8 1.14.4 1.15.0 > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.12.9, 1.13.8, 1.14.4, 1.15.0, 1.16.0 >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0, 1.16.0 > > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10015) gfsh does not send hostname in SNI header
[
https://issues.apache.org/jira/browse/GEODE-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes updated GEODE-10015:
Summary: gfsh does not send hostname in SNI header (was: gfsh sends does
not send hostname in SNI header)
> gfsh does not send hostname in SNI header
> -
>
> Key: GEODE-10015
> URL: https://issues.apache.org/jira/browse/GEODE-10015
> Project: Geode
> Issue Type: Bug
> Components: gfsh, jmx
>Affects Versions: 1.15.0, 1.16.0
>Reporter: Jacob Barrett
>Priority: Blocker
> Labels: blocks-1.15.0
>
> When {{gfsh}} tries to connect the JMX port on the locator it sends the IP
> address of the locator in the SNI header rather than the hostname. This
> results in a certificate validation failure when the IP is not found in the
> SAN entries.
> Version 1.14.3 sends the correct hostname in the SNI. Something changed
> between 1.14.3 and now.
>
> Reproduction:
> {noformat}
> gfsh -e version --full -e start locator --name=locator2
> --bind-address=myhost.example.com --port=20005
> --J=-Dgemfire.jmx-manager-port=20007
> --security-properties-file=/path/to/security.properties --http-service-port=0
> --locators=myhost.example.com[20004]
> (1) Executing - version --full
> ...
> Product-Version: 1.16.0-build.0
> ...
> (2) Executing - start locator --name=locator2
> --bind-address=myhost.example.com --port=20005
> --J=-Dgemfire.jmx-manager-port=20007 --security-properties-file=
> --http-service-port=0 --locators=myhost.example.com[20004]
> ...
> [fatal 2022/02/02 19:47:27.050 PST tid=0x1] Problem forming SSL
> connection to /192.168.68.56[20007].
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative names matching IP address 192.168.68.56 found
> ...
> Locator in /path/to/locator2 on myhost.example.com[20005] as locator2 is
> currently online.
> ...
> Unable to auto-connect (Security Manager may be enabled). Please use "connect
> --locator=myhost.example.com[20005]" to connect Gfsh to the locator.
> SSL configuration required to connect to the Manager.
> Failed to connect; unknown cause: error during JRMP connection establishment;
> nested exception is:
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
> {noformat}
> Where {{/path/to/security.properties}} contains:
> {noformat}
> ssl-require-authentication=true
> ssl-keystore=/path/to/keystore.jks
> ssl-truststore-type=jks
> ssl-keystore-password=password
> ssl-truststore=/path/to/truststore.jks
> ssl-enabled-components=all
> ssl-truststore-password=password
> ssl-protocols=any
> ssl-endpoint-identification-enabled=true
> ssl-keystore-type=jks
> {noformat}
> The certificate used in the key store is singed by a fake CA and contains
> only the hostname, {{myhost.example.com}}. The trust store contains the fake
> CA.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10030) Remove obsolete cross-reference in geode-native user docs
Dave Barnes created GEODE-10030: --- Summary: Remove obsolete cross-reference in geode-native user docs Key: GEODE-10030 URL: https://issues.apache.org/jira/browse/GEODE-10030 Project: Geode Issue Type: Bug Components: docs Reporter: Dave Barnes The System Properties page contains a cross-reference to the System Statistics page, which no longer exists. Just remove the link from both the .NET and C++ versions of the user guide. It's in the System Archiving Properties table. .NET: https://geode.apache.org/docs/geode-native/dotnet/114/configuring/sysprops.html#attributes-gfcpp__table_durable_client_props C++: https://geode.apache.org/docs/geode-native/cpp/114/configuring/sysprops.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10030) Remove obsolete cross-reference in geode-native user docs
[ https://issues.apache.org/jira/browse/GEODE-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-10030: --- Assignee: Dave Barnes > Remove obsolete cross-reference in geode-native user docs > - > > Key: GEODE-10030 > URL: https://issues.apache.org/jira/browse/GEODE-10030 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: needsTriage > > The System Properties page contains a cross-reference to the System > Statistics page, which no longer exists. Just remove the link from both the > .NET and C++ versions of the user guide. It's in the System Archiving > Properties table. > .NET: > https://geode.apache.org/docs/geode-native/dotnet/114/configuring/sysprops.html#attributes-gfcpp__table_durable_client_props > C++: > https://geode.apache.org/docs/geode-native/cpp/114/configuring/sysprops.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10030) Remove obsolete cross-reference in geode-native user docs
[ https://issues.apache.org/jira/browse/GEODE-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-10030: Fix Version/s: 1.16.0 > Remove obsolete cross-reference in geode-native user docs > - > > Key: GEODE-10030 > URL: https://issues.apache.org/jira/browse/GEODE-10030 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.16.0 > > > The System Properties page contains a cross-reference to the System > Statistics page, which no longer exists. Just remove the link from both the > .NET and C++ versions of the user guide. It's in the System Archiving > Properties table. > .NET: > https://geode.apache.org/docs/geode-native/dotnet/114/configuring/sysprops.html#attributes-gfcpp__table_durable_client_props > C++: > https://geode.apache.org/docs/geode-native/cpp/114/configuring/sysprops.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10030) Remove obsolete cross-reference in geode-native user docs
[ https://issues.apache.org/jira/browse/GEODE-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-10030: Fix Version/s: 1.12.9 1.13.8 1.14.4 > Remove obsolete cross-reference in geode-native user docs > - > > Key: GEODE-10030 > URL: https://issues.apache.org/jira/browse/GEODE-10030 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.16.0 > > > The System Properties page contains a cross-reference to the System > Statistics page, which no longer exists. Just remove the link from both the > .NET and C++ versions of the user guide. It's in the System Archiving > Properties table. > .NET: > https://geode.apache.org/docs/geode-native/dotnet/114/configuring/sysprops.html#attributes-gfcpp__table_durable_client_props > C++: > https://geode.apache.org/docs/geode-native/cpp/114/configuring/sysprops.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10030) Remove obsolete cross-reference in geode-native user docs
[ https://issues.apache.org/jira/browse/GEODE-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-10030: Fix Version/s: 1.15.0 > Remove obsolete cross-reference in geode-native user docs > - > > Key: GEODE-10030 > URL: https://issues.apache.org/jira/browse/GEODE-10030 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0, 1.16.0 > > > The System Properties page contains a cross-reference to the System > Statistics page, which no longer exists. Just remove the link from both the > .NET and C++ versions of the user guide. It's in the System Archiving > Properties table. > .NET: > https://geode.apache.org/docs/geode-native/dotnet/114/configuring/sysprops.html#attributes-gfcpp__table_durable_client_props > C++: > https://geode.apache.org/docs/geode-native/cpp/114/configuring/sysprops.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10030) Remove obsolete cross-reference in geode-native user docs
[ https://issues.apache.org/jira/browse/GEODE-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-10030: Labels: pull-request-available (was: needsTriage pull-request-available) > Remove obsolete cross-reference in geode-native user docs > - > > Key: GEODE-10030 > URL: https://issues.apache.org/jira/browse/GEODE-10030 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0, 1.16.0 > > > The System Properties page contains a cross-reference to the System > Statistics page, which no longer exists. Just remove the link from both the > .NET and C++ versions of the user guide. It's in the System Archiving > Properties table. > .NET: > https://geode.apache.org/docs/geode-native/dotnet/114/configuring/sysprops.html#attributes-gfcpp__table_durable_client_props > C++: > https://geode.apache.org/docs/geode-native/cpp/114/configuring/sysprops.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10057) Redis documentation has passive and active expiration descriptions reversed
[ https://issues.apache.org/jira/browse/GEODE-10057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-10057: Fix Version/s: 1.14.3 > Redis documentation has passive and active expiration descriptions reversed > --- > > Key: GEODE-10057 > URL: https://issues.apache.org/jira/browse/GEODE-10057 > Project: Geode > Issue Type: Bug > Components: docs, redis >Affects Versions: 1.15.0, 1.16.0 >Reporter: Donal Evans >Assignee: Donal Evans >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.14.3, 1.15.0, 1.16.0 > > > The geode-for-redis documentation describes the difference in behaviour for > active expiration and passive expiration, but the way these terms are used is > flipped from how they're typically used in documentation about open source > Redis: https://redis.io/commands/expire#how-redis-expires-keys. The docs > should be updated to match the usage in open source Redis documentation. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10057) Redis documentation has passive and active expiration descriptions reversed
[ https://issues.apache.org/jira/browse/GEODE-10057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493441#comment-17493441 ] Dave Barnes commented on GEODE-10057: - Back-ported to 1.15 and 1.14. > Redis documentation has passive and active expiration descriptions reversed > --- > > Key: GEODE-10057 > URL: https://issues.apache.org/jira/browse/GEODE-10057 > Project: Geode > Issue Type: Bug > Components: docs, redis >Affects Versions: 1.15.0, 1.16.0 >Reporter: Donal Evans >Assignee: Donal Evans >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.14.3, 1.15.0, 1.16.0 > > > The geode-for-redis documentation describes the difference in behaviour for > active expiration and passive expiration, but the way these terms are used is > flipped from how they're typically used in documentation about open source > Redis: https://redis.io/commands/expire#how-redis-expires-keys. The docs > should be updated to match the usage in open source Redis documentation. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10062) Update Native Client Docs to minimize redirects
Dave Barnes created GEODE-10062: --- Summary: Update Native Client Docs to minimize redirects Key: GEODE-10062 URL: https://issues.apache.org/jira/browse/GEODE-10062 Project: Geode Issue Type: Improvement Components: docs, native client Affects Versions: 1.14.3 Reporter: Dave Barnes Geode Native Client doc sources could be improved for ease of building and use by reducing dependency on the ruby redirect feature, through measures such as: - Replace ruby redirects, where feasible, with template variables, e.g. links to API docs and server guide - Standardizing template variables, e.g. use 'serverman' consistently, retiring other alternatives such as 'geodeman' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10062) Update Native Client Docs to minimize redirects
[ https://issues.apache.org/jira/browse/GEODE-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-10062: --- Assignee: Dave Barnes > Update Native Client Docs to minimize redirects > --- > > Key: GEODE-10062 > URL: https://issues.apache.org/jira/browse/GEODE-10062 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > Geode Native Client doc sources could be improved for ease of building and > use by reducing dependency on the ruby redirect feature, through measures > such as: > - Replace ruby redirects, where feasible, with template variables, e.g. links > to API docs and server guide > - Standardizing template variables, e.g. use 'serverman' consistently, > retiring other alternatives such as 'geodeman' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10078) Geode website: add 'latest' link for user guide
Dave Barnes created GEODE-10078: --- Summary: Geode website: add 'latest' link for user guide Key: GEODE-10078 URL: https://issues.apache.org/jira/browse/GEODE-10078 Project: Geode Issue Type: Improvement Components: docs Affects Versions: 1.14.3 Reporter: Dave Barnes On the Geode website, the latest apidocs can be found under a 'latest' version link. Emulate this structure for the user guide. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10078) Geode website: add 'latest' link for user guide
[ https://issues.apache.org/jira/browse/GEODE-10078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-10078: --- Assignee: Dave Barnes > Geode website: add 'latest' link for user guide > --- > > Key: GEODE-10078 > URL: https://issues.apache.org/jira/browse/GEODE-10078 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > On the Geode website, the latest apidocs can be found under a 'latest' > version link. > Emulate this structure for the user guide. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10078) Geode website: add 'latest' link for user guide
[ https://issues.apache.org/jira/browse/GEODE-10078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10078. - Resolution: Fixed > Geode website: add 'latest' link for user guide > --- > > Key: GEODE-10078 > URL: https://issues.apache.org/jira/browse/GEODE-10078 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Fix For: 1.14.3 > > > On the Geode website, the latest apidocs can be found under a 'latest' > version link. > Emulate this structure for the user guide. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10078) Geode website: add 'latest' link for user guide
[ https://issues.apache.org/jira/browse/GEODE-10078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-10078: Fix Version/s: 1.14.3 > Geode website: add 'latest' link for user guide > --- > > Key: GEODE-10078 > URL: https://issues.apache.org/jira/browse/GEODE-10078 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Fix For: 1.14.3 > > > On the Geode website, the latest apidocs can be found under a 'latest' > version link. > Emulate this structure for the user guide. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10062) Update Native Client Docs to minimize redirects
[ https://issues.apache.org/jira/browse/GEODE-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10062. - Fix Version/s: 1.14.4 1.15.0 Resolution: Fixed > Update Native Client Docs to minimize redirects > --- > > Key: GEODE-10062 > URL: https://issues.apache.org/jira/browse/GEODE-10062 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.4, 1.15.0 > > > Geode Native Client doc sources could be improved for ease of building and > use by reducing dependency on the ruby redirect feature, through measures > such as: > - Replace ruby redirects, where feasible, with template variables, e.g. links > to API docs and server guide > - Standardizing template variables, e.g. use 'serverman' consistently, > retiring other alternatives such as 'geodeman' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10150) alter runtime command and change loglevel command docs bug & improvements
Dave Barnes created GEODE-10150: --- Summary: alter runtime command and change loglevel command docs bug & improvements Key: GEODE-10150 URL: https://issues.apache.org/jira/browse/GEODE-10150 Project: Geode Issue Type: Improvement Components: docs Affects Versions: 1.14.4 Reporter: Deepak Khopade The parameters information for gfsh>alter runtime --log-level shows an incorrect parameter name in a table where all parameter's description is provided. The actual expects --log-level but the row in a table says --loglevel. See the screenshot attached. (https://gemfire.docs.pivotal.io/910/geode/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B) Another important point is, we should add a line on both the links below to state the difference when using these commands (alter runtime and change loglevel). https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/change.html When I tried both of these commands, it has been found that for locator we need to use gfsh>change loglevel --loglevel=config --member=locator and gfsh>alter runtime --log-level for cache server members. The alter runtime --log-level command doesn't work for Locators. So adding a line or changing an existing line on the docs will help new customers. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10150) alter runtime command and change loglevel command docs bug & improvements
[ https://issues.apache.org/jira/browse/GEODE-10150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-10150: --- Assignee: Dave Barnes > alter runtime command and change loglevel command docs bug & improvements > - > > Key: GEODE-10150 > URL: https://issues.apache.org/jira/browse/GEODE-10150 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Deepak Khopade >Assignee: Dave Barnes >Priority: Major > > The parameters information for gfsh>alter runtime --log-level shows an > incorrect parameter name in a table where all parameter's description is > provided. The actual expects --log-level but the row in a table says > --loglevel. See the screenshot attached. > (https://gemfire.docs.pivotal.io/910/geode/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B) > Another important point is, we should add a line on both the links below to > state the difference when using these commands (alter runtime and change > loglevel). > https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B > https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/change.html > When I tried both of these commands, it has been found that for locator we > need to use gfsh>change loglevel --loglevel=config --member=locator and > gfsh>alter runtime --log-level for cache server members. The alter runtime > --log-level command doesn't work for Locators. > So adding a line or changing an existing line on the docs will help new > customers. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10150) alter runtime command and change loglevel command docs bug & improvements
[ https://issues.apache.org/jira/browse/GEODE-10150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-10150: Labels: blocks-1.15.0 (was: ) > alter runtime command and change loglevel command docs bug & improvements > - > > Key: GEODE-10150 > URL: https://issues.apache.org/jira/browse/GEODE-10150 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Deepak Khopade >Assignee: Dave Barnes >Priority: Major > Labels: blocks-1.15.0 > > The parameters information for gfsh>alter runtime --log-level shows an > incorrect parameter name in a table where all parameter's description is > provided. The actual expects --log-level but the row in a table says > --loglevel. See the screenshot attached. > (https://gemfire.docs.pivotal.io/910/geode/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B) > Another important point is, we should add a line on both the links below to > state the difference when using these commands (alter runtime and change > loglevel). > https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B > https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/change.html > When I tried both of these commands, it has been found that for locator we > need to use gfsh>change loglevel --loglevel=config --member=locator and > gfsh>alter runtime --log-level for cache server members. The alter runtime > --log-level command doesn't work for Locators. > So adding a line or changing an existing line on the docs will help new > customers. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10150) alter runtime command and change loglevel command docs bug & improvements
[ https://issues.apache.org/jira/browse/GEODE-10150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510904#comment-17510904 ] Dave Barnes commented on GEODE-10150: - [~dkhopade] Please review the pull request https://github.com/apache/geode/pull/7474 > alter runtime command and change loglevel command docs bug & improvements > - > > Key: GEODE-10150 > URL: https://issues.apache.org/jira/browse/GEODE-10150 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Deepak Khopade >Assignee: Dave Barnes >Priority: Major > Labels: blocks-1.15.0, pull-request-available > > The parameters information for gfsh>alter runtime --log-level shows an > incorrect parameter name in a table where all parameter's description is > provided. The actual expects --log-level but the row in a table says > --loglevel. See the screenshot attached. > (https://gemfire.docs.pivotal.io/910/geode/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B) > Another important point is, we should add a line on both the links below to > state the difference when using these commands (alter runtime and change > loglevel). > https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B > https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/change.html > When I tried both of these commands, it has been found that for locator we > need to use gfsh>change loglevel --loglevel=config --member=locator and > gfsh>alter runtime --log-level for cache server members. The alter runtime > --log-level command doesn't work for Locators. > So adding a line or changing an existing line on the docs will help new > customers. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10150) alter runtime command and change loglevel command docs bug & improvements
[ https://issues.apache.org/jira/browse/GEODE-10150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-10150: Labels: pull-request-available (was: blocks-1.15.0 pull-request-available) > alter runtime command and change loglevel command docs bug & improvements > - > > Key: GEODE-10150 > URL: https://issues.apache.org/jira/browse/GEODE-10150 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Deepak Khopade >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0 > > > The parameters information for gfsh>alter runtime --log-level shows an > incorrect parameter name in a table where all parameter's description is > provided. The actual expects --log-level but the row in a table says > --loglevel. See the screenshot attached. > (https://gemfire.docs.pivotal.io/910/geode/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B) > Another important point is, we should add a line on both the links below to > state the difference when using these commands (alter runtime and change > loglevel). > https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B > https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/change.html > When I tried both of these commands, it has been found that for locator we > need to use gfsh>change loglevel --loglevel=config --member=locator and > gfsh>alter runtime --log-level for cache server members. The alter runtime > --log-level command doesn't work for Locators. > So adding a line or changing an existing line on the docs will help new > customers. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10150) alter runtime command and change loglevel command docs bug & improvements
[ https://issues.apache.org/jira/browse/GEODE-10150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10150. - Fix Version/s: 1.12.10 1.13.9 1.14.5 1.15.0 Resolution: Fixed Fixed in develop, back-ported to 1.14, 1.13, 1.12. > alter runtime command and change loglevel command docs bug & improvements > - > > Key: GEODE-10150 > URL: https://issues.apache.org/jira/browse/GEODE-10150 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Deepak Khopade >Assignee: Dave Barnes >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0 > > > The parameters information for gfsh>alter runtime --log-level shows an > incorrect parameter name in a table where all parameter's description is > provided. The actual expects --log-level but the row in a table says > --loglevel. See the screenshot attached. > (https://gemfire.docs.pivotal.io/910/geode/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B) > Another important point is, we should add a line on both the links below to > state the difference when using these commands (alter runtime and change > loglevel). > https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B > https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/change.html > When I tried both of these commands, it has been found that for locator we > need to use gfsh>change loglevel --loglevel=config --member=locator and > gfsh>alter runtime --log-level for cache server members. The alter runtime > --log-level command doesn't work for Locators. > So adding a line or changing an existing line on the docs will help new > customers. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
[
https://issues.apache.org/jira/browse/GEODE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes updated GEODE-10172:
Affects Version/s: 1.14.4
> User Guide: Escape braces and angle brackets for format consistency
> ---
>
> Key: GEODE-10172
> URL: https://issues.apache.org/jira/browse/GEODE-10172
> Project: Geode
> Issue Type: Improvement
>Affects Versions: 1.14.4
>Reporter: Dave Barnes
>Priority: Major
>
> The REST Apps section contains expressions that make heavy use of braces {}
> and angle-brackets <>. Escape these chars for more consistent rendering by
> various formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
Dave Barnes created GEODE-10172:
---
Summary: User Guide: Escape braces and angle brackets for format
consistency
Key: GEODE-10172
URL: https://issues.apache.org/jira/browse/GEODE-10172
Project: Geode
Issue Type: Improvement
Reporter: Dave Barnes
The REST Apps section contains expressions that make heavy use of braces {} and
angle-brackets <>. Escape these chars for more consistent rendering by various
formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
[
https://issues.apache.org/jira/browse/GEODE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes updated GEODE-10172:
Component/s: docs
> User Guide: Escape braces and angle brackets for format consistency
> ---
>
> Key: GEODE-10172
> URL: https://issues.apache.org/jira/browse/GEODE-10172
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Affects Versions: 1.14.4
>Reporter: Dave Barnes
>Priority: Major
>
> The REST Apps section contains expressions that make heavy use of braces {}
> and angle-brackets <>. Escape these chars for more consistent rendering by
> various formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
[
https://issues.apache.org/jira/browse/GEODE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes reassigned GEODE-10172:
---
Assignee: Dave Barnes
> User Guide: Escape braces and angle brackets for format consistency
> ---
>
> Key: GEODE-10172
> URL: https://issues.apache.org/jira/browse/GEODE-10172
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Affects Versions: 1.14.4
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
>
> The REST Apps section contains expressions that make heavy use of braces {}
> and angle-brackets <>. Escape these chars for more consistent rendering by
> various formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
[
https://issues.apache.org/jira/browse/GEODE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes resolved GEODE-10172.
-
Fix Version/s: 1.15.0
Resolution: Fixed
> User Guide: Escape braces and angle brackets for format consistency
> ---
>
> Key: GEODE-10172
> URL: https://issues.apache.org/jira/browse/GEODE-10172
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Affects Versions: 1.14.4
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> The REST Apps section contains expressions that make heavy use of braces {}
> and angle-brackets <>. Escape these chars for more consistent rendering by
> various formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10207) check log levels for gfsh commands
Dave Barnes created GEODE-10207: --- Summary: check log levels for gfsh commands Key: GEODE-10207 URL: https://issues.apache.org/jira/browse/GEODE-10207 Project: Geode Issue Type: Sub-task Components: docs Affects Versions: 1.14.4 Reporter: Dave Barnes Community member Tod Morrison suggests checking log levels for gfsh commands `alter runtime` and `change loglevel`. The levels don’t look right: The new log level. This option is required and you must specify a value. Valid values are: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF. (Default is INFO) See https://geode.apache.org/docs/guide/114/managing/logging/setting_up_logging.html, which shows valid choices of `severe`, `error`, `warning`, `info`, `config`, and `fine`. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10232) User Guide - reformat list for more reliable rendering
Dave Barnes created GEODE-10232: --- Summary: User Guide - reformat list for more reliable rendering Key: GEODE-10232 URL: https://issues.apache.org/jira/browse/GEODE-10232 Project: Geode Issue Type: Improvement Components: docs Affects Versions: 1.14.4 Reporter: Dave Barnes The How Function Execution Works page contains a bullet list with bold elements and en-dashes (apparently entered via keyboard shortcuts) that are not always interpreted in the same way by different Markdown interpreters. https://geode.apache.org/docs/guide/114/developing/function_exec/how_function_execution_works.html Simplify the layout for more reliable output across various flavors of Markdown. Suggested modification: Replace each en-dash with a colon+space combination. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10232) User Guide - reformat list for more reliable rendering
[ https://issues.apache.org/jira/browse/GEODE-10232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-10232: --- Assignee: Dave Barnes > User Guide - reformat list for more reliable rendering > -- > > Key: GEODE-10232 > URL: https://issues.apache.org/jira/browse/GEODE-10232 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > The How Function Execution Works page contains a bullet list with bold > elements and en-dashes (apparently entered via keyboard shortcuts) that are > not always interpreted in the same way by different Markdown interpreters. > https://geode.apache.org/docs/guide/114/developing/function_exec/how_function_execution_works.html > Simplify the layout for more reliable output across various flavors of > Markdown. > Suggested modification: Replace each en-dash with a colon+space combination. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10233) User guide: Improve format of cache elements and client-cache elements reference pages
Dave Barnes created GEODE-10233: --- Summary: User guide: Improve format of cache elements and client-cache elements reference pages Key: GEODE-10233 URL: https://issues.apache.org/jira/browse/GEODE-10233 Project: Geode Issue Type: Improvement Components: docs Affects Versions: 1.14.4 Reporter: Dave Barnes The reference pages for cache.xml and client_cache.xml use 3-column tables to describe their respective elements. * https://geode.apache.org/docs/guide/114/reference/topics/cache_xml.html * https://geode.apache.org/docs/guide/114/reference/topics/client-cache.html Problem: Almost all content is confined to Column 2. Columns 1 and 3 contain very little content. Column 2 even contains nested tables and sample code. This presentation is very hard to read, and very hard to search or browse. For example, see the table in cache_xml.html describingattributes. Solution: Devise a better format that's easier to read and better adapted to searching and browsing. An outline structure with headings, subheadings, and paragraphs would be one suggestion. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10232) User Guide - reformat list for more reliable rendering
[ https://issues.apache.org/jira/browse/GEODE-10232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10232. - Fix Version/s: 1.12.10 1.13.9 1.14.5 1.15.0 Resolution: Fixed Fixed on develop, backported to 1.12, 1.13, 1.14 > User Guide - reformat list for more reliable rendering > -- > > Key: GEODE-10232 > URL: https://issues.apache.org/jira/browse/GEODE-10232 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0 > > > The How Function Execution Works page contains a bullet list with bold > elements and en-dashes (apparently entered via keyboard shortcuts) that are > not always interpreted in the same way by different Markdown interpreters. > https://geode.apache.org/docs/guide/114/developing/function_exec/how_function_execution_works.html > Simplify the layout for more reliable output across various flavors of > Markdown. > Suggested modification: Replace each en-dash with a colon+space combination. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9759) User Guide: gfsh command pages - problem with double-hyphens
[ https://issues.apache.org/jira/browse/GEODE-9759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9759: -- Assignee: Max Hufnagel (was: Dave Barnes) > User Guide: gfsh command pages - problem with double-hyphens > > > Key: GEODE-9759 > URL: https://issues.apache.org/jira/browse/GEODE-9759 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.14.0 >Reporter: Dave Barnes >Assignee: Max Hufnagel >Priority: Major > Labels: pull-request-available > > In the tables of gfsh command options, double-hyphen prefixes are often (but > not always) collapsed to a single hyphen. > This is a format issue with dozens (possibly hundreds?) of occurrences. > See, for example, the `alter` command page, > http://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/alter.html. > Note the difference between the entry for > `--entry-idle-time-expiration-action` and the following entry > `-entry-time-to-live-expiration`. The tricky bit is that the source code in > both cases uses the same HTML construct: `\-\-entry-time-to-live-expiration`, but the results > differ. > One likely remedy is to replace the hyphen pair with the code for two > non-breaking hyphens: `‑‑`. > Behavior may differ depending on whether the entry occurs in an HTML table, a > nested HTML table, or a Markdown table. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10264) Geode user guide: remove the "Connect to the server from your application" section
Dave Barnes created GEODE-10264: --- Summary: Geode user guide: remove the "Connect to the server from your application" section Key: GEODE-10264 URL: https://issues.apache.org/jira/browse/GEODE-10264 Project: Geode Issue Type: Bug Components: docs Affects Versions: 1.14.4 Reporter: Dave Barnes Community member John Martin reported: We need to remove the "Connect to the server from your application" section from this page please: https://geode.apache.org/docs/guide/114/getting_started/intro_to_clients.html it is not accurate, and was a section I thought I had deleted before submitting, but apparently I had not. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10215) WAN replication not working after re-creating the partitioned region
[
https://issues.apache.org/jira/browse/GEODE-10215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531771#comment-17531771
]
Dave Barnes commented on GEODE-10215:
-
I have approved adding a warning to the docs, because it's better than nothing.
But it feels to me like an incomplete remedy for a design flaw.
> WAN replication not working after re-creating the partitioned region
>
>
> Key: GEODE-10215
> URL: https://issues.apache.org/jira/browse/GEODE-10215
> Project: Geode
> Issue Type: Bug
>Reporter: Jakov Varenina
>Assignee: Jakov Varenina
>Priority: Major
> Labels: pull-request-available
>
> Steps to reproduce the issue:
> Start multi-site with at least 3 servers on each site. If there are less than
> three servers then issue will not reproduce.
> Configuration site 1:
> {code:java}
> create disk-store --name=queue_disk_store --dir=ds2
> create gateway-sender -id="remote_site_2" --parallel="true"
> --remote-distributed-system-id="1" -enable-persistence=true
> --disk-store-name=queue_disk_store
> create disk-store --name=data_disk_store --dir=ds1
> create region --name=example-region --type=PARTITION_PERSISTENT
> --gateway-sender-id="remote_site_2" --disk-store=data_disk_store
> --total-num-buckets=1103 --redundant-copies=1 --enable-synchronous-disk=false
> #Configure the remote site 2 with the region and the gateway-receiver
> #Run some traffic so that all buckets are created and data is replicated to
> the other site
> alter region --name=/example-region --gateway-sender-id=""
> destroy region --name=/example-region
> create region --name=example-region --type=PARTITION_PERSISTENT
> --gateway-sender-id="remote_site_2" --disk-store=data_disk_store
> --total-num-buckets=1103 --redundant-copies=1 --enable-synchronous-disk=false
> #run traffic to see that some data is not replicated to the remote site 2
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (GEODE-10215) WAN replication not working after re-creating the partitioned region
[
https://issues.apache.org/jira/browse/GEODE-10215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531771#comment-17531771
]
Dave Barnes edited comment on GEODE-10215 at 5/4/22 2:59 PM:
-
I have approved adding a warning to the docs, because it's better than nothing.
But it feels to me like an incomplete remedy for a design flaw.
I leave it to others to determine whether this truly 'resolves' the bug.
was (Author: dbarnes97):
I have approved adding a warning to the docs, because it's better than nothing.
But it feels to me like an incomplete remedy for a design flaw.
> WAN replication not working after re-creating the partitioned region
>
>
> Key: GEODE-10215
> URL: https://issues.apache.org/jira/browse/GEODE-10215
> Project: Geode
> Issue Type: Bug
>Reporter: Jakov Varenina
>Assignee: Jakov Varenina
>Priority: Major
> Labels: pull-request-available
>
> Steps to reproduce the issue:
> Start multi-site with at least 3 servers on each site. If there are less than
> three servers then issue will not reproduce.
> Configuration site 1:
> {code:java}
> create disk-store --name=queue_disk_store --dir=ds2
> create gateway-sender -id="remote_site_2" --parallel="true"
> --remote-distributed-system-id="1" -enable-persistence=true
> --disk-store-name=queue_disk_store
> create disk-store --name=data_disk_store --dir=ds1
> create region --name=example-region --type=PARTITION_PERSISTENT
> --gateway-sender-id="remote_site_2" --disk-store=data_disk_store
> --total-num-buckets=1103 --redundant-copies=1 --enable-synchronous-disk=false
> #Configure the remote site 2 with the region and the gateway-receiver
> #Run some traffic so that all buckets are created and data is replicated to
> the other site
> alter region --name=/example-region --gateway-sender-id=""
> destroy region --name=/example-region
> create region --name=example-region --type=PARTITION_PERSISTENT
> --gateway-sender-id="remote_site_2" --disk-store=data_disk_store
> --total-num-buckets=1103 --redundant-copies=1 --enable-synchronous-disk=false
> #run traffic to see that some data is not replicated to the remote site 2
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (GEODE-10307) Doc changes needed for enable security-manager property
Dave Barnes created GEODE-10307: --- Summary: Doc changes needed for enable security-manager property Key: GEODE-10307 URL: https://issues.apache.org/jira/browse/GEODE-10307 Project: Geode Issue Type: Improvement Affects Versions: 1.14.4 Reporter: Dave Barnes Community member Eric Shu reports: Here is the description for enable security properties: (https://geode.apache.org/docs/guide/114/managing/security/enable_security.html) security-manager Property The authentication callback and the authorization callback that implement the SecurityManager interface are specified with the security-manager property. When this property is defined, authentication and authorization are enabled. The definition of the security-manager property is the fully qualified name of the class that implements the SecurityManager interface. For example: security-manager = com.example.security.MySecurityManager To ensure that the security-manager property is applied consistently across a cluster, follow these guidelines: Specify the security-manager property in a properties file, such as gemfire.properties, not in a cluster configuration file (such as cluster.properties). Specify the properties file when you start the first locator for the cluster. The locator will propagate the value to all members (locators and servers) that follow. If you must specify the security-manager property for servers (neither necessary nor recommended) make sure its value is exactly identical to that specified for the first locator. This is true if the cluster has enabled the cluster configuration service, and new members have set the `use-cluster-configuration=true`. Documentation should explain that if cluster configuration is not enabled, you must specify the security-manager property for servers, makng sure its value is exactly identical to that specified for the first locator. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10307) Doc changes needed for enable security-manager property
[ https://issues.apache.org/jira/browse/GEODE-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10307. - Fix Version/s: 1.12.10 1.14.5 1.15.0 1.16.0 Assignee: Dave Barnes Resolution: Fixed > Doc changes needed for enable security-manager property > --- > > Key: GEODE-10307 > URL: https://issues.apache.org/jira/browse/GEODE-10307 > Project: Geode > Issue Type: Improvement >Affects Versions: 1.14.4 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.10, 1.14.5, 1.15.0, 1.16.0 > > > Community member Eric Shu reports: > Here is the description for enable security properties: > (https://geode.apache.org/docs/guide/114/managing/security/enable_security.html) > security-manager Property > The authentication callback and the authorization callback that implement the > SecurityManager interface are specified with the security-manager property. > When this property is defined, authentication and authorization are enabled. > The definition of the security-manager property is the fully qualified name > of the class that implements the SecurityManager interface. For example: > security-manager = com.example.security.MySecurityManager > To ensure that the security-manager property is applied consistently across a > cluster, follow these guidelines: > Specify the security-manager property in a properties file, such as > gemfire.properties, not in a cluster configuration file (such as > cluster.properties). > Specify the properties file when you start the first locator for the cluster. > The locator will propagate the value to all members (locators and servers) > that follow. > If you must specify the security-manager property for servers (neither > necessary nor recommended) make sure its value is exactly identical to that > specified for the first locator. > This is true if the cluster has enabled the cluster configuration service, > and new members have set the `use-cluster-configuration=true`. > Documentation should explain that if cluster configuration is not enabled, > you must specify the security-manager property for servers, makng sure its > value is exactly identical to that specified for the first locator. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (GEODE-3845) local-destroy setting of eviction breaks the consistency of the partition region
[
https://issues.apache.org/jira/browse/GEODE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes reassigned GEODE-3845:
--
Assignee: Dave Barnes
> local-destroy setting of eviction breaks the consistency of the partition
> region
>
>
> Key: GEODE-3845
> URL: https://issues.apache.org/jira/browse/GEODE-3845
> Project: Geode
> Issue Type: Bug
> Components: docs, eviction
>Reporter: Masaki Yamakawa
>Assignee: Dave Barnes
> Labels: geode-150
>
> I use entry-idle-time and eviction together in a partition region that holds
> one redundant copy.
> Details of setting are as follows:
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
> {code}
> In this setting, the data held by the cache server is different. Then,
> inconsistent results are returned depending on the server to be connected.
> Eviction of the partition region can only select local-destroy or
> overflow-to-disk. On the other hand, it is written that the expire chapter of
> the document can not use local-destroy, local-invalidate in the partition
> region. Likewise, I think that data inconsistency will occur even with the
> settings like this time.
> Below is the test code:
> https://github.com/masaki-yamakawa/geode/blob/bug-partition-local-destroy/geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/BugExpireAndEvictionDUnitTest.java
> I think that it is necessary to add a check at the time of region creation or
> write it in the document.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (GEODE-3758) Ensure all expiration help text has units
[
https://issues.apache.org/jira/browse/GEODE-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16323294#comment-16323294
]
Dave Barnes commented on GEODE-3758:
Expiration units are seconds.
> Ensure all expiration help text has units
> -
>
> Key: GEODE-3758
> URL: https://issues.apache.org/jira/browse/GEODE-3758
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>
> The following command's help text does not have units.
> {noformat}
> gfsh>create region --name=test --type=PARTITION_HEAP_LRU
> --region-time-to-live-expiration
> Value is required for parameter "region-time-to-live-expiration: How long the
> region can remain in the cache without being accessed or updated. The default
> is no expiration of this type."
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (GEODE-4294) User Guide: Region level expiration is not supported for partitioned regions
[ https://issues.apache.org/jira/browse/GEODE-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-4294: -- Assignee: Dave Barnes > User Guide: Region level expiration is not supported for partitioned regions > > > Key: GEODE-4294 > URL: https://issues.apache.org/jira/browse/GEODE-4294 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes > > Akihiro Kitada reports: > Partitioned regions do not support region level expiration. Please make this > clear in the docs, like "Partitioned region does not support region level > expiration". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEODE-4294) User Guide: Region level expiration is not supported for partitioned regions
Dave Barnes created GEODE-4294: -- Summary: User Guide: Region level expiration is not supported for partitioned regions Key: GEODE-4294 URL: https://issues.apache.org/jira/browse/GEODE-4294 Project: Geode Issue Type: Bug Components: docs Reporter: Dave Barnes Akihiro Kitada reports: Partitioned regions do not support region level expiration. Please make this clear in the docs, like "Partitioned region does not support region level expiration". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEODE-4297) User Guide: Clarify logging from developer's perspective
Dave Barnes created GEODE-4297: -- Summary: User Guide: Clarify logging from developer's perspective Key: GEODE-4297 URL: https://issues.apache.org/jira/browse/GEODE-4297 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes [Request from Mark Secrist] I find the documentation doesn’t go far enough to cover how to do logging - particularly on the server side from a developer perspective. I figured out how to set up logging by jumping through GemFire code and found something like the following ```Logger logger = LogService.getLogger() ``` This is the recommended way, but it's not covered in the docs. Also - the logging doesn’t tend to have the level of detail I like (ex class & method). I realize this has to do with how the overall appender is configured. I’m curious if we have recommended ways of overriding this in certain situations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4297) User Guide: Clarify logging from developer's perspective
[ https://issues.apache.org/jira/browse/GEODE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327993#comment-16327993 ] Dave Barnes commented on GEODE-4297: [also from Mark Secrist] I think there may be some inaccuracies here: https://gemfire.docs.pivotal.io/geode/managing/logging/configuring_log4j2.html related to use of LogWriter, which I believe is deprecated > User Guide: Clarify logging from developer's perspective > > > Key: GEODE-4297 > URL: https://issues.apache.org/jira/browse/GEODE-4297 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Priority: Major > > [Request from Mark Secrist] > I find the documentation doesn’t go far enough to cover how to do logging - > particularly on the server side from a developer perspective. > I figured out how to set up logging by jumping through GemFire code and found > something like the following > ```Logger logger = LogService.getLogger() ``` > This is the recommended way, but it's not covered in the docs. Also - the > logging doesn’t tend to have the level of detail I like (ex class & method). > I realize this has to do with how the overall appender is configured. I’m > curious if we have recommended ways of overriding this in certain situations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4294) User Guide: Region level expiration is not supported for partitioned regions
[ https://issues.apache.org/jira/browse/GEODE-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-4294. Resolution: Fixed Fix Version/s: 1.4.0 > User Guide: Region level expiration is not supported for partitioned regions > > > Key: GEODE-4294 > URL: https://issues.apache.org/jira/browse/GEODE-4294 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.4.0 > > > Akihiro Kitada reports: > Partitioned regions do not support region level expiration. Please make this > clear in the docs, like "Partitioned region does not support region level > expiration". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3745) User Guide: Incomplete diagram, durable client
[ https://issues.apache.org/jira/browse/GEODE-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-3745. Resolution: Fixed Fix Version/s: 1.4.0 > User Guide: Incomplete diagram, durable client > -- > > Key: GEODE-3745 > URL: https://issues.apache.org/jira/browse/GEODE-3745 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > Fix For: 1.4.0 > > > Under "Implementing Durable Client/Server Messaging" there's a diagram that > is incomplete due to cropping on the right-hand side. Needs to be restored > from source (if one can be found) or redrawn for completeness. > The image source file is > ...geode-docs/images/ClientServerAdvancedTopics-6.gif. Manual page is > http://geode.apache.org/docs/guide/12/developing/events/implementing_durable_client_server_messaging.html, > under the "Reconnection" heading. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4325) User Guide: Clarify eviction actions
Dave Barnes created GEODE-4325: -- Summary: User Guide: Clarify eviction actions Key: GEODE-4325 URL: https://issues.apache.org/jira/browse/GEODE-4325 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes Astute reader Gideon Low observes: The documentation for eviction action configuration don't make clear that localDestroy is invalid for Partitioned Regions. This is made more confusing by the following verbiage on overflow-to-disk, which implies that other eviction action options exist for PR's: "For partitioned regions, this provides the most reliable read behavior across the region" . . . Yes, it is the most reliable behavior, but it is also the ONLY supported behavior. The fact that local-destroy eviction action states "Not available for replicated regions" without mentioning PR's makes this even more confusing. Here's the link for lru-entry-count (lru-heap-percentage and lru-memory-size have the exact same problem): [http://gemfire82.docs.pivotal.io/docs-gemfire/latest/reference/topics/cache_xml.html#lru-entry-count] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4325) User Guide: Clarify eviction actions
[ https://issues.apache.org/jira/browse/GEODE-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-4325: -- Assignee: Dave Barnes > User Guide: Clarify eviction actions > > > Key: GEODE-4325 > URL: https://issues.apache.org/jira/browse/GEODE-4325 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > Astute reader Gideon Low observes: > The documentation for eviction action configuration don't make clear that > localDestroy is invalid for Partitioned Regions. This is made more confusing > by the following verbiage on overflow-to-disk, which implies that other > eviction action options exist for PR's: "For partitioned regions, this > provides the most reliable read behavior across the region" . . . Yes, it is > the most reliable behavior, but it is also the ONLY supported behavior. The > fact that local-destroy eviction action states "Not available for replicated > regions" without mentioning PR's makes this even more confusing. Here's the > link for lru-entry-count (lru-heap-percentage and lru-memory-size have the > exact same problem): > [http://gemfire82.docs.pivotal.io/docs-gemfire/latest/reference/topics/cache_xml.html#lru-entry-count] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-4297) User Guide: Clarify logging from developer's perspective
[ https://issues.apache.org/jira/browse/GEODE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327993#comment-16327993 ] Dave Barnes edited comment on GEODE-4297 at 1/22/18 6:27 PM: - [also from Mark Secrist] I think there may be some inaccuracies here: http://geode.apache.org/docs/guide/13/managing/logging/configuring_log4j2.html related to use of LogWriter, which I believe is deprecated was (Author: dbarnes97): [also from Mark Secrist] I think there may be some inaccuracies here: https://gemfire.docs.pivotal.io/geode/managing/logging/configuring_log4j2.html related to use of LogWriter, which I believe is deprecated > User Guide: Clarify logging from developer's perspective > > > Key: GEODE-4297 > URL: https://issues.apache.org/jira/browse/GEODE-4297 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Priority: Major > > [Request from Mark Secrist] > I find the documentation doesn’t go far enough to cover how to do logging - > particularly on the server side from a developer perspective. > I figured out how to set up logging by jumping through GemFire code and found > something like the following > ```Logger logger = LogService.getLogger() ``` > This is the recommended way, but it's not covered in the docs. Also - the > logging doesn’t tend to have the level of detail I like (ex class & method). > I realize this has to do with how the overall appender is configured. I’m > curious if we have recommended ways of overriding this in certain situations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4360) User Guide: Remove --enable-eviction option from gfsh create region doc
Dave Barnes created GEODE-4360: -- Summary: User Guide: Remove --enable-eviction option from gfsh create region doc Key: GEODE-4360 URL: https://issues.apache.org/jira/browse/GEODE-4360 Project: Geode Issue Type: Bug Components: docs Reporter: Dave Barnes This option was added to the docs per the writeup of GEODE-1897, but the option was never, in fact, implemented. Remove from docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4360) User Guide: Remove --enable-eviction option from gfsh create region doc
[ https://issues.apache.org/jira/browse/GEODE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-4360: --- Priority: Minor (was: Major) > User Guide: Remove --enable-eviction option from gfsh create region doc > --- > > Key: GEODE-4360 > URL: https://issues.apache.org/jira/browse/GEODE-4360 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.4.0 >Reporter: Dave Barnes >Priority: Minor > > This option was added to the docs per the writeup of GEODE-1897, but the > option was never, in fact, implemented. Remove from docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4360) User Guide: Remove --enable-eviction option from gfsh create region doc
[ https://issues.apache.org/jira/browse/GEODE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-4360: --- Affects Version/s: 1.4.0 > User Guide: Remove --enable-eviction option from gfsh create region doc > --- > > Key: GEODE-4360 > URL: https://issues.apache.org/jira/browse/GEODE-4360 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.4.0 >Reporter: Dave Barnes >Priority: Minor > > This option was added to the docs per the writeup of GEODE-1897, but the > option was never, in fact, implemented. Remove from docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4360) User Guide: Remove --enable-eviction option from gfsh create region doc
[ https://issues.apache.org/jira/browse/GEODE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-4360: -- Assignee: Dave Barnes > User Guide: Remove --enable-eviction option from gfsh create region doc > --- > > Key: GEODE-4360 > URL: https://issues.apache.org/jira/browse/GEODE-4360 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.4.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > This option was added to the docs per the writeup of GEODE-1897, but the > option was never, in fact, implemented. Remove from docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4361) Provide a gfsh command to modify eviction heap/off-heap percentages
Dave Barnes created GEODE-4361: -- Summary: Provide a gfsh command to modify eviction heap/off-heap percentages Key: GEODE-4361 URL: https://issues.apache.org/jira/browse/GEODE-4361 Project: Geode Issue Type: New Feature Components: docs, gfsh Reporter: Dave Barnes The gfsh start server command allows the user to set the eviction-heap-percentage and eviction-off-heap-percentage. We should provide a gfsh command to modify these values on a running server. (Perhaps by adding capabilities to the gfsh alter runtime command?) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4354) On create region command change option --skip-if-exists to --if-not-exist
[
https://issues.apache.org/jira/browse/GEODE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes reassigned GEODE-4354:
--
Assignee: Dave Barnes
> On create region command change option --skip-if-exists to --if-not-exist
> -
>
> Key: GEODE-4354
> URL: https://issues.apache.org/jira/browse/GEODE-4354
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
>Reporter: Barbara Pruijn
>Assignee: Dave Barnes
>Priority: Major
>
> The gfsh {{create region}} command tries to be idempotent. If I try to create
> the same region twice I get the below message:
> {noformat}
> Member | Status
> -- | --
> serv1 | Skipping "serv1". Region "foo" already exists.{noformat}
> Currently, there is a
> {{--skip-if-exists}}
> option. This should be consistent with other gfsh commands and should be
> rename
> {{--if-not-exists}}
> This option should also be added the {{help create region}} command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4360) User Guide: Remove --eviction-enabled option from gfsh create region doc
[ https://issues.apache.org/jira/browse/GEODE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-4360: --- Summary: User Guide: Remove --eviction-enabled option from gfsh create region doc (was: User Guide: Remove --enable-eviction option from gfsh create region doc) > User Guide: Remove --eviction-enabled option from gfsh create region doc > > > Key: GEODE-4360 > URL: https://issues.apache.org/jira/browse/GEODE-4360 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.4.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > This option was added to the docs per the writeup of GEODE-1897, but the > option was never, in fact, implemented. Remove from docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4361) Provide a gfsh command to modify eviction heap/off-heap percentages
[ https://issues.apache.org/jira/browse/GEODE-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-4361: --- Issue Type: Sub-task (was: New Feature) Parent: GEODE-2656 > Provide a gfsh command to modify eviction heap/off-heap percentages > --- > > Key: GEODE-4361 > URL: https://issues.apache.org/jira/browse/GEODE-4361 > Project: Geode > Issue Type: Sub-task > Components: docs, gfsh >Reporter: Dave Barnes >Priority: Major > > The gfsh start server command allows the user to set the > eviction-heap-percentage and eviction-off-heap-percentage. We should provide > a gfsh command to modify these values on a running server. (Perhaps by adding > capabilities to the gfsh alter runtime command?) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4361) Provide a gfsh command to modify eviction heap/off-heap percentages
[ https://issues.apache.org/jira/browse/GEODE-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-4361: --- Description: The gfsh start server command allows the user to set the eviction-heap-percentage and eviction-off-heap-percentage. We should provide a gfsh command to modify these values on a running server. (Perhaps by adding capabilities to the gfsh alter runtime command?) We should also provide the same capability for modifying critical heap/off-heap percentage. was:The gfsh start server command allows the user to set the eviction-heap-percentage and eviction-off-heap-percentage. We should provide a gfsh command to modify these values on a running server. (Perhaps by adding capabilities to the gfsh alter runtime command?) > Provide a gfsh command to modify eviction heap/off-heap percentages > --- > > Key: GEODE-4361 > URL: https://issues.apache.org/jira/browse/GEODE-4361 > Project: Geode > Issue Type: Sub-task > Components: docs, gfsh >Reporter: Dave Barnes >Priority: Major > > The gfsh start server command allows the user to set the > eviction-heap-percentage and eviction-off-heap-percentage. We should provide > a gfsh command to modify these values on a running server. (Perhaps by adding > capabilities to the gfsh alter runtime command?) > We should also provide the same capability for modifying critical > heap/off-heap percentage. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4360) User Guide: Remove --eviction-enabled option from gfsh create region doc
[ https://issues.apache.org/jira/browse/GEODE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-4360. Resolution: Fixed > User Guide: Remove --eviction-enabled option from gfsh create region doc > > > Key: GEODE-4360 > URL: https://issues.apache.org/jira/browse/GEODE-4360 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.4.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > This option was added to the docs per the writeup of GEODE-1897, but the > option was never, in fact, implemented. Remove from docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3843) gfsh shutdown error message suggests non-existent option
[ https://issues.apache.org/jira/browse/GEODE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-3843. Resolution: Fixed Fix Version/s: 1.4.0 > gfsh shutdown error message suggests non-existent option > > > Key: GEODE-3843 > URL: https://issues.apache.org/jira/browse/GEODE-3843 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Dave Barnes >Assignee: Srikanth Manvi >Priority: Minor > Fix For: 1.4.0 > > > 1. Start gfsh. > 2. Start a locator. > 3. Issue the 'shutdown' command. > gfsh prompts for 'do you really want to...', then issues an error message > alerting you to the lack of data nodes. OK so far. > This is followed by a line recommending that you use '--shutdown-locators' to > stop your locator. > Should be '--include-locators=true'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4394) gfsh put command: change option --skip-if-exists to --if-not-exists
Dave Barnes created GEODE-4394: -- Summary: gfsh put command: change option --skip-if-exists to --if-not-exists Key: GEODE-4394 URL: https://issues.apache.org/jira/browse/GEODE-4394 Project: Geode Issue Type: Improvement Components: docs, gfsh Reporter: Dave Barnes Change the gfsh put command `--skip-if-exists` option to `--if-not-exists` for consistency with other gfsh commands, most notably create region (see GEODE-4354). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-2563) All destroy commands in gfsh should be idempotent
[ https://issues.apache.org/jira/browse/GEODE-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343939#comment-16343939 ] Dave Barnes commented on GEODE-2563: Added documentation in Geode v1.5 docs for the --if-exists option for the four commands in question: destroy disk-store destroy gateway-sender destroy index destroy region Plus the newly-added destroy async-event-queue command > All destroy commands in gfsh should be idempotent > - > > Key: GEODE-2563 > URL: https://issues.apache.org/jira/browse/GEODE-2563 > Project: Geode > Issue Type: Improvement > Components: docs, gfsh >Reporter: Swapnil Bawaskar >Priority: Major > Fix For: 1.4.0 > > > If a developer is using gfsh script to define the geode cluster, we should > support the ability to run the gfsh script multiple times. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-2563) All destroy commands in gfsh should be idempotent
[ https://issues.apache.org/jira/browse/GEODE-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343939#comment-16343939 ] Dave Barnes edited comment on GEODE-2563 at 1/29/18 8:07 PM: - Added documentation in Geode v1.4 docs for the --if-exists option for the four commands in question: destroy disk-store destroy gateway-sender destroy index destroy region Plus the newly-added destroy async-event-queue command was (Author: dbarnes97): Added documentation in Geode v1.5 docs for the --if-exists option for the four commands in question: destroy disk-store destroy gateway-sender destroy index destroy region Plus the newly-added destroy async-event-queue command > All destroy commands in gfsh should be idempotent > - > > Key: GEODE-2563 > URL: https://issues.apache.org/jira/browse/GEODE-2563 > Project: Geode > Issue Type: Improvement > Components: docs, gfsh >Reporter: Swapnil Bawaskar >Priority: Major > Fix For: 1.4.0 > > > If a developer is using gfsh script to define the geode cluster, we should > support the ability to run the gfsh script multiple times. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-2563) All destroy commands in gfsh should be idempotent
[ https://issues.apache.org/jira/browse/GEODE-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-2563: -- Assignee: Dave Barnes > All destroy commands in gfsh should be idempotent > - > > Key: GEODE-2563 > URL: https://issues.apache.org/jira/browse/GEODE-2563 > Project: Geode > Issue Type: Improvement > Components: docs, gfsh >Reporter: Swapnil Bawaskar >Assignee: Dave Barnes >Priority: Major > Fix For: 1.4.0 > > > If a developer is using gfsh script to define the geode cluster, we should > support the ability to run the gfsh script multiple times. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2563) All destroy commands in gfsh should be idempotent
[ https://issues.apache.org/jira/browse/GEODE-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-2563. Resolution: Fixed > All destroy commands in gfsh should be idempotent > - > > Key: GEODE-2563 > URL: https://issues.apache.org/jira/browse/GEODE-2563 > Project: Geode > Issue Type: Improvement > Components: docs, gfsh >Reporter: Swapnil Bawaskar >Assignee: Dave Barnes >Priority: Major > Fix For: 1.4.0 > > > If a developer is using gfsh script to define the geode cluster, we should > support the ability to run the gfsh script multiple times. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4373) gfsh 'describe region' not showing accessor region description
[
https://issues.apache.org/jira/browse/GEODE-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes updated GEODE-4373:
---
Component/s: docs
> gfsh 'describe region' not showing accessor region description
> --
>
> Key: GEODE-4373
> URL: https://issues.apache.org/jira/browse/GEODE-4373
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> gfsh not displaying accessor region description.
> on Develop:
> {noformat}
> Command result for :
> ..
> Name : testRegion
> Data Policy : persistent replicate
> Hosting Members : server-5
> server-4
> server-3
> server-2
> Non-Default Attributes Shared By Hosting Members
> Type | Name| Value
> -- | --- |
> Region | data-policy | PERSISTENT_REPLICATE
>| disk-store-name | testDiskStore
>| size| 0
>| scope | distributed-ack{noformat}
>
> But in v1.3.0 it used to display accessor region description as a separate
> table.
> {noformat}
> Command result for :
> ...
> Name: testRegion
> Data Policy : persistent replicate
> Hosting Members : server-3
> server-2
> Non-Default Attributes Shared By Hosting Members
> Type | Name | Value
> -- | --- |
> Region | data-policy | PERSISTENT_REPLICATE
>| disk-store-name | testDiskStore
>| size| 0
>| scope | distributed-ack
> ...
> Name : testRegion
> Data Policy : empty
> Accessor Members : server-1
> Non-Default Attributes Shared By Accessor Members
> Type |Name | Value
> -- | --- | ---
> Region | data-policy | EMPTY
>| size| 0
>| scope | distributed-ack
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4608) User Guide: Update Quick Reference of gfsh Commands by Functional Area
Dave Barnes created GEODE-4608: -- Summary: User Guide: Update Quick Reference of gfsh Commands by Functional Area Key: GEODE-4608 URL: https://issues.apache.org/jira/browse/GEODE-4608 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes Command descriptions recently-added to the section "gfsh Command Help" have not been consistently added to the section "Quick Reference of gfsh Commands by Functional Area". The quick ref should be brought up to date for the benefit of readers searching for a gfsh capability without already knowing the name of its implementing command. Examples prompting this ticket are 'destroy gateway-sender' and 'destroy async-event-queue', which should be added to the quick ref's table of Gateway (WAN) commands. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4609) Create region gfsh command option --skip-if-exists defaults to false
[
https://issues.apache.org/jira/browse/GEODE-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354480#comment-16354480
]
Dave Barnes commented on GEODE-4609:
Based on the description and some off-line discussions, it appears to me that
the text in the Description column is correct, but the entry in the "Default"
column needs to be changed to "false".
> Create region gfsh command option --skip-if-exists defaults to false
>
>
> Key: GEODE-4609
> URL: https://issues.apache.org/jira/browse/GEODE-4609
> Project: Geode
> Issue Type: Bug
> Components: docs
>Affects Versions: 1.4.0
>Reporter: Barbara Pruijn
>Priority: Minor
>
> This ticket is filed for updating the documentation.
> The create region gfsh command's default behavior for --skip-if-exists
> default behavior changed in 1.4.0. The default behavior when you do not
> specify this option is now false.
> [http://gemfire.docs.pivotal.io/geode/tools_modules/gfsh/command-pages/create.html#topic_54B0985FEC5241CA9D26B0CE0A5EA863]
>
> {code:java}
> gfsh>create region --name=test --type=PARTITION --skip-if-exists
> optional --skip-if-exists: Skip region creation if the region already
> exists.; default if option present: 'true'; default if option not present:
> 'false'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-4609) Create region gfsh command option --skip-if-exists defaults to false
[
https://issues.apache.org/jira/browse/GEODE-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes reassigned GEODE-4609:
--
Assignee: Dave Barnes
> Create region gfsh command option --skip-if-exists defaults to false
>
>
> Key: GEODE-4609
> URL: https://issues.apache.org/jira/browse/GEODE-4609
> Project: Geode
> Issue Type: Bug
> Components: docs
>Affects Versions: 1.4.0
>Reporter: Barbara Pruijn
>Assignee: Dave Barnes
>Priority: Minor
>
> This ticket is filed for updating the documentation.
> The create region gfsh command's default behavior for --skip-if-exists
> default behavior changed in 1.4.0. The default behavior when you do not
> specify this option is now false.
> [http://gemfire.docs.pivotal.io/geode/tools_modules/gfsh/command-pages/create.html#topic_54B0985FEC5241CA9D26B0CE0A5EA863]
>
> {code:java}
> gfsh>create region --name=test --type=PARTITION --skip-if-exists
> optional --skip-if-exists: Skip region creation if the region already
> exists.; default if option present: 'true'; default if option not present:
> 'false'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (GEODE-4354) On create region command change option --skip-if-exists to --if-not-exists
[
https://issues.apache.org/jira/browse/GEODE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes reopened GEODE-4354:
Reopened pending doc update
> On create region command change option --skip-if-exists to --if-not-exists
> --
>
> Key: GEODE-4354
> URL: https://issues.apache.org/jira/browse/GEODE-4354
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
>Reporter: Barbara Pruijn
>Assignee: Dave Barnes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The gfsh {{create region}} command tries to be idempotent. If I try to create
> the same region twice I get the below message:
> {noformat}
> Member | Status
> -- | --
> serv1 | Skipping "serv1". Region "foo" already exists.{noformat}
> Currently, there is a
> {{--skip-if-exists}}
> option. This should be consistent with other gfsh commands and should be
> rename
> {{--if-not-exists}}
> This option should also be added the {{help create region}} command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
