[jira] [Resolved] (GEODE-7125) Simplify documentation navigation (remove left nav parent links; add in-page TOCs)
[ https://issues.apache.org/jira/browse/GEODE-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-7125. Resolution: Won't Fix > Simplify documentation navigation (remove left nav parent links; add in-page > TOCs) > -- > > Key: GEODE-7125 > URL: https://issues.apache.org/jira/browse/GEODE-7125 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Joey McAllister >Assignee: Dave Barnes >Priority: Minor > > The Geode user guide uses Bookbinder to create HTML documentation from > markdown files. This ticket is about changing two ways in which Geode > currently uses Bookbinder sub-optimally: > # For listings in the left navigation with submenus, we give the parent > listing a link to a TOC page—e.g., [Prerequisites and Installation > Instructions|[https://geode.apache.org/docs/guide/19/prereq_and_install.html]]. > This isn't inherently bad (though it is somewhat redundant, as the left > navigation also serves this purpose), but when a user visits such a link, the > submenu on the left collapses. _Note:_ _The menu does not collapse when a > user visits a child link in the submenu of these items._ > ** Fix/Improvement: Wherever possible, remove the link from the subnav > parent item (leaving the now-unclickable parent item) and the related TOC > page. If the TOC page contains content beyond a TOC for the child pages, move > that content to an appropriate place within the existing child pages or, if > necessary, create a new page for it. For instance, the information above the > TOC in [Configuring and Running a > Cluster|[https://geode.apache.org/docs/guide/19/configuring/chapter_overview.html]] > could move to a new page at the top of that parent's submenu or, more > likely, to the Overview of the [Cluster Configuration > Service|[https://geode.apache.org/docs/guide/19/configuring/cluster_config/gfsh_persist.html]] > page. > # For left nav listings with submenus where all the pages link to anchors > within a page (instead of to topics on individual pages), Bookbinder provides > an option called "quicklinks" that automatically uses H2 (`##`) and smaller > subheads to create a small, in-page TOC at the top of the page. We currently > disable this functionality. > ** Fix/Improvement: Remove the "no-quicklinks" tags from anchors that we > want to appear in the in-page TOC. Also remove any duplicate links from the > left navigation. (In other words, the in-page TOC will now replace some > navigation functionality currently performed by the left nav, thereby > simplifying the left nav.) For example, see [Managing Heap and Off-heap > Memory|[https://geode.apache.org/docs/guide/19/managing/heap_use/heap_management.html]], > where many (but, notably, not all) of the child links in the left nav lead > to anchors within one page. These can become one new child page/link called > Managing Heap Memory, leaving only Resource Manager Example Configurations, > Managing Off-Heap Memory, and Locking Memory as child links alongside the new > one. The rest become in-page TOC anchor links in Managing Heap Memory. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Closed] (GEODE-7125) Simplify documentation navigation (remove left nav parent links; add in-page TOCs)
[ https://issues.apache.org/jira/browse/GEODE-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes closed GEODE-7125. -- > Simplify documentation navigation (remove left nav parent links; add in-page > TOCs) > -- > > Key: GEODE-7125 > URL: https://issues.apache.org/jira/browse/GEODE-7125 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Joey McAllister >Assignee: Dave Barnes >Priority: Minor > > The Geode user guide uses Bookbinder to create HTML documentation from > markdown files. This ticket is about changing two ways in which Geode > currently uses Bookbinder sub-optimally: > # For listings in the left navigation with submenus, we give the parent > listing a link to a TOC page—e.g., [Prerequisites and Installation > Instructions|[https://geode.apache.org/docs/guide/19/prereq_and_install.html]]. > This isn't inherently bad (though it is somewhat redundant, as the left > navigation also serves this purpose), but when a user visits such a link, the > submenu on the left collapses. _Note:_ _The menu does not collapse when a > user visits a child link in the submenu of these items._ > ** Fix/Improvement: Wherever possible, remove the link from the subnav > parent item (leaving the now-unclickable parent item) and the related TOC > page. If the TOC page contains content beyond a TOC for the child pages, move > that content to an appropriate place within the existing child pages or, if > necessary, create a new page for it. For instance, the information above the > TOC in [Configuring and Running a > Cluster|[https://geode.apache.org/docs/guide/19/configuring/chapter_overview.html]] > could move to a new page at the top of that parent's submenu or, more > likely, to the Overview of the [Cluster Configuration > Service|[https://geode.apache.org/docs/guide/19/configuring/cluster_config/gfsh_persist.html]] > page. > # For left nav listings with submenus where all the pages link to anchors > within a page (instead of to topics on individual pages), Bookbinder provides > an option called "quicklinks" that automatically uses H2 (`##`) and smaller > subheads to create a small, in-page TOC at the top of the page. We currently > disable this functionality. > ** Fix/Improvement: Remove the "no-quicklinks" tags from anchors that we > want to appear in the in-page TOC. Also remove any duplicate links from the > left navigation. (In other words, the in-page TOC will now replace some > navigation functionality currently performed by the left nav, thereby > simplifying the left nav.) For example, see [Managing Heap and Off-heap > Memory|[https://geode.apache.org/docs/guide/19/managing/heap_use/heap_management.html]], > where many (but, notably, not all) of the child links in the left nav lead > to anchors within one page. These can become one new child page/link called > Managing Heap Memory, leaving only Resource Manager Example Configurations, > Managing Off-Heap Memory, and Locking Memory as child links alongside the new > one. The rest become in-page TOC anchor links in Managing Heap Memory. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10385) User Guide: Remove bad G1 tuning advice
[ https://issues.apache.org/jira/browse/GEODE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10385. - Fix Version/s: 1.15.1 1.15.0 Resolution: Fixed > User Guide: Remove bad G1 tuning advice > --- > > Key: GEODE-10385 > URL: https://issues.apache.org/jira/browse/GEODE-10385 > 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.1, 1.15.0 > > > The "Managing Heap Memory" page provides some G1 tuning advice that is > actually detrimental to performance. The whole section needs some work, but > this passage, in particular, is wrong: > If you find the Apache Geode Resource Manager does not detect crossing the > eviction or critical threshold quickly enough, it has been observed that its > responsiveness is increased by reducing the default value of > --J-XX:MaxGCPauseMillis=VALUE JVM parameter (which is 200). Be sure to take > into account that this change also increases the amount of time spent in > garbage collection. > Cause: This advice was originally intended only to maximize performance of a > specific test case. It is NOT good advice for production systems. > https://geode.apache.org/docs/guide/114/managing/heap_use/heap_management.html > Short-term solution: delete the passage. > Long-term solution: Come up with some better ideas. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Closed] (GEODE-10385) User Guide: Remove bad G1 tuning advice
[ https://issues.apache.org/jira/browse/GEODE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes closed GEODE-10385. --- > User Guide: Remove bad G1 tuning advice > --- > > Key: GEODE-10385 > URL: https://issues.apache.org/jira/browse/GEODE-10385 > 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, 1.15.1 > > > The "Managing Heap Memory" page provides some G1 tuning advice that is > actually detrimental to performance. The whole section needs some work, but > this passage, in particular, is wrong: > If you find the Apache Geode Resource Manager does not detect crossing the > eviction or critical threshold quickly enough, it has been observed that its > responsiveness is increased by reducing the default value of > --J-XX:MaxGCPauseMillis=VALUE JVM parameter (which is 200). Be sure to take > into account that this change also increases the amount of time spent in > garbage collection. > Cause: This advice was originally intended only to maximize performance of a > specific test case. It is NOT good advice for production systems. > https://geode.apache.org/docs/guide/114/managing/heap_use/heap_management.html > Short-term solution: delete the passage. > Long-term solution: Come up with some better ideas. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10386) Document JDK 17 for 1.15 release
[ https://issues.apache.org/jira/browse/GEODE-10386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10386. - Fix Version/s: 1.15.0 1.15.1 Resolution: Fixed > Document JDK 17 for 1.15 release > > > Key: GEODE-10386 > URL: https://issues.apache.org/jira/browse/GEODE-10386 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.15.0 >Reporter: Dave Barnes >Assignee: Max Hufnagel >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0, 1.15.1 > > > Document JDK 17 for 1.5 release -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10389) Document upgrade to Geode 1.15 with SSL protocol workaround
[ https://issues.apache.org/jira/browse/GEODE-10389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10389. - Fix Version/s: 1.15.0 1.15.1 Resolution: Fixed > Document upgrade to Geode 1.15 with SSL protocol workaround > --- > > Key: GEODE-10389 > URL: https://issues.apache.org/jira/browse/GEODE-10389 > Project: Geode > Issue Type: Sub-task > Components: docs >Affects Versions: 1.15.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0, 1.15.1 > > > Document migration steps to mitigate protocol setting mismatch (GEODE-9991) > when upgrading to v1.5 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (GEODE-10389) Document upgrade to Geode 1.15 with SSL protocol workaround
[ https://issues.apache.org/jira/browse/GEODE-10389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-10389: --- Assignee: Dave Barnes > Document upgrade to Geode 1.15 with SSL protocol workaround > --- > > Key: GEODE-10389 > URL: https://issues.apache.org/jira/browse/GEODE-10389 > Project: Geode > Issue Type: Sub-task > Components: docs >Affects Versions: 1.15.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Document migration steps to mitigate protocol setting mismatch (GEODE-9991) > when upgrading to v1.5 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10390) User guide: update authentication expiry instructions
[ https://issues.apache.org/jira/browse/GEODE-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10390. - Fix Version/s: 1.15.0 1.15.1 Resolution: Fixed > User guide: update authentication expiry instructions > - > > Key: GEODE-10390 > URL: https://issues.apache.org/jira/browse/GEODE-10390 > Project: Geode > Issue Type: Improvement >Affects Versions: 1.15.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0, 1.15.1 > > > In "Implementing Authentication" indicate that "A SecurityManager > implementation that supports reauthentication using expiring credentials must > also support non-expiring credentials for cluster members” > In "Implementing Authentication Expiry", indicate that "Authentication expiry > is supported only with client connections." -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (GEODE-10390) User guide: update authentication expiry instructions
[ https://issues.apache.org/jira/browse/GEODE-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-10390: --- Assignee: Dave Barnes > User guide: update authentication expiry instructions > - > > Key: GEODE-10390 > URL: https://issues.apache.org/jira/browse/GEODE-10390 > Project: Geode > Issue Type: Improvement >Affects Versions: 1.15.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > In "Implementing Authentication" indicate that "A SecurityManager > implementation that supports reauthentication using expiring credentials must > also support non-expiring credentials for cluster members” > In "Implementing Authentication Expiry", indicate that "Authentication expiry > is supported only with client connections." -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10390) User guide: update authentication expiry instructions
Dave Barnes created GEODE-10390: --- Summary: User guide: update authentication expiry instructions Key: GEODE-10390 URL: https://issues.apache.org/jira/browse/GEODE-10390 Project: Geode Issue Type: Improvement Affects Versions: 1.15.0 Reporter: Dave Barnes In "Implementing Authentication" indicate that "A SecurityManager implementation that supports reauthentication using expiring credentials must also support non-expiring credentials for cluster members” In "Implementing Authentication Expiry", indicate that "Authentication expiry is supported only with client connections." -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10389) Document upgrade to Geode 1.15 with SSL protocol workaround
Dave Barnes created GEODE-10389: --- Summary: Document upgrade to Geode 1.15 with SSL protocol workaround Key: GEODE-10389 URL: https://issues.apache.org/jira/browse/GEODE-10389 Project: Geode Issue Type: Sub-task Components: docs Affects Versions: 1.15.0 Reporter: Dave Barnes Document migration steps to mitigate protocol setting mismatch (GEODE-9991) when upgrading to v1.5 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10386) Document JDK 17 for 1.15 release
Dave Barnes created GEODE-10386: --- Summary: Document JDK 17 for 1.15 release Key: GEODE-10386 URL: https://issues.apache.org/jira/browse/GEODE-10386 Project: Geode Issue Type: Improvement Components: docs Affects Versions: 1.15.0 Reporter: Dave Barnes Document JDK 17 for 1.5 release -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (GEODE-10386) Document JDK 17 for 1.15 release
[ https://issues.apache.org/jira/browse/GEODE-10386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-10386: --- Assignee: Max Hufnagel > Document JDK 17 for 1.15 release > > > Key: GEODE-10386 > URL: https://issues.apache.org/jira/browse/GEODE-10386 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.15.0 >Reporter: Dave Barnes >Assignee: Max Hufnagel >Priority: Major > > Document JDK 17 for 1.5 release -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (GEODE-10385) User Guide: Remove bad G1 tuning advice
[ https://issues.apache.org/jira/browse/GEODE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-10385: --- Assignee: Dave Barnes > User Guide: Remove bad G1 tuning advice > --- > > Key: GEODE-10385 > URL: https://issues.apache.org/jira/browse/GEODE-10385 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > The "Managing Heap Memory" page provides some G1 tuning advice that is > actually detrimental to performance. The whole section needs some work, but > this passage, in particular, is wrong: > If you find the Apache Geode Resource Manager does not detect crossing the > eviction or critical threshold quickly enough, it has been observed that its > responsiveness is increased by reducing the default value of > --J-XX:MaxGCPauseMillis=VALUE JVM parameter (which is 200). Be sure to take > into account that this change also increases the amount of time spent in > garbage collection. > Cause: This advice was originally intended only to maximize performance of a > specific test case. It is NOT good advice for production systems. > https://geode.apache.org/docs/guide/114/managing/heap_use/heap_management.html > Short-term solution: delete the passage. > Long-term solution: Come up with some better ideas. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10385) User Guide: Remove bad G1 tuning advice
Dave Barnes created GEODE-10385: --- Summary: User Guide: Remove bad G1 tuning advice Key: GEODE-10385 URL: https://issues.apache.org/jira/browse/GEODE-10385 Project: Geode Issue Type: Improvement Components: docs Affects Versions: 1.14.4 Reporter: Dave Barnes The "Managing Heap Memory" page provides some G1 tuning advice that is actually detrimental to performance. The whole section needs some work, but this passage, in particular, is wrong: If you find the Apache Geode Resource Manager does not detect crossing the eviction or critical threshold quickly enough, it has been observed that its responsiveness is increased by reducing the default value of --J-XX:MaxGCPauseMillis=VALUE JVM parameter (which is 200). Be sure to take into account that this change also increases the amount of time spent in garbage collection. Cause: This advice was originally intended only to maximize performance of a specific test case. It is NOT good advice for production systems. https://geode.apache.org/docs/guide/114/managing/heap_use/heap_management.html Short-term solution: delete the passage. Long-term solution: Come up with some better ideas. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10299) Creating Regions Dynamically Example in User's Guide is Broken
[ https://issues.apache.org/jira/browse/GEODE-10299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10299. - Fix Version/s: 1.14.5 1.15.0 1.16.0 Resolution: Fixed > Creating Regions Dynamically Example in User's Guide is Broken > -- > > Key: GEODE-10299 > URL: https://issues.apache.org/jira/browse/GEODE-10299 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Max Hufnagel >Assignee: Max Hufnagel >Priority: Major > Labels: pull-request-available > Fix For: 1.14.5, 1.15.0, 1.16.0 > > Attachments: CreateRegionCacheListener.java, CreateRegionFunction.java > > > The example on > [https://geode.apache.org/docs/guide/114/developing/region_options/dynamic_region_creation.html] > no longer works. The RegionAttributesImpl class was made not Serializable in > Geode 1.11 ([GEODE-7090|https://issues.apache.org/jira/browse/GEODE-7090]), > so instances can no longer be passed from the client to the server making > this function unusable from a client. > Barry Oglesby has created updated versions of the two classes (see attached). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10313) User Guide: Add javadocs template variable
[ https://issues.apache.org/jira/browse/GEODE-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10313. - Fix Version/s: 1.15.0 1.16.0 Resolution: Fixed > User Guide: Add javadocs template variable > -- > > Key: GEODE-10313 > URL: https://issues.apache.org/jira/browse/GEODE-10313 > 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, 1.16.0 > > > Improve User Guide publishing flexibility by incorporating a 'javadocs' > template variable in place of hard-coded path to the API docs. > Affected files: > geode-book/config.yml > geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb > geode-docs/developing/gemfire_data_serialization.html.md.erb > geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb > geode-docs/developing/events/implementing_write_behind_event_handler.html.md.erb > geode-docs/developing/function_exec/function_execution.html.md.erb > geode-docs/developing/query_additional/using_query_bind_parameters.html.md.erb > geode-docs/developing/query_index/maintaining_indexes.html.md.erb > geode-docs/developing/query_select/the_select_statement.html.md.erb > geode-docs/developing/querying_basics/querying_partitioned_regions.html.md.erb > geode-docs/developing/querying_basics/running_a_query.html.md.erb > geode-docs/getting_started/querying_quick_reference.html.md.erb -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (GEODE-10313) User Guide: Add javadocs template variable
[ https://issues.apache.org/jira/browse/GEODE-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-10313: --- Assignee: Dave Barnes > User Guide: Add javadocs template variable > -- > > Key: GEODE-10313 > URL: https://issues.apache.org/jira/browse/GEODE-10313 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > Improve User Guide publishing flexibility by incorporating a 'javadocs' > template variable in place of hard-coded path to the API docs. > Affected files: > geode-book/config.yml > geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb > geode-docs/developing/gemfire_data_serialization.html.md.erb > geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb > geode-docs/developing/events/implementing_write_behind_event_handler.html.md.erb > geode-docs/developing/function_exec/function_execution.html.md.erb > geode-docs/developing/query_additional/using_query_bind_parameters.html.md.erb > geode-docs/developing/query_index/maintaining_indexes.html.md.erb > geode-docs/developing/query_select/the_select_statement.html.md.erb > geode-docs/developing/querying_basics/querying_partitioned_regions.html.md.erb > geode-docs/developing/querying_basics/running_a_query.html.md.erb > geode-docs/getting_started/querying_quick_reference.html.md.erb -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10313) User Guide: Add javadocs template variable
Dave Barnes created GEODE-10313: --- Summary: User Guide: Add javadocs template variable Key: GEODE-10313 URL: https://issues.apache.org/jira/browse/GEODE-10313 Project: Geode Issue Type: Improvement Components: docs Affects Versions: 1.14.4 Reporter: Dave Barnes Improve User Guide publishing flexibility by incorporating a 'javadocs' template variable in place of hard-coded path to the API docs. Affected files: geode-book/config.yml geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb geode-docs/developing/gemfire_data_serialization.html.md.erb geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb geode-docs/developing/events/implementing_write_behind_event_handler.html.md.erb geode-docs/developing/function_exec/function_execution.html.md.erb geode-docs/developing/query_additional/using_query_bind_parameters.html.md.erb geode-docs/developing/query_index/maintaining_indexes.html.md.erb geode-docs/developing/query_select/the_select_statement.html.md.erb geode-docs/developing/querying_basics/querying_partitioned_regions.html.md.erb geode-docs/developing/querying_basics/running_a_query.html.md.erb geode-docs/getting_started/querying_quick_reference.html.md.erb -- 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] [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] [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=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] [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=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] [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] [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] [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] [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 describing region-attributes attributes. 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] [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-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] [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] [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] [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] [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] [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] [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] [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=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: 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] [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] [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] [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] [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] [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] [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-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-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] [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=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] [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] [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-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: 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.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] [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] [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] [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] [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] [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] [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=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] [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=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] [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=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: 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=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] [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] [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] [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] [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] [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=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] [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] [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] [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] [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] [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] [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-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] [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] [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] [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] [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] [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] [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-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] [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] [Resolved] (GEODE-9628) Documentation fix for setting credentials in a client
[
https://issues.apache.org/jira/browse/GEODE-9628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes resolved GEODE-9628.
Fix Version/s: 1.15.0
1.14.1
Resolution: Fixed
> Documentation fix for setting credentials in a client
> -
>
> Key: GEODE-9628
> URL: https://issues.apache.org/jira/browse/GEODE-9628
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Nabarun Nag
>Assignee: Dave Barnes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.1, 1.15.0
>
>
> Current:
> {noformat}
> How a Client Cache Sets Its CredentialIn order to connect with a locator or a
> server that does authentication, a client will need to set its credential,
> composed of the two properties security-username and security-password.
> Choose one of these two ways to accomplish this:{noformat}
> The last line needs to be changed to needing both the steps, instead of
> choosing one of the two steps
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9628) Documentation fix for setting credentials in a client
[
https://issues.apache.org/jira/browse/GEODE-9628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes reassigned GEODE-9628:
--
Assignee: Dave Barnes (was: Nabarun Nag)
> Documentation fix for setting credentials in a client
> -
>
> Key: GEODE-9628
> URL: https://issues.apache.org/jira/browse/GEODE-9628
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Nabarun Nag
>Assignee: Dave Barnes
>Priority: Major
> Labels: pull-request-available
>
> Current:
> {noformat}
> How a Client Cache Sets Its CredentialIn order to connect with a locator or a
> server that does authentication, a client will need to set its credential,
> composed of the two properties security-username and security-password.
> Choose one of these two ways to accomplish this:{noformat}
> The last line needs to be changed to needing both the steps, instead of
> choosing one of the two steps
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9568) Geode User Guide build script: allow doc to be retained
[ https://issues.apache.org/jira/browse/GEODE-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17422836#comment-17422836 ] Dave Barnes commented on GEODE-9568: Good work, [~alberto.bustamante.reyes]. I approved and merged your PR into the develop branch, and also cherry-picked it to the support/1.14 branch. > Geode User Guide build script: allow doc to be retained > --- > > Key: GEODE-9568 > URL: https://issues.apache.org/jira/browse/GEODE-9568 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > > The user guide build script allows the user to build and preview the user > guide. > When the script completes, it always deletes the user guide. > Allow the user to keep the compiled guide. > Relevant files: > dev-tools/docker/docs/preview-user-guide.sh > geode-book/README.md -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9656) User guide: Document Async disk writer exit behavior
Dave Barnes created GEODE-9656: -- Summary: 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 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] [Created] (GEODE-9652) Geode for Redis Rename - doc followup
Dave Barnes created GEODE-9652: -- Summary: Geode for Redis Rename - doc followup Key: GEODE-9652 URL: https://issues.apache.org/jira/browse/GEODE-9652 Project: Geode Issue Type: Sub-task Components: docs Affects Versions: 1.15.0 Reporter: Dave Barnes After GEODE-9567 has been completed, follow up in the user guide sources to tidy up doc loose ends. Task list (add to this if needed): - Verify that the "Experimental" modifier has been removed from all occurrences of Geode for Redis, as per GEODE-9566. - Move the Geode for Redis section entry in the left-hand navigation pane from "Developing..." to "Tools and Modules". Suggested location: following gfsh, before Gemcached. Check for affected references, for example in the Developing intro. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9611) Incorrect spelling
[
https://issues.apache.org/jira/browse/GEODE-9611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes resolved GEODE-9611.
Fix Version/s: 1.15.0
1.14.1
Resolution: Fixed
> Incorrect spelling
> --
>
> Key: GEODE-9611
> URL: https://issues.apache.org/jira/browse/GEODE-9611
> Project: Geode
> Issue Type: Improvement
> Components: configuration
>Affects Versions: 1.14.0
>Reporter: Deepak Khopade
>Assignee: Dave Barnes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.1, 1.15.0
>
>
> Incorrect spelling is found in the below error message that is getting
> printed in the logs. It should be.
> {code:java}
> parameterization{code}
> https://github.com/apache/geode/blob/a5bd36f9fa787d3a71c6e6efafed5a7b0fe52d2b/geode-core/src/main/java/org/apache/geode/internal/cache/xmlcache/CacheXmlPropertyResolver.java#L125
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9611) Incorrect spelling
[
https://issues.apache.org/jira/browse/GEODE-9611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419303#comment-17419303
]
Dave Barnes commented on GEODE-9611:
I merged the PR to develop and cherry-picked to support/1.14
> Incorrect spelling
> --
>
> Key: GEODE-9611
> URL: https://issues.apache.org/jira/browse/GEODE-9611
> Project: Geode
> Issue Type: Improvement
> Components: configuration
>Affects Versions: 1.14.0
>Reporter: Deepak Khopade
>Priority: Major
> Labels: pull-request-available
>
> Incorrect spelling is found in the below error message that is getting
> printed in the logs. It should be.
> {code:java}
> parameterization{code}
> https://github.com/apache/geode/blob/a5bd36f9fa787d3a71c6e6efafed5a7b0fe52d2b/geode-core/src/main/java/org/apache/geode/internal/cache/xmlcache/CacheXmlPropertyResolver.java#L125
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9611) Incorrect spelling
[
https://issues.apache.org/jira/browse/GEODE-9611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes reassigned GEODE-9611:
--
Assignee: Dave Barnes
> Incorrect spelling
> --
>
> Key: GEODE-9611
> URL: https://issues.apache.org/jira/browse/GEODE-9611
> Project: Geode
> Issue Type: Improvement
> Components: configuration
>Affects Versions: 1.14.0
>Reporter: Deepak Khopade
>Assignee: Dave Barnes
>Priority: Major
> Labels: pull-request-available
>
> Incorrect spelling is found in the below error message that is getting
> printed in the logs. It should be.
> {code:java}
> parameterization{code}
> https://github.com/apache/geode/blob/a5bd36f9fa787d3a71c6e6efafed5a7b0fe52d2b/geode-core/src/main/java/org/apache/geode/internal/cache/xmlcache/CacheXmlPropertyResolver.java#L125
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9619) README.md (top level) - fix format problems
[ https://issues.apache.org/jira/browse/GEODE-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-9619. Fix Version/s: 1.15.0 1.14.1 Resolution: Fixed > README.md (top level) - fix format problems > --- > > Key: GEODE-9619 > URL: https://issues.apache.org/jira/browse/GEODE-9619 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > Labels: pull-request-available > Fix For: 1.14.1, 1.15.0 > > > Community member Kaustubh Maske Patil notes that the top-level Geode > README.md file contains a numbered list in which items 9 and 10 appear on a > single line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9619) README.md (top level) - fix format problems
[ https://issues.apache.org/jira/browse/GEODE-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418739#comment-17418739 ] Dave Barnes commented on GEODE-9619: [~nikochiko] Thank you for your contribution. Your pull-request (including a typo fix by another community member) has been merged into the codebase for the develop branch. I will propagate the change to the v1.14 branch before closing this ticket. In response to your earlier comment: To request eligibility for JIRA ticket assignment, please send a request to the project mailing list, d...@geode.apache.org. > README.md (top level) - fix format problems > --- > > Key: GEODE-9619 > URL: https://issues.apache.org/jira/browse/GEODE-9619 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > Labels: pull-request-available > > Community member Kaustubh Maske Patil notes that the top-level Geode > README.md file contains a numbered list in which items 9 and 10 appear on a > single line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9619) README.md (top level) - fix format problems
[ https://issues.apache.org/jira/browse/GEODE-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-9619: --- Priority: Minor (was: Major) > README.md (top level) - fix format problems > --- > > Key: GEODE-9619 > URL: https://issues.apache.org/jira/browse/GEODE-9619 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > Community member Kaustubh Maske Patil notes that the top-level Geode > README.md file contains a numbered list in which items 9 and 10 appear on a > single line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9619) README.md (top level) - fix format problems
[ https://issues.apache.org/jira/browse/GEODE-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418253#comment-17418253 ] Dave Barnes commented on GEODE-9619: Reporting community member K M Patil submitted a PR to address this issue: https://github.com/apache/geode/pull/6888#pullrequestreview-760068904 > README.md (top level) - fix format problems > --- > > Key: GEODE-9619 > URL: https://issues.apache.org/jira/browse/GEODE-9619 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > Community member Kaustubh Maske Patil notes that the top-level Geode > README.md file contains a numbered list in which items 9 and 10 appear on a > single line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9619) README.md (top level) - fix format problems
[ https://issues.apache.org/jira/browse/GEODE-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9619: -- Assignee: Dave Barnes > README.md (top level) - fix format problems > --- > > Key: GEODE-9619 > URL: https://issues.apache.org/jira/browse/GEODE-9619 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.0 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > Community member Kaustubh Maske Patil notes that the top-level Geode > README.md file contains a numbered list in which items 9 and 10 appear on a > single line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
