[geode] branch support/1.15 updated: GEODE-10385: User Guide - Remove bad G1GC tuning advice (#7815)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new 8cc780a557 GEODE-10385: User Guide - Remove bad G1GC tuning advice (#7815) 8cc780a557 is described below commit 8cc780a557ad9052a27c12de00e18ac0bdf1016c Author: Dave Barnes AuthorDate: Thu Jun 23 09:59:03 2022 -0700 GEODE-10385: User Guide - Remove bad G1GC tuning advice (#7815) --- geode-docs/managing/heap_use/heap_management.html.md.erb | 1 - 1 file changed, 1 deletion(-) diff --git a/geode-docs/managing/heap_use/heap_management.html.md.erb b/geode-docs/managing/heap_use/heap_management.html.md.erb index 682d7113e9..b138716574 100644 --- a/geode-docs/managing/heap_use/heap_management.html.md.erb +++ b/geode-docs/managing/heap_use/heap_management.html.md.erb @@ -153,7 +153,6 @@ $ gfsh start server --name=app.MyApplication --initial-heap=30m --max-heap=30m \ Although the garbage first (G1) garbage collector works effectively with <%=vars.product_name_long%>, issues can arise in some cases due to the differences between CMS and G1. For example, G1 by design is not able to set a maximum tenured heap size, so when this value is requested from the garbage collector, it reports the total heap maximum size. This impacts <%=vars.product_name_long%>, as the resource manager uses the maximum size of the tenured heap size to calculate the value in bytes of the eviction and critical percentages. Extensive testing is recommended before using G1 garbage collector. See your JVM documentation for all JVM-specific settings that can be used to improve garbage collection (GC) response. -If you find the <%=vars.product_name_long%> 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. Size of objects stored on a region must also be taken into account. If the primary heap objects you allocate are larger than 50 percent of the G1 region size (what are called "humongous" objects), this can cause the JVM to report `out of heap memory` when it has used only 50 percent of the heap. The default G1 region size is 1 Mb; it can be increased up to 32 Mb (with values that are always a power of 2) by using the `--J-XX:G1HeapRegionSize=VALUE` JVM parameter. If you are using large objects and want to use G1GC without increasing its heap region size (or if your values are larger than 16 Mb), then you could configure your <%=vars.product_name_long%> regions to store the large values off-heap. However, even if you do that the large off-heap values will allocate large temporary [...]
[geode] branch develop updated: GEODE-10385: User Guide - Remove bad G1GC tuning advice (#7815)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/develop by this push: new ac92c6fdab GEODE-10385: User Guide - Remove bad G1GC tuning advice (#7815) ac92c6fdab is described below commit ac92c6fdabd96182a1e02a5574f1ef5faf7c2410 Author: Dave Barnes AuthorDate: Thu Jun 23 09:59:03 2022 -0700 GEODE-10385: User Guide - Remove bad G1GC tuning advice (#7815) --- geode-docs/managing/heap_use/heap_management.html.md.erb | 1 - 1 file changed, 1 deletion(-) diff --git a/geode-docs/managing/heap_use/heap_management.html.md.erb b/geode-docs/managing/heap_use/heap_management.html.md.erb index 682d7113e9..b138716574 100644 --- a/geode-docs/managing/heap_use/heap_management.html.md.erb +++ b/geode-docs/managing/heap_use/heap_management.html.md.erb @@ -153,7 +153,6 @@ $ gfsh start server --name=app.MyApplication --initial-heap=30m --max-heap=30m \ Although the garbage first (G1) garbage collector works effectively with <%=vars.product_name_long%>, issues can arise in some cases due to the differences between CMS and G1. For example, G1 by design is not able to set a maximum tenured heap size, so when this value is requested from the garbage collector, it reports the total heap maximum size. This impacts <%=vars.product_name_long%>, as the resource manager uses the maximum size of the tenured heap size to calculate the value in bytes of the eviction and critical percentages. Extensive testing is recommended before using G1 garbage collector. See your JVM documentation for all JVM-specific settings that can be used to improve garbage collection (GC) response. -If you find the <%=vars.product_name_long%> 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. Size of objects stored on a region must also be taken into account. If the primary heap objects you allocate are larger than 50 percent of the G1 region size (what are called "humongous" objects), this can cause the JVM to report `out of heap memory` when it has used only 50 percent of the heap. The default G1 region size is 1 Mb; it can be increased up to 32 Mb (with values that are always a power of 2) by using the `--J-XX:G1HeapRegionSize=VALUE` JVM parameter. If you are using large objects and want to use G1GC without increasing its heap region size (or if your values are larger than 16 Mb), then you could configure your <%=vars.product_name_long%> regions to store the large values off-heap. However, even if you do that the large off-heap values will allocate large temporary [...]
[geode-site] branch master updated: Update for 1.15.0 release
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/geode-site.git The following commit(s) were added to refs/heads/master by this push: new a7cb69d1 Update for 1.15.0 release a7cb69d1 is described below commit a7cb69d1ddf9d19812428d708b9db268a0944428 Author: Dave Barnes AuthorDate: Tue Jun 21 11:22:37 2022 -0700 Update for 1.15.0 release --- website/content/docs/index.html | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/website/content/docs/index.html b/website/content/docs/index.html index 21b2df9a..b77cfab9 100644 --- a/website/content/docs/index.html +++ b/website/content/docs/index.html @@ -44,7 +44,10 @@ under the License. --> Apache Geode 1.14 User Guide - Apache Geode 1.13 User Guide + Apache Geode Native .NET Client 1.15 Guide + + + Apache Geode Native C++ Client 1.15 Guide Apache Geode Native .NET Client 1.14 Guide
[geode-site] branch master updated: Update for 1.15.0 release
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/geode-site.git The following commit(s) were added to refs/heads/master by this push: new a319482a Update for 1.15.0 release a319482a is described below commit a319482af07ff81b271c9c0b9f3fd10478471f45 Author: Dave Barnes AuthorDate: Tue Jun 21 11:22:37 2022 -0700 Update for 1.15.0 release --- website/content/docs/index.html | 12 ++--- website/content/index.html | 4 +- website/content/releases/index.html | 96 ++--- 3 files changed, 53 insertions(+), 59 deletions(-) diff --git a/website/content/docs/index.html b/website/content/docs/index.html index 5551149c..21b2df9a 100644 --- a/website/content/docs/index.html +++ b/website/content/docs/index.html @@ -38,13 +38,13 @@ under the License. --> - Apache Geode 1.14 User Guide + Apache Geode 1.15 User Guide - Apache Geode 1.13 User Guide + Apache Geode 1.14 User Guide - Apache Geode 1.12 User Guide + Apache Geode 1.13 User Guide Apache Geode Native .NET Client 1.14 Guide @@ -58,12 +58,6 @@ under the License. --> Apache Geode Native C++ Client 1.13 Guide - - Apache Geode Native .NET Client 1.12 Guide - - - Apache Geode Native C++ Client 1.12 Guide - diff --git a/website/content/index.html b/website/content/index.html index 48cb81cf..5e9f742d 100644 --- a/website/content/index.html +++ b/website/content/index.html @@ -113,7 +113,7 @@ under the License. --> Clients - Clients are available for Java, C++, and C# .NET. A REST API is available for all other languages. + Clients are available for Java, C++, and C# .NET Framework. A REST API is available for all other languages. @@ -123,7 +123,7 @@ under the License. --> Adapters - Geode can be used as a drop-in replacement for Redis and memcached, allowing users of these caches to use Geode's server-side features like multi-cluster replication. + Geode can be used as a drop-in replacement for memcached, allowing use of Geode's server-side features like multi-cluster replication. diff --git a/website/content/releases/index.html b/website/content/releases/index.html index b094097f..9dc57ae2 100644 --- a/website/content/releases/index.html +++ b/website/content/releases/index.html @@ -34,39 +34,39 @@ under the License. --> - -1.14.4 + +1.15.0 -https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.14.4;>Release Notes +https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.15.0;>Release Notes Binaries - [https://apache.org/dyn/closer.cgi/geode/1.14.4/apache-geode-1.14.4.tgz;>TGZ, https://downloads.apache.org/geode/1.14.4/apache-geode-1.14.4.tgz.sha256;>SHA-256, - https://downloads.apache.org/geode/1.14.4/apache-geode-1.14.4.tgz.asc;>PGP ] + [https://apache.org/dyn/closer.cgi/geode/1.15.0/apache-geode-1.15.0.tgz;>TGZ, https://downloads.apache.org/geode/1.15.0/apache-geode-1.15.0.tgz.sha256;>SHA-256, + https://downloads.apache.org/geode/1.15.0/apache-geode-1.15.0.tgz.asc;>PGP ] Source - [https://apache.org/dyn/closer.cgi/geode/1.14.4/apache-geode-1.14.4-src.tgz;>TGZ, https://downloads.apache.org/geode/1.14.4/apache-geode-1.14.4-src.tgz.sha256;>SHA-256, - https://downloads.apache.org/geode/1.14.4/apache-geode-1.14.4-src.tgz.asc;>PGP + [https://apache.org/dyn/closer.cgi/geode/1.15.0/apache-geode-1.15.0-src.tgz;>TGZ, https://downloads.apache.org/geode/1.15.0/apache-geode-1.15.0-src.tgz.sha256;>SHA-256, + https://downloads.apache.org/geode/1.15.0/apache-geode-1.15.0-src.tgz.asc;>PGP ] Geode Native Source - [https://apache.org/dyn/closer.cgi/geode/1.14.4/apache-geode-native-1.14.4-src.tgz;>TGZ, https://downloads.apache.org/geode/1.14.4/apache-geode-native-1.14.4-src.tgz.sha256;>SHA-256, - https://downloads.apache.org/geode/1.14.4/apache-geode-native-1.14.4
[geode] branch support/1.15 updated: GEODE-10386:Document JDK 17 for 1.15 release (#7813)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new ab5e533494 GEODE-10386:Document JDK 17 for 1.15 release (#7813) ab5e533494 is described below commit ab5e533494787922a22d278ae01d87c1d031e212 Author: Dave Barnes AuthorDate: Fri Jun 17 13:34:44 2022 -0700 GEODE-10386:Document JDK 17 for 1.15 release (#7813) Co-authored by: @animatedmax --- .../source/subnavs/geode-subnav.erb| 3 + .../system_requirements/host_machine.html.md.erb | 2 +- .../system_requirements/java_support.html.md.erb | 151 + 3 files changed, 155 insertions(+), 1 deletion(-) diff --git a/geode-book/master_middleman/source/subnavs/geode-subnav.erb b/geode-book/master_middleman/source/subnavs/geode-subnav.erb index 8f1b3566da..018b6213fb 100644 --- a/geode-book/master_middleman/source/subnavs/geode-subnav.erb +++ b/geode-book/master_middleman/source/subnavs/geode-subnav.erb @@ -38,6 +38,9 @@ limitations under the License. Host Machine Requirements + +Java Support + How to Install diff --git a/geode-docs/getting_started/system_requirements/host_machine.html.md.erb b/geode-docs/getting_started/system_requirements/host_machine.html.md.erb index e3b5b95458..51d4e86689 100644 --- a/geode-docs/getting_started/system_requirements/host_machine.html.md.erb +++ b/geode-docs/getting_started/system_requirements/host_machine.html.md.erb @@ -24,7 +24,7 @@ Host machines must meet a set of requirements for <%=vars.product_name_long%>. Each machine that will run <%=vars.product_name_long%> must meet the following requirements: -- Java SE Development Kit <%=vars.min_java_version%> with update <%=vars.min_java_update%> or a more recent version <%=vars.min_java_version%> update. The same versions are supported with OpenJDK. +- Java SE Development Kit <%=vars.min_java_version%> with update <%=vars.min_java_update%> or a more recent version <%=vars.min_java_version%> update. The same versions are supported with OpenJDK. See [Java Support](java_support.html) for details. - A system clock set to the correct time and a time synchronization service such as Network Time Protocol (NTP). Correct time stamps permit the following activities: - Logs that are useful for troubleshooting. Synchronized time stamps ensure that log messages from different hosts can be merged to reproduce an accurate chronological history of a distributed run. - Aggregate product-level and application-level time statistics. diff --git a/geode-docs/getting_started/system_requirements/java_support.html.md.erb b/geode-docs/getting_started/system_requirements/java_support.html.md.erb new file mode 100644 index 00..4bb44a4063 --- /dev/null +++ b/geode-docs/getting_started/system_requirements/java_support.html.md.erb @@ -0,0 +1,151 @@ +--- +title: Java Support +--- + + + +This version of <%=vars.product_name%> requires Java 8 release <%=vars.min_java_update %> or +a more recent version 8 update. The same versions are supported with OpenJDK (HotSpot). + +<%=vars.product_name%> is also compatible with Open JDK 11 and JDK 17. + +The <%=vars.product_name%> product download does not include Java. +Download and install a supported JRE or JDK on each system running <%=vars.product_name%>. +VMware recommends the installation of a full JDK (and not just a JRE) +to obtain better performance with `gfsh status` and `gfsh stop` commands. + +The IBM SDK, Java Technology Edition, Version 8 is supported for application clients only. Some +client region eviction configurations such as `HEAP_LRU` are known to not function properly with +this SDK. + +## Java Modules and <%=vars.product_name%> + +### How JDK 17 Encapsulation Affects <%=vars.product_name%> + +Beginning with Java 17, the JVM strongly enforces the encapsulation policies introduced in Java 9 by the Java Platform Module System. + +Several <%=vars.product_name%> features, such as serialization and eviction, use deep reflection to inspect the Java objects used as keys and values. In Java 17, this deep reflection requires that the object's type be made explicitly available for reflection. + +By default, each type declared in a named module is available for reflection only if the declaring module opens the type's package. + +As a result, <%=vars.product_name%>, by default, cannot inspect the following encapsulated types and fields: +- The private and pro
[geode] branch support/1.15 updated: GEODE-10389: Document upgrade to Geode 1.15 with SSL protocol workaround (#7812)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new ececd27a03 GEODE-10389: Document upgrade to Geode 1.15 with SSL protocol workaround (#7812) ececd27a03 is described below commit ececd27a039dc7dd1eb836d09532995782486869 Author: Dave Barnes AuthorDate: Fri Jun 17 11:59:07 2022 -0700 GEODE-10389: Document upgrade to Geode 1.15 with SSL protocol workaround (#7812) --- .../upgrade/upgrade_overview.html.md.erb | 50 ++ 1 file changed, 50 insertions(+) diff --git a/geode-docs/getting_started/upgrade/upgrade_overview.html.md.erb b/geode-docs/getting_started/upgrade/upgrade_overview.html.md.erb index cfecad3fac..899da9bc5f 100644 --- a/geode-docs/getting_started/upgrade/upgrade_overview.html.md.erb +++ b/geode-docs/getting_started/upgrade/upgrade_overview.html.md.erb @@ -54,3 +54,53 @@ you will need to accomplish the upgrade. Then select the appropriate upgrade pro - **[Upgrading Clients](upgrade_clients.html)** +When you upgrade your <%=vars.product_name%> server software, you may need to update your client +applications in order to maintain compatibility with the upgraded servers. + +## Upgrading to v1.15 + +For some users, issues regarding SSL protocols and their default values require a preparatory SSL protocol migration step when upgrading to <%=vars.product_name%> v1.15. +Please read the following section carefully to determine whether your system requires this additional SSL protocol migration step. + +### Does my System Require SSL Protocol Migration Before Upgrading to <%=vars.product_name%> v1.15? + +To determine whether your system requires the SSL protocol migration preparatory step, see if your system meets both of the following conditions: + +- If `ssl-endpoint-identification-enabled` is set to `true` AND +- If `ssl-protocols` is set to a value other than "any", that is, it specifies a list of specific protocols, but does not include "SSLv2Hello", + +THEN your system requires the SSL protocol migration step. + +**How do I determine my system's settings for the `ssl-endpoint-identification-enabled` and `ssl-protocols` properties?** + +SSL properties may be set in properties files or on the gfsh command line. To determine the settings for these parameters, + +- Check `gemfire.properties` and `gfsecurity.properties` for +`ssl-endpoint-identification-enabled=true`. Also look for `ssl-use-default-context=true`, which sets +`ssl-endpoint-identification-enabled=true`. + +- Search system logs for these properties (using `grep`, for example). + +## Preparatory SSL Protocol Migration + +The preparatory SSL protocol migration process consists of replacing one property, `ssl-protocols`, +with two new properties, `ssl-client-protocols` and `ssl-server-protocols`, then removing the old +`ssl-protocols` definition. Perform this substitution in whatever way the original `ssl-protocols` +were defined: in `.properties` files or on a command line. + +1. If your system is running JDK 8, upgrade to the latest version of JDK 8 before proceeding. This is necessary, even if you plan to +perform the optional JDK upgrade step to JDK 11 or JDK 17. +1. Shutdown a member (server or locator). +2. Install <%=vars.product_name%> 1.15. +3. Optionally install a new Java JDK. +4. Add security property `ssl-client-protocols` with the same definition as the old `ssl-protocols` property. +5. Add security property `ssl-server-protocols` with the same definition as the old `ssl-protocols` property PLUS "SSLv2Hello". +For example, if the original value of `ssl-protocols` is "TLSv1.2", then define +- `ssl-client-protocols="TLSv1.2"` +- `ssl-server-protocols="TLSv1.2,SSLv2Hello"` +6. Start the member. +7. Verify successful cluster join. +8. Repeat from step 1 for the next member. + +Optionally, after your upgrade is complete, you may restore your original `ssl-protocols` property +and restart all your members to eliminate the `SSLv2Hello` protocol support.
[geode] branch support/1.15 updated: GEODE-10390: User guide: update authentication expiry instructions (#7809)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new 81ae2db3e5 GEODE-10390: User guide: update authentication expiry instructions (#7809) 81ae2db3e5 is described below commit 81ae2db3e54f093cb7d0bbcc6d462d4cf6141873 Author: Dave Barnes AuthorDate: Thu Jun 16 16:37:15 2022 -0700 GEODE-10390: User guide: update authentication expiry instructions (#7809) --- .../implementing_authentication.html.md.erb| 1 + .../implementing_authentication_expiry.html.md.erb | 22 +- 2 files changed, 10 insertions(+), 13 deletions(-) diff --git a/geode-docs/managing/security/implementing_authentication.html.md.erb b/geode-docs/managing/security/implementing_authentication.html.md.erb index a79e5d14c6..972ed9d57a 100644 --- a/geode-docs/managing/security/implementing_authentication.html.md.erb +++ b/geode-docs/managing/security/implementing_authentication.html.md.erb @@ -36,6 +36,7 @@ which is discussed in detail in the [authorization](authorization_overview.html) In case of an `AuthenticationExpiredException` the <%=vars.product_name%> client code will make one automatic attempt to re-connect to the member that sent the exception. +A `SecurityManager` implementation that supports reauthentication using expiring credentials must also support non-expiring credentials for cluster members. A well-designed `authenticate` method will have a set of known credentials, such as user and password pairs, that can be compared to the credentials presented or will have a way of obtaining those credentials. diff --git a/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb b/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb index b535f1afac..d6f5131249 100644 --- a/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb +++ b/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb @@ -19,15 +19,17 @@ See the License for the specific language governing permissions and limitations under the License. --> +Authentication expiry is supported only with client connections. +The use of expirable credentials is most common when used in combination with token-based authentication and authorization. Authentication expiry makes it possible for cluster administrators to limit the life span of client -and peer connections within the cluster. The use of expirable credentials is most common when used in -combination with token based authentication and authorization. +connections within the cluster. -Client connections are notified of expiry through `AuthenticationExpiredException`, +Client connections are notified of expiry by `AuthenticationExpiredException`, which is thrown in the implementations of `SecurityManager.authenticate` or `SecurityManager.authorize`. -Clients will do one automatic attempt to reconnect. Upon receiving a second `AuthenticationExpiredException` -the exception will be propagated up the chain for the user to handle. There are some differences in +Upon receiving the AuthenticationExpiredException, clients will make one automatic attempt to gather new credentials and reconnect (AuthInitialize.getCredentials()). +Upon receiving a second `AuthenticationExpiredException` +the exception is thrown back to the user to handle. There are some differences in behavior between older and newer clients. **Support for AutomaticReconnect** @@ -56,15 +58,9 @@ The common cycle for authentication and authorization is the following: AuthInitialize.getCredentials(...) -> SecurityManager.authenticate(...) -> SecurityManager.authorize(...) ``` -Where `AuthInitialize.getCredentials()` provides the `security properties` for `SecurityManager.authenticate()` -which in turn provides the `principal object` for `SecurityManager.authorize()`. It's important to -understand that some time will pass between the `AuthInitialize.getCredentials()` call and the -`SecurityManager.authorize()` call. The specific amount of time depends on the implementation and -runtime environment details. - In case of the use of an external token provider we assume that this token provider will be asked for -a token in the `AuthInitialize.getCredentials()` call. A token provider can return existing tokens for -a given user so it is recommended that implementers of the `AuthInitialize` and `SecurityManager` +a token in the `AuthInitialize.getCredentials()` call. A token provider can return existing tokens (which are about to expire) for +a given user, so it is recommended that implementers of the `AuthInitialize` and `SecurityManager` interfaces take imminent timeout and token refresh in consideration to avoid receiving multiple unintended `AuthenticationExpiredExcep
[geode] branch support/1.15 updated: Disabling->Disable
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new 08a32920b0 Disabling->Disable 08a32920b0 is described below commit 08a32920b033b965c698d7fdd5100504f2494191 Author: Dave Barnes AuthorDate: Wed Jun 15 16:42:46 2022 -0700 Disabling->Disable --- geode-docs/managing/monitor_tune/chapter_overview.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb b/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb index af2c485717..9e63eade3f 100644 --- a/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb +++ b/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb @@ -21,7 +21,7 @@ limitations under the License. A collection of tools and controls allow you to monitor and adjust <%=vars.product_name_long%> performance. -- **[Disabling TCP SYN Cookies](disabling_tcp_syn_cookies.html)** +- **[Disable TCP SYN Cookies](disabling_tcp_syn_cookies.html)** This is a must-do for Linux systems.
[geode] 01/02: Incorporated reviewer suggestions
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git commit c4ed0fcc7ebfa95cf1fdd5816eac40723ef32784 Author: Dave Barnes AuthorDate: Wed Jun 15 16:26:12 2022 -0700 Incorporated reviewer suggestions --- .../managing/security/implementing_authentication_expiry.html.md.erb| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb b/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb index 200ce3e87e..b535f1afac 100644 --- a/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb +++ b/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb @@ -23,7 +23,7 @@ Authentication expiry makes it possible for cluster administrators to limit the and peer connections within the cluster. The use of expirable credentials is most common when used in combination with token based authentication and authorization. -Client connections are notified of expiry through the throwing of an `AuthenticationExpiredException` +Client connections are notified of expiry through `AuthenticationExpiredException`, which is thrown in the implementations of `SecurityManager.authenticate` or `SecurityManager.authorize`. Clients will do one automatic attempt to reconnect. Upon receiving a second `AuthenticationExpiredException`
[geode] 02/02: Correct name of Disable SYN Cookies in TOC and cross-ref
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git commit ed86d71c0e395767ab8ca2bbbf41c224219feab1 Author: Dave Barnes AuthorDate: Wed Jun 15 16:28:58 2022 -0700 Correct name of Disable SYN Cookies in TOC and cross-ref --- geode-book/master_middleman/source/subnavs/geode-subnav.erb | 2 +- geode-docs/getting_started/system_requirements/host_machine.html.md.erb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/geode-book/master_middleman/source/subnavs/geode-subnav.erb b/geode-book/master_middleman/source/subnavs/geode-subnav.erb index c88b7fd9b4..8f1b3566da 100644 --- a/geode-book/master_middleman/source/subnavs/geode-subnav.erb +++ b/geode-book/master_middleman/source/subnavs/geode-subnav.erb @@ -672,7 +672,7 @@ limitations under the License. Performance Tuning and Configuration -Disabling TCP SYN Cookies +Disable TCP SYN Cookies Improving Performance on vSphere diff --git a/geode-docs/getting_started/system_requirements/host_machine.html.md.erb b/geode-docs/getting_started/system_requirements/host_machine.html.md.erb index 9ce558d4f3..e3b5b95458 100644 --- a/geode-docs/getting_started/system_requirements/host_machine.html.md.erb +++ b/geode-docs/getting_started/system_requirements/host_machine.html.md.erb @@ -49,4 +49,4 @@ server clusters behind advanced firewall protection. sysctl -p ``` -See [Disabling TCP SYN Cookies](../../managing/monitor_tune/disabling_tcp_syn_cookies.html) for details. +See [Disable TCP SYN Cookies](../../managing/monitor_tune/disabling_tcp_syn_cookies.html) for details.
[geode] branch support/1.15 updated (d72711fcea -> ed86d71c0e)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git from d72711fcea (no JIRA ticket) user guide Security section: Typo & format fixes (#7802) new c4ed0fcc7e Incorporated reviewer suggestions new ed86d71c0e Correct name of Disable SYN Cookies in TOC and cross-ref The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: geode-book/master_middleman/source/subnavs/geode-subnav.erb | 2 +- geode-docs/getting_started/system_requirements/host_machine.html.md.erb | 2 +- .../managing/security/implementing_authentication_expiry.html.md.erb| 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
[geode] branch support/1.15 updated: (no JIRA ticket) user guide Security section: Typo & format fixes (#7802)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new d72711fcea (no JIRA ticket) user guide Security section: Typo & format fixes (#7802) d72711fcea is described below commit d72711fceaab63e097ace0f1a3595d23c6c40eea Author: Dave Barnes AuthorDate: Wed Jun 15 14:07:00 2022 -0700 (no JIRA ticket) user guide Security section: Typo & format fixes (#7802) --- .../implementing_authentication_expiry.html.md.erb | 2 +- .../managing/security/implementing_ssl.html.md.erb | 92 +++--- 2 files changed, 47 insertions(+), 47 deletions(-) diff --git a/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb b/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb index 25f59e946a..200ce3e87e 100644 --- a/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb +++ b/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb @@ -48,7 +48,7 @@ is one of the following types where the exception will always be propagated up t * multi-user client mode * event-dispatching (CQ and registered interest) -## Authentication Expiry Considerations +## Authentication Expiry Considerations The common cycle for authentication and authorization is the following: diff --git a/geode-docs/managing/security/implementing_ssl.html.md.erb b/geode-docs/managing/security/implementing_ssl.html.md.erb index d43142344b..8f797e9ab0 100644 --- a/geode-docs/managing/security/implementing_ssl.html.md.erb +++ b/geode-docs/managing/security/implementing_ssl.html.md.erb @@ -32,32 +32,32 @@ You can specify that SSL be used system-wide, or you can independently configure system components. The following list shows the system components that can be separately configured to communicate using SSL, and the kind of communications to which each component name refers: -**cluster** -Peer-to-peer communications among members of a cluster +**cluster** +:Peer-to-peer communications among members of a cluster -**gateway** -Communication across WAN gateways from one site to another +**gateway** +:Communication across WAN gateways from one site to another -**web** -All web-based services hosted on the configured server, which can include the Developer REST API +**web** +:All web-based services hosted on the configured server, which can include the Developer REST API service, the Management REST API service (used for remote cluster management) and the Pulse -monitoring tool's web-based user interface. +monitoring tool's web-based user interface. -**jmx** -Java management extension communications, including communications with the `gfsh` utility. +**jmx** +:Java management extension communications, including communications with the `gfsh` utility. The Pulse monitoring tool uses JMX for server-side communication with a locator, but SSL applies to this connection only if Pulse is located on an app server separate from the locator. When Pulse and the locator are colocated, JMX communication between the two does not -involve a TCP connection, so SSL does not apply. +involve a TCP connection, so SSL does not apply. -**locator** -Communication with and between locators +**locator** +:Communication with and between locators -**server** -Communication between clients and servers +**server** +:Communication between clients and servers -**all** -All of the above (use SSL system-wide) +**all** +:All of the above (use SSL system-wide) Specifying that a component is enabled for SSL applies to the component's server-socket side and its client-socket side. For example, if you enable SSL for locators, then any process that communicates @@ -68,55 +68,55 @@ with a locator must also have SSL enabled. If you provide "" as the value, SSL You can use <%=vars.product_name%> configuration properties to enable or disable SSL, to identify SSL ciphers and protocols, and to provide the location and credentials for key and trust stores. -**ssl-enabled-components** -List of components for which to enable SSL. Component list can be "" (disable SSL), "all", or a comma-separated list of components. +**ssl-enabled-components** +:List of components for which to enable SSL. Component list can be "" (disable SSL), "all", or a comma-separated list of components. -**ssl-endpoint-identification-enabled** -A boolean value that, when set to true, causes clients to validate the server's hostname using the server's certificate. +**ssl-endpoint-identification-enabled** +:A boolean value that, when set to true, causes clients to validate the server's hostname using the server's certificate. The default value is false. -Enabling endpoint i
[geode] branch develop updated: (no JIRA ticket) user guide Security section: Typo & format fixes (#7802)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/develop by this push: new 4c6e94af7c (no JIRA ticket) user guide Security section: Typo & format fixes (#7802) 4c6e94af7c is described below commit 4c6e94af7cb91b3c146618b5f6882c565e5881bb Author: Dave Barnes AuthorDate: Wed Jun 15 14:07:00 2022 -0700 (no JIRA ticket) user guide Security section: Typo & format fixes (#7802) --- .../implementing_authentication_expiry.html.md.erb | 2 +- .../managing/security/implementing_ssl.html.md.erb | 94 +++--- 2 files changed, 48 insertions(+), 48 deletions(-) diff --git a/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb b/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb index 25f59e946a..200ce3e87e 100644 --- a/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb +++ b/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb @@ -48,7 +48,7 @@ is one of the following types where the exception will always be propagated up t * multi-user client mode * event-dispatching (CQ and registered interest) -## Authentication Expiry Considerations +## Authentication Expiry Considerations The common cycle for authentication and authorization is the following: diff --git a/geode-docs/managing/security/implementing_ssl.html.md.erb b/geode-docs/managing/security/implementing_ssl.html.md.erb index 8516e58296..8f797e9ab0 100644 --- a/geode-docs/managing/security/implementing_ssl.html.md.erb +++ b/geode-docs/managing/security/implementing_ssl.html.md.erb @@ -32,32 +32,32 @@ You can specify that SSL be used system-wide, or you can independently configure system components. The following list shows the system components that can be separately configured to communicate using SSL, and the kind of communications to which each component name refers: -**cluster** -Peer-to-peer communications among members of a cluster +**cluster** +:Peer-to-peer communications among members of a cluster -**gateway** -Communication across WAN gateways from one site to another +**gateway** +:Communication across WAN gateways from one site to another -**web** -All web-based services hosted on the configured server, which can include the Developer REST API +**web** +:All web-based services hosted on the configured server, which can include the Developer REST API service, the Management REST API service (used for remote cluster management) and the Pulse -monitoring tool's web-based user interface. +monitoring tool's web-based user interface. -**jmx** -Java management extension communications, including communications with the `gfsh` utility. +**jmx** +:Java management extension communications, including communications with the `gfsh` utility. The Pulse monitoring tool uses JMX for server-side communication with a locator, but SSL applies to this connection only if Pulse is located on an app server separate from the locator. When Pulse and the locator are colocated, JMX communication between the two does not -involve a TCP connection, so SSL does not apply. +involve a TCP connection, so SSL does not apply. -**locator** -Communication with and between locators +**locator** +:Communication with and between locators -**server** -Communication between clients and servers +**server** +:Communication between clients and servers -**all** -All of the above (use SSL system-wide) +**all** +:All of the above (use SSL system-wide) Specifying that a component is enabled for SSL applies to the component's server-socket side and its client-socket side. For example, if you enable SSL for locators, then any process that communicates @@ -68,55 +68,55 @@ with a locator must also have SSL enabled. If you provide "" as the value, SSL You can use <%=vars.product_name%> configuration properties to enable or disable SSL, to identify SSL ciphers and protocols, and to provide the location and credentials for key and trust stores. -**ssl-enabled-components** -List of components for which to enable SSL. Component list can be "" (disable SSL), "all", or a comma-separated list of components. +**ssl-enabled-components** +:List of components for which to enable SSL. Component list can be "" (disable SSL), "all", or a comma-separated list of components. -**ssl-endpoint-identification-enabled** -A boolean value that, when set to true, causes clients to validate the server's hostname using the server's certificate. +**ssl-endpoint-identification-enabled** +:A boolean value that, when set to true, causes clients to validate the server's hostname using the server's certificate. The default value is false. -Enabling endpoint identifica
[geode] branch support/1.14 updated: GEODE-10342: Simplify copying jars (#7789)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.14 by this push: new 951a28d319 GEODE-10342: Simplify copying jars (#7789) 951a28d319 is described below commit 951a28d319305b4d4d78bcfc81c8ec1285e85ad7 Author: Max Hufnagel AuthorDate: Wed Jun 8 12:36:13 2022 -0700 GEODE-10342: Simplify copying jars (#7789) --- .../tomcat_installing_the_module.html.md.erb | 106 ++--- 1 file changed, 7 insertions(+), 99 deletions(-) diff --git a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb index a43d70fe3d..5f987289f3 100644 --- a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb +++ b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb @@ -47,104 +47,12 @@ This adds jar files to the `lib` subdirectory and XML files to the `conf` subdir cd $CATALINA_HOME unzip $GEODE_HOME/tools/Modules/Apache_Geode_Modules-SERVER-VERSION-Tomcat.zip ``` -6. Copy the following jar files from the <%=vars.product_name%> `lib` subdirectory to the `lib` subdirectory of your Tomcat server (`$CATALINA_HOME/lib`), adding version numbers to the filenames as needed: -* antlr jar -* classgraph jar -* commons-beanutils jar -* commons-codec jar -* commons-collections jar -* commons-io jar -* commons-lang3 jar -* commons-logging jar -* commons-math3 jar -* commons-modeler jar -* commons-validator jar -* fastutil jar -* geo jar -* geode-common jar -* geode-connectors jar -* geode-core jar -* geode-cq jar -* geode-gfsh jar -* geode-http-service jar -* geode-log4j jar -* geode-logging jar -* geode-lucene jar -* geode-management jar -* geode-membership jar -* geode-memcached jar -* geode-old-client-support jar -* geode-protobuf jar -* geode-protobuf-messages jar -* geode-rebalancer jar -* geode-redis jar -* geode-serialization jar -* geode-tcp-server jar -* geode-unsafe jar -* geode-wan jar -* grumpy-core jar -* HdrHistogram jar -* HikariCP jar -* httpclient jar -* httpcore jar -* istack-commons-runtime jar -* jackson-annotations jar -* jackson-core jar -* jackson-databind jar -* javax.activation jar -* javax.activation-api jar -* javax.mail-api jar -* javax.resource-api jar -* javax.servlet-api jar -* javax.transaction-api jar -* jaxb-api jar -* jaxb-impl jar -* jetty-http jar -* jetty-io jar -* jetty-security jar -* jetty-server jar -* jetty-servlet jar -* jetty-util jar -* jetty-util-ajax jar -* jetty-webapp jar -* jetty-xml jar -* jgroups jar -* jline jar -* jna jar -* jna-platform jar -* jopt-simple jar -* LatencyUtils jar -* log4j-api jar -* log4j-core jar -* log4j-jcl jar -* log4j-jul jar -* log4j-slf4j-impl jar -* lucene-analyzers-common jar -* lucene-analyzers-phonetic jar -* lucene-core jar -* lucene-queries jar -* lucene-queryparser jar -* micrometer-core jar -* mx4j jar -* mx4j-remote jar -* mx4j-tools jar -* netty-all jar -* protobuf-java jar -* rmiio jar -* shiro-cache jar -* shiro-config-core jar -* shiro-config-ogdl jar -* shiro-core jar -* shiro-crypto-cipher jar -* shiro-crypto-core jar -* shiro-crypto-hash jar -* shiro-event jar -* shiro-lang jar -* slf4j-api jar -* snappy jar -* spring-core jar -* spring-jcl jar -* spring-shell jar -* swagger-annotations jar + +6. Copy all of the jar files from the <%=vars.product_name%> `lib` subdirectory to the `lib` subdirectory of your Tomcat server (`$CATALINA_HOME/lib`): + +``` +cd $CATALINA_HOME/lib +cp $GEODE_HOME/lib/*.jar . +``` Proceed to [Setting Up the HTTP Module for Tomcat](./tomcat_setting_up_the_module.html) to complete your Tomcat configuration.
[geode] branch support/1.12 updated: GEODE-10342: Simplify copying jars (#7790)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.12 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.12 by this push: new b3c7582a93 GEODE-10342: Simplify copying jars (#7790) b3c7582a93 is described below commit b3c7582a9311877eb9e421e341b188acdb7d5da8 Author: Max Hufnagel AuthorDate: Wed Jun 8 12:35:42 2022 -0700 GEODE-10342: Simplify copying jars (#7790) --- .../tomcat_installing_the_module.html.md.erb | 24 ++ 1 file changed, 6 insertions(+), 18 deletions(-) diff --git a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb index 1412b0931b..efbf248e89 100644 --- a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb +++ b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb @@ -25,23 +25,11 @@ This topic describes how to install the HTTP session management module for Tomca 2. The HTTP Session Management Module for Tomcat is included in the <%=vars.product_name%> installation package. After you install <%=vars.product_name_long%>, you will find the module in the `tools/Modules` directory of the installation. 3. Unzip the module into the `$CATALINA_HOME` directory or wherever you installed the application server. -4. Copy the following jar files to the `lib` directory of your Tomcat server (`$CATALINA_HOME/lib`): -- antlr jar -- commons-io jar -- commons-lang jar -- commons-validator jar -- fastutil jar -- geode-commons jar -- geode-core jar -- geode-logging jar -- geode-management jar -- geode-serialization jar -- javax.transaction-api jar -- jgroups jar -- log4j-api jar -- log4j-core jar -- log4j-jul jar -- micrometer-core jar -- shiro-core jar +4. Copy all of the jar files from the <%=vars.product_name%> `lib` subdirectory to the `lib` subdirectory of your Tomcat server (`$CATALINA_HOME/lib`): + +``` +cd $CATALINA_HOME/lib +cp $GEODE_HOME/lib/*.jar . +```
[geode] branch support/1.15 updated: GEODE-10342: Simplify copying jars (#7788)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new 90cb26ba60 GEODE-10342: Simplify copying jars (#7788) 90cb26ba60 is described below commit 90cb26ba60598e074e34789d1b75459422a87c25 Author: Max Hufnagel AuthorDate: Wed Jun 8 12:33:59 2022 -0700 GEODE-10342: Simplify copying jars (#7788) --- .../tomcat_installing_the_module.html.md.erb | 106 ++--- 1 file changed, 7 insertions(+), 99 deletions(-) diff --git a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb index af1c297e29..c2d1a7b766 100644 --- a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb +++ b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb @@ -47,104 +47,12 @@ This adds jar files to the `lib` subdirectory and XML files to the `conf` subdir cd $CATALINA_HOME unzip $GEODE_HOME/tools/Modules/Apache_Geode_Modules-SERVER-VERSION-Tomcat.zip ``` -6. Copy the following jar files from the <%=vars.product_name%> `lib` subdirectory to the `lib` subdirectory of your Tomcat server (`$CATALINA_HOME/lib`), adding version numbers to the filenames as needed: -* antlr jar -* classgraph jar -* commons-beanutils jar -* commons-codec jar -* commons-collections jar -* commons-io jar -* commons-lang3 jar -* commons-logging jar -* commons-math3 jar -* commons-modeler jar -* commons-validator jar -* fastutil jar -* geo jar -* geode-common jar -* geode-connectors jar -* geode-core jar -* geode-cq jar -* geode-gfsh jar -* geode-http-service jar -* geode-log4j jar -* geode-logging jar -* geode-lucene jar -* geode-management jar -* geode-membership jar -* geode-memcached jar -* geode-old-client-support jar -* geode-protobuf jar -* geode-protobuf-messages jar -* geode-rebalancer jar -* geode-redis jar -* geode-serialization jar -* geode-tcp-server jar -* geode-unsafe jar -* geode-wan jar -* grumpy-core jar -* HdrHistogram jar -* HikariCP jar -* httpclient jar -* httpcore jar -* istack-commons-runtime jar -* jackson-annotations jar -* jackson-core jar -* jackson-databind jar -* javax.activation jar -* javax.activation-api jar -* javax.mail-api jar -* javax.resource-api jar -* javax.servlet-api jar -* javax.transaction-api jar -* jaxb-api jar -* jaxb-impl jar -* jetty-http jar -* jetty-io jar -* jetty-security jar -* jetty-server jar -* jetty-servlet jar -* jetty-util jar -* jetty-util-ajax jar -* jetty-webapp jar -* jetty-xml jar -* jgroups jar -* jline jar -* jna jar -* jna-platform jar -* jopt-simple jar -* LatencyUtils jar -* log4j-api jar -* log4j-core jar -* log4j-jcl jar -* log4j-jul jar -* log4j-slf4j-impl jar -* lucene-analyzers-common jar -* lucene-analyzers-phonetic jar -* lucene-core jar -* lucene-queries jar -* lucene-queryparser jar -* micrometer-core jar -* mx4j jar -* mx4j-remote jar -* mx4j-tools jar -* netty-all jar -* protobuf-java jar -* rmiio jar -* shiro-cache jar -* shiro-config-core jar -* shiro-config-ogdl jar -* shiro-core jar -* shiro-crypto-cipher jar -* shiro-crypto-core jar -* shiro-crypto-hash jar -* shiro-event jar -* shiro-lang jar -* slf4j-api jar -* snappy jar -* spring-core jar -* spring-jcl jar -* spring-shell jar -* swagger-annotations jar + +6. Copy all of the jar files from the <%=vars.product_name%> `lib` subdirectory to the `lib` subdirectory of your Tomcat server (`$CATALINA_HOME/lib`): + +``` +cd $CATALINA_HOME/lib +cp $GEODE_HOME/lib/*.jar . +``` Proceed to [Setting Up the HTTP Module for Tomcat](./tomcat_setting_up_the_module.html) to complete your Tomcat configuration.
[geode] branch support/1.12 updated: GEODE-10365: add missing components to table (#7782)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.12 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.12 by this push: new 8726dffea3 GEODE-10365: add missing components to table (#7782) 8726dffea3 is described below commit 8726dffea3dbbb45ce947c59945ec0803d6effc1 Author: Max Hufnagel AuthorDate: Tue Jun 7 17:05:40 2022 -0700 GEODE-10365: add missing components to table (#7782) --- geode-docs/managing/security/implementing_ssl.html.md.erb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/geode-docs/managing/security/implementing_ssl.html.md.erb b/geode-docs/managing/security/implementing_ssl.html.md.erb index f5472a5799..8112112d31 100644 --- a/geode-docs/managing/security/implementing_ssl.html.md.erb +++ b/geode-docs/managing/security/implementing_ssl.html.md.erb @@ -218,8 +218,10 @@ The following table lists the properties you can use to configure SSL on your <% | ssl-protocols | list of SSL protocols | comma-separated list (default "any") | | ssl-keystore | path to key store | string | | ssl-keystore-password | key store password | string | +| ssl-keystore-type | trust store type | string | | ssl-truststore | path to trust store | string | | ssl-truststore-password| trust store password | string | +| ssl-truststore-type| trust store type | string | ## Procedure
[geode] branch support/1.14 updated: GEODE-10365: add missing components to table (#7781)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.14 by this push: new 2611996997 GEODE-10365: add missing components to table (#7781) 2611996997 is described below commit 26119969977534af5a225a27c993a696d57ca560 Author: Max Hufnagel AuthorDate: Tue Jun 7 17:05:13 2022 -0700 GEODE-10365: add missing components to table (#7781) --- geode-docs/managing/security/implementing_ssl.html.md.erb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/geode-docs/managing/security/implementing_ssl.html.md.erb b/geode-docs/managing/security/implementing_ssl.html.md.erb index 23b4993df2..d43142344b 100644 --- a/geode-docs/managing/security/implementing_ssl.html.md.erb +++ b/geode-docs/managing/security/implementing_ssl.html.md.erb @@ -218,8 +218,10 @@ The following table lists the properties you can use to configure SSL on your <% | ssl-protocols | list of SSL protocols | comma-separated list (default "any") | | ssl-keystore | path to key store | string | | ssl-keystore-password | key store password | string | +| ssl-keystore-type | trust store type | string | | ssl-truststore | path to trust store | string | | ssl-truststore-password| trust store password | string | +| ssl-truststore-type| trust store type | string | ## Procedure
[geode] branch support/1.15 updated: GEODE-10365: add missing components to table (#7780)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new 0376348409 GEODE-10365: add missing components to table (#7780) 0376348409 is described below commit 0376348409e9ed56511631d2c7d81f880a9431e9 Author: Max Hufnagel AuthorDate: Tue Jun 7 17:04:43 2022 -0700 GEODE-10365: add missing components to table (#7780) --- geode-docs/managing/security/implementing_ssl.html.md.erb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/geode-docs/managing/security/implementing_ssl.html.md.erb b/geode-docs/managing/security/implementing_ssl.html.md.erb index 23b4993df2..d43142344b 100644 --- a/geode-docs/managing/security/implementing_ssl.html.md.erb +++ b/geode-docs/managing/security/implementing_ssl.html.md.erb @@ -218,8 +218,10 @@ The following table lists the properties you can use to configure SSL on your <% | ssl-protocols | list of SSL protocols | comma-separated list (default "any") | | ssl-keystore | path to key store | string | | ssl-keystore-password | key store password | string | +| ssl-keystore-type | trust store type | string | | ssl-truststore | path to trust store | string | | ssl-truststore-password| trust store password | string | +| ssl-truststore-type| trust store type | string | ## Procedure
[geode] branch develop updated: GEODE-10342: Simplify copying jars (#7778)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/develop by this push: new 395c56b4d8 GEODE-10342: Simplify copying jars (#7778) 395c56b4d8 is described below commit 395c56b4d8d0ede376f020528bfb3754c3e62337 Author: Max Hufnagel AuthorDate: Tue Jun 7 17:04:05 2022 -0700 GEODE-10342: Simplify copying jars (#7778) --- .../tomcat_installing_the_module.html.md.erb | 107 ++--- 1 file changed, 8 insertions(+), 99 deletions(-) diff --git a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb index af1c297e29..9590dff4ba 100644 --- a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb +++ b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb @@ -47,104 +47,13 @@ This adds jar files to the `lib` subdirectory and XML files to the `conf` subdir cd $CATALINA_HOME unzip $GEODE_HOME/tools/Modules/Apache_Geode_Modules-SERVER-VERSION-Tomcat.zip ``` -6. Copy the following jar files from the <%=vars.product_name%> `lib` subdirectory to the `lib` subdirectory of your Tomcat server (`$CATALINA_HOME/lib`), adding version numbers to the filenames as needed: -* antlr jar -* classgraph jar -* commons-beanutils jar -* commons-codec jar -* commons-collections jar -* commons-io jar -* commons-lang3 jar -* commons-logging jar -* commons-math3 jar -* commons-modeler jar -* commons-validator jar -* fastutil jar -* geo jar -* geode-common jar -* geode-connectors jar -* geode-core jar -* geode-cq jar -* geode-gfsh jar -* geode-http-service jar -* geode-log4j jar -* geode-logging jar -* geode-lucene jar -* geode-management jar -* geode-membership jar -* geode-memcached jar -* geode-old-client-support jar -* geode-protobuf jar -* geode-protobuf-messages jar -* geode-rebalancer jar -* geode-redis jar -* geode-serialization jar -* geode-tcp-server jar -* geode-unsafe jar -* geode-wan jar -* grumpy-core jar -* HdrHistogram jar -* HikariCP jar -* httpclient jar -* httpcore jar -* istack-commons-runtime jar -* jackson-annotations jar -* jackson-core jar -* jackson-databind jar -* javax.activation jar -* javax.activation-api jar -* javax.mail-api jar -* javax.resource-api jar -* javax.servlet-api jar -* javax.transaction-api jar -* jaxb-api jar -* jaxb-impl jar -* jetty-http jar -* jetty-io jar -* jetty-security jar -* jetty-server jar -* jetty-servlet jar -* jetty-util jar -* jetty-util-ajax jar -* jetty-webapp jar -* jetty-xml jar -* jgroups jar -* jline jar -* jna jar -* jna-platform jar -* jopt-simple jar -* LatencyUtils jar -* log4j-api jar -* log4j-core jar -* log4j-jcl jar -* log4j-jul jar -* log4j-slf4j-impl jar -* lucene-analyzers-common jar -* lucene-analyzers-phonetic jar -* lucene-core jar -* lucene-queries jar -* lucene-queryparser jar -* micrometer-core jar -* mx4j jar -* mx4j-remote jar -* mx4j-tools jar -* netty-all jar -* protobuf-java jar -* rmiio jar -* shiro-cache jar -* shiro-config-core jar -* shiro-config-ogdl jar -* shiro-core jar -* shiro-crypto-cipher jar -* shiro-crypto-core jar -* shiro-crypto-hash jar -* shiro-event jar -* shiro-lang jar -* slf4j-api jar -* snappy jar -* spring-core jar -* spring-jcl jar -* spring-shell jar -* swagger-annotations jar + + +6. Copy all of the jar files from the <%=vars.product_name%> `lib` subdirectory to the `lib` subdirectory of your Tomcat server (`$CATALINA_HOME/lib`): + +``` +cd $CATALINA_HOME/lib +cp $GEODE_HOME/lib/*.jar . +``` Proceed to [Setting Up the HTTP Module for Tomcat](./tomcat_setting_up_the_module.html) to complete your Tomcat configuration.
[geode] branch develop updated (0700975d24 -> fc57331474)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git from 0700975d24 GEODE-10280: add Status Message to Status Server Command (#7662) add fc57331474 GEODE-10365: Add referenced but missing components to table (#7775) No new revisions were added by this update. Summary of changes: geode-docs/managing/security/implementing_ssl.html.md.erb | 2 ++ 1 file changed, 2 insertions(+)
[geode] branch develop updated (af5810650c -> 728467cfd7)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git from af5810650c Short-circuit CI checks for PRs that don't touch buildable files (#7763) add 728467cfd7 GEODE-10352: Update Ruby version in Geode doc preview tool (#7753) No new revisions were added by this update. Summary of changes: dev-tools/docker/docs/Dockerfile | 18 +- 1 file changed, 9 insertions(+), 9 deletions(-)
[geode] branch support/1.15 updated: GEODE-10342: Add current jars to HTTP Module for Tomcat instructions 1.15 (#7768)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new b20081a4c4 GEODE-10342: Add current jars to HTTP Module for Tomcat instructions 1.15 (#7768) b20081a4c4 is described below commit b20081a4c4b44fb55566ec060722860a731c409b Author: Max Hufnagel AuthorDate: Fri Jun 3 10:38:17 2022 -0700 GEODE-10342: Add current jars to HTTP Module for Tomcat instructions 1.15 (#7768) --- .../tomcat_installing_the_module.html.md.erb | 116 + 1 file changed, 98 insertions(+), 18 deletions(-) diff --git a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb index 08fd93a5ca..af1c297e29 100644 --- a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb +++ b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb @@ -48,23 +48,103 @@ This adds jar files to the `lib` subdirectory and XML files to the `conf` subdir unzip $GEODE_HOME/tools/Modules/Apache_Geode_Modules-SERVER-VERSION-Tomcat.zip ``` 6. Copy the following jar files from the <%=vars.product_name%> `lib` subdirectory to the `lib` subdirectory of your Tomcat server (`$CATALINA_HOME/lib`), adding version numbers to the filenames as needed: -- commons-io jar -- commons-lang jar -- commons-validator jar -- fastutil jar -- geode-common jar -- geode-core jar -- geode-logging jar -- geode-management jar -- geode-membership jar -- geode-serialization jar -- geode-tcp-server jar -- javax.transaction-api jar -- jgroups jar -- log4j-api jar -- log4j-core jar -- log4j-jul jar -- micrometer-core jar -- shiro-core jar +* antlr jar +* classgraph jar +* commons-beanutils jar +* commons-codec jar +* commons-collections jar +* commons-io jar +* commons-lang3 jar +* commons-logging jar +* commons-math3 jar +* commons-modeler jar +* commons-validator jar +* fastutil jar +* geo jar +* geode-common jar +* geode-connectors jar +* geode-core jar +* geode-cq jar +* geode-gfsh jar +* geode-http-service jar +* geode-log4j jar +* geode-logging jar +* geode-lucene jar +* geode-management jar +* geode-membership jar +* geode-memcached jar +* geode-old-client-support jar +* geode-protobuf jar +* geode-protobuf-messages jar +* geode-rebalancer jar +* geode-redis jar +* geode-serialization jar +* geode-tcp-server jar +* geode-unsafe jar +* geode-wan jar +* grumpy-core jar +* HdrHistogram jar +* HikariCP jar +* httpclient jar +* httpcore jar +* istack-commons-runtime jar +* jackson-annotations jar +* jackson-core jar +* jackson-databind jar +* javax.activation jar +* javax.activation-api jar +* javax.mail-api jar +* javax.resource-api jar +* javax.servlet-api jar +* javax.transaction-api jar +* jaxb-api jar +* jaxb-impl jar +* jetty-http jar +* jetty-io jar +* jetty-security jar +* jetty-server jar +* jetty-servlet jar +* jetty-util jar +* jetty-util-ajax jar +* jetty-webapp jar +* jetty-xml jar +* jgroups jar +* jline jar +* jna jar +* jna-platform jar +* jopt-simple jar +* LatencyUtils jar +* log4j-api jar +* log4j-core jar +* log4j-jcl jar +* log4j-jul jar +* log4j-slf4j-impl jar +* lucene-analyzers-common jar +* lucene-analyzers-phonetic jar +* lucene-core jar +* lucene-queries jar +* lucene-queryparser jar +* micrometer-core jar +* mx4j jar +* mx4j-remote jar +* mx4j-tools jar +* netty-all jar +* protobuf-java jar +* rmiio jar +* shiro-cache jar +* shiro-config-core jar +* shiro-config-ogdl jar +* shiro-core jar +* shiro-crypto-cipher jar +* shiro-crypto-core jar +* shiro-crypto-hash jar +* shiro-event jar +* shiro-lang jar +* slf4j-api jar +* snappy jar +* spring-core jar +* spring-jcl jar +* spring-shell jar +* swagger-annotations jar Proceed to [Setting Up the HTTP Module for Tomcat](./tomcat_setting_up_the_module.html) to complete your Tomcat configuration.
[geode] branch support/1.14 updated: GEODE-10342: Add current jars to HTTP Module for Tomcat instructions 1.14 (#7767)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.14 by this push: new bb4c7dc439 GEODE-10342: Add current jars to HTTP Module for Tomcat instructions 1.14 (#7767) bb4c7dc439 is described below commit bb4c7dc4392fe38f6206bffc36d60cd651cee906 Author: Max Hufnagel AuthorDate: Fri Jun 3 10:38:06 2022 -0700 GEODE-10342: Add current jars to HTTP Module for Tomcat instructions 1.14 (#7767) --- .../tomcat_installing_the_module.html.md.erb | 116 + 1 file changed, 98 insertions(+), 18 deletions(-) diff --git a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb index 5e4ac9b6a7..a43d70fe3d 100644 --- a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb +++ b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb @@ -48,23 +48,103 @@ This adds jar files to the `lib` subdirectory and XML files to the `conf` subdir unzip $GEODE_HOME/tools/Modules/Apache_Geode_Modules-SERVER-VERSION-Tomcat.zip ``` 6. Copy the following jar files from the <%=vars.product_name%> `lib` subdirectory to the `lib` subdirectory of your Tomcat server (`$CATALINA_HOME/lib`), adding version numbers to the filenames as needed: -- commons-io jar -- commons-lang jar -- commons-validator jar -- fastutil jar -- geode-common jar -- geode-core jar -- geode-logging jar -- geode-management jar -- geode-membership jar -- geode-serialization jar -- geode-tcp-server jar -- javax.transaction-api jar -- jgroups jar -- log4j-api jar -- log4j-core jar -- log4j-jul jar -- micrometer-core jar -- shiro-core jar +* antlr jar +* classgraph jar +* commons-beanutils jar +* commons-codec jar +* commons-collections jar +* commons-io jar +* commons-lang3 jar +* commons-logging jar +* commons-math3 jar +* commons-modeler jar +* commons-validator jar +* fastutil jar +* geo jar +* geode-common jar +* geode-connectors jar +* geode-core jar +* geode-cq jar +* geode-gfsh jar +* geode-http-service jar +* geode-log4j jar +* geode-logging jar +* geode-lucene jar +* geode-management jar +* geode-membership jar +* geode-memcached jar +* geode-old-client-support jar +* geode-protobuf jar +* geode-protobuf-messages jar +* geode-rebalancer jar +* geode-redis jar +* geode-serialization jar +* geode-tcp-server jar +* geode-unsafe jar +* geode-wan jar +* grumpy-core jar +* HdrHistogram jar +* HikariCP jar +* httpclient jar +* httpcore jar +* istack-commons-runtime jar +* jackson-annotations jar +* jackson-core jar +* jackson-databind jar +* javax.activation jar +* javax.activation-api jar +* javax.mail-api jar +* javax.resource-api jar +* javax.servlet-api jar +* javax.transaction-api jar +* jaxb-api jar +* jaxb-impl jar +* jetty-http jar +* jetty-io jar +* jetty-security jar +* jetty-server jar +* jetty-servlet jar +* jetty-util jar +* jetty-util-ajax jar +* jetty-webapp jar +* jetty-xml jar +* jgroups jar +* jline jar +* jna jar +* jna-platform jar +* jopt-simple jar +* LatencyUtils jar +* log4j-api jar +* log4j-core jar +* log4j-jcl jar +* log4j-jul jar +* log4j-slf4j-impl jar +* lucene-analyzers-common jar +* lucene-analyzers-phonetic jar +* lucene-core jar +* lucene-queries jar +* lucene-queryparser jar +* micrometer-core jar +* mx4j jar +* mx4j-remote jar +* mx4j-tools jar +* netty-all jar +* protobuf-java jar +* rmiio jar +* shiro-cache jar +* shiro-config-core jar +* shiro-config-ogdl jar +* shiro-core jar +* shiro-crypto-cipher jar +* shiro-crypto-core jar +* shiro-crypto-hash jar +* shiro-event jar +* shiro-lang jar +* slf4j-api jar +* snappy jar +* spring-core jar +* spring-jcl jar +* spring-shell jar +* swagger-annotations jar Proceed to [Setting Up the HTTP Module for Tomcat](./tomcat_setting_up_the_module.html) to complete your Tomcat configuration.
[geode] branch develop updated: GEODE-10342: Add current jars to HTTP Module for Tomcat instructions (#7745)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/develop by this push: new 300a1596ae GEODE-10342: Add current jars to HTTP Module for Tomcat instructions (#7745) 300a1596ae is described below commit 300a1596aecd89aebd2c71615da584a2e0a8442c Author: Max Hufnagel AuthorDate: Fri Jun 3 08:24:40 2022 -0700 GEODE-10342: Add current jars to HTTP Module for Tomcat instructions (#7745) --- .../tomcat_installing_the_module.html.md.erb | 116 + 1 file changed, 98 insertions(+), 18 deletions(-) diff --git a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb index 08fd93a5ca..af1c297e29 100644 --- a/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb +++ b/geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb @@ -48,23 +48,103 @@ This adds jar files to the `lib` subdirectory and XML files to the `conf` subdir unzip $GEODE_HOME/tools/Modules/Apache_Geode_Modules-SERVER-VERSION-Tomcat.zip ``` 6. Copy the following jar files from the <%=vars.product_name%> `lib` subdirectory to the `lib` subdirectory of your Tomcat server (`$CATALINA_HOME/lib`), adding version numbers to the filenames as needed: -- commons-io jar -- commons-lang jar -- commons-validator jar -- fastutil jar -- geode-common jar -- geode-core jar -- geode-logging jar -- geode-management jar -- geode-membership jar -- geode-serialization jar -- geode-tcp-server jar -- javax.transaction-api jar -- jgroups jar -- log4j-api jar -- log4j-core jar -- log4j-jul jar -- micrometer-core jar -- shiro-core jar +* antlr jar +* classgraph jar +* commons-beanutils jar +* commons-codec jar +* commons-collections jar +* commons-io jar +* commons-lang3 jar +* commons-logging jar +* commons-math3 jar +* commons-modeler jar +* commons-validator jar +* fastutil jar +* geo jar +* geode-common jar +* geode-connectors jar +* geode-core jar +* geode-cq jar +* geode-gfsh jar +* geode-http-service jar +* geode-log4j jar +* geode-logging jar +* geode-lucene jar +* geode-management jar +* geode-membership jar +* geode-memcached jar +* geode-old-client-support jar +* geode-protobuf jar +* geode-protobuf-messages jar +* geode-rebalancer jar +* geode-redis jar +* geode-serialization jar +* geode-tcp-server jar +* geode-unsafe jar +* geode-wan jar +* grumpy-core jar +* HdrHistogram jar +* HikariCP jar +* httpclient jar +* httpcore jar +* istack-commons-runtime jar +* jackson-annotations jar +* jackson-core jar +* jackson-databind jar +* javax.activation jar +* javax.activation-api jar +* javax.mail-api jar +* javax.resource-api jar +* javax.servlet-api jar +* javax.transaction-api jar +* jaxb-api jar +* jaxb-impl jar +* jetty-http jar +* jetty-io jar +* jetty-security jar +* jetty-server jar +* jetty-servlet jar +* jetty-util jar +* jetty-util-ajax jar +* jetty-webapp jar +* jetty-xml jar +* jgroups jar +* jline jar +* jna jar +* jna-platform jar +* jopt-simple jar +* LatencyUtils jar +* log4j-api jar +* log4j-core jar +* log4j-jcl jar +* log4j-jul jar +* log4j-slf4j-impl jar +* lucene-analyzers-common jar +* lucene-analyzers-phonetic jar +* lucene-core jar +* lucene-queries jar +* lucene-queryparser jar +* micrometer-core jar +* mx4j jar +* mx4j-remote jar +* mx4j-tools jar +* netty-all jar +* protobuf-java jar +* rmiio jar +* shiro-cache jar +* shiro-config-core jar +* shiro-config-ogdl jar +* shiro-core jar +* shiro-crypto-cipher jar +* shiro-crypto-core jar +* shiro-crypto-hash jar +* shiro-event jar +* shiro-lang jar +* slf4j-api jar +* snappy jar +* spring-core jar +* spring-jcl jar +* spring-shell jar +* swagger-annotations jar Proceed to [Setting Up the HTTP Module for Tomcat](./tomcat_setting_up_the_module.html) to complete your Tomcat configuration.
[geode] branch develop updated: GEODE-10348: Fix documentation on conflation (#7746)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/develop by this push: new 03875b8eac GEODE-10348: Fix documentation on conflation (#7746) 03875b8eac is described below commit 03875b8eac351ee901377155fcb841bbd3c11b10 Author: Alberto Gomez AuthorDate: Thu Jun 2 19:55:19 2022 +0200 GEODE-10348: Fix documentation on conflation (#7746) The Geode documentation states on conflation: "When an update is added to a queue that has conflation enabled, if there is already an update message in the queue for the entry key, then the existing message assumes the value of the new update and the new update is dropped, as shown here for key A." Nevertheless, that is not correct. The actual behavior is the following: "When an update is added to a queue that has conflation enabled, if there is already an update message in the queue for the entry key, then the existing message is removed and the new update is added to the end of the queue, as shown here for key A." The text has been updated as well as the the figure with the example. --- .../events/conflate_multisite_gateway_queue.html.md.erb | 4 ++-- geode-docs/images/MultiSite-4.gif| Bin 4991 -> 0 bytes geode-docs/images_svg/MultiSite-4.svg| 4 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/geode-docs/developing/events/conflate_multisite_gateway_queue.html.md.erb b/geode-docs/developing/events/conflate_multisite_gateway_queue.html.md.erb index 5fa8df905c..4d2ed5f0bc 100644 --- a/geode-docs/developing/events/conflate_multisite_gateway_queue.html.md.erb +++ b/geode-docs/developing/events/conflate_multisite_gateway_queue.html.md.erb @@ -25,9 +25,9 @@ Conflating a queue improves distribution performance. When conflation is enabled **Note:** Do not use conflation if your receiving applications depend on the specific ordering of entry modifications, or if they need to be notified of every change to an entry. -Conflation is most useful when a single entry is updated frequently, but other sites only need to know the current value of the entry (rather than the value of each update). When an update is added to a queue that has conflation enabled, if there is already an update message in the queue for the entry key, then the existing message assumes the value of the new update and the new update is dropped, as shown here for key A. +Conflation is most useful when a single entry is updated frequently, but other sites only need to know the current value of the entry (rather than the value of each update). When an update is added to a queue that has conflation enabled, if there is already an update message in the queue for the entry key, then the existing message is removed and the new update is added to the end of the queue, as shown here for key A. - + **Note:** This method of conflation is different from the one used for server-to-client subscription queue conflation and peer-to-peer distribution within a cluster. diff --git a/geode-docs/images/MultiSite-4.gif b/geode-docs/images/MultiSite-4.gif deleted file mode 100644 index c4a4b7d16f..00 Binary files a/geode-docs/images/MultiSite-4.gif and /dev/null differ diff --git a/geode-docs/images_svg/MultiSite-4.svg b/geode-docs/images_svg/MultiSite-4.svg new file mode 100644 index 00..e58a4e6a02 --- /dev/null +++ b/geode-docs/images_svg/MultiSite-4.svg @@ -0,0 +1,4 @@ + + +http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;> +http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink; version="1.1" width="624px" height="391px" viewBox="-0.5 -0.5 624 391" content="mxfile host=Electron modified=2022-06-01T08:05:30.280Z agent=5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) draw.io/17.2.4 Chrome/96.0.4664.174 Electron/16.1.0 Safari/537.36 etag=owQXNkmOwgtk-nMk95M2 version=17.2.4 type=devicedia [...] \ No newline at end of file
[geode] branch develop updated: GEODE-10341: add note that snapshot includes in-cache and overflow entries (#7729)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/develop by this push: new 356e361708 GEODE-10341: add note that snapshot includes in-cache and overflow entries (#7729) 356e361708 is described below commit 356e361708e29bc55de893c67a070c2fa216d623 Author: Max Hufnagel AuthorDate: Fri May 27 08:19:29 2022 -0700 GEODE-10341: add note that snapshot includes in-cache and overflow entries (#7729) --- geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb b/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb index 339e5ff280..1cc198fb08 100644 --- a/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb +++ b/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb @@ -44,7 +44,10 @@ Optionally, you can set a filter on the snapshot entries during the export. See ## Exporting a Region Snapshot -You can also export a specific region using the following API or gfsh commands: +You can also export a specific region using the API or gfsh commands below. + +**Note:** +In the case of non-persistent regions, the snapshot that you export contains both in-cache entries and entries that overflow to disk. **Java API:**
[geode] branch support/1.14 updated: GEODE-10299: update examples for creating dynamic regions (#7681)
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch support/1.14
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/support/1.14 by this push:
new 5aada08049 GEODE-10299: update examples for creating dynamic regions
(#7681)
5aada08049 is described below
commit 5aada08049d67782130d8cff04b03ccf677d80b4
Author: Max Hufnagel
AuthorDate: Wed May 11 16:17:52 2022 -0700
GEODE-10299: update examples for creating dynamic regions (#7681)
---
.../dynamic_region_creation.html.md.erb| 133 -
1 file changed, 50 insertions(+), 83 deletions(-)
diff --git
a/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
b/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
index fd88b7259c..54a54130ca 100644
--- a/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
+++ b/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
@@ -38,58 +38,49 @@ In the following example, the `CreateRegionFunction` class
defines a function in
#CreateRegionFunction.java
import org.apache.geode.cache.Cache;
-import org.apache.geode.cache.CacheFactory;
import org.apache.geode.cache.DataPolicy;
import org.apache.geode.cache.Declarable;
import org.apache.geode.cache.Region;
-import org.apache.geode.cache.RegionAttributes;
import org.apache.geode.cache.RegionFactory;
import org.apache.geode.cache.Scope;
+import org.apache.geode.cache.configuration.RegionConfig;
+
import org.apache.geode.cache.execute.Function;
import org.apache.geode.cache.execute.FunctionContext;
import java.util.Properties;
-public class CreateRegionFunction implements Function, Declarable {
+public class CreateRegionFunction implements Function,
Declarable {
- private final Cache cache;
-
- private final Region regionAttributesMetadataRegion;
+ private Region regionAttributesMetadataRegion;
private static final String REGION_ATTRIBUTES_METADATA_REGION =
- "_regionAttributesMetadata";
+
"_regionAttributesMetadata";
- public enum Status {SUCCESSFUL, UNSUCCESSFUL, ALREADY_EXISTS};
-
- public CreateRegionFunction() {
-this.cache = CacheFactory.getAnyInstance();
-this.regionAttributesMetadataRegion =
createRegionAttributesMetadataRegion();
- }
+ public enum Status {SUCCESSFUL, UNSUCCESSFUL, ALREADY_EXISTS}
- public void execute(FunctionContext context) {
-Object[] arguments = (Object[]) context.getArguments();
-String regionName = (String) arguments[0];
-RegionAttributes attributes = (RegionAttributes) arguments[1];
+ public void execute(FunctionContext context) {
+RegionConfig regionConfig = context.getArguments();
// Create or retrieve region
-Status status = createOrRetrieveRegion(regionName, attributes);
+Status status = createOrRetrieveRegion(context.getCache(), regionConfig);
// Return status
context.getResultSender().lastResult(status);
}
-
- private Status createOrRetrieveRegion(String regionName,
-RegionAttributes attributes) {
+
+ private Status createOrRetrieveRegion(Cache cache, RegionConfig
regionConfig) {
Status status = Status.SUCCESSFUL;
-Region region = this.cache.getRegion(regionName);
+String regionName = regionConfig.getName();
+Region region = cache.getRegion(regionName);
if (region == null) {
- // Put the attributes into the metadata region. The afterCreate call will
- // actually create the region.
- this.regionAttributesMetadataRegion.put(regionName, attributes);
+ // Put the attributes into the metadata region. The afterCreate call
+ // creates the region.
+ this.regionAttributesMetadataRegion.put(regionName, regionConfig);
// Retrieve the region after creating it
- region = this.cache.getRegion(regionName);
+ region = cache.getRegion(regionName);
if (region == null) {
status = Status.UNSUCCESSFUL;
}
@@ -99,38 +90,25 @@ public class CreateRegionFunction implements Function,
Declarable {
return status;
}
- private Region
- createRegionAttributesMetadataRegion() {
-Region metaRegion =
-
this.cache.getRegion(REGION_ATTRIBUTES_METADATA_REGION);
-if (metaRegion == null) {
- RegionFactory factory =
- this.cache.createRegionFactory();
+ private void initializeRegionAttributesMetadataRegion(Cache cache) {
+this.regionAttributesMetadataRegion =
+
cache.getRegion(REGION_ATTRIBUTES_METADATA_REGION);
+if (this.regionAttributesMetadataRegion == null) {
+ RegionFactory factory =
cache.createRegionFactory();
factory.setDataPolicy(DataPolicy.REPLICATE);
[geode] branch support/1.15 updated: GEODE-10299: update examples for creating dynamic regions (#7681)
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch support/1.15
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/support/1.15 by this push:
new 53cbccaeb5 GEODE-10299: update examples for creating dynamic regions
(#7681)
53cbccaeb5 is described below
commit 53cbccaeb5bcf2bfa6773481ff98e47f27704e86
Author: Max Hufnagel
AuthorDate: Wed May 11 16:17:52 2022 -0700
GEODE-10299: update examples for creating dynamic regions (#7681)
---
.../dynamic_region_creation.html.md.erb| 133 -
1 file changed, 50 insertions(+), 83 deletions(-)
diff --git
a/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
b/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
index fd88b7259c..54a54130ca 100644
--- a/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
+++ b/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
@@ -38,58 +38,49 @@ In the following example, the `CreateRegionFunction` class
defines a function in
#CreateRegionFunction.java
import org.apache.geode.cache.Cache;
-import org.apache.geode.cache.CacheFactory;
import org.apache.geode.cache.DataPolicy;
import org.apache.geode.cache.Declarable;
import org.apache.geode.cache.Region;
-import org.apache.geode.cache.RegionAttributes;
import org.apache.geode.cache.RegionFactory;
import org.apache.geode.cache.Scope;
+import org.apache.geode.cache.configuration.RegionConfig;
+
import org.apache.geode.cache.execute.Function;
import org.apache.geode.cache.execute.FunctionContext;
import java.util.Properties;
-public class CreateRegionFunction implements Function, Declarable {
+public class CreateRegionFunction implements Function,
Declarable {
- private final Cache cache;
-
- private final Region regionAttributesMetadataRegion;
+ private Region regionAttributesMetadataRegion;
private static final String REGION_ATTRIBUTES_METADATA_REGION =
- "_regionAttributesMetadata";
+
"_regionAttributesMetadata";
- public enum Status {SUCCESSFUL, UNSUCCESSFUL, ALREADY_EXISTS};
-
- public CreateRegionFunction() {
-this.cache = CacheFactory.getAnyInstance();
-this.regionAttributesMetadataRegion =
createRegionAttributesMetadataRegion();
- }
+ public enum Status {SUCCESSFUL, UNSUCCESSFUL, ALREADY_EXISTS}
- public void execute(FunctionContext context) {
-Object[] arguments = (Object[]) context.getArguments();
-String regionName = (String) arguments[0];
-RegionAttributes attributes = (RegionAttributes) arguments[1];
+ public void execute(FunctionContext context) {
+RegionConfig regionConfig = context.getArguments();
// Create or retrieve region
-Status status = createOrRetrieveRegion(regionName, attributes);
+Status status = createOrRetrieveRegion(context.getCache(), regionConfig);
// Return status
context.getResultSender().lastResult(status);
}
-
- private Status createOrRetrieveRegion(String regionName,
-RegionAttributes attributes) {
+
+ private Status createOrRetrieveRegion(Cache cache, RegionConfig
regionConfig) {
Status status = Status.SUCCESSFUL;
-Region region = this.cache.getRegion(regionName);
+String regionName = regionConfig.getName();
+Region region = cache.getRegion(regionName);
if (region == null) {
- // Put the attributes into the metadata region. The afterCreate call will
- // actually create the region.
- this.regionAttributesMetadataRegion.put(regionName, attributes);
+ // Put the attributes into the metadata region. The afterCreate call
+ // creates the region.
+ this.regionAttributesMetadataRegion.put(regionName, regionConfig);
// Retrieve the region after creating it
- region = this.cache.getRegion(regionName);
+ region = cache.getRegion(regionName);
if (region == null) {
status = Status.UNSUCCESSFUL;
}
@@ -99,38 +90,25 @@ public class CreateRegionFunction implements Function,
Declarable {
return status;
}
- private Region
- createRegionAttributesMetadataRegion() {
-Region metaRegion =
-
this.cache.getRegion(REGION_ATTRIBUTES_METADATA_REGION);
-if (metaRegion == null) {
- RegionFactory factory =
- this.cache.createRegionFactory();
+ private void initializeRegionAttributesMetadataRegion(Cache cache) {
+this.regionAttributesMetadataRegion =
+
cache.getRegion(REGION_ATTRIBUTES_METADATA_REGION);
+if (this.regionAttributesMetadataRegion == null) {
+ RegionFactory factory =
cache.createRegionFactory();
factory.setDataPolicy(DataPolicy.REPLICATE);
[geode] branch support/1.15 updated: GEODE-10313: User Guide: Add javadocs template variable (#7696)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new 4d53566658 GEODE-10313: User Guide: Add javadocs template variable (#7696) 4d53566658 is described below commit 4d5356665868d46a0417a5bbd9902de047b3f07d Author: Dave Barnes AuthorDate: Tue May 17 06:39:13 2022 -0700 GEODE-10313: User Guide: Add javadocs template variable (#7696) --- geode-book/config.yml | 1 + .../data_serialization/extending_the_autoserializer.html.md.erb | 2 +- .../data_serialization/gemfire_data_serialization.html.md.erb | 2 +- .../events/configuring_gateway_concurrency_levels.html.md.erb | 2 +- .../events/implementing_write_behind_event_handler.html.md.erb | 4 ++-- geode-docs/developing/function_exec/function_execution.html.md.erb | 2 +- .../query_additional/using_query_bind_parameters.html.md.erb| 2 +- geode-docs/developing/query_index/maintaining_indexes.html.md.erb | 2 +- geode-docs/developing/query_select/the_select_statement.html.md.erb | 2 +- .../querying_basics/querying_partitioned_regions.html.md.erb| 6 +++--- geode-docs/developing/querying_basics/running_a_query.html.md.erb | 4 ++-- geode-docs/getting_started/querying_quick_reference.html.md.erb | 6 +++--- 12 files changed, 18 insertions(+), 17 deletions(-) diff --git a/geode-book/config.yml b/geode-book/config.yml index 16547b0cb8..c156d7e965 100644 --- a/geode-book/config.yml +++ b/geode-book/config.yml @@ -45,5 +45,6 @@ template_variables: book_title_short: Geode Docs local_header_title: Apache Geode local_header_img: /images/Apache_Geode_logo_symbol.png + javadocs: /releases/latest/javadoc broken_link_exclusions: iefix|using_custom_classes|arrowhead|cppdocs|DotNetDocs diff --git a/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb b/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb index 47ee92bd94..d80bf13394 100644 --- a/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb +++ b/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb @@ -44,7 +44,7 @@ You can customize the specific behaviors in `ReflectionBasedAutoSerializer` by o These methods are only called the first time the `ReflectionBasedAutoSerializer` sees a new class. The results will be remembered and used the next time the same class is seen. -For details on these methods and their default behaviors, see the JavaDocs on [ReflectionBasedAutoSerializer](/releases/latest/javadoc/org/apache/geode/pdx/ReflectionBasedAutoSerializer.html) for details. +For details on these methods and their default behaviors, see the JavaDocs on [ReflectionBasedAutoSerializer](<%=vars.javadocs%>/org/apache/geode/pdx/ReflectionBasedAutoSerializer.html) for details. ## Example of Optimizing Autoserialization of BigInteger and BigDecimal Types diff --git a/geode-docs/developing/data_serialization/gemfire_data_serialization.html.md.erb b/geode-docs/developing/data_serialization/gemfire_data_serialization.html.md.erb index 96689ecb08..9411f02066 100644 --- a/geode-docs/developing/data_serialization/gemfire_data_serialization.html.md.erb +++ b/geode-docs/developing/data_serialization/gemfire_data_serialization.html.md.erb @@ -47,4 +47,4 @@ In addition to speeding standard object serialization, you can use the `DataSeri You can also use `DataSerializer` to serialize domain objects. It serializes data in the same way as `DataSerializable` but allows you to serialize classes without modifying the domain class code. -See the JavaDocs on [DataSerializable](/releases/latest/javadoc/org/apache/geode/DataSerializable.html) and [DataSerializer](/releases/latest/javadoc/org/apache/geode/DataSerializer.html) for more information. +See the JavaDocs on [DataSerializable](<%=vars.javadocs%>/org/apache/geode/DataSerializable.html) and [DataSerializer](<%=vars.javadocs%>/org/apache/geode/DataSerializer.html) for more information. diff --git a/geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb b/geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb index f637064ecf..1ec3636eec 100644 --- a/geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb +++ b/geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb @@ -50,7 +50,7 @@ When using multiple `dispatcher-threads` (greater than 1) with a serial event qu - **key (default)**. All updates to the same key are distributed in order. <%=vars.product_name%> preserves key ordering by placing all updates to the same key in the same dispatcher thread queue. You typically use key ordering
[geode] branch develop updated: GEODE-10313: User Guide: Add javadocs template variable (#7696)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/develop by this push: new cbd8795bc3 GEODE-10313: User Guide: Add javadocs template variable (#7696) cbd8795bc3 is described below commit cbd8795bc30dd595b6956b957301167f2f0ac5d5 Author: Dave Barnes AuthorDate: Tue May 17 06:39:13 2022 -0700 GEODE-10313: User Guide: Add javadocs template variable (#7696) --- geode-book/config.yml | 1 + .../data_serialization/extending_the_autoserializer.html.md.erb | 2 +- .../data_serialization/gemfire_data_serialization.html.md.erb | 2 +- .../events/configuring_gateway_concurrency_levels.html.md.erb | 2 +- .../events/implementing_write_behind_event_handler.html.md.erb | 4 ++-- geode-docs/developing/function_exec/function_execution.html.md.erb | 2 +- .../query_additional/using_query_bind_parameters.html.md.erb| 2 +- geode-docs/developing/query_index/maintaining_indexes.html.md.erb | 2 +- geode-docs/developing/query_select/the_select_statement.html.md.erb | 2 +- .../querying_basics/querying_partitioned_regions.html.md.erb| 6 +++--- geode-docs/developing/querying_basics/running_a_query.html.md.erb | 4 ++-- geode-docs/getting_started/querying_quick_reference.html.md.erb | 6 +++--- 12 files changed, 18 insertions(+), 17 deletions(-) diff --git a/geode-book/config.yml b/geode-book/config.yml index 28cda59fd9..c055f8113e 100644 --- a/geode-book/config.yml +++ b/geode-book/config.yml @@ -45,5 +45,6 @@ template_variables: book_title_short: Geode Docs local_header_title: Apache Geode local_header_img: /images/Apache_Geode_logo_symbol.png + javadocs: /releases/latest/javadoc broken_link_exclusions: iefix|using_custom_classes|arrowhead|cppdocs|DotNetDocs diff --git a/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb b/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb index 47ee92bd94..d80bf13394 100644 --- a/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb +++ b/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb @@ -44,7 +44,7 @@ You can customize the specific behaviors in `ReflectionBasedAutoSerializer` by o These methods are only called the first time the `ReflectionBasedAutoSerializer` sees a new class. The results will be remembered and used the next time the same class is seen. -For details on these methods and their default behaviors, see the JavaDocs on [ReflectionBasedAutoSerializer](/releases/latest/javadoc/org/apache/geode/pdx/ReflectionBasedAutoSerializer.html) for details. +For details on these methods and their default behaviors, see the JavaDocs on [ReflectionBasedAutoSerializer](<%=vars.javadocs%>/org/apache/geode/pdx/ReflectionBasedAutoSerializer.html) for details. ## Example of Optimizing Autoserialization of BigInteger and BigDecimal Types diff --git a/geode-docs/developing/data_serialization/gemfire_data_serialization.html.md.erb b/geode-docs/developing/data_serialization/gemfire_data_serialization.html.md.erb index 96689ecb08..9411f02066 100644 --- a/geode-docs/developing/data_serialization/gemfire_data_serialization.html.md.erb +++ b/geode-docs/developing/data_serialization/gemfire_data_serialization.html.md.erb @@ -47,4 +47,4 @@ In addition to speeding standard object serialization, you can use the `DataSeri You can also use `DataSerializer` to serialize domain objects. It serializes data in the same way as `DataSerializable` but allows you to serialize classes without modifying the domain class code. -See the JavaDocs on [DataSerializable](/releases/latest/javadoc/org/apache/geode/DataSerializable.html) and [DataSerializer](/releases/latest/javadoc/org/apache/geode/DataSerializer.html) for more information. +See the JavaDocs on [DataSerializable](<%=vars.javadocs%>/org/apache/geode/DataSerializable.html) and [DataSerializer](<%=vars.javadocs%>/org/apache/geode/DataSerializer.html) for more information. diff --git a/geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb b/geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb index f637064ecf..1ec3636eec 100644 --- a/geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb +++ b/geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb @@ -50,7 +50,7 @@ When using multiple `dispatcher-threads` (greater than 1) with a serial event qu - **key (default)**. All updates to the same key are distributed in order. <%=vars.product_name%> preserves key ordering by placing all updates to the same key in the same dispatcher thread queue. You typically use key ordering when
[geode] branch support/1.12 updated: GEODE-10307: Doc changes needed for enable security-manager property (#7687)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.12 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.12 by this push: new d8c401699b GEODE-10307: Doc changes needed for enable security-manager property (#7687) d8c401699b is described below commit d8c401699b346d3e3922da993a5d68ef11138836 Author: Dave Barnes AuthorDate: Fri May 13 13:20:56 2022 -0700 GEODE-10307: Doc changes needed for enable security-manager property (#7687) * GEODE-10307: Doc changes needed for enable security-manager property --- .../cluster_config/gfsh_persist.html.md.erb| 8 ++--- .../managing/security/enable_security.html.md.erb | 37 -- 2 files changed, 39 insertions(+), 6 deletions(-) diff --git a/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb b/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb index 8b64843c0a..d47d9663fd 100644 --- a/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb +++ b/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb @@ -21,7 +21,7 @@ limitations under the License. The <%=vars.product_name_long%> cluster configuration service persists cluster configurations created by `gfsh` commands to the locators in a cluster and distributes the configurations to members of the cluster. -## Why Use the Cluster Configuration Service +## Why Use the Cluster Configuration Service We highly recommend that you use the `gfsh` command line and the cluster configuration service as the primary mechanism @@ -38,7 +38,7 @@ You can use the cluster configuration service to: - Start additional servers without having to configure each server separately. - Configure some servers to host certain regions and other servers to host different regions, and configure all servers to host a set of common regions. -## Using the Cluster Configuration Service +## Using the Cluster Configuration Service To use the cluster configuration service in <%=vars.product_name%>, you must use dedicated, standalone locators in your deployment. You cannot use the cluster configuration service with co-located locators (locators running in another process such as a server) or in multicast environments. @@ -54,7 +54,7 @@ command after starting up a locator. Subsequently, any servers that you start with `gfsh` that have `--use-cluster-configuration` set to `true` will pick up the cluster configuration from the locator as well as any appropriate group-level configurations (for member groups they belong to). To disable the cluster configuration service on a server, you must start the server with the `--use-cluster-configuration` parameter set to `false`. By default, the parameter is set to true. -## How the Cluster Configuration Service Works +## How the Cluster Configuration Service Works When you use `gfsh` commands to create <%=vars.product_name_long%> regions, disk-stores, and other objects, the cluster configuration service saves the configurations on each locator in the cluster. If you specify a group when issuing these commands, a separate configuration is saved containing only configurations that apply to the group. @@ -62,7 +62,7 @@ When you use `gfsh` to start new <%=vars.product_name_long%> servers, the locato -## gfsh Commands that Create Cluster Configurations +## gfsh Commands that Create Cluster Configurations The following `gfsh` commands cause the configuration to be written to all locators in the cluster (the locators write the configuration to disk): diff --git a/geode-docs/managing/security/enable_security.html.md.erb b/geode-docs/managing/security/enable_security.html.md.erb index a86428feba..72b8dff5d8 100644 --- a/geode-docs/managing/security/enable_security.html.md.erb +++ b/geode-docs/managing/security/enable_security.html.md.erb @@ -34,11 +34,44 @@ For example: security-manager = com.example.security.MySecurityManager ``` +### Apply security-manager to All Members + 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. + +- Specify the properties file when you start the first locator for the cluster. + +### Is Cluster Management Enabled? + +The next steps in applying the `security-manager` property across the cluster de
[geode] branch support/1.15 updated: GEODE-10307: Doc changes needed for enable security-manager property (#7687)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new 08fe5c543c GEODE-10307: Doc changes needed for enable security-manager property (#7687) 08fe5c543c is described below commit 08fe5c543c1ebf6c9b09776a1b1e16afac7acb41 Author: Dave Barnes AuthorDate: Fri May 13 13:20:56 2022 -0700 GEODE-10307: Doc changes needed for enable security-manager property (#7687) * GEODE-10307: Doc changes needed for enable security-manager property --- .../cluster_config/gfsh_persist.html.md.erb| 8 ++--- .../managing/security/enable_security.html.md.erb | 37 -- 2 files changed, 39 insertions(+), 6 deletions(-) diff --git a/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb b/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb index 93b34335cf..e7a4bb9473 100644 --- a/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb +++ b/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb @@ -21,7 +21,7 @@ limitations under the License. The <%=vars.product_name_long%> cluster configuration service persists cluster configurations created by `gfsh` commands to the locators in a cluster and distributes the configurations to members of the cluster. -## Why Use the Cluster Configuration Service +## Why Use the Cluster Configuration Service We highly recommend that you use the `gfsh` command line and the cluster configuration service as the primary mechanism @@ -38,7 +38,7 @@ You can use the cluster configuration service to: - Start additional servers without having to configure each server separately. - Configure some servers to host certain regions and other servers to host different regions, and configure all servers to host a set of common regions. -## Using the Cluster Configuration Service +## Using the Cluster Configuration Service To use the cluster configuration service in <%=vars.product_name%>, you must use dedicated, standalone locators in your deployment. You cannot use the cluster configuration service with co-located locators (locators running in another process such as a server) or in multicast environments. @@ -54,7 +54,7 @@ command after starting up a locator. Subsequently, any servers that you start with `gfsh` that have `--use-cluster-configuration` set to `true` will pick up the cluster configuration from the locator as well as any appropriate group-level configurations (for member groups they belong to). To disable the cluster configuration service on a server, you must start the server with the `--use-cluster-configuration` parameter set to `false`. By default, the parameter is set to true. -## How the Cluster Configuration Service Works +## How the Cluster Configuration Service Works When you use `gfsh` commands to create <%=vars.product_name_long%> regions, disk-stores, and other objects, the cluster configuration service saves the configurations on each locator in the cluster. If you specify a group when issuing these commands, a separate configuration is saved containing only configurations that apply to the group. @@ -62,7 +62,7 @@ When you use `gfsh` to start new <%=vars.product_name_long%> servers, the locato -## gfsh Commands that Create Cluster Configurations +## gfsh Commands that Create Cluster Configurations The following `gfsh` commands cause the configuration to be written to all locators in the cluster (the locators write the configuration to disk): diff --git a/geode-docs/managing/security/enable_security.html.md.erb b/geode-docs/managing/security/enable_security.html.md.erb index a86428feba..72b8dff5d8 100644 --- a/geode-docs/managing/security/enable_security.html.md.erb +++ b/geode-docs/managing/security/enable_security.html.md.erb @@ -34,11 +34,44 @@ For example: security-manager = com.example.security.MySecurityManager ``` +### Apply security-manager to All Members + 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. + +- Specify the properties file when you start the first locator for the cluster. + +### Is Cluster Management Enabled? + +The next steps in applying the `security-manager` property across the cluster de
[geode] branch support/1.14 updated: GEODE-10307: Doc changes needed for enable security-manager property (#7687)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.14 by this push: new f0664f1197 GEODE-10307: Doc changes needed for enable security-manager property (#7687) f0664f1197 is described below commit f0664f11972ea30c4e4e9462118cba7b10d5e6ff Author: Dave Barnes AuthorDate: Fri May 13 13:20:56 2022 -0700 GEODE-10307: Doc changes needed for enable security-manager property (#7687) * GEODE-10307: Doc changes needed for enable security-manager property --- .../cluster_config/gfsh_persist.html.md.erb| 8 ++--- .../managing/security/enable_security.html.md.erb | 37 -- 2 files changed, 39 insertions(+), 6 deletions(-) diff --git a/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb b/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb index 93b34335cf..e7a4bb9473 100644 --- a/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb +++ b/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb @@ -21,7 +21,7 @@ limitations under the License. The <%=vars.product_name_long%> cluster configuration service persists cluster configurations created by `gfsh` commands to the locators in a cluster and distributes the configurations to members of the cluster. -## Why Use the Cluster Configuration Service +## Why Use the Cluster Configuration Service We highly recommend that you use the `gfsh` command line and the cluster configuration service as the primary mechanism @@ -38,7 +38,7 @@ You can use the cluster configuration service to: - Start additional servers without having to configure each server separately. - Configure some servers to host certain regions and other servers to host different regions, and configure all servers to host a set of common regions. -## Using the Cluster Configuration Service +## Using the Cluster Configuration Service To use the cluster configuration service in <%=vars.product_name%>, you must use dedicated, standalone locators in your deployment. You cannot use the cluster configuration service with co-located locators (locators running in another process such as a server) or in multicast environments. @@ -54,7 +54,7 @@ command after starting up a locator. Subsequently, any servers that you start with `gfsh` that have `--use-cluster-configuration` set to `true` will pick up the cluster configuration from the locator as well as any appropriate group-level configurations (for member groups they belong to). To disable the cluster configuration service on a server, you must start the server with the `--use-cluster-configuration` parameter set to `false`. By default, the parameter is set to true. -## How the Cluster Configuration Service Works +## How the Cluster Configuration Service Works When you use `gfsh` commands to create <%=vars.product_name_long%> regions, disk-stores, and other objects, the cluster configuration service saves the configurations on each locator in the cluster. If you specify a group when issuing these commands, a separate configuration is saved containing only configurations that apply to the group. @@ -62,7 +62,7 @@ When you use `gfsh` to start new <%=vars.product_name_long%> servers, the locato -## gfsh Commands that Create Cluster Configurations +## gfsh Commands that Create Cluster Configurations The following `gfsh` commands cause the configuration to be written to all locators in the cluster (the locators write the configuration to disk): diff --git a/geode-docs/managing/security/enable_security.html.md.erb b/geode-docs/managing/security/enable_security.html.md.erb index a86428feba..72b8dff5d8 100644 --- a/geode-docs/managing/security/enable_security.html.md.erb +++ b/geode-docs/managing/security/enable_security.html.md.erb @@ -34,11 +34,44 @@ For example: security-manager = com.example.security.MySecurityManager ``` +### Apply security-manager to All Members + 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. + +- Specify the properties file when you start the first locator for the cluster. + +### Is Cluster Management Enabled? + +The next steps in applying the `security-manager` property across the cluster de
[geode] branch develop updated: GEODE-10307: Doc changes needed for enable security-manager property (#7687)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/develop by this push: new 0ed7793518 GEODE-10307: Doc changes needed for enable security-manager property (#7687) 0ed7793518 is described below commit 0ed779351824eddbdd1b6801268e185b0b321950 Author: Dave Barnes AuthorDate: Fri May 13 13:20:56 2022 -0700 GEODE-10307: Doc changes needed for enable security-manager property (#7687) * GEODE-10307: Doc changes needed for enable security-manager property --- .../cluster_config/gfsh_persist.html.md.erb| 8 ++--- .../managing/security/enable_security.html.md.erb | 37 -- 2 files changed, 39 insertions(+), 6 deletions(-) diff --git a/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb b/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb index 93b34335cf..e7a4bb9473 100644 --- a/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb +++ b/geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb @@ -21,7 +21,7 @@ limitations under the License. The <%=vars.product_name_long%> cluster configuration service persists cluster configurations created by `gfsh` commands to the locators in a cluster and distributes the configurations to members of the cluster. -## Why Use the Cluster Configuration Service +## Why Use the Cluster Configuration Service We highly recommend that you use the `gfsh` command line and the cluster configuration service as the primary mechanism @@ -38,7 +38,7 @@ You can use the cluster configuration service to: - Start additional servers without having to configure each server separately. - Configure some servers to host certain regions and other servers to host different regions, and configure all servers to host a set of common regions. -## Using the Cluster Configuration Service +## Using the Cluster Configuration Service To use the cluster configuration service in <%=vars.product_name%>, you must use dedicated, standalone locators in your deployment. You cannot use the cluster configuration service with co-located locators (locators running in another process such as a server) or in multicast environments. @@ -54,7 +54,7 @@ command after starting up a locator. Subsequently, any servers that you start with `gfsh` that have `--use-cluster-configuration` set to `true` will pick up the cluster configuration from the locator as well as any appropriate group-level configurations (for member groups they belong to). To disable the cluster configuration service on a server, you must start the server with the `--use-cluster-configuration` parameter set to `false`. By default, the parameter is set to true. -## How the Cluster Configuration Service Works +## How the Cluster Configuration Service Works When you use `gfsh` commands to create <%=vars.product_name_long%> regions, disk-stores, and other objects, the cluster configuration service saves the configurations on each locator in the cluster. If you specify a group when issuing these commands, a separate configuration is saved containing only configurations that apply to the group. @@ -62,7 +62,7 @@ When you use `gfsh` to start new <%=vars.product_name_long%> servers, the locato -## gfsh Commands that Create Cluster Configurations +## gfsh Commands that Create Cluster Configurations The following `gfsh` commands cause the configuration to be written to all locators in the cluster (the locators write the configuration to disk): diff --git a/geode-docs/managing/security/enable_security.html.md.erb b/geode-docs/managing/security/enable_security.html.md.erb index a86428feba..72b8dff5d8 100644 --- a/geode-docs/managing/security/enable_security.html.md.erb +++ b/geode-docs/managing/security/enable_security.html.md.erb @@ -34,11 +34,44 @@ For example: security-manager = com.example.security.MySecurityManager ``` +### Apply security-manager to All Members + 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. + +- Specify the properties file when you start the first locator for the cluster. + +### Is Cluster Management Enabled? + +The next steps in applying the `security-manager` property across the cluster depend on whe
[geode] branch develop updated: GEODE-10299: update examples for creating dynamic regions (#7681)
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/develop by this push:
new 485411b5f6 GEODE-10299: update examples for creating dynamic regions
(#7681)
485411b5f6 is described below
commit 485411b5f6b927c6a7a8d016084ab6e49260bfb5
Author: Max Hufnagel
AuthorDate: Wed May 11 16:17:52 2022 -0700
GEODE-10299: update examples for creating dynamic regions (#7681)
---
.../dynamic_region_creation.html.md.erb| 133 -
1 file changed, 50 insertions(+), 83 deletions(-)
diff --git
a/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
b/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
index fd88b7259c..54a54130ca 100644
--- a/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
+++ b/geode-docs/developing/region_options/dynamic_region_creation.html.md.erb
@@ -38,58 +38,49 @@ In the following example, the `CreateRegionFunction` class
defines a function in
#CreateRegionFunction.java
import org.apache.geode.cache.Cache;
-import org.apache.geode.cache.CacheFactory;
import org.apache.geode.cache.DataPolicy;
import org.apache.geode.cache.Declarable;
import org.apache.geode.cache.Region;
-import org.apache.geode.cache.RegionAttributes;
import org.apache.geode.cache.RegionFactory;
import org.apache.geode.cache.Scope;
+import org.apache.geode.cache.configuration.RegionConfig;
+
import org.apache.geode.cache.execute.Function;
import org.apache.geode.cache.execute.FunctionContext;
import java.util.Properties;
-public class CreateRegionFunction implements Function, Declarable {
+public class CreateRegionFunction implements Function,
Declarable {
- private final Cache cache;
-
- private final Region regionAttributesMetadataRegion;
+ private Region regionAttributesMetadataRegion;
private static final String REGION_ATTRIBUTES_METADATA_REGION =
- "_regionAttributesMetadata";
+
"_regionAttributesMetadata";
- public enum Status {SUCCESSFUL, UNSUCCESSFUL, ALREADY_EXISTS};
-
- public CreateRegionFunction() {
-this.cache = CacheFactory.getAnyInstance();
-this.regionAttributesMetadataRegion =
createRegionAttributesMetadataRegion();
- }
+ public enum Status {SUCCESSFUL, UNSUCCESSFUL, ALREADY_EXISTS}
- public void execute(FunctionContext context) {
-Object[] arguments = (Object[]) context.getArguments();
-String regionName = (String) arguments[0];
-RegionAttributes attributes = (RegionAttributes) arguments[1];
+ public void execute(FunctionContext context) {
+RegionConfig regionConfig = context.getArguments();
// Create or retrieve region
-Status status = createOrRetrieveRegion(regionName, attributes);
+Status status = createOrRetrieveRegion(context.getCache(), regionConfig);
// Return status
context.getResultSender().lastResult(status);
}
-
- private Status createOrRetrieveRegion(String regionName,
-RegionAttributes attributes) {
+
+ private Status createOrRetrieveRegion(Cache cache, RegionConfig
regionConfig) {
Status status = Status.SUCCESSFUL;
-Region region = this.cache.getRegion(regionName);
+String regionName = regionConfig.getName();
+Region region = cache.getRegion(regionName);
if (region == null) {
- // Put the attributes into the metadata region. The afterCreate call will
- // actually create the region.
- this.regionAttributesMetadataRegion.put(regionName, attributes);
+ // Put the attributes into the metadata region. The afterCreate call
+ // creates the region.
+ this.regionAttributesMetadataRegion.put(regionName, regionConfig);
// Retrieve the region after creating it
- region = this.cache.getRegion(regionName);
+ region = cache.getRegion(regionName);
if (region == null) {
status = Status.UNSUCCESSFUL;
}
@@ -99,38 +90,25 @@ public class CreateRegionFunction implements Function,
Declarable {
return status;
}
- private Region
- createRegionAttributesMetadataRegion() {
-Region metaRegion =
-
this.cache.getRegion(REGION_ATTRIBUTES_METADATA_REGION);
-if (metaRegion == null) {
- RegionFactory factory =
- this.cache.createRegionFactory();
+ private void initializeRegionAttributesMetadataRegion(Cache cache) {
+this.regionAttributesMetadataRegion =
+
cache.getRegion(REGION_ATTRIBUTES_METADATA_REGION);
+if (this.regionAttributesMetadataRegion == null) {
+ RegionFactory factory =
cache.createRegionFactory();
factory.setDataPolicy(DataPolicy.REPLICATE);
[geode] branch develop updated: GEODE-10215: Document warning for parallel gws (#7623)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/develop by this push: new ff9b3be5e3 GEODE-10215: Document warning for parallel gws (#7623) ff9b3be5e3 is described below commit ff9b3be5e3a11ac227856065f1a602b2c72a5229 Author: Jakov Varenina <62134331+jvaren...@users.noreply.github.com> AuthorDate: Wed May 4 16:58:46 2022 +0200 GEODE-10215: Document warning for parallel gws (#7623) --- geode-docs/tools_modules/gfsh/command-pages/destroy.html.md.erb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/geode-docs/tools_modules/gfsh/command-pages/destroy.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/destroy.html.md.erb index 194581c4e0..882b65a59e 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/destroy.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/destroy.html.md.erb @@ -200,6 +200,8 @@ similar to: ``` pre gfsh>alter region --name=regionA --gateway-sender-id="" ``` +**Note:** Do not reuse the removed parallel gateway-sender in the new region unless that region +is colocated with the previously attached region, as that will lead to data replication issues. **Availability:** Online. You must be connected in `gfsh` to a JMX Manager member to use this command.
[geode-site] branch asf-site updated: GEODE-10264: remove 'connect to the server from your application' section (#19)
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new dd6dedf5 GEODE-10264: remove 'connect to the server from your
application' section (#19)
dd6dedf5 is described below
commit dd6dedf594b8bc8dfe93458781b2ec1737bacad2
Author: Max Hufnagel
AuthorDate: Tue May 3 15:39:01 2022 -0700
GEODE-10264: remove 'connect to the server from your application' section
(#19)
---
docs/guide/114/getting_started/intro_to_clients.html | 20
1 file changed, 20 deletions(-)
diff --git a/docs/guide/114/getting_started/intro_to_clients.html
b/docs/guide/114/getting_started/intro_to_clients.html
index d2be90e1..405567c6 100644
--- a/docs/guide/114/getting_started/intro_to_clients.html
+++ b/docs/guide/114/getting_started/intro_to_clients.html
@@ -2735,26 +2735,6 @@ Apache Geode that you have installed.
}
-Connect to the server from your application
-import
org.apache.geode.cache.client.ClientCache;
-import org.apache.geode.cache.client.ClientCacheFactory;
-
-public class HelloWorld {
-
- public static void main(String[] args) {
- ClientCache cache = new ClientCacheFactory().addPoolLocator("127.0.0.1",
10334).create();
-
- System.out.println(cache.getDefaultPool().getLocators());
-
- cache.close();
- }
-}
-
-
-The information printed out should match the host and port of your Apache
Geode instance locators and should resemble
-[/127.0.0.1:10334]
-
-
Simple Put and Get with Apache Geode Java client
public static void main(String[] args) {
ClientCache cache = new ClientCacheFactory().addPoolLocator("127.0.0.1",
10334).create();
[geode] branch support/1.14 updated: GEODE-10264: remove 'connect to the server from your application' section (#7641)
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch support/1.14
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/support/1.14 by this push:
new 5d2c5cdc0b GEODE-10264: remove 'connect to the server from your
application' section (#7641)
5d2c5cdc0b is described below
commit 5d2c5cdc0b8828e7cedf2006ff87dd7e1faa44dc
Author: Max Hufnagel
AuthorDate: Mon May 2 17:06:35 2022 -0700
GEODE-10264: remove 'connect to the server from your application' section
(#7641)
---
.../getting_started/intro_to_clients.html.md.erb | 23 --
1 file changed, 23 deletions(-)
diff --git a/geode-docs/getting_started/intro_to_clients.html.md.erb
b/geode-docs/getting_started/intro_to_clients.html.md.erb
index c553c9a823..62ac9ea150 100644
--- a/geode-docs/getting_started/intro_to_clients.html.md.erb
+++ b/geode-docs/getting_started/intro_to_clients.html.md.erb
@@ -83,29 +83,6 @@ dependencies {
}
```
-**Connect to the server from your application**
-
-```
-import org.apache.geode.cache.client.ClientCache;
-import org.apache.geode.cache.client.ClientCacheFactory;
-
-public class HelloWorld {
-
- public static void main(String[] args) {
- ClientCache cache = new ClientCacheFactory().addPoolLocator("127.0.0.1",
10334).create();
-
- System.out.println(cache.getDefaultPool().getLocators());
-
- cache.close();
- }
-}
-```
-
-The information printed out should match the host and port of your
<%=vars.product_name_long%> instance locators and should resemble
-
-```
-[/127.0.0.1:10334]
-```
**Simple Put and Get with <%=vars.product_name_long%> Java client**
[geode] branch develop updated (f7fa244c9f -> 8536dffe39)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git from f7fa244c9f Revert "GEODE-10249: Adds BufferPoolMXBean stats. (#7607)" (#7638) add 8536dffe39 GEODE-10264: remove 'connect to the server from your application' section (#7641) No new revisions were added by this update. Summary of changes: .../getting_started/intro_to_clients.html.md.erb | 23 -- 1 file changed, 23 deletions(-)
[geode-native] branch support/1.12 updated: GEODE-9921: Rename .NET to .NET Framework (#964)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.12 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.12 by this push: new b456d7e20 GEODE-9921: Rename .NET to .NET Framework (#964) b456d7e20 is described below commit b456d7e20d2de3269f8502ad7adc6f10734b4e6f Author: Max Hufnagel AuthorDate: Mon Apr 25 18:16:15 2022 -0700 GEODE-9921: Rename .NET to .NET Framework (#964) --- docs/geode-native-book-dotnet/config.yml | 6 +- .../about-client-users-guide.html.md.erb | 9 ++- .../client-cache-ref.html.md.erb | 4 +- .../configuring/config-client-cache.html.md.erb| 3 +- .../configuring/sysprops.html.md.erb | 4 +- .../continuous-queries.html.md.erb | 4 +- .../function-execution.html.md.erb | 8 +-- .../app-dev-walkthrough-dotnet.html.md.erb | 12 ++-- .../getting-started-nc-client.html.md.erb | 4 +- .../getting-started/put-get-example.html.md.erb| 11 ++-- .../config-durable-reconnect.html.md.erb | 2 +- .../using-queue-conflation.html.md.erb | 2 +- .../regions/regions.html.md.erb| 2 +- .../registering-interest-for-entries.html.md.erb | 2 +- .../remote-queries.html.md.erb | 2 +- .../security/authentication.html.md.erb| 2 +- .../serialization/data-serialization.html.md.erb | 14 ++-- .../dotnet-pdx-autoserializer.html.md.erb | 8 +-- .../dotnet-pdx-serialization.html.md.erb | 4 +- .../pdx-serializable-examples.html.md.erb} | 77 ++ .../serialize-using-ipdxserializable.html.md.erb | 2 +- .../transactions.html.md.erb | 8 +-- 22 files changed, 75 insertions(+), 115 deletions(-) diff --git a/docs/geode-native-book-dotnet/config.yml b/docs/geode-native-book-dotnet/config.yml index 206fa70c7..b88ba23c5 100644 --- a/docs/geode-native-book-dotnet/config.yml +++ b/docs/geode-native-book-dotnet/config.yml @@ -31,11 +31,11 @@ template_variables: product_version: "1.12" product_version_nodot: 112 product_language: dotnet - client_name: Geode Native Client for .NET + client_name: Geode Native Client for .NET Framework min_java_update: 121 support_url: http://geode.apache.org/community product_url: http://geode.apache.org - book_title: Apache Geode Native .NET Documentation + book_title: Apache Geode Native .NET Framework Documentation book_header_img: /images/Apache_Geode_logo_symbol_white.png support_link: http://geode.apache.org/community; target="_blank">Community support_call_to_action: http://geode.apache.org/community; target="_blank">Need Help? @@ -43,7 +43,7 @@ template_variables: product_link: http://geode.apache.org;>Back to Product Page domain_name: apache.org book_title_short: Geode Native .NET Docs - local_header_title: Apache Geode Native .NET + local_header_title: Apache Geode Native .NET Framework local_header_img: /images/Apache_Geode_logo_symbol.png broken_link_exclusions: iefix|using_custom_classes|arrowhead|cppdocs|dotnetdocs|# diff --git a/docs/geode-native-docs-dotnet/about-client-users-guide.html.md.erb b/docs/geode-native-docs-dotnet/about-client-users-guide.html.md.erb index e55f621cd..5759865fc 100644 --- a/docs/geode-native-docs-dotnet/about-client-users-guide.html.md.erb +++ b/docs/geode-native-docs-dotnet/about-client-users-guide.html.md.erb @@ -17,16 +17,15 @@ See the License for the specific language governing permissions and limitations under the License. --> -This documentation describes the Apache Geode Native Client version <%=vars.product_version%>. -Source files are available from the [Apache Geode-Native Github repository](https://github.com/apache/geode-native) +This documentation describes the Apache Geode Native Client version <%=vars.product_version%>. +Source files are available from the [Apache Geode-Native Github repository](https://github.com/apache/geode-native) and instructions on how to build this documentation are available in the project README file found at that location. -The Apache Geode Native Client is a library that provides access for C++ and Microsoft® .NET™ clients to an Apache Geode cluster. +The Apache Geode Native Client is a library that provides access for C++ and Microsoft® .NET™ Framework clients to an Apache Geode cluster. See the API docs for API details: - [C++ API docs](https://geode.apache.org/releases/latest/cppdocs/index.html) - - [.NET API docs](https://geode.apache.org/releases/latest/dotnetdocs/index.html) + - [.NET Framework API docs](https://geode.apache.org/releases/latest/dotnetdocs/index.html) See the [_<%=vars.product_name_long%> User Guide_](serverman/about_<
[geode-native] branch support/1.14 updated: GEODE-9921: Rename .NET to .NET Framework (#963)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.14 by this push: new 147552987 GEODE-9921: Rename .NET to .NET Framework (#963) 147552987 is described below commit 1475529874a7b4f5d75c2ed309ccfcc58026f70f Author: Max Hufnagel AuthorDate: Mon Apr 25 18:16:03 2022 -0700 GEODE-9921: Rename .NET to .NET Framework (#963) --- docs/geode-native-book-dotnet/config.yml | 6 ++-- .../about-client-users-guide.html.md.erb | 9 +++--- .../client-cache-ref.html.md.erb | 4 +-- .../configuring/config-client-cache.html.md.erb| 2 +- .../configuring/sysprops.html.md.erb | 2 +- .../continuous-queries.html.md.erb | 4 +-- .../function-execution.html.md.erb | 8 ++--- .../app-dev-walkthrough-dotnet.html.md.erb | 12 .../getting-started-nc-client.html.md.erb | 4 +-- .../getting-started/put-get-example.html.md.erb| 11 --- .../config-durable-reconnect.html.md.erb | 2 +- .../using-queue-conflation.html.md.erb | 2 +- .../regions/regions.html.md.erb| 2 +- .../registering-interest-for-entries.html.md.erb | 2 +- .../remote-queries.html.md.erb | 2 +- .../security/authentication.html.md.erb| 2 +- .../serialization/data-serialization.html.md.erb | 15 - .../dotnet-pdx-autoserializer.html.md.erb | 36 -- .../dotnet-pdx-serialization.html.md.erb | 32 ++- .../pdx-serializable-examples.html.md.erb | 12 .../serialize-using-ipdxserializable.html.md.erb | 2 +- .../transactions.html.md.erb | 8 ++--- 22 files changed, 93 insertions(+), 86 deletions(-) diff --git a/docs/geode-native-book-dotnet/config.yml b/docs/geode-native-book-dotnet/config.yml index 39c93c760..09af77893 100644 --- a/docs/geode-native-book-dotnet/config.yml +++ b/docs/geode-native-book-dotnet/config.yml @@ -31,11 +31,11 @@ template_variables: product_version: "1.14" product_version_nodot: 114 product_language: dotnet - client_name: Geode Native Client for .NET + client_name: Geode Native Client for .NET Framework min_java_update: 121 support_url: http://geode.apache.org/community product_url: http://geode.apache.org - book_title: Apache Geode Native .NET Documentation + book_title: Apache Geode Native .NET Framework Documentation book_header_img: /images/Apache_Geode_logo_symbol_white.png support_link: http://geode.apache.org/community; target="_blank">Community support_call_to_action: http://geode.apache.org/community; target="_blank">Need Help? @@ -43,7 +43,7 @@ template_variables: product_link: http://geode.apache.org;>Back to Product Page domain_name: apache.org book_title_short: Geode Native .NET Docs - local_header_title: Apache Geode Native .NET + local_header_title: Apache Geode Native .NET Framework local_header_img: /images/Apache_Geode_logo_symbol.png serverman: https://geode.apache.org/docs/guide/latest geodeman: https://geode.apache.org/docs/guide/latest diff --git a/docs/geode-native-docs-dotnet/about-client-users-guide.html.md.erb b/docs/geode-native-docs-dotnet/about-client-users-guide.html.md.erb index 34114c7ba..10c147b89 100644 --- a/docs/geode-native-docs-dotnet/about-client-users-guide.html.md.erb +++ b/docs/geode-native-docs-dotnet/about-client-users-guide.html.md.erb @@ -17,16 +17,15 @@ See the License for the specific language governing permissions and limitations under the License. --> -This documentation describes the Apache Geode Native Client version <%=vars.product_version%>. -Source files are available from the [Apache Geode-Native Github repository](https://github.com/apache/geode-native) +This documentation describes the Apache Geode Native Client version <%=vars.product_version%>. +Source files are available from the [Apache Geode-Native Github repository](https://github.com/apache/geode-native) and instructions on how to build this documentation are available in the project README file found at that location. -The Apache Geode Native Client is a library that provides access for C++ and Microsoft® .NET™ clients to an Apache Geode cluster. +The Apache Geode Native Client is a library that provides access for C++ and Microsoft® .NET™ Framework clients to an Apache Geode cluster. See the API docs for API details: - [C++ API docs](https://geode.apache.org/releases/latest/cppdocs/hierarchy.html) - - [.NET API docs](https://geode.apache.org/releases/latest/dotnetdocs/hierarchy.html) + - [.NET Framework API docs](https://geode.apache.org/releases/latest/dotnetdocs/hierarchy.html)
[geode-site] branch asf-site updated: Update 1.14 user guide
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new f475246b Update 1.14 user guide
f475246b is described below
commit f475246b6aea78664328cdb2531db21992560fa4
Author: Dave Barnes
AuthorDate: Thu Apr 14 17:14:20 2022 -0700
Update 1.14 user guide
---
.../how_function_execution_works.html | 8 +-
.../disk_storage/compacting_disk_stores.html | 2 +-
.../tools_modules/gfsh/command-pages/create.html | 4 +-
.../114/tools_modules/gfsh/command-pages/list.html | 93 --
.../setting_up_a_multisite_system.html | 66 ---
.../how_function_execution_works.html | 8 +-
.../tools_modules/gfsh/command-pages/create.html | 4 +-
.../tools_modules/gfsh/command-pages/list.html | 93 --
.../setting_up_a_multisite_system.html | 66 ---
9 files changed, 179 insertions(+), 165 deletions(-)
diff --git
a/docs/guide/114/developing/function_exec/how_function_execution_works.html
b/docs/guide/114/developing/function_exec/how_function_execution_works.html
index ca159f55..07269a6e 100644
--- a/docs/guide/114/developing/function_exec/how_function_execution_works.html
+++ b/docs/guide/114/developing/function_exec/how_function_execution_works.html
@@ -2676,15 +2676,15 @@ limitations under the License.
For Data-independent Functions
- On a specific member or members—Execute the function
within a peer-to-peer cluster, specifying the member or members where you want
to run the function by using FunctionService methods
onMember() and onMembers().
- On a specific server or set of servers—If you are
connected to a cluster as a client, you can execute the function on a server or
servers configured for a specific connection pool, or on a server or servers
connected to a given cache using the default connection pool. For
data-independent functions on client/server architectures, a client invokes
FunctionService methods onServer() or
onServers(). (See Configuring
and Running a Cluster for more information about using member groups.) You
can invoke a data independent function on all members in a specified member
group or member groups, or execute the function on only one member of each
specified member group.
+ On a specific member or members: Execute the function
within a peer-to-peer cluster, specifying the member or members where you want
to run the function by using FunctionService methods
onMember() and onMembers().
+ On a specific server or set of servers: If you are
connected to a cluster as a client, you can execute the function on a server or
servers configured for a specific connection pool, or on a server or servers
connected to a given cache using the default connection pool. For
data-independent functions on client/server architectures, a client invokes
FunctionService methods onServer() or
onServers(). (See Configuring
and Running a Cluster for more information about using member groups.) You
can invoke a data independent function on all members in a specified member
group or member groups, or execute the function on only one member of each
specified member group.
For Data-dependent Functions
- On a region—If you are executing a data-dependent
function, specify a region and, optionally, a set of keys on which to run the
function. The method FunctionService.onRegion() directs a
data-dependent function to execute on a specific region.
+ On a region: If you are executing a data-dependent
function, specify a region and, optionally, a set of keys on which to run the
function. The method FunctionService.onRegion() directs a
data-dependent function to execute on a specific region.
See the org.apache.geode.cache.execute.FunctionService Java
API documentation for more details.
diff --git a/docs/guide/114/managing/disk_storage/compacting_disk_stores.html
b/docs/guide/114/managing/disk_storage/compacting_disk_stores.html
index 0a9f63ae..0c9c3a59 100644
--- a/docs/guide/114/managing/disk_storage/compacting_disk_stores.html
+++ b/docs/guide/114/managing/disk_storage/compacting_disk_stores.html
@@ -2708,7 +2708,7 @@ See Disk Sto
Compact the logs for a single online disk store through the API, with
the forceCompaction method. This method first rolls the oplogs and
then compacts them. Example:
-myCache.findDiskStore("myDiskStore").forceCompaction();
+myCache.getDiskStore("myDiskStore").forceCompaction();
Using gfsh, compact a disk store with the compact
disk-store command. Examples:
gfshcompact disk-store --name=Disk1
diff --git a/docs/guide/114/tools_modules/gfsh/command-pages/create.html
b/docs/guide/114/tools_modules/gfsh/command-pages/create.html
index 926d3543..5f8232bc 100644
--- a/docs/guide/114/tools_module
[geode] branch support/1.14 updated: GEODE-5337: End-port is not exclusive when creating a gw receiver (#6370)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.14 by this push: new e19bf94807 GEODE-5337: End-port is not exclusive when creating a gw receiver (#6370) e19bf94807 is described below commit e19bf9480724afc676bf9c9052d5a4c20a9325e2 Author: Alberto Bustamante Reyes AuthorDate: Tue Apr 27 09:34:30 2021 +0200 GEODE-5337: End-port is not exclusive when creating a gw receiver (#6370) --- geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb index 11b4192199..c276a7198e 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb @@ -423,13 +423,13 @@ if this option is specified and cluster configuration is enabled. \-\-start-port Starting port number to use when specifying the range of possible port numbers this gateway receiver will use to connects to gateway senders in other sites. <%=vars.product_name%> chooses an unused port number in the specified port number range to start the receiver. If no port numbers in the range are available, an exception is thrown. -The STARTPORT value is inclusive while the ENDPORT value is exclusive. For example, if you specify STARTPORT=50510 and ENDPORT=50520, <%=vars.product_name%> chooses a port value from 50510 to 50519. +The start-port and end-port values are inclusive. For example, if you specify start-port=50510 and end-port=50520, <%=vars.product_name%> chooses a port value from 50510 to 50520. 5000 \-\-end-port Defines the upper bound port number to use when specifying the range of possible port numbers this gateway receiver will use to for connections from gateway senders in other sites. <%=vars.product_name%> chooses an unused port number in the specified port number range to start the receiver. If no port numbers in the range are available, an exception is thrown. -The ENDPORT value is exclusive while the STARTPORT value is inclusive. For example, if you specify STARTPORT=50510 and ENDPORT=50520, <%=vars.product_name%> chooses a port value from 50510 to 50519. +The end-port and start-port values are inclusive. For example, if you specify start-port=50510 and end-port=50520, <%=vars.product_name%> chooses a port value from 50510 to 50520. 5500
[geode] branch support/1.12 updated: GEODE-5337: End-port is not exclusive when creating a gw receiver (#6370)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.12 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.12 by this push: new 89f41fd2e6 GEODE-5337: End-port is not exclusive when creating a gw receiver (#6370) 89f41fd2e6 is described below commit 89f41fd2e681fad1838d5c34b3191d022c712979 Author: Alberto Bustamante Reyes AuthorDate: Tue Apr 27 09:34:30 2021 +0200 GEODE-5337: End-port is not exclusive when creating a gw receiver (#6370) --- geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb index 80627bcf48..323e727453 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb @@ -423,13 +423,13 @@ if this option is specified and cluster configuration is enabled. \-\-start-port Starting port number to use when specifying the range of possible port numbers this gateway receiver will use to connects to gateway senders in other sites. <%=vars.product_name%> chooses an unused port number in the specified port number range to start the receiver. If no port numbers in the range are available, an exception is thrown. -The STARTPORT value is inclusive while the ENDPORT value is exclusive. For example, if you specify STARTPORT=50510 and ENDPORT=50520, <%=vars.product_name%> chooses a port value from 50510 to 50519. +The start-port and end-port values are inclusive. For example, if you specify start-port=50510 and end-port=50520, <%=vars.product_name%> chooses a port value from 50510 to 50520. 5000 \-\-end-port Defines the upper bound port number to use when specifying the range of possible port numbers this gateway receiver will use to for connections from gateway senders in other sites. <%=vars.product_name%> chooses an unused port number in the specified port number range to start the receiver. If no port numbers in the range are available, an exception is thrown. -The ENDPORT value is exclusive while the STARTPORT value is inclusive. For example, if you specify STARTPORT=50510 and ENDPORT=50520, <%=vars.product_name%> chooses a port value from 50510 to 50519. +The end-port and start-port values are inclusive. For example, if you specify start-port=50510 and end-port=50520, <%=vars.product_name%> chooses a port value from 50510 to 50520. 5500
[geode] branch support/1.12 updated: GEODE-4709: Add list gateways output sample in UG (#6372)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.12 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.12 by this push: new 22a722bb0c GEODE-4709: Add list gateways output sample in UG (#6372) 22a722bb0c is described below commit 22a722bb0ce63fe73048cba3ed307f64febf Author: Alberto Bustamante Reyes AuthorDate: Tue Apr 27 23:39:28 2021 +0200 GEODE-4709: Add list gateways output sample in UG (#6372) * GEODE-4709: Add list gateways output sample in UG --- .../gfsh/command-pages/list.html.md.erb| 85 ++-- .../setting_up_a_multisite_system.html.md.erb | 113 ++--- 2 files changed, 108 insertions(+), 90 deletions(-) diff --git a/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb index 01b6faa1b3..7a60d606d5 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb @@ -29,7 +29,7 @@ List existing <%=vars.product_name%> resources such as deployed applications, di - **[list clients](#topic_ts1_qb1_dk)** -Displays a list of connected clients. +Display a list of connected clients. - **[list deployed](#topic_59DF60DE71AD4097B281749425254BFF)** @@ -49,7 +49,7 @@ List existing <%=vars.product_name%> resources such as deployed applications, di - **[list gateways](#topic_B1D89671C7B74074899C7D52F15849ED)** -Displays the gateway senders and receivers for a member or members. +Display the gateway senders and receivers for a member or members. - **[list indexes](#topic_B3B51B6DEA484EE086C4F657EC9831F2)** @@ -91,9 +91,7 @@ list async-event-queues ## list clients -Displays a list of connected clients. - -Displays a list of connected clients and the servers they are connected to. +Display a list of connected clients and the servers to which they connect. **Availability:** Online. You must be connected in `gfsh` to a JMX Manager member to use this command. @@ -116,8 +114,8 @@ gfsh>list clients ClientList -Client Name / ID | Server Name / ID -- | - + Client Name / ID | Server Name / ID + | - 192.0.2.0(4987:loner):58922:7b3398cf | member=server2,port=53508; member=server1,port=56806 192.0.2.0(5065:loner):39906:a6f598cf | member=server2,port=53508; member=server1,port=56806 ``` @@ -167,9 +165,9 @@ No JAR Files Found ## list disk-stores -List all available disk stores across the <%=vars.product_name%> cluster +List all available disk stores across the <%=vars.product_name%> cluster. -The command also lists the configured disk directories and any Regions, Cache Servers, Gateways, PDX Serialization and Async Event Queues using Disk Stores to either overflow and/or persist information to disk. Use the `describe disk-store` command to see the details for a particular Disk Store. +The command also lists the configured disk directories and any Regions, Cache Servers, Gateways, PDX Serialization and Async Event Queues using Disk Stores to either overflow and/or persist information to disk. Use the `describe disk-store` command to see the details for a particular Disk Store. **Availability:** Online. You must be connected in `gfsh` to a JMX Manager member to use this command. @@ -190,8 +188,8 @@ list disk-stores ``` pre gfsh> list disk-stores - Member Name | Member Id | Disk Store Name |Disk Store ID - -- | - | --- | + Member Name | Member Id | Disk Store Name |Disk Store ID + -- | --| --- | consumerServer | 192.0.2.0(consumerServer:13825):3545 | consumerData | 4029af26-fd82-4997-bd6c-33382cdbb5e9 consumerServer | 192.0.2.0(consumerServer:13825):3545 | observerData | 7e0316ad-963c-49b0-9b01-8f59b8d9e29e producerServer | 192.0.2.0(producerServer:13826):53764 | producerData | 4670e4eb-1c50-4465-b418-08ede3d5dbed @@ -200,9 +198,7 @@ gfsh> list disk-stores **Error Messages:** ``` pre -gfsh> list disk-stores No Disk Stores Found - ``` ## list durable-cqs @@ -249,8 +245,6 @@ server4 | cq3 **Error Messages:** ``` pre -gfsh>list durable-cqs --durable-client-id=client1 - Unable to list durable-cqs for durable-client-id : "client1" due to following reasons. N
[geode] branch support/1.14 updated: GEODE-4709: Add list gateways output sample in UG (#6372)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.14 by this push: new 75d08d6b0a GEODE-4709: Add list gateways output sample in UG (#6372) 75d08d6b0a is described below commit 75d08d6b0abb1b438b5051164e1e06fff5760816 Author: Alberto Bustamante Reyes AuthorDate: Tue Apr 27 23:39:28 2021 +0200 GEODE-4709: Add list gateways output sample in UG (#6372) * GEODE-4709: Add list gateways output sample in UG --- .../gfsh/command-pages/list.html.md.erb| 89 ++--- .../setting_up_a_multisite_system.html.md.erb | 105 ++--- 2 files changed, 106 insertions(+), 88 deletions(-) diff --git a/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb index b18aefb6b7..3a7a92462d 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb @@ -29,7 +29,7 @@ List existing <%=vars.product_name%> resources such as deployed applications, di - **[list clients](#topic_ts1_qb1_dk)** -Displays a list of connected clients. +Display a list of connected clients. - **[list deployed](#topic_59DF60DE71AD4097B281749425254BFF)** @@ -49,7 +49,7 @@ List existing <%=vars.product_name%> resources such as deployed applications, di - **[list gateways](#topic_B1D89671C7B74074899C7D52F15849ED)** -Displays the gateway senders and receivers for a member or members. +Display the gateway senders and receivers for a member or members. - **[list indexes](#topic_B3B51B6DEA484EE086C4F657EC9831F2)** @@ -91,9 +91,7 @@ list async-event-queues ## list clients -Displays a list of connected clients. - -Displays a list of connected clients and the servers they are connected to. +Display a list of connected clients and the servers to which they connect. **Availability:** Online. You must be connected in `gfsh` to a JMX Manager member to use this command. @@ -116,8 +114,8 @@ gfsh>list clients ClientList -Client Name / ID | Server Name / ID -- | - + Client Name / ID | Server Name / ID + | - 192.0.2.0(4987:loner):58922:7b3398cf | member=server2,port=53508; member=server1,port=56806 192.0.2.0(5065:loner):39906:a6f598cf | member=server2,port=53508; member=server1,port=56806 ``` @@ -167,9 +165,9 @@ No JAR Files Found ## list disk-stores -List all available disk stores across the <%=vars.product_name%> cluster +List all available disk stores across the <%=vars.product_name%> cluster. -The command also lists the configured disk directories and any Regions, Cache Servers, Gateways, PDX Serialization and Async Event Queues using Disk Stores to either overflow and/or persist information to disk. Use the `describe disk-store` command to see the details for a particular Disk Store. +The command also lists the configured disk directories and any Regions, Cache Servers, Gateways, PDX Serialization and Async Event Queues using Disk Stores to either overflow and/or persist information to disk. Use the `describe disk-store` command to see the details for a particular Disk Store. **Availability:** Online. You must be connected in `gfsh` to a JMX Manager member to use this command. @@ -190,8 +188,8 @@ list disk-stores ``` pre gfsh> list disk-stores - Member Name | Member Id | Disk Store Name |Disk Store ID - -- | - | --- | + Member Name | Member Id | Disk Store Name |Disk Store ID + -- | --| --- | consumerServer | 192.0.2.0(consumerServer:13825):3545 | consumerData | 4029af26-fd82-4997-bd6c-33382cdbb5e9 consumerServer | 192.0.2.0(consumerServer:13825):3545 | observerData | 7e0316ad-963c-49b0-9b01-8f59b8d9e29e producerServer | 192.0.2.0(producerServer:13826):53764 | producerData | 4670e4eb-1c50-4465-b418-08ede3d5dbed @@ -200,9 +198,7 @@ gfsh> list disk-stores **Error Messages:** ``` pre -gfsh> list disk-stores No Disk Stores Found - ``` ## list durable-cqs @@ -249,8 +245,6 @@ server4 | cq3 **Error Messages:** ``` pre -gfsh>list durable-cqs --durable-client-id=client1 - Unable to list durable-cqs for durable-client-id : "client1" due to following reasons. N
[geode] branch develop updated (09b8b46ef2 -> 0e6d8377b4)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git from 09b8b46ef2 GEODE-8228: Use assertThat without embedded comparisons. add 0e6d8377b4 GEODE-9759: replaces double-hyphens with (#7560) No new revisions were added by this update. Summary of changes: .../use_pdx_high_level_steps.html.md.erb | 2 +- .../configuring_bucket_for_pr.html.md.erb | 2 +- .../query_grammar_and_reserved_words.html.md.erb | 2 +- .../15_minute_quickstart_gfsh.html.md.erb | 2 +- .../management_system_overview.html.md.erb | 4 +- .../failure_detection.html.md.erb | 8 +- .../implementing_authorization.html.md.erb | 2 +- .../memory_requirements_for_cache_data.html.md.erb | 2 +- .../gfsh/command-pages/alter.html.md.erb | 118 - .../gfsh/command-pages/backup.html.md.erb | 6 +- .../gfsh/command-pages/change.html.md.erb | 6 +- .../gfsh/command-pages/close.html.md.erb | 14 +- .../gfsh/command-pages/compact.html.md.erb | 14 +- .../gfsh/command-pages/configure.html.md.erb | 10 +- .../gfsh/command-pages/connect.html.md.erb | 32 +-- .../gfsh/command-pages/create.html.md.erb | 274 ++--- .../gfsh/command-pages/define.html.md.erb | 6 +- .../gfsh/command-pages/deploy.html.md.erb | 4 +- .../gfsh/command-pages/describe.html.md.erb| 24 +- .../gfsh/command-pages/destroy.html.md.erb | 24 +- .../gfsh/command-pages/echo.html.md.erb| 2 +- .../gfsh/command-pages/execute.html.md.erb | 14 +- .../gfsh/command-pages/export.html.md.erb | 46 ++-- .../gfsh/command-pages/gc.html.md.erb | 4 +- .../gfsh/command-pages/get.html.md.erb | 8 +- .../gfsh/command-pages/history.html.md.erb | 4 +- .../gfsh/command-pages/import.html.md.erb | 8 +- .../gfsh/command-pages/list.html.md.erb| 26 +- .../gfsh/command-pages/load-balance.html.md.erb| 2 +- .../gfsh/command-pages/locate.html.md.erb | 8 +- .../gfsh/command-pages/netstat.html.md.erb | 6 +- .../gfsh/command-pages/pause.html.md.erb | 6 +- .../gfsh/command-pages/pdx.html.md.erb | 6 +- .../gfsh/command-pages/put.html.md.erb | 10 +- .../gfsh/command-pages/rebalance.html.md.erb | 8 +- .../gfsh/command-pages/remove.html.md.erb | 6 +- .../gfsh/command-pages/resume.html.md.erb | 12 +- .../gfsh/command-pages/revoke.html.md.erb | 2 +- .../gfsh/command-pages/run.html.md.erb | 9 +- .../gfsh/command-pages/search.html.md.erb | 8 +- .../gfsh/command-pages/sh.html.md.erb | 4 +- .../gfsh/command-pages/show.html.md.erb| 24 +- .../gfsh/command-pages/shutdown.html.md.erb| 4 +- .../gfsh/command-pages/sleep.html.md.erb | 2 +- .../gfsh/command-pages/start.html.md.erb | 162 ++-- .../gfsh/command-pages/status.html.md.erb | 18 +- .../gfsh/command-pages/stop.html.md.erb| 12 +- .../gfsh/command-pages/undeploy.html.md.erb| 4 +- .../gfsh/command-pages/validate.html.md.erb| 4 +- .../gfsh/command-pages/version.html.md.erb | 2 +- .../using_bind_addresses.html.md.erb | 4 +- 51 files changed, 495 insertions(+), 496 deletions(-)
[geode] branch support/1.12 updated: GEODE-10232: reformat list for more reliable rendering (#7581)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.12 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.12 by this push: new 976a0a1b07 GEODE-10232: reformat list for more reliable rendering (#7581) 976a0a1b07 is described below commit 976a0a1b07cffa345b81e5533e08c4e246ae75b9 Author: Dave Barnes AuthorDate: Tue Apr 12 11:56:00 2022 -0700 GEODE-10232: reformat list for more reliable rendering (#7581) --- .../function_exec/how_function_execution_works.html.md.erb| 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb b/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb index 365e2bb17c..834db7aeaf 100644 --- a/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb +++ b/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb @@ -25,13 +25,13 @@ You can execute data-independent functions or data-dependent functions in <%=var **For Data-independent Functions** -- **On a specific member or members—**Execute the function within a peer-to-peer cluster, specifying the member or members where you want to run the function by using `FunctionService` methods `onMember()` and `onMembers()`. -- **On a specific server or set of servers—**If you are connected to a cluster as a client, you can execute the function on a server or servers configured for a specific connection pool, or on a server or servers connected to a given cache using the default connection pool. For data-independent functions on client/server architectures, a client invokes `FunctionService` methods `onServer()` or `onServers()`. (See [How Client/Server Connections Work](../../topologies_and_comm/topology_c [...] -- **On member groups or on a single member within each member group—**You can organize members into logical member groups. (See [Configuring and Running a Cluster](../../configuring/chapter_overview.html#concept_lrh_gyq_s4) for more information about using member groups.) You can invoke a data independent function on all members in a specified member group or member groups, or execute the function on only one member of each specified member group. +- **On a specific member or members:** Execute the function within a peer-to-peer cluster, specifying the member or members where you want to run the function by using `FunctionService` methods `onMember()` and `onMembers()`. +- **On a specific server or set of servers:** If you are connected to a cluster as a client, you can execute the function on a server or servers configured for a specific connection pool, or on a server or servers connected to a given cache using the default connection pool. For data-independent functions on client/server architectures, a client invokes `FunctionService` methods `onServer()` or `onServers()`. (See [How Client/Server Connections Work](../../topologies_and_comm/topology_ [...] +- **On member groups or on a single member within each member group:** You can organize members into logical member groups. (See [Configuring and Running a Cluster](../../configuring/chapter_overview.html#concept_lrh_gyq_s4) for more information about using member groups.) You can invoke a data independent function on all members in a specified member group or member groups, or execute the function on only one member of each specified member group. **For Data-dependent Functions** -- **On a region—**If you are executing a data-dependent function, specify a region and, optionally, a set of keys on which to run the function. The method `FunctionService.onRegion()` directs a data-dependent function to execute on a specific region. +- **On a region:** If you are executing a data-dependent function, specify a region and, optionally, a set of keys on which to run the function. The method `FunctionService.onRegion()` directs a data-dependent function to execute on a specific region. See the `org.apache.geode.cache.execute.FunctionService` Java API documentation for more details.
[geode] branch support/1.13 updated: GEODE-10232: reformat list for more reliable rendering (#7581)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.13 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.13 by this push: new 63d500f590 GEODE-10232: reformat list for more reliable rendering (#7581) 63d500f590 is described below commit 63d500f5906ffc8dca7db0a018209e2f382c7705 Author: Dave Barnes AuthorDate: Tue Apr 12 11:56:00 2022 -0700 GEODE-10232: reformat list for more reliable rendering (#7581) --- .../function_exec/how_function_execution_works.html.md.erb| 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb b/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb index 365e2bb17c..834db7aeaf 100644 --- a/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb +++ b/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb @@ -25,13 +25,13 @@ You can execute data-independent functions or data-dependent functions in <%=var **For Data-independent Functions** -- **On a specific member or members—**Execute the function within a peer-to-peer cluster, specifying the member or members where you want to run the function by using `FunctionService` methods `onMember()` and `onMembers()`. -- **On a specific server or set of servers—**If you are connected to a cluster as a client, you can execute the function on a server or servers configured for a specific connection pool, or on a server or servers connected to a given cache using the default connection pool. For data-independent functions on client/server architectures, a client invokes `FunctionService` methods `onServer()` or `onServers()`. (See [How Client/Server Connections Work](../../topologies_and_comm/topology_c [...] -- **On member groups or on a single member within each member group—**You can organize members into logical member groups. (See [Configuring and Running a Cluster](../../configuring/chapter_overview.html#concept_lrh_gyq_s4) for more information about using member groups.) You can invoke a data independent function on all members in a specified member group or member groups, or execute the function on only one member of each specified member group. +- **On a specific member or members:** Execute the function within a peer-to-peer cluster, specifying the member or members where you want to run the function by using `FunctionService` methods `onMember()` and `onMembers()`. +- **On a specific server or set of servers:** If you are connected to a cluster as a client, you can execute the function on a server or servers configured for a specific connection pool, or on a server or servers connected to a given cache using the default connection pool. For data-independent functions on client/server architectures, a client invokes `FunctionService` methods `onServer()` or `onServers()`. (See [How Client/Server Connections Work](../../topologies_and_comm/topology_ [...] +- **On member groups or on a single member within each member group:** You can organize members into logical member groups. (See [Configuring and Running a Cluster](../../configuring/chapter_overview.html#concept_lrh_gyq_s4) for more information about using member groups.) You can invoke a data independent function on all members in a specified member group or member groups, or execute the function on only one member of each specified member group. **For Data-dependent Functions** -- **On a region—**If you are executing a data-dependent function, specify a region and, optionally, a set of keys on which to run the function. The method `FunctionService.onRegion()` directs a data-dependent function to execute on a specific region. +- **On a region:** If you are executing a data-dependent function, specify a region and, optionally, a set of keys on which to run the function. The method `FunctionService.onRegion()` directs a data-dependent function to execute on a specific region. See the `org.apache.geode.cache.execute.FunctionService` Java API documentation for more details.
[geode] branch support/1.14 updated: GEODE-10232: reformat list for more reliable rendering (#7581)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.14 by this push: new bf647776cc GEODE-10232: reformat list for more reliable rendering (#7581) bf647776cc is described below commit bf647776cc3de8b845a81ea27d86532c68c7a95f Author: Dave Barnes AuthorDate: Tue Apr 12 11:56:00 2022 -0700 GEODE-10232: reformat list for more reliable rendering (#7581) --- .../function_exec/how_function_execution_works.html.md.erb| 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb b/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb index 365e2bb17c..834db7aeaf 100644 --- a/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb +++ b/geode-docs/developing/function_exec/how_function_execution_works.html.md.erb @@ -25,13 +25,13 @@ You can execute data-independent functions or data-dependent functions in <%=var **For Data-independent Functions** -- **On a specific member or members—**Execute the function within a peer-to-peer cluster, specifying the member or members where you want to run the function by using `FunctionService` methods `onMember()` and `onMembers()`. -- **On a specific server or set of servers—**If you are connected to a cluster as a client, you can execute the function on a server or servers configured for a specific connection pool, or on a server or servers connected to a given cache using the default connection pool. For data-independent functions on client/server architectures, a client invokes `FunctionService` methods `onServer()` or `onServers()`. (See [How Client/Server Connections Work](../../topologies_and_comm/topology_c [...] -- **On member groups or on a single member within each member group—**You can organize members into logical member groups. (See [Configuring and Running a Cluster](../../configuring/chapter_overview.html#concept_lrh_gyq_s4) for more information about using member groups.) You can invoke a data independent function on all members in a specified member group or member groups, or execute the function on only one member of each specified member group. +- **On a specific member or members:** Execute the function within a peer-to-peer cluster, specifying the member or members where you want to run the function by using `FunctionService` methods `onMember()` and `onMembers()`. +- **On a specific server or set of servers:** If you are connected to a cluster as a client, you can execute the function on a server or servers configured for a specific connection pool, or on a server or servers connected to a given cache using the default connection pool. For data-independent functions on client/server architectures, a client invokes `FunctionService` methods `onServer()` or `onServers()`. (See [How Client/Server Connections Work](../../topologies_and_comm/topology_ [...] +- **On member groups or on a single member within each member group:** You can organize members into logical member groups. (See [Configuring and Running a Cluster](../../configuring/chapter_overview.html#concept_lrh_gyq_s4) for more information about using member groups.) You can invoke a data independent function on all members in a specified member group or member groups, or execute the function on only one member of each specified member group. **For Data-dependent Functions** -- **On a region—**If you are executing a data-dependent function, specify a region and, optionally, a set of keys on which to run the function. The method `FunctionService.onRegion()` directs a data-dependent function to execute on a specific region. +- **On a region:** If you are executing a data-dependent function, specify a region and, optionally, a set of keys on which to run the function. The method `FunctionService.onRegion()` directs a data-dependent function to execute on a specific region. See the `org.apache.geode.cache.execute.FunctionService` Java API documentation for more details.
[geode] branch develop updated (7965968003 -> ce975a0c1c)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git from 7965968003 GEODE-10204: Add Test Coverage for SizeableByteArrayList (#7566) add ce975a0c1c GEODE-10232: reformat list for more reliable rendering (#7581) No new revisions were added by this update. Summary of changes: .../function_exec/how_function_execution_works.html.md.erb| 8 1 file changed, 4 insertions(+), 4 deletions(-)
[geode-site] branch asf-site updated: GEODE-10205: Correct Java API method from getDiskStore to findDiskStore (#16)
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 924d3555 GEODE-10205: Correct Java API method from getDiskStore to
findDiskStore (#16)
924d3555 is described below
commit 924d3555c8265b8c5e2a7ad93547ba6f12f73109
Author: Max Hufnagel
AuthorDate: Tue Apr 5 16:34:28 2022 -0700
GEODE-10205: Correct Java API method from getDiskStore to findDiskStore
(#16)
---
docs/guide/114/managing/disk_storage/compacting_disk_stores.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/guide/114/managing/disk_storage/compacting_disk_stores.html
b/docs/guide/114/managing/disk_storage/compacting_disk_stores.html
index 0c9c3a59..0a9f63ae 100644
--- a/docs/guide/114/managing/disk_storage/compacting_disk_stores.html
+++ b/docs/guide/114/managing/disk_storage/compacting_disk_stores.html
@@ -2708,7 +2708,7 @@ See Disk Sto
Compact the logs for a single online disk store through the API, with
the forceCompaction method. This method first rolls the oplogs and
then compacts them. Example:
-myCache.getDiskStore("myDiskStore").forceCompaction();
+myCache.findDiskStore("myDiskStore").forceCompaction();
Using gfsh, compact a disk store with the compact
disk-store command. Examples:
gfshcompact disk-store --name=Disk1
[geode] branch develop updated (b5e710e -> 1d2f4a6)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git. from b5e710e GEODE-10199: Make retried putIfAbsent work (#7520) add 1d2f4a6 GEODE-9568 Update Bookbindery gem (#7541) No new revisions were added by this update. Summary of changes: geode-book/Gemfile.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
[geode] branch develop updated (fb17fe4 -> c1f3402)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git. from fb17fe4 GEODE-10171: Update versioning for no-op operations (#7527) add c1f3402 GEM-3405 Correct Java API method (#7534) No new revisions were added by this update. Summary of changes: geode-docs/managing/disk_storage/compacting_disk_stores.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
[geode] branch develop updated: GEODE-9568-User-Guide-script-keeps-generated-files (#7518)
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/develop by this push:
new 8828173 GEODE-9568-User-Guide-script-keeps-generated-files (#7518)
8828173 is described below
commit 88281735a48cf46d6682e7ca444eecbf339e681b
Author: Max Hufnagel
AuthorDate: Wed Mar 30 20:58:35 2022 -0700
GEODE-9568-User-Guide-script-keeps-generated-files (#7518)
Add explanation: What to do with the generated files
---
geode-book/README.md | 26 ++
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/geode-book/README.md b/geode-book/README.md
index 07c8569..01eb967 100644
--- a/geode-book/README.md
+++ b/geode-book/README.md
@@ -3,11 +3,11 @@
This document contains instructions for building and viewing the Apache Geode
User Guide locally and moving the built guide to the Apache Geode website for
publication.
- [About](#about)
-- [Automatic build](#automatic-build)
-- [Manual build](#manual-build)
- - [Prerequisites](#prerequisites)
- - [Bookbinder Usage](#bookbinder-usage)
- - [Building the Documentation](#building-the-documentation)
+- [Preview the User Guide](#preview-the-user-guide)
+- [Build the User Guide](#build-the-user-guide)
+ - [Prerequisites](#prerequisites)
+ - [Bookbinder Usage](#bookbinder-usage)
+ - [Building the Documentation](#building-the-documentation)
- [Publishing the User Guide to the Geode
Website](#publishing-the-user-guide-to-the-geode-website)
## About
@@ -41,8 +41,18 @@ Use Ctrl-C to stop
```
You will find the user guide at `0.0.0.0:9292`.
-Files generated by Bookbinder will be at
`{geode-project-dir}/geode-book/final_app`
-
+You can find the files generated by Bookbinder at
`{geode-project-dir}/geode-book/final_app`.
+To view the generated files after exiting the `preview-user-guide.sh` script:
+
+1. Run Rackup from the `final_app` directory.
+2. In a web browser, open http://localhost:9292.
+
+Example:
+```
+$ cd {geode-project-dir}/geode-book/final_app
+$ bundle exec rackup
+```
+
## Build the User Guide
@@ -91,4 +101,4 @@ For Geode, a preconfigured **book** is provided in the
directory `{geode-project
Once you have reviewed your local build of the User Guide, you can publish it
by copying it to the Apache Geode website. The target directory should contain
a Geode version number.
-To copy the User Guide to the website repo, follow the instructions in the
`README.md` file on the *master* branch of the geode-site repo ([github:
https://github.com/apache/geode-site](https://github.com/apache/geode-site))
under the topic **Add a new user guide**.
+To copy the User Guide to the website repository, follow the instructions in
the `README.md` file on the *master* branch of the geode-site repository
([github:
https://github.com/apache/geode-site](https://github.com/apache/geode-site))
under the topic **Add a new user guide**.
[geode] branch develop updated (dfedcbd -> 5272cbb)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git. from dfedcbd GEODE-10140: Opens/exports for QueryResultFormatter tests (#7481) add 5272cbb user guide: typo repair in troubleshooting section (#7508) No new revisions were added by this update. Summary of changes: .../managing/troubleshooting/log_messages_and_solutions.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
[geode] branch develop updated (9b23510 -> 09ea856)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git. from 9b23510 GEODE-10164: Revert wording change in rebalance result (#7490) add 09ea856 GEODE-10172: User Guide: Escape braces and angle brackets for format consistency (#7495) No new revisions were added by this update. Summary of changes: geode-docs/rest_apps/rest_functions.html.md.erb | 2 +- geode-docs/rest_apps/rest_queries.html.md.erb | 6 +++--- geode-docs/rest_apps/rest_regions.html.md.erb | 26 - 3 files changed, 17 insertions(+), 17 deletions(-)
[geode-site] branch asf-site updated: GEODE-10510: User guide updates - alter runtime command and change loglevel command docs bug & improvements
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/geode-site.git The following commit(s) were added to refs/heads/asf-site by this push: new 5ac455f GEODE-10510: User guide updates - alter runtime command and change loglevel command docs bug & improvements 5ac455f is described below commit 5ac455fd0e713c4bbd5c8113d5dd410d9c4d08ce Author: Dave Barnes AuthorDate: Wed Mar 23 12:22:33 2022 -0700 GEODE-10510: User guide updates - alter runtime command and change loglevel command docs bug & improvements --- .../socket_communication_have_enough_sockets.html| 2 +- docs/guide/112/tools_modules/gfsh/command-pages/alter.html | 12 docs/guide/112/tools_modules/gfsh/command-pages/change.html | 10 ++ .../socket_communication_have_enough_sockets.html| 2 +- docs/guide/113/tools_modules/gfsh/command-pages/alter.html | 12 docs/guide/113/tools_modules/gfsh/command-pages/change.html | 10 ++ docs/guide/114/tools_modules/gfsh/command-pages/alter.html | 12 docs/guide/114/tools_modules/gfsh/command-pages/change.html | 10 ++ .../socket_communication_have_enough_sockets.html| 2 +- .../guide/latest/tools_modules/gfsh/command-pages/alter.html | 12 .../latest/tools_modules/gfsh/command-pages/change.html | 10 ++ 11 files changed, 59 insertions(+), 35 deletions(-) diff --git a/docs/guide/112/managing/monitor_tune/socket_communication_have_enough_sockets.html b/docs/guide/112/managing/monitor_tune/socket_communication_have_enough_sockets.html index 1815e67..dc3819a 100644 --- a/docs/guide/112/managing/monitor_tune/socket_communication_have_enough_sockets.html +++ b/docs/guide/112/managing/monitor_tune/socket_communication_have_enough_sockets.html @@ -2649,7 +2649,7 @@ recommend that you set conserve-sockets to false. You can force the release of an idle socket connection for peer-to-peer and client-to-server connections: - 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. + 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 closes that socket. The next time the thread needs a socket, it creates a new socket. Client. For client connections, you can affect the same lease-time behavior by setting the pool idle-timeout. diff --git a/docs/guide/112/tools_modules/gfsh/command-pages/alter.html b/docs/guide/112/tools_modules/gfsh/command-pages/alter.html index d27876e..3ce1ed8 100644 --- a/docs/guide/112/tools_modules/gfsh/command-pages/alter.html +++ b/docs/guide/112/tools_modules/gfsh/command-pages/alter.html @@ -3089,7 +3089,11 @@ server1 | Region "/customer" altered on "server1" alter runtime -Alters configuration properties for all members or a subset of members while the member or members are running. +Alters configuration properties for all servers or a subset of servers while the member or members are running. +Alter runtime is a cluster configuration command that affects the configuration for newly joining servers. +In order for running members to adopt the alteration, they must be stopped and restarted. + +The alter runtime command does not apply to locators. For more information on these configuration properties, see cache.xml and configuration parameter reference. @@ -3151,7 +3155,7 @@ server1 | Region "/customer" altered on "server1" 0 -loglevel +log-level 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. INFO @@ -3200,11 +3204,11 @@ Valid values are: ALL, TRACE, DEBUG, Example Commands: -alter runtime --members=server1 --loglevel=WARN --enable-statistics=true +alter runtime --members=server1 --log-level=WARN --enable-statistics=true Sample Output: -gfshalter runtime --members=server1 --loglevel=WARN --enable-statistics=true +gfshalter runtime --members=server1 --log-level=WARN --enable-statistics=true Runtime configuration altered successfully for the following member(s) 192.0.2.0(server1:240)v1:64871 diff --git a/docs/guide/112/tools_modules/gfsh/command-pages/change.html b/docs/guide/112/tools_modules/gfsh/command-pages/change.html index 9d71ede..9767847 100644 --- a/docs/guide/112/tools_modules/gfsh/command-pages/change.html +++ b
[geode] branch support/1.12 updated: GEODE-10150: alter runtime command and change loglevel command docs bug & improvements (#7474)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.12 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.12 by this push: new f57421d GEODE-10150: alter runtime command and change loglevel command docs bug & improvements (#7474) f57421d is described below commit f57421d909872834dd94e311948843cd9f47a916 Author: Dave Barnes AuthorDate: Wed Mar 23 08:39:17 2022 -0700 GEODE-10150: alter runtime command and change loglevel command docs bug & improvements (#7474) --- .../tools_modules/gfsh/command-pages/alter.html.md.erb | 12 .../tools_modules/gfsh/command-pages/change.html.md.erb | 10 ++ 2 files changed, 14 insertions(+), 8 deletions(-) diff --git a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb index dbb7223..69703b8 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb @@ -463,7 +463,11 @@ server1 | Region "/customer" altered on "server1" ## alter runtime -Alters configuration properties for all members or a subset of members while the member or members are running. +Alters configuration properties for all servers or a subset of servers while the member or members are running. +Alter runtime is a cluster configuration command that affects the configuration for newly joining servers. +In order for running members to adopt the alteration, they must be stopped and restarted. + +The alter runtime command does not apply to locators. For more information on these configuration properties, see [cache.xml](../../../reference/topics/chapter_overview_cache_xml.html#cache_xml) and configuration parameter reference. @@ -527,7 +531,7 @@ alter runtime [--members=value(,value)*] [--groups=value(,value)*] 0 -\-\-loglevel +\-\-log-level 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`. INFO @@ -578,13 +582,13 @@ Valid values are: `ALL`, `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `FATAL`, `OF **Example Commands:** ``` pre -alter runtime --members=server1 --loglevel=WARN --enable-statistics=true +alter runtime --members=server1 --log-level=WARN --enable-statistics=true ``` **Sample Output:** ``` pre -gfsh>alter runtime --members=server1 --loglevel=WARN --enable-statistics=true +gfsh>alter runtime --members=server1 --log-level=WARN --enable-statistics=true Runtime configuration altered successfully for the following member(s) 192.0.2.0(server1:240):64871 ``` diff --git a/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb index 50ad246..e4c65a7 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb @@ -22,12 +22,14 @@ limitations under the License. Changes the logging level on specified members. +The `change loglevel` command applies only to the members specified, whether they are servers or locators. The change does not apply to unspecified or subsequently-added members. + **Availability:** Online. You must be connected in `gfsh` to a JMX Manager member to use this command. **Syntax:** ``` pre -change loglevel --loglevel=value [--members=value(,value)*] [--groups=value(,value)*] +change loglevel --log-level=value [--members=value(,value)*] [--groups=value(,value)*] ``` @@ -58,7 +60,7 @@ change loglevel --loglevel=value [--members=value(,value)*] [--groups=value(,val -\-\-loglevel +\-\-log-level Required. Log level to change. Valid options are: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF. @@ -72,13 +74,13 @@ change loglevel --loglevel=value [--members=value(,value)*] [--groups=value(,val **Example Commands:** ``` pre -gfsh>change loglevel --loglevel=DEBUG --members=server1 +gfsh>change loglevel --log-level=DEBUG --members=server1 ``` **Sample Output:** ``` pre -gfsh>change loglevel --loglevel=DEBUG --members=server1 +gfsh>change loglevel --log-level=DEBUG --members=server1 Summary
[geode] branch support/1.13 updated: GEODE-10150: alter runtime command and change loglevel command docs bug & improvements (#7474)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.13 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.13 by this push: new 8ac3d82 GEODE-10150: alter runtime command and change loglevel command docs bug & improvements (#7474) 8ac3d82 is described below commit 8ac3d8217ab51910ba4199b0ef4eca61ebb96fe4 Author: Dave Barnes AuthorDate: Wed Mar 23 08:39:17 2022 -0700 GEODE-10150: alter runtime command and change loglevel command docs bug & improvements (#7474) --- .../tools_modules/gfsh/command-pages/alter.html.md.erb | 12 .../tools_modules/gfsh/command-pages/change.html.md.erb | 10 ++ 2 files changed, 14 insertions(+), 8 deletions(-) diff --git a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb index dbb7223..69703b8 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb @@ -463,7 +463,11 @@ server1 | Region "/customer" altered on "server1" ## alter runtime -Alters configuration properties for all members or a subset of members while the member or members are running. +Alters configuration properties for all servers or a subset of servers while the member or members are running. +Alter runtime is a cluster configuration command that affects the configuration for newly joining servers. +In order for running members to adopt the alteration, they must be stopped and restarted. + +The alter runtime command does not apply to locators. For more information on these configuration properties, see [cache.xml](../../../reference/topics/chapter_overview_cache_xml.html#cache_xml) and configuration parameter reference. @@ -527,7 +531,7 @@ alter runtime [--members=value(,value)*] [--groups=value(,value)*] 0 -\-\-loglevel +\-\-log-level 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`. INFO @@ -578,13 +582,13 @@ Valid values are: `ALL`, `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `FATAL`, `OF **Example Commands:** ``` pre -alter runtime --members=server1 --loglevel=WARN --enable-statistics=true +alter runtime --members=server1 --log-level=WARN --enable-statistics=true ``` **Sample Output:** ``` pre -gfsh>alter runtime --members=server1 --loglevel=WARN --enable-statistics=true +gfsh>alter runtime --members=server1 --log-level=WARN --enable-statistics=true Runtime configuration altered successfully for the following member(s) 192.0.2.0(server1:240):64871 ``` diff --git a/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb index 806afc0..ecf3ac8 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb @@ -24,12 +24,14 @@ Changes the logging level on specified members. This command takes effect if the When using a custom `Log4J` configuration, this command takes effect only if the member whose logging level you want to change was started using the `--J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS` system property. +The `change loglevel` command applies only to the members specified, whether they are servers or locators. The change does not apply to unspecified or subsequently-added members. + **Availability:** Online. You must be connected in `gfsh` to a JMX Manager member to use this command. **Syntax:** ``` pre -change loglevel --loglevel=value [--members=value(,value)*] [--groups=value(,value)*] +change loglevel --log-level=value [--members=value(,value)*] [--groups=value(,value)*] ``` @@ -60,7 +62,7 @@ change loglevel --loglevel=value [--members=value(,value)*] [--groups=value(,val -\-\-loglevel +\-\-log-level Required. Log level to change. Valid options are: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF. @@ -74,13 +76,13 @@ change loglevel --loglevel=value [--members=value(,value)*] [--groups=value(,val **Example Commands:** ``` pre -gfsh>change loglevel --loglevel=DEBUG --members=server1 +gfsh>change loglevel --log-level=DEBUG --members=server1 ``` **Sample Output:** ``` pre -gfsh>change loglevel --loglevel=DEBUG --members=server1 +gfsh>change loglevel --log-level=DEBUG --members=server1 Summary
[geode] branch support/1.14 updated: GEODE-10150: alter runtime command and change loglevel command docs bug & improvements (#7474)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.14 by this push: new 90b1633 GEODE-10150: alter runtime command and change loglevel command docs bug & improvements (#7474) 90b1633 is described below commit 90b163317420492e8fdd29ec1c10658d049d0ef7 Author: Dave Barnes AuthorDate: Wed Mar 23 08:39:17 2022 -0700 GEODE-10150: alter runtime command and change loglevel command docs bug & improvements (#7474) --- .../tools_modules/gfsh/command-pages/alter.html.md.erb | 12 .../tools_modules/gfsh/command-pages/change.html.md.erb | 10 ++ 2 files changed, 14 insertions(+), 8 deletions(-) diff --git a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb index 98e681c..da9d64f 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb @@ -463,7 +463,11 @@ server1 | Region "/customer" altered on "server1" ## alter runtime -Alters configuration properties for all members or a subset of members while the member or members are running. +Alters configuration properties for all servers or a subset of servers while the member or members are running. +Alter runtime is a cluster configuration command that affects the configuration for newly joining servers. +In order for running members to adopt the alteration, they must be stopped and restarted. + +The alter runtime command does not apply to locators. For more information on these configuration properties, see [cache.xml](../../../reference/topics/chapter_overview_cache_xml.html#cache_xml) and configuration parameter reference. @@ -527,7 +531,7 @@ alter runtime [--members=value(,value)*] [--groups=value(,value)*] 0 -\-\-loglevel +\-\-log-level 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`. INFO @@ -578,13 +582,13 @@ Valid values are: `ALL`, `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `FATAL`, `OF **Example Commands:** ``` pre -alter runtime --members=server1 --loglevel=WARN --enable-statistics=true +alter runtime --members=server1 --log-level=WARN --enable-statistics=true ``` **Sample Output:** ``` pre -gfsh>alter runtime --members=server1 --loglevel=WARN --enable-statistics=true +gfsh>alter runtime --members=server1 --log-level=WARN --enable-statistics=true Runtime configuration altered successfully for the following member(s) 192.0.2.0(server1:240):64871 ``` diff --git a/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb index 806afc0..ecf3ac8 100644 --- a/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb +++ b/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb @@ -24,12 +24,14 @@ Changes the logging level on specified members. This command takes effect if the When using a custom `Log4J` configuration, this command takes effect only if the member whose logging level you want to change was started using the `--J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS` system property. +The `change loglevel` command applies only to the members specified, whether they are servers or locators. The change does not apply to unspecified or subsequently-added members. + **Availability:** Online. You must be connected in `gfsh` to a JMX Manager member to use this command. **Syntax:** ``` pre -change loglevel --loglevel=value [--members=value(,value)*] [--groups=value(,value)*] +change loglevel --log-level=value [--members=value(,value)*] [--groups=value(,value)*] ``` @@ -60,7 +62,7 @@ change loglevel --loglevel=value [--members=value(,value)*] [--groups=value(,val -\-\-loglevel +\-\-log-level Required. Log level to change. Valid options are: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF. @@ -74,13 +76,13 @@ change loglevel --loglevel=value [--members=value(,value)*] [--groups=value(,val **Example Commands:** ``` pre -gfsh>change loglevel --loglevel=DEBUG --members=server1 +gfsh>change loglevel --log-level=DEBUG --members=server1 ``` **Sample Output:** ``` pre -gfsh>change loglevel --loglevel=DEBUG --members=server1 +gfsh>change loglevel --log-level=DEBUG --members=server1 Summary
[geode] branch develop updated (6b43b76 -> d3d6915)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git. from 6b43b76 GEODE-10048: Add framework for Redis events and BLPOP command (#7408) add d3d6915 GEODE-10150: alter runtime command and change loglevel command docs bug & improvements (#7474) No new revisions were added by this update. Summary of changes: .../tools_modules/gfsh/command-pages/alter.html.md.erb | 12 .../tools_modules/gfsh/command-pages/change.html.md.erb | 10 ++ 2 files changed, 14 insertions(+), 8 deletions(-)
[geode-site] branch master updated: Update for 1.14.4 release
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/master by this push:
new 5771745 Update for 1.14.4 release
5771745 is described below
commit 57717454f59415b5c274684fb3d038ad50a7dc6d
Author: Dave Barnes
AuthorDate: Thu Mar 17 15:23:23 2022 -0700
Update for 1.14.4 release
---
website/content/releases/index.html | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/website/content/releases/index.html
b/website/content/releases/index.html
index e1b777a..b094097 100644
--- a/website/content/releases/index.html
+++ b/website/content/releases/index.html
@@ -34,39 +34,39 @@ under the License. -->
-
-1.14.3
+
+1.14.4
-https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.14.3;>Release
Notes
+https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.14.4;>Release
Notes
Binaries
- [https://apache.org/dyn/closer.cgi/geode/1.14.3/apache-geode-1.14.3.tgz;>TGZ,
https://downloads.apache.org/geode/1.14.3/apache-geode-1.14.3.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.14.3/apache-geode-1.14.3.tgz.asc;>PGP
]
+ [https://apache.org/dyn/closer.cgi/geode/1.14.4/apache-geode-1.14.4.tgz;>TGZ,
https://downloads.apache.org/geode/1.14.4/apache-geode-1.14.4.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.14.4/apache-geode-1.14.4.tgz.asc;>PGP
]
Source
- [https://apache.org/dyn/closer.cgi/geode/1.14.3/apache-geode-1.14.3-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.14.3/apache-geode-1.14.3-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.14.3/apache-geode-1.14.3-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.14.4/apache-geode-1.14.4-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.14.4/apache-geode-1.14.4-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.14.4/apache-geode-1.14.4-src.tgz.asc;>PGP
]
Geode Native Source
- [https://apache.org/dyn/closer.cgi/geode/1.14.3/apache-geode-native-1.14.3-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.14.3/apache-geode-native-1.14.3-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.14.3/apache-geode-native-1.14.3-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.14.4/apache-geode-native-1.14.4-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.14.4/apache-geode-native-1.14.4-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.14.4/apache-geode-native-1.14.4-src.tgz.asc;>PGP
]
Benchmarks
- [https://apache.org/dyn/closer.cgi/geode/1.14.3/apache-geode-benchmarks-1.14.3-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.14.3/apache-geode-benchmarks-1.14.3-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.14.3/apache-geode-benchmarks-1.14.3-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.14.4/apache-geode-benchmarks-1.14.4-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.14.4/apache-geode-benchmarks-1.14.4-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.14.4/apache-geode-benchmarks-1.14.4-src.tgz.asc;>PGP
]
Examples
- [https://apache.org/dyn/closer.cgi/geode/1.14.3/apache-geode-examples-1.14.3-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.14.3/apache-geode-examples-1.14.3-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.14.3/apache-geode-examples-1.14.3-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.14.4/apache-geode-examples-1.14.4-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.14.4/apache-geode-examples-1.14.4-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.14.4/apache-geode-examples-1.14.4-src.tgz.asc;>PGP
]
@@ -75,7 +75,7 @@ under the License. -->
Gradle
dependencies {
- compile 'org.apache.geode:geode-core:1.14.3'
+ compile 'org.apache.geode:geode-core:1.14.4'
}
Maven
@@ -84,12 +84,12 @@ dependencies {
dependency
groupIdorg.apache.geode/groupId
artifactIdgeode-core/artifactId
-version1.14.3/version
+version1.14.4/version
/dependency
/dependencies
-
+
1.13.8
[geode-site] branch asf-site updated: update for 1.13.8 release
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 240c890 update for 1.13.8 release
240c890 is described below
commit 240c8908bbe091bb6194967ceb5c7fc397e2cce6
Author: Dave Barnes
AuthorDate: Tue Mar 15 15:30:28 2022 -0700
update for 1.13.8 release
---
releases/index.html | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/releases/index.html b/releases/index.html
index 431e800..a0671b1 100644
--- a/releases/index.html
+++ b/releases/index.html
@@ -168,39 +168,39 @@ dependencies {
-
-1.13.7
+
+1.13.8
-https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.7;>Release
Notes
+https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.8;>Release
Notes
Binaries
- [https://apache.org/dyn/closer.cgi/geode/1.13.7/apache-geode-1.13.7.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.7/apache-geode-1.13.7.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.13.7/apache-geode-1.13.7.tgz.asc;>PGP
]
+ [https://apache.org/dyn/closer.cgi/geode/1.13.8/apache-geode-1.13.8.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.8/apache-geode-1.13.8.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.13.8/apache-geode-1.13.8.tgz.asc;>PGP
]
Source
- [https://apache.org/dyn/closer.cgi/geode/1.13.7/apache-geode-1.13.7-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.7/apache-geode-1.13.7-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.13.7/apache-geode-1.13.7-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.13.8/apache-geode-1.13.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.8/apache-geode-1.13.8-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.13.8/apache-geode-1.13.8-src.tgz.asc;>PGP
]
Geode Native Source
- [https://apache.org/dyn/closer.cgi/geode/1.13.7/apache-geode-native-1.13.7-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.7/apache-geode-native-1.13.7-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.13.7/apache-geode-native-1.13.7-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.13.8/apache-geode-native-1.13.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.8/apache-geode-native-1.13.8-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.13.8/apache-geode-native-1.13.8-src.tgz.asc;>PGP
]
Benchmarks
- [https://apache.org/dyn/closer.cgi/geode/1.13.7/apache-geode-benchmarks-1.13.7-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.7/apache-geode-benchmarks-1.13.7-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.13.7/apache-geode-benchmarks-1.13.7-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.13.8/apache-geode-benchmarks-1.13.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.8/apache-geode-benchmarks-1.13.8-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.13.8/apache-geode-benchmarks-1.13.8-src.tgz.asc;>PGP
]
Examples
- [https://apache.org/dyn/closer.cgi/geode/1.13.7/apache-geode-examples-1.13.7-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.7/apache-geode-examples-1.13.7-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.13.7/apache-geode-examples-1.13.7-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.13.8/apache-geode-examples-1.13.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.8/apache-geode-examples-1.13.8-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.13.8/apache-geode-examples-1.13.8-src.tgz.asc;>PGP
]
@@ -209,7 +209,7 @@ dependencies {
Gradle
dependencies {
- compile 'org.apache.geode:geode-core:1.13.7'
+ compile 'org.apache.geode:geode-core:1.13.8'
}
Maven
@@ -218,12 +218,12 @@ dependencies {
dependency
groupIdorg.apache.geode/groupId
artifactIdgeode-core/artifactId
-version1.13.7/version
+version1.13.8/version
/dependency
/dependencies
-
+
1.12.9
[geode-site] branch master updated: Update for 1.13.8 release
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/master by this push:
new 7d41860 Update for 1.13.8 release
7d41860 is described below
commit 7d418602186b2fd8fb53d40c2b6d6126ef5653e7
Author: Dave Barnes
AuthorDate: Tue Mar 15 15:28:07 2022 -0700
Update for 1.13.8 release
---
website/content/releases/index.html | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/website/content/releases/index.html
b/website/content/releases/index.html
index b41e753..e1b777a 100644
--- a/website/content/releases/index.html
+++ b/website/content/releases/index.html
@@ -91,39 +91,39 @@ dependencies {
-
-1.13.7
+
+1.13.8
-https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.7;>Release
Notes
+https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.8;>Release
Notes
Binaries
- [https://apache.org/dyn/closer.cgi/geode/1.13.7/apache-geode-1.13.7.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.7/apache-geode-1.13.7.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.13.7/apache-geode-1.13.7.tgz.asc;>PGP
]
+ [https://apache.org/dyn/closer.cgi/geode/1.13.8/apache-geode-1.13.8.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.8/apache-geode-1.13.8.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.13.8/apache-geode-1.13.8.tgz.asc;>PGP
]
Source
- [https://apache.org/dyn/closer.cgi/geode/1.13.7/apache-geode-1.13.7-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.7/apache-geode-1.13.7-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.13.7/apache-geode-1.13.7-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.13.8/apache-geode-1.13.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.8/apache-geode-1.13.8-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.13.8/apache-geode-1.13.8-src.tgz.asc;>PGP
]
Geode Native Source
- [https://apache.org/dyn/closer.cgi/geode/1.13.7/apache-geode-native-1.13.7-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.7/apache-geode-native-1.13.7-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.13.7/apache-geode-native-1.13.7-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.13.8/apache-geode-native-1.13.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.8/apache-geode-native-1.13.8-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.13.8/apache-geode-native-1.13.8-src.tgz.asc;>PGP
]
Benchmarks
- [https://apache.org/dyn/closer.cgi/geode/1.13.7/apache-geode-benchmarks-1.13.7-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.7/apache-geode-benchmarks-1.13.7-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.13.7/apache-geode-benchmarks-1.13.7-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.13.8/apache-geode-benchmarks-1.13.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.8/apache-geode-benchmarks-1.13.8-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.13.8/apache-geode-benchmarks-1.13.8-src.tgz.asc;>PGP
]
Examples
- [https://apache.org/dyn/closer.cgi/geode/1.13.7/apache-geode-examples-1.13.7-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.7/apache-geode-examples-1.13.7-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.13.7/apache-geode-examples-1.13.7-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.13.8/apache-geode-examples-1.13.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.13.8/apache-geode-examples-1.13.8-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.13.8/apache-geode-examples-1.13.8-src.tgz.asc;>PGP
]
@@ -132,7 +132,7 @@ dependencies {
Gradle
dependencies {
- compile 'org.apache.geode:geode-core:1.13.7'
+ compile 'org.apache.geode:geode-core:1.13.8'
}
Maven
@@ -141,12 +141,12 @@ dependencies {
dependency
groupIdorg.apache.geode/groupId
artifactIdgeode-core/artifactId
-version1.13.7/version
+version1.13.8/version
/dependency
/dependencies
-
+
1.12.9
[geode-site] branch asf-site updated: Update for Geode 1.12.9
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 48ba6db Update for Geode 1.12.9
48ba6db is described below
commit 48ba6dbce4f41befa0514ee86670c73695035d30
Author: Dave Barnes
AuthorDate: Wed Mar 9 15:13:42 2022 -0800
Update for Geode 1.12.9
---
.htaccess | 6 +++---
releases/index.html | 32
2 files changed, 19 insertions(+), 19 deletions(-)
diff --git a/.htaccess b/.htaccess
index 204e28f..03c72fc 100755
--- a/.htaccess
+++ b/.htaccess
@@ -16,10 +16,10 @@
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
-RedirectMatch 301 /serverman/(.*) https://geode.apache.org/docs/guide/latest/$1
-RedirectMatch 301 /geodeman/(.*) https://geode.apache.org/docs/guide/latest/$1
+RedirectMatch 301 /serverman/(.*) https://geode.apache.org/docs/guide/114/$1
+RedirectMatch 301 /geodeman/(.*) https://geode.apache.org/docs/guide/114/$1
RedirectMatch 301 /cppapiref/(.*)
https://geode.apache.org/releases/latest/cppdocs/$1
RedirectMatch 301 /dotnetapiref/(.*)
https://geode.apache.org/releases/latest/dotnetdocs/$1
# Removed document versions redirect to latest, will redirect to doc index if
missing after that.
-RedirectMatch 301 /docs/guide/(?:111|110|19|18|17|16|15|14|13|12|11|10)/(.*)
https://geode.apache.org/docs/guide/latest/$1
+RedirectMatch 301 /docs/guide/(?:111|110|19|18|17|16|15|14|13|12|11|10)/(.*)
https://geode.apache.org/docs/guide/114/$1
diff --git a/releases/index.html b/releases/index.html
index ca444f8..431e800 100644
--- a/releases/index.html
+++ b/releases/index.html
@@ -225,39 +225,39 @@ dependencies {
-
-1.12.8
+
+1.12.9
-https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.8;>Release
Notes
+https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.9;>Release
Notes
Binaries
- [https://apache.org/dyn/closer.cgi/geode/1.12.8/apache-geode-1.12.8.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.8/apache-geode-1.12.8.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.12.8/apache-geode-1.12.8.tgz.asc;>PGP
]
+ [https://apache.org/dyn/closer.cgi/geode/1.12.9/apache-geode-1.12.9.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.9/apache-geode-1.12.9.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.12.9/apache-geode-1.12.9.tgz.asc;>PGP
]
Source
- [https://apache.org/dyn/closer.cgi/geode/1.12.8/apache-geode-1.12.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.8/apache-geode-1.12.8-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.12.8/apache-geode-1.12.8-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.12.9/apache-geode-1.12.9-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.9/apache-geode-1.12.9-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.12.9/apache-geode-1.12.9-src.tgz.asc;>PGP
]
Geode Native Source
- [https://apache.org/dyn/closer.cgi/geode/1.12.8/apache-geode-native-1.12.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.8/apache-geode-native-1.12.8-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.12.8/apache-geode-native-1.12.8-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.12.9/apache-geode-native-1.12.9-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.9/apache-geode-native-1.12.9-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.12.9/apache-geode-native-1.12.9-src.tgz.asc;>PGP
]
Benchmarks
- [https://apache.org/dyn/closer.cgi/geode/1.12.8/apache-geode-benchmarks-1.12.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.8/apache-geode-benchmarks-1.12.8-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.12.8/apache-geode-benchmarks-1.12.8-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.12.9/apache-geode-benchmarks-1.12.9-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.9/apache-geode-benchmarks-1.12.9-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.12.9/apache-geode-benchmarks-1.12.9-src.tgz.asc;>PGP
]
Examples
- [https://apache.org/dyn/closer.cgi/geode/1.12.8/apache-geode-examples-1.12.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.8/apache-geode-examples-1.12.8-src.tgz.sha256;>SHA-256,
- https://downloads.apac
[geode-site] branch master updated: Update for Geode 1.12.9
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/master by this push:
new 1092007 Update for Geode 1.12.9
1092007 is described below
commit 10920070e0e080b1c412f273876c6b31e7ea06a0
Author: Dave Barnes
AuthorDate: Wed Mar 9 15:12:27 2022 -0800
Update for Geode 1.12.9
---
website/content/releases/index.html | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/website/content/releases/index.html
b/website/content/releases/index.html
index 5ed4f0c..b41e753 100644
--- a/website/content/releases/index.html
+++ b/website/content/releases/index.html
@@ -148,39 +148,39 @@ dependencies {
-
-1.12.8
+
+1.12.9
-https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.8;>Release
Notes
+https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.9;>Release
Notes
Binaries
- [https://apache.org/dyn/closer.cgi/geode/1.12.8/apache-geode-1.12.8.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.8/apache-geode-1.12.8.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.12.8/apache-geode-1.12.8.tgz.asc;>PGP
]
+ [https://apache.org/dyn/closer.cgi/geode/1.12.9/apache-geode-1.12.9.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.9/apache-geode-1.12.9.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.12.9/apache-geode-1.12.9.tgz.asc;>PGP
]
Source
- [https://apache.org/dyn/closer.cgi/geode/1.12.8/apache-geode-1.12.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.8/apache-geode-1.12.8-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.12.8/apache-geode-1.12.8-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.12.9/apache-geode-1.12.9-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.9/apache-geode-1.12.9-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.12.9/apache-geode-1.12.9-src.tgz.asc;>PGP
]
Geode Native Source
- [https://apache.org/dyn/closer.cgi/geode/1.12.8/apache-geode-native-1.12.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.8/apache-geode-native-1.12.8-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.12.8/apache-geode-native-1.12.8-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.12.9/apache-geode-native-1.12.9-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.9/apache-geode-native-1.12.9-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.12.9/apache-geode-native-1.12.9-src.tgz.asc;>PGP
]
Benchmarks
- [https://apache.org/dyn/closer.cgi/geode/1.12.8/apache-geode-benchmarks-1.12.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.8/apache-geode-benchmarks-1.12.8-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.12.8/apache-geode-benchmarks-1.12.8-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.12.9/apache-geode-benchmarks-1.12.9-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.9/apache-geode-benchmarks-1.12.9-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.12.9/apache-geode-benchmarks-1.12.9-src.tgz.asc;>PGP
]
Examples
- [https://apache.org/dyn/closer.cgi/geode/1.12.8/apache-geode-examples-1.12.8-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.8/apache-geode-examples-1.12.8-src.tgz.sha256;>SHA-256,
- https://downloads.apache.org/geode/1.12.8/apache-geode-examples-1.12.8-src.tgz.asc;>PGP
+ [https://apache.org/dyn/closer.cgi/geode/1.12.9/apache-geode-examples-1.12.9-src.tgz;>TGZ,
https://downloads.apache.org/geode/1.12.9/apache-geode-examples-1.12.9-src.tgz.sha256;>SHA-256,
+ https://downloads.apache.org/geode/1.12.9/apache-geode-examples-1.12.9-src.tgz.asc;>PGP
]
@@ -189,7 +189,7 @@ dependencies {
Gradle
dependencies {
- compile 'org.apache.geode:geode-core:1.12.8'
+ compile 'org.apache.geode:geode-core:1.12.9'
}
Maven
@@ -198,12 +198,12 @@ dependencies {
dependency
groupIdorg.apache.geode/groupId
artifactIdgeode-core/artifactId
-version1.12.8/version
+version1.12.9/version
/dependency
/dependencies
-
+
Geode Kafka Connector 1.1.0
[geode-native] branch support/1.14 updated: GEODE-10062: Update Native Client Docs to minimize redirects - additions and corrections
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.14 by this push: new d924d99 GEODE-10062: Update Native Client Docs to minimize redirects - additions and corrections d924d99 is described below commit d924d995597ca05d82e7043ff8e1a942dbf0ece3 Author: Dave Barnes AuthorDate: Thu Feb 24 12:55:22 2022 -0800 GEODE-10062: Update Native Client Docs to minimize redirects - additions and corrections --- .../client-cache-ref.html.md.erb | 19 +++ .../configuring/sysprops.html.md.erb | 2 +- .../app-dev-walkthrough-cpp.html.md.erb | 2 +- .../client-cache-ref.html.md.erb | 10 +- .../configuring/sysprops.html.md.erb | 2 +- .../app-dev-walkthrough-dotnet.html.md.erb| 7 --- 6 files changed, 23 insertions(+), 19 deletions(-) diff --git a/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb b/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb index 71a0139..c993bf8 100644 --- a/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb +++ b/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb @@ -357,7 +357,7 @@ Use the `` sub-element to specify duration and expiration A partition resolver is used for single-hop access to partitioned region entries on the server side. This resolver implementation must match that of the `PartitionResolver` on the server side. -See the [API Class Reference](/apidocs/hierarchy.html) for the **PartitionResolver** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **PartitionResolver** class. For example: @@ -369,27 +369,30 @@ For example: ## \ -\ identifies a cache loader function by specifying `library-name` and `library-function-name`. -See the [API Class Reference](/apidocs/hierarchy.html) for the **CacheLoader** class. +\ identifies a cache loader function by specifying `library-function-name` and optionally a `library-name`. +Take into account that if `library-name` is not specified, the function will be looked for in the application itself. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheLoader** class. ## \ -\ identifies a cache listener function by specifying `library-name` and `library-function-name`. -See the [API Class Reference](/apidocs/hierarchy.html) for the **CacheListener** class. +\ identifies a cache listener function by specifying `library-function-name` and optionally a `library-name`. +Take into account that if `library-name` is not specified, the function will be looked for in the application itself. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheListener** class. ## \ -\ identifies a cache writer function by specifying `library-name` and `library-function-name`. -See the [API Class Reference](/apidocs/hierarchy.html) for the **CacheWriter** class. +\ identifies a cache writer function by specifying `library-function-name` and optionally a `library-name`. +Take into account that if `library-name` is not specified, the function will be looked for in the application itself. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheWriter** class. ## \ For each region, if the disk-policy attribute is set to `overflows`, a persistence-manager plug-in must perform cache-to-disk and disk-to-cache operations. -See the [API Class Reference](/apidocs/hierarchy.html) for the **PersistenceManager** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **PersistenceManager** class. \ identifies a persistence manager function by specifying `library-name` and `library-function-name`. You can also specify a set of properties to be passed to the function as parameters. diff --git a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb index 7a1ec63..a01b0b1 100644 --- a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb +++ b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb @@ -20,7 +20,7 @@ limitations under the License. --> A variety of system properties can be specified when a client connects to a distributed system, either programmatically or in a `geode.properties` file. -See `apache::geode::client::SystemProperties` in the [C++ API docs](cppdocs). +See `apache::geode::client::SystemProperties` in the [C++ API docs](<%=vars.cppapiref%>/hierarchy.html). The following settings can be configured: diff --git a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb b/docs/geode-native-docs-cpp/getting-started/ap
[geode-native] branch develop updated: GEODE-10062: Update Native Client Docs to minimize redirects - additions and corrections (#934)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/develop by this push: new 0461806 GEODE-10062: Update Native Client Docs to minimize redirects - additions and corrections (#934) 0461806 is described below commit 0461806f6dd00fdd3997c12bc181e538280c19c9 Author: Dave Barnes AuthorDate: Thu Feb 24 13:46:14 2022 -0800 GEODE-10062: Update Native Client Docs to minimize redirects - additions and corrections (#934) --- docs/geode-native-docs-cpp/client-cache-ref.html.md.erb| 10 +- docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb| 2 +- .../getting-started/app-dev-walkthrough-cpp.html.md.erb| 2 +- docs/geode-native-docs-dotnet/client-cache-ref.html.md.erb | 10 +- docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb | 2 +- .../getting-started/app-dev-walkthrough-dotnet.html.md.erb | 7 --- 6 files changed, 17 insertions(+), 16 deletions(-) diff --git a/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb b/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb index 7e398a6..250caad 100644 --- a/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb +++ b/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb @@ -364,7 +364,7 @@ Take into account that if `library-name` is not specified, the function will be A partition resolver is used for single-hop access to partitioned region entries on the server side. This resolver implementation must match that of the `PartitionResolver` on the server side. -See the [API Class Reference](/<%=vars.cppapiref_version%>/hierarchy.html) for the **PartitionResolver** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **PartitionResolver** class. For example: @@ -378,28 +378,28 @@ For example: \ identifies a cache loader function by specifying `library-function-name` and optionally a `library-name`. Take into account that if `library-name` is not specified, the function will be looked for in the application itself. -See the [API Class Reference](/<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheLoader** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheLoader** class. ## \ \ identifies a cache listener function by specifying `library-function-name` and optionally a `library-name`. Take into account that if `library-name` is not specified, the function will be looked for in the application itself. -See the [API Class Reference](/<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheListener** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheListener** class. ## \ \ identifies a cache writer function by specifying `library-function-name` and optionally a `library-name`. Take into account that if `library-name` is not specified, the function will be looked for in the application itself. -See the [API Class Reference](/<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheWriter** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheWriter** class. ## \ For each region, if the disk-policy attribute is set to `overflows`, a persistence-manager plug-in must perform cache-to-disk and disk-to-cache operations. -See the [API Class Reference](/<%=vars.cppapiref_version%>/hierarchy.html) for the **PersistenceManager** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **PersistenceManager** class. \ identifies a persistence manager function by specifying `library-function-name` and optionally a `library-name`. Take into account that if `library-name` is not specified, the function will be looked for in the application itself. diff --git a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb index 7a1ec63..a01b0b1 100644 --- a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb +++ b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb @@ -20,7 +20,7 @@ limitations under the License. --> A variety of system properties can be specified when a client connects to a distributed system, either programmatically or in a `geode.properties` file. -See `apache::geode::client::SystemProperties` in the [C++ API docs](cppdocs). +See `apache::geode::client::SystemProperties` in the [C++ API docs](<%=vars.cppapiref%>/hierarchy.html). The following settings can be configured: diff --git a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb b/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb index 13a109b..20e
[geode-native] branch feature/GEODE-10062 created (now c5d81c1)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch feature/GEODE-10062 in repository https://gitbox.apache.org/repos/asf/geode-native.git. at c5d81c1 GEODE-10062: Update Native Client Docs to minimize redirects - additions and corrections This branch includes the following new commits: new c5d81c1 GEODE-10062: Update Native Client Docs to minimize redirects - additions and corrections The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference.
[geode-native] 01/01: GEODE-10062: Update Native Client Docs to minimize redirects - additions and corrections
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch feature/GEODE-10062 in repository https://gitbox.apache.org/repos/asf/geode-native.git commit c5d81c18a1922f08d9e78fd6a422e0409342293d Author: Dave Barnes AuthorDate: Thu Feb 24 12:55:22 2022 -0800 GEODE-10062: Update Native Client Docs to minimize redirects - additions and corrections --- docs/geode-native-docs-cpp/client-cache-ref.html.md.erb| 10 +- docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb| 2 +- .../getting-started/app-dev-walkthrough-cpp.html.md.erb| 2 +- docs/geode-native-docs-dotnet/client-cache-ref.html.md.erb | 10 +- docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb | 2 +- .../getting-started/app-dev-walkthrough-dotnet.html.md.erb | 7 --- 6 files changed, 17 insertions(+), 16 deletions(-) diff --git a/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb b/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb index 7e398a6..250caad 100644 --- a/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb +++ b/docs/geode-native-docs-cpp/client-cache-ref.html.md.erb @@ -364,7 +364,7 @@ Take into account that if `library-name` is not specified, the function will be A partition resolver is used for single-hop access to partitioned region entries on the server side. This resolver implementation must match that of the `PartitionResolver` on the server side. -See the [API Class Reference](/<%=vars.cppapiref_version%>/hierarchy.html) for the **PartitionResolver** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **PartitionResolver** class. For example: @@ -378,28 +378,28 @@ For example: \ identifies a cache loader function by specifying `library-function-name` and optionally a `library-name`. Take into account that if `library-name` is not specified, the function will be looked for in the application itself. -See the [API Class Reference](/<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheLoader** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheLoader** class. ## \ \ identifies a cache listener function by specifying `library-function-name` and optionally a `library-name`. Take into account that if `library-name` is not specified, the function will be looked for in the application itself. -See the [API Class Reference](/<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheListener** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheListener** class. ## \ \ identifies a cache writer function by specifying `library-function-name` and optionally a `library-name`. Take into account that if `library-name` is not specified, the function will be looked for in the application itself. -See the [API Class Reference](/<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheWriter** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **CacheWriter** class. ## \ For each region, if the disk-policy attribute is set to `overflows`, a persistence-manager plug-in must perform cache-to-disk and disk-to-cache operations. -See the [API Class Reference](/<%=vars.cppapiref_version%>/hierarchy.html) for the **PersistenceManager** class. +See the [API Class Reference](<%=vars.cppapiref_version%>/hierarchy.html) for the **PersistenceManager** class. \ identifies a persistence manager function by specifying `library-function-name` and optionally a `library-name`. Take into account that if `library-name` is not specified, the function will be looked for in the application itself. diff --git a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb index 7a1ec63..a01b0b1 100644 --- a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb +++ b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb @@ -20,7 +20,7 @@ limitations under the License. --> A variety of system properties can be specified when a client connects to a distributed system, either programmatically or in a `geode.properties` file. -See `apache::geode::client::SystemProperties` in the [C++ API docs](cppdocs). +See `apache::geode::client::SystemProperties` in the [C++ API docs](<%=vars.cppapiref%>/hierarchy.html). The following settings can be configured: diff --git a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb b/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb index 13a109b..20e7bfd 100644 --- a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb +++ b/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb @@ -34,7 +34,7 @@ This wal
[geode-native] branch support/1.14 updated: GEODE-10062: Update Native Client Docs to minimize redirects (#931)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.14 by this push: new 8a5244a GEODE-10062: Update Native Client Docs to minimize redirects (#931) 8a5244a is described below commit 8a5244a84beca9b1561dff3281245b1724ab4ec4 Author: Dave Barnes AuthorDate: Thu Feb 24 09:03:30 2022 -0800 GEODE-10062: Update Native Client Docs to minimize redirects (#931) --- docs/geode-native-book-cpp/config.yml | 5 + docs/geode-native-book-dotnet/config.yml| 5 + docs/geode-native-docs-cpp/about-client-users-guide.html.md.erb | 2 +- .../configuring/config-client-cache.html.md.erb | 2 +- docs/geode-native-docs-cpp/configuring/configuration.html.md.erb| 2 +- .../connection-pools/subscription-properties.html.md.erb| 2 +- docs/geode-native-docs-cpp/continuous-queries.html.md.erb | 6 +++--- docs/geode-native-docs-cpp/function-execution.html.md.erb | 2 +- .../getting-started/getting-started-nc-client.html.md.erb | 6 +++--- docs/geode-native-docs-cpp/regions/regions.html.md.erb | 2 +- docs/geode-native-docs-cpp/remote-queries.html.md.erb | 4 ++-- docs/geode-native-docs-cpp/security/authentication.html.md.erb | 2 +- docs/geode-native-docs-cpp/security/security.html.md.erb| 2 +- docs/geode-native-docs-cpp/security/sslclientserver.html.md.erb | 4 ++-- .../serialization/data-serialization.html.md.erb| 2 +- docs/geode-native-docs-cpp/transactions.html.md.erb | 2 +- docs/geode-native-docs-dotnet/about-client-users-guide.html.md.erb | 2 +- .../configuring/config-client-cache.html.md.erb | 2 +- docs/geode-native-docs-dotnet/configuring/configuration.html.md.erb | 2 +- .../connection-pools/subscription-properties.html.md.erb| 2 +- docs/geode-native-docs-dotnet/continuous-queries.html.md.erb| 6 +++--- docs/geode-native-docs-dotnet/function-execution.html.md.erb| 2 +- .../getting-started/getting-started-nc-client.html.md.erb | 6 +++--- .../preserving-data/configuring-durable-nc.html.md.erb | 2 +- .../preserving-data/durable-client-messaging-req.html.md.erb| 2 +- .../preserving-data/high-availability-client-server.html.md.erb | 2 +- .../impl-cache-listeners-durable-clients.html.md.erb| 2 +- .../preserving-data/using-queue-conflation.html.md.erb | 2 +- docs/geode-native-docs-dotnet/regions/regions.html.md.erb | 2 +- docs/geode-native-docs-dotnet/remote-queries.html.md.erb| 4 ++-- docs/geode-native-docs-dotnet/security/authentication.html.md.erb | 2 +- docs/geode-native-docs-dotnet/security/security.html.md.erb | 2 +- docs/geode-native-docs-dotnet/security/sslclientserver.html.md.erb | 4 ++-- .../serialization/data-serialization.html.md.erb| 2 +- docs/geode-native-docs-dotnet/transactions.html.md.erb | 2 +- 35 files changed, 55 insertions(+), 45 deletions(-) diff --git a/docs/geode-native-book-cpp/config.yml b/docs/geode-native-book-cpp/config.yml index 1e6d091..7f030d3 100644 --- a/docs/geode-native-book-cpp/config.yml +++ b/docs/geode-native-book-cpp/config.yml @@ -45,5 +45,10 @@ template_variables: book_title_short: Geode Native C++ Docs local_header_title: Apache Geode Native C++ local_header_img: /images/Apache_Geode_logo_symbol.png + serverman: https://geode.apache.org/docs/guide/latest + geodeman: https://geode.apache.org/docs/guide/latest + cppapiref: https://geode.apache.org/releases/latest/cppdocs/ + dotnetapiref: https://geode.apache.org/releases/latest/dotnetdocs/ + javaapiref: https://geode.apache.org/releases/latest/javadoc/index.html broken_link_exclusions: iefix|using_custom_classes|arrowhead|cppdocs|dotnetdocs|# diff --git a/docs/geode-native-book-dotnet/config.yml b/docs/geode-native-book-dotnet/config.yml index 40ac6ff..39c93c7 100644 --- a/docs/geode-native-book-dotnet/config.yml +++ b/docs/geode-native-book-dotnet/config.yml @@ -45,5 +45,10 @@ template_variables: book_title_short: Geode Native .NET Docs local_header_title: Apache Geode Native .NET local_header_img: /images/Apache_Geode_logo_symbol.png + serverman: https://geode.apache.org/docs/guide/latest + geodeman: https://geode.apache.org/docs/guide/latest + cppapiref: https://geode.apache.org/releases/latest/cppdocs/ + dotnetapiref: https://geode.apache.org/releases/latest/dotnetdocs/ + javaapiref: https://geode.apache.org/releases/latest/javadoc/index.html broken_link_exclusions: iefix|using_custom_classes|arrowhead|cppdocs|dotnetdocs|114|# diff --git a/docs/geode-native-docs-cpp/about-client-users
[geode-native] branch develop updated: GEODE-10062: Update Native Client Docs to minimize redirects (#931)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/develop by this push: new 87891bd GEODE-10062: Update Native Client Docs to minimize redirects (#931) 87891bd is described below commit 87891bd2b3ab3741a98f2c2e7aa4d4785f05cc3f Author: Dave Barnes AuthorDate: Thu Feb 24 09:03:30 2022 -0800 GEODE-10062: Update Native Client Docs to minimize redirects (#931) --- docs/geode-native-book-cpp/config.yml | 5 + docs/geode-native-book-dotnet/config.yml| 5 + docs/geode-native-docs-cpp/about-client-users-guide.html.md.erb | 2 +- .../configuring/config-client-cache.html.md.erb | 2 +- docs/geode-native-docs-cpp/configuring/configuration.html.md.erb| 2 +- .../connection-pools/subscription-properties.html.md.erb| 2 +- docs/geode-native-docs-cpp/continuous-queries.html.md.erb | 6 +++--- docs/geode-native-docs-cpp/function-execution.html.md.erb | 2 +- .../getting-started/getting-started-nc-client.html.md.erb | 6 +++--- docs/geode-native-docs-cpp/regions/regions.html.md.erb | 2 +- docs/geode-native-docs-cpp/remote-queries.html.md.erb | 4 ++-- docs/geode-native-docs-cpp/security/authentication.html.md.erb | 2 +- docs/geode-native-docs-cpp/security/security.html.md.erb| 2 +- docs/geode-native-docs-cpp/security/sslclientserver.html.md.erb | 4 ++-- .../serialization/data-serialization.html.md.erb| 2 +- docs/geode-native-docs-cpp/transactions.html.md.erb | 2 +- docs/geode-native-docs-dotnet/about-client-users-guide.html.md.erb | 2 +- .../configuring/config-client-cache.html.md.erb | 2 +- docs/geode-native-docs-dotnet/configuring/configuration.html.md.erb | 2 +- .../connection-pools/subscription-properties.html.md.erb| 2 +- docs/geode-native-docs-dotnet/continuous-queries.html.md.erb| 6 +++--- docs/geode-native-docs-dotnet/function-execution.html.md.erb| 2 +- .../getting-started/getting-started-nc-client.html.md.erb | 6 +++--- .../preserving-data/configuring-durable-nc.html.md.erb | 2 +- .../preserving-data/durable-client-messaging-req.html.md.erb| 2 +- .../preserving-data/high-availability-client-server.html.md.erb | 2 +- .../impl-cache-listeners-durable-clients.html.md.erb| 2 +- .../preserving-data/using-queue-conflation.html.md.erb | 2 +- docs/geode-native-docs-dotnet/regions/regions.html.md.erb | 2 +- docs/geode-native-docs-dotnet/remote-queries.html.md.erb| 4 ++-- docs/geode-native-docs-dotnet/security/authentication.html.md.erb | 2 +- docs/geode-native-docs-dotnet/security/security.html.md.erb | 2 +- docs/geode-native-docs-dotnet/security/sslclientserver.html.md.erb | 4 ++-- .../serialization/data-serialization.html.md.erb| 2 +- docs/geode-native-docs-dotnet/transactions.html.md.erb | 2 +- 35 files changed, 55 insertions(+), 45 deletions(-) diff --git a/docs/geode-native-book-cpp/config.yml b/docs/geode-native-book-cpp/config.yml index ae90968..1040524 100644 --- a/docs/geode-native-book-cpp/config.yml +++ b/docs/geode-native-book-cpp/config.yml @@ -49,5 +49,10 @@ template_variables: book_title_short: Geode Native C++ Docs local_header_title: Apache Geode Native C++ local_header_img: /images/Apache_Geode_logo_symbol.png + serverman: https://geode.apache.org/docs/guide/latest + geodeman: https://geode.apache.org/docs/guide/latest + cppapiref: https://geode.apache.org/releases/latest/cppdocs/ + dotnetapiref: https://geode.apache.org/releases/latest/dotnetdocs/ + javaapiref: https://geode.apache.org/releases/latest/javadoc/index.html broken_link_exclusions: iefix|using_custom_classes|arrowhead|cppdocs|dotnetdocs|# diff --git a/docs/geode-native-book-dotnet/config.yml b/docs/geode-native-book-dotnet/config.yml index e02f681..1f2cdb9 100644 --- a/docs/geode-native-book-dotnet/config.yml +++ b/docs/geode-native-book-dotnet/config.yml @@ -49,5 +49,10 @@ template_variables: book_title_short: Geode Native .NET Docs local_header_title: Apache Geode Native .NET local_header_img: /images/Apache_Geode_logo_symbol.png + serverman: https://geode.apache.org/docs/guide/latest + geodeman: https://geode.apache.org/docs/guide/latest + cppapiref: https://geode.apache.org/releases/latest/cppdocs/ + dotnetapiref: https://geode.apache.org/releases/latest/dotnetdocs/ + javaapiref: https://geode.apache.org/releases/latest/javadoc/index.html broken_link_exclusions: iefix|using_custom_classes|arrowhead|cppdocs|dotnetdocs|# diff --git a/docs/geode-native-docs-cpp/about-client-users
[geode-site] branch asf-site updated (dbc215e -> 88d2856)
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/geode-site.git.
discard dbc215e GEODE-10078: add 'latest' link for user guide
new 88d2856 GEODE-10078: add 'latest' link for user guide
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (dbc215e)
\
N -- N -- N refs/heads/asf-site (88d2856)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/guide/{114 => latest}/CONTRIBUTE | 0
docs/guide/{114 => latest}/about_geode.html | 0
docs/guide/{114 => latest}/basic_config/book_intro.html | 0
.../basic_config/config_concepts/chapter_overview.html | 0
.../distributed_system_member_configuration.html| 0
.../basic_config/config_concepts/local_vs_remote.html | 0
.../data_entries_custom_classes/chapter_overview.html | 0
.../data_entries_custom_classes/copy_on_read.html | 0
.../data_entries_custom_classes/managing_data_entries.html | 0
.../data_entries_custom_classes/using_custom_classes.html | 0
.../basic_config/data_regions/chapter_overview.html | 0
.../data_regions/creating_custom_attributes.html| 0
.../basic_config/data_regions/managing_data_regions.html| 0
.../data_regions/managing_region_attributes.html| 0
.../basic_config/data_regions/new_region_existing_data.html | 0
.../basic_config/data_regions/region_naming.html| 0
.../basic_config/data_regions/region_shortcuts.html | 0
.../data_regions/store_retrieve_region_shortcuts.html | 0
.../gemfire_properties/setting_distributed_properties.html | 0
.../basic_config/the_cache/chapter_overview.html| 0
.../basic_config/the_cache/intro_cache_management.html | 0
.../basic_config/the_cache/managing_a_client_cache.html | 0
.../basic_config/the_cache/managing_a_multiuser_cache.html | 0
.../the_cache/managing_a_peer_server_cache.html | 0
.../basic_config/the_cache/managing_a_secure_cache.html | 0
.../basic_config/the_cache/setting_cache_initializer.html | 0
.../basic_config/the_cache/setting_cache_properties.html| 0
.../guide/{114 => latest}/configuring/chapter_overview.html | 0
.../cluster_config/deploying_application_jars.html | 0
.../configuring/cluster_config/export-import.html | 0
.../cluster_config/gfsh_config_troubleshooting.html | 0
.../configuring/cluster_config/gfsh_persist.html| 0
.../configuring/cluster_config/gfsh_remote.html | 0
.../cluster_config/persisting_configurations.html | 0
.../configuring/cluster_config/using_member_groups.html | 0
.../configuring/running/change_file_spec.html | 0
.../configuring/running/cluster-management-service.html | 0
.../configuring/running/default_file_specs.html | 0
.../configuring/running/deploy_config_files_intro.html | 0
.../configuring/running/deploying_config_files.html | 0
.../configuring/running/deploying_config_jar_files.html | 0
.../configuring/running/firewall_ports_config.html | 0
.../configuring/running/firewalls_connections.html | 0
.../configuring/running/firewalls_ports.html| 0
.../configuring/running/managing_output_files.html | 0
.../configuring/running/running_the_cacheserver.html| 0
.../configuring/running/running_the_locator.html| 0
.../configuring/running/starting_up_shutting_down.html | 0
docs/guide/{114 => latest}/developing/book_intro.html | 0
.../developing/continuous_querying/chapter_overview.html| 0
.../continuous_querying/continuous_querying_whats_next.html | 0
.../continuous_querying/how_continuous_querying_works.html | 0
.../implementing_continuous_querying.html | 0
.../data_serialization/PDX_Serialization_Features.html | 0
.../developing/data_serialization/auto_serialization.html | 0
[geode-site] branch master updated: Update README file
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/master by this push:
new 5a3e5ee Update README file
5a3e5ee is described below
commit 5a3e5ee44de5797d3c124adb7093d4bdcdcd4df7
Author: Dave Barnes
AuthorDate: Wed Feb 23 10:06:54 2022 -0800
Update README file
---
README.md | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 620b478..a055cea 100644
--- a/README.md
+++ b/README.md
@@ -126,10 +126,10 @@ The `gradlew publish` command *does not* update the `css`
and `stylesheets` dire
```
{geode-site}/docs/guide/XY
```
- where `XY` is the product version of your documentation (e.g.,
`{geode-site}/website/content/docs/guide/17` if you are publishing the
documentation for Apache Geode 1.7). So, if your current working directory is
the top level of `{geode-site}`, you would create the destination directory
with the following command:
+ where `XY` is the product version of your documentation (e.g.,
`{geode-site}/website/content/docs/guide/17` if you are publishing the
documentation for Apache Geode 1.14). So, if your current working directory is
the top level of `{geode-site}`, you would create the destination directory
with the following command:
```
-$ mkdir -p {geode-site}/docs/guide/XY
+$ mkdir -p {geode-site}/docs/guide/114
```
1. Navigate to the User Guide you have built in the Geode repository:
`{geode-project-dir}/geode-book/final_app/public/docs/guide/XY`.
@@ -149,6 +149,16 @@ The `gradlew publish` command *does not* update the `css`
and `stylesheets` dire
$ tar xvf ~/Desktop/new-guide-content.tar
```
+ - Replace the entire `docs/guide/latest` directory with a copy of the latest
user guide's directory. Use `tar` (rather than `cp`) to preserve the original
directory's structure.
+
+```
+$ cd {geode-site}/docs/guide
+$ rm -rf latest
+$ mkdir latest
+$ cd latest
+$ (cd ../XY && tar cf - *) | (tar xf -)
+```
+
### 3. Publish new javadocs
You should still be on the __asf-site__ branch. Copy new javadocs directly to
the directory
[geode-site] branch asf-site updated: GEODE-10078: add 'latest' link for user guide
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new dbc215e GEODE-10078: add 'latest' link for user guide
dbc215e is described below
commit dbc215edfaba3acc14915263cca4a3280072fea4
Author: Dave Barnes
AuthorDate: Wed Feb 23 09:54:59 2022 -0800
GEODE-10078: add 'latest' link for user guide
---
.htaccess | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/.htaccess b/.htaccess
index 03c72fc..204e28f 100755
--- a/.htaccess
+++ b/.htaccess
@@ -16,10 +16,10 @@
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
-RedirectMatch 301 /serverman/(.*) https://geode.apache.org/docs/guide/114/$1
-RedirectMatch 301 /geodeman/(.*) https://geode.apache.org/docs/guide/114/$1
+RedirectMatch 301 /serverman/(.*) https://geode.apache.org/docs/guide/latest/$1
+RedirectMatch 301 /geodeman/(.*) https://geode.apache.org/docs/guide/latest/$1
RedirectMatch 301 /cppapiref/(.*)
https://geode.apache.org/releases/latest/cppdocs/$1
RedirectMatch 301 /dotnetapiref/(.*)
https://geode.apache.org/releases/latest/dotnetdocs/$1
# Removed document versions redirect to latest, will redirect to doc index if
missing after that.
-RedirectMatch 301 /docs/guide/(?:111|110|19|18|17|16|15|14|13|12|11|10)/(.*)
https://geode.apache.org/docs/guide/114/$1
+RedirectMatch 301 /docs/guide/(?:111|110|19|18|17|16|15|14|13|12|11|10)/(.*)
https://geode.apache.org/docs/guide/latest/$1
[geode-site] branch asf-site updated: GEODE-10057: Correct geode-for-redis docs (updated v1.14 user guide)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/geode-site.git The following commit(s) were added to refs/heads/asf-site by this push: new 2ba72a9 GEODE-10057: Correct geode-for-redis docs (updated v1.14 user guide) 2ba72a9 is described below commit 2ba72a909fde0a9cb2c9b3dec2f959791b8aca21 Author: Dave Barnes AuthorDate: Wed Feb 16 11:17:45 2022 -0800 GEODE-10057: Correct geode-for-redis docs (updated v1.14 user guide) --- docs/guide/114/developing/geode_apis_compatible_with_redis.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guide/114/developing/geode_apis_compatible_with_redis.html b/docs/guide/114/developing/geode_apis_compatible_with_redis.html index cd9b6ef..f60961b 100644 --- a/docs/guide/114/developing/geode_apis_compatible_with_redis.html +++ b/docs/guide/114/developing/geode_apis_compatible_with_redis.html @@ -2865,8 +2865,8 @@ Commands not listed above are not implemented. Keys are expired in two ways, actively and passively: - With active expiration, expiration is evaluated whenever a key is accessed. If the key is due to expire, it is deleted. - With passive expiration, keys are evaluated every 3 minutes. If they are due to expire, they are deleted. + With passive expiration, expiration is evaluated whenever a key is accessed. If the key is due to expire, it is deleted. + With active expiration, keys are evaluated every 3 minutes. If they are due to expire, they are deleted. High Availability Model
[geode] branch support/1.14 updated: GEODE-10057: Correct geode-for-redis docs
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.14 by this push: new 63c98d0 GEODE-10057: Correct geode-for-redis docs 63c98d0 is described below commit 63c98d0bf76b7d8199d0fc087c2ba608227b4300 Author: Dave Barnes AuthorDate: Wed Feb 16 11:11:20 2022 -0800 GEODE-10057: Correct geode-for-redis docs --- geode-docs/developing/geode_apis_compatible_with_redis.html.md.erb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/geode-docs/developing/geode_apis_compatible_with_redis.html.md.erb b/geode-docs/developing/geode_apis_compatible_with_redis.html.md.erb index 54d995b..e438de2 100644 --- a/geode-docs/developing/geode_apis_compatible_with_redis.html.md.erb +++ b/geode-docs/developing/geode_apis_compatible_with_redis.html.md.erb @@ -183,8 +183,8 @@ These commands are supported for Redis 5. Keys are expired in two ways, actively and passively: -- With active expiration, expiration is evaluated whenever a key is accessed. If the key is due to expire, it is deleted. -- With passive expiration, keys are evaluated every 3 minutes. If they are due to expire, they are deleted. +- With passive expiration, expiration is evaluated whenever a key is accessed. If the key is due to expire, it is deleted. +- With active expiration, keys are evaluated every 3 minutes. If they are due to expire, they are deleted. ## High Availability Model
[geode] branch support/1.15 updated: GEODE-10057: Correct geode-for-redis docs (#7370)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new 8b9c03b GEODE-10057: Correct geode-for-redis docs (#7370) 8b9c03b is described below commit 8b9c03b0b867009be6d745252c57ae1a82b1eb0c Author: Donal Evans AuthorDate: Wed Feb 16 10:43:02 2022 -0800 GEODE-10057: Correct geode-for-redis docs (#7370) - Swap usage of active and passive in descriptions of expiration to match their usage in open source Redis documentation Authored-by: Donal Evans --- geode-docs/tools_modules/geode_for_redis.html.md.erb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/geode-docs/tools_modules/geode_for_redis.html.md.erb b/geode-docs/tools_modules/geode_for_redis.html.md.erb index dc6c2b9..920a9c4 100644 --- a/geode-docs/tools_modules/geode_for_redis.html.md.erb +++ b/geode-docs/tools_modules/geode_for_redis.html.md.erb @@ -238,8 +238,8 @@ integer (+/-9223372036854775807) for CURSOR. Keys are expired in two ways, actively and passively: -- With active expiration, expiration is evaluated **whenever a key is accessed**. If the key is due to expire, it is deleted. -- With passive expiration, keys are evaluated **every three minutes**. If they are due to expire, they are deleted. +- With passive expiration, expiration is evaluated **whenever a key is accessed**. If the key is due to expire, it is deleted. +- With active expiration, keys are evaluated **every three minutes**. If they are due to expire, they are deleted. ## Loss of Connections
[geode] branch develop updated (cd0b52e -> 5f79b21)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git. from cd0b52e GEODE-10047: Fix expiration interval log (#7359) add 5f79b21 GEODE-10057: Correct geode-for-redis docs (#7370) No new revisions were added by this update. Summary of changes: geode-docs/tools_modules/geode_for_redis.html.md.erb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
[geode-native] branch support/1.12 updated: Add license text to some doc sources
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.12 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.12 by this push: new 5510fa0 Add license text to some doc sources 5510fa0 is described below commit 5510fa05ebc0d61fa3be69735d47632ff10175aa Author: Dave Barnes AuthorDate: Wed Feb 9 14:44:40 2022 -0800 Add license text to some doc sources --- .../getting-started/app-dev-walkthrough-cpp.html.md.erb | 17 + .../getting-started-nc-client.html.md.erb | 17 + .../app-dev-walkthrough-dotnet.html.md.erb | 17 + .../getting-started-nc-client.html.md.erb | 17 + 4 files changed, 68 insertions(+) diff --git a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb b/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb index ddaa413..13a109b 100644 --- a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb +++ b/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb @@ -2,6 +2,23 @@ title: C++ Application Development Walkthrough --- + + This section describes how to set up a native client development environment using C++ and CMake. ## Prerequisites diff --git a/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb b/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb index a192d84..df39e90 100644 --- a/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb +++ b/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb @@ -2,6 +2,23 @@ title: Getting Started with the Native Library --- + + To use the <%=vars.product_name%> Native Library for developing <%=vars.product_name%> client applications: - Obtain a distribution of the Native library and install it on your development platform. diff --git a/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb b/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb index 7e815fe..9896edc 100644 --- a/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb +++ b/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb @@ -2,6 +2,23 @@ title: .NET Application Development Walkthrough --- + + This section describes how to set up a .NET native client development environment using C# and CMake. ## Prerequisites diff --git a/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb b/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb index 270b655..f5b019e 100644 --- a/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb +++ b/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb @@ -2,6 +2,23 @@ title: Getting Started with the Native Library --- + + To use the <%=vars.product_name%> Native Library for developing <%=vars.product_name%> client applications: - Obtain a distribution of the Native library and install it on your development platform.
[geode-native] branch support/1.13 updated: Add license text to some doc sources
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.13 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.13 by this push: new d3c9f84 Add license text to some doc sources d3c9f84 is described below commit d3c9f8413df8a0d39a56de75989d5a6327524b4e Author: Dave Barnes AuthorDate: Wed Feb 9 14:44:40 2022 -0800 Add license text to some doc sources --- .../getting-started/app-dev-walkthrough-cpp.html.md.erb | 17 + .../getting-started-nc-client.html.md.erb | 17 + .../app-dev-walkthrough-dotnet.html.md.erb | 17 + .../getting-started-nc-client.html.md.erb | 17 + 4 files changed, 68 insertions(+) diff --git a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb b/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb index ddaa413..13a109b 100644 --- a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb +++ b/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb @@ -2,6 +2,23 @@ title: C++ Application Development Walkthrough --- + + This section describes how to set up a native client development environment using C++ and CMake. ## Prerequisites diff --git a/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb b/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb index 3a6ca5d..4be7ba7 100644 --- a/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb +++ b/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb @@ -2,6 +2,23 @@ title: Getting Started with the Native Library --- + + To use the <%=vars.product_name%> Native Library for developing <%=vars.product_name%> client applications: - Obtain a distribution of the Native library and install it on your development platform. diff --git a/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb b/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb index 7e815fe..9896edc 100644 --- a/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb +++ b/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb @@ -2,6 +2,23 @@ title: .NET Application Development Walkthrough --- + + This section describes how to set up a .NET native client development environment using C# and CMake. ## Prerequisites diff --git a/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb b/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb index 270b655..f5b019e 100644 --- a/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb +++ b/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb @@ -2,6 +2,23 @@ title: Getting Started with the Native Library --- + + To use the <%=vars.product_name%> Native Library for developing <%=vars.product_name%> client applications: - Obtain a distribution of the Native library and install it on your development platform.
[geode-native] branch support/1.14 updated: Add license text to some doc sources
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.14 by this push: new 166b851 Add license text to some doc sources 166b851 is described below commit 166b8518661ff198239d7433c4c124e69b5621bb Author: Dave Barnes AuthorDate: Wed Feb 9 14:44:40 2022 -0800 Add license text to some doc sources --- .../getting-started/app-dev-walkthrough-cpp.html.md.erb | 17 + .../getting-started-nc-client.html.md.erb | 17 + .../app-dev-walkthrough-dotnet.html.md.erb | 17 + .../getting-started-nc-client.html.md.erb | 17 + 4 files changed, 68 insertions(+) diff --git a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb b/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb index ddaa413..13a109b 100644 --- a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb +++ b/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb @@ -2,6 +2,23 @@ title: C++ Application Development Walkthrough --- + + This section describes how to set up a native client development environment using C++ and CMake. ## Prerequisites diff --git a/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb b/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb index 3a6ca5d..4be7ba7 100644 --- a/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb +++ b/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb @@ -2,6 +2,23 @@ title: Getting Started with the Native Library --- + + To use the <%=vars.product_name%> Native Library for developing <%=vars.product_name%> client applications: - Obtain a distribution of the Native library and install it on your development platform. diff --git a/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb b/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb index 7e815fe..9896edc 100644 --- a/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb +++ b/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb @@ -2,6 +2,23 @@ title: .NET Application Development Walkthrough --- + + This section describes how to set up a .NET native client development environment using C# and CMake. ## Prerequisites diff --git a/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb b/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb index 1ee5324..37e9aff 100644 --- a/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb +++ b/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb @@ -2,6 +2,23 @@ title: Getting Started with the Native Library --- + + To use the <%=vars.product_name%> Native Library for developing <%=vars.product_name%> client applications: - Obtain a distribution of the Native library and install it on your development platform.
[geode-native] branch support/1.15 updated: Add license text to some doc sources
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.15 by this push: new 6b21d7f Add license text to some doc sources 6b21d7f is described below commit 6b21d7f35dd6a47c31dfd3c02600d89d12cc9c98 Author: Dave Barnes AuthorDate: Wed Feb 9 14:44:40 2022 -0800 Add license text to some doc sources --- .../getting-started/app-dev-walkthrough-cpp.html.md.erb | 17 + .../getting-started-nc-client.html.md.erb | 17 + .../app-dev-walkthrough-dotnet.html.md.erb | 17 + .../getting-started-nc-client.html.md.erb | 17 + 4 files changed, 68 insertions(+) diff --git a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb b/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb index ddaa413..13a109b 100644 --- a/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb +++ b/docs/geode-native-docs-cpp/getting-started/app-dev-walkthrough-cpp.html.md.erb @@ -2,6 +2,23 @@ title: C++ Application Development Walkthrough --- + + This section describes how to set up a native client development environment using C++ and CMake. ## Prerequisites diff --git a/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb b/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb index 3a6ca5d..4be7ba7 100644 --- a/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb +++ b/docs/geode-native-docs-cpp/getting-started/getting-started-nc-client.html.md.erb @@ -2,6 +2,23 @@ title: Getting Started with the Native Library --- + + To use the <%=vars.product_name%> Native Library for developing <%=vars.product_name%> client applications: - Obtain a distribution of the Native library and install it on your development platform. diff --git a/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb b/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb index 7e815fe..9896edc 100644 --- a/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb +++ b/docs/geode-native-docs-dotnet/getting-started/app-dev-walkthrough-dotnet.html.md.erb @@ -2,6 +2,23 @@ title: .NET Application Development Walkthrough --- + + This section describes how to set up a .NET native client development environment using C# and CMake. ## Prerequisites diff --git a/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb b/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb index 1ee5324..37e9aff 100644 --- a/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb +++ b/docs/geode-native-docs-dotnet/getting-started/getting-started-nc-client.html.md.erb @@ -2,6 +2,23 @@ title: Getting Started with the Native Library --- + + To use the <%=vars.product_name%> Native Library for developing <%=vars.product_name%> client applications: - Obtain a distribution of the Native library and install it on your development platform.
[geode-native] branch support/1.15 updated: GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.15 by this push: new 0b46698 GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921) 0b46698 is described below commit 0b46698c7a0be115256d0e44d5614afa957ac071 Author: Dave Barnes AuthorDate: Wed Feb 9 11:05:03 2022 -0800 GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921) --- docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb| 2 +- docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb index 96a7868..7a1ec63 100644 --- a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb +++ b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb @@ -212,7 +212,7 @@ When the chunk handler is not operative (enable-chunk-handler=false), each appli enable-time-statistics -Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. See System Statistics. +Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default./td> false diff --git a/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb b/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb index d214243..f6cbf51 100644 --- a/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb +++ b/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb @@ -212,7 +212,7 @@ When the chunk handler is not operative (enable-chunk-handler=false), each appli enable-time-statistics -Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. See System Statistics. +Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. false
[geode-native] branch support/1.12 updated: GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.12 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.12 by this push: new af4922d GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921) af4922d is described below commit af4922d53aad235fbc106bae512db072c21521ee Author: Dave Barnes AuthorDate: Wed Feb 9 11:05:03 2022 -0800 GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921) --- docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb| 2 +- docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb index 27037ab..ef05ebc 100644 --- a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb +++ b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb @@ -212,7 +212,7 @@ When the chunk handler is not operative (enable-chunk-handler=false), each appli enable-time-statistics -Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. See System Statistics. +Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default./td> false diff --git a/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb b/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb index d214243..f6cbf51 100644 --- a/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb +++ b/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb @@ -212,7 +212,7 @@ When the chunk handler is not operative (enable-chunk-handler=false), each appli enable-time-statistics -Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. See System Statistics. +Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. false
[geode-native] branch support/1.13 updated: GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.13 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.13 by this push: new a57a708 GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921) a57a708 is described below commit a57a7080b040f70de8ee9a37a6b5f7341d1d033e Author: Dave Barnes AuthorDate: Wed Feb 9 11:05:03 2022 -0800 GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921) --- docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb| 2 +- docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb index 27037ab..ef05ebc 100644 --- a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb +++ b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb @@ -212,7 +212,7 @@ When the chunk handler is not operative (enable-chunk-handler=false), each appli enable-time-statistics -Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. See System Statistics. +Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default./td> false diff --git a/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb b/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb index d214243..f6cbf51 100644 --- a/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb +++ b/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb @@ -212,7 +212,7 @@ When the chunk handler is not operative (enable-chunk-handler=false), each appli enable-time-statistics -Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. See System Statistics. +Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. false
[geode-native] branch support/1.14 updated: GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode-native.git The following commit(s) were added to refs/heads/support/1.14 by this push: new cd5c0d1 GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921) cd5c0d1 is described below commit cd5c0d124bf1951c546ceef38e4cad5a650d4967 Author: Dave Barnes AuthorDate: Wed Feb 9 11:05:03 2022 -0800 GEODE-10030: Remove obsolete cross-reference in geode-native user docs (#921) --- docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb| 2 +- docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb index 96a7868..7a1ec63 100644 --- a/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb +++ b/docs/geode-native-docs-cpp/configuring/sysprops.html.md.erb @@ -212,7 +212,7 @@ When the chunk handler is not operative (enable-chunk-handler=false), each appli enable-time-statistics -Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. See System Statistics. +Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default./td> false diff --git a/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb b/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb index d214243..f6cbf51 100644 --- a/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb +++ b/docs/geode-native-docs-dotnet/configuring/sysprops.html.md.erb @@ -212,7 +212,7 @@ When the chunk handler is not operative (enable-chunk-handler=false), each appli enable-time-statistics -Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. See System Statistics. +Enables time-based statistics for the distributed system and caching. For performance reasons, time-based statistics are disabled by default. false
[geode] 02/02: remove stray markdown file (#7314)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git commit 73026a0b0fb94a759cd63c82c1544ada5ce4d3e2 Author: Dave Barnes AuthorDate: Wed Jan 26 17:51:09 2022 -0800 remove stray markdown file (#7314) --- geode-docs/tools_modules/geode_for_redis.html.md | 242 --- 1 file changed, 242 deletions(-) diff --git a/geode-docs/tools_modules/geode_for_redis.html.md b/geode-docs/tools_modules/geode_for_redis.html.md deleted file mode 100644 index 735c5d1..000 --- a/geode-docs/tools_modules/geode_for_redis.html.md +++ /dev/null @@ -1,242 +0,0 @@ - - -<% set_title(product_name, "for Redis") %> - -<%=vars.product_name%> for Redis allows <%=vars.product_name%> to function as a drop-in replacement for a -highly-available Redis data store, letting Redis applications take advantage of -<%=vars.product_name%>’s scaling capabilities without changing their client code. Redis clients connect to a <%=vars.product_name%> -server in the same way they connect to a Redis server, using a hostname and a port number, with -optional password authentication. - - - -## Using <%=vars.product_name%> for Redis - -The <%=vars.product_name%> cluster must have at least one server that is set up to handle the incoming Redis commands. - -Use gfsh to start at least one server with a command of the form: - -```pre -start server \ - --name= \ - --locators= \ - --geode-for-redis-port= \ - --geode-for-redis-bind-address= \ - --geode-for-redis-password= -``` - -If any of the options `geode-for-redis-bind-address`, `geode-for-redis-password`, or `geode-for-redis-port` -are included, a <%=vars.product_name%> server with <%=vars.product_name%> for Redis will be started. - -Replace `` with the name of your server. - -Replace `` with your locator port. - -Replace `` with the port that the <%=vars.product_name%> server - listens on for Redis commands. The typical port used with a cluster compatible with Redis is 6379. - -Replace `` with the address of the server host. - -Replace `` with the password clients use to authenticate. - -To confirm the server is listening, run: - -``` pre -redis-cli -h -p -a ping -``` - -Replace ``,``, and `` with the same values as the server. - -If the server is functioning properly, you should see a response of `PONG`. - -## Supported Redis Commands - -<%=vars.product_name%> for Redis supports the following Redis commands. - - - - APPEND - - AUTH - - DECR - - DECRBY - - DEL - - EXISTS - - EXPIRE - - EXPIREAT - - GET - - GETRANGE - - HDEL - - HEXISTS - - HGET - - HGETALL - - HINCRBY - - HINCRBYFLOAT - - HLEN - - HMGET - - HMSET - - HSCAN **[1]** - - HSET - - HSETNX - - HSTRLEN - - HVALS - - HKEYS - - INCR - - INCRBY - - INCRBYFLOAT - - INFO **[2]** - - KEYS - - MGET - - PERSIST - - PEXPIRE - - PEXPIREAT - - PING - - PSUBSCRIBE - - PTTL - - PUBLISH - - PUNSUBSCRIBE - - QUIT - - RENAME - - SADD - - SCARD - - SDIFF - - SDIFFSTORE - - SISMEMBER - - SET - - SETNX - - SLOWLOG **[3]** - - SMEMBERS - - SREM - - STRLEN - - SUBSCRIBE - - TTL - - TYPE - - UNSUBSCRIBE - - -Commands not listed above are **not implemented**. - - -**NOTES:** - -These commands are supported for Redis 5. - -**[1]** Redis accepts 64-bit signed integers for the HSCAN cursor and COUNT parameters. - <%=vars.product_name%> for Redis is limited to 32-bit integer values for these parameters. - -**[2]** INFO is implemented for the sections and fields listed below: - - - clients - -- connected_clients - -- blocked_clients (always returns 0) - - - cluster - -- cluster_enables (always returns 0) - - - keyspace - -- returns stats for db: 0 - - - memory - -- maxmemory - -- used_memory - -- mem_fragmentation_ratio (always reports 1.00) - - - persistence - -- loading (always returns 0) - -- rdb_changes_since_last_save (always returns 0) - -- rdb_last_save_time (always returns 0) - - - replication - -- role - -- connected_slaves (always returns 0) - - - server - - - redis_version - - - redis_mode - - - tcp_port - - - uptime_in_seconds - - - uptime_in_days - - - stats - -- total_commands_processed - -- instantaneous_ops_per_sec - -- total_net_input_bytes - -- instantaneous_input_kbps - -- total_connections_received - -- keyspace_hits - -- keyspace_misses - -- evicted_keys (always returns 0) - -- rejected_connections (always returns 0) - -**[3]** SLOWLOG is implemented as a NoOp. - -## Advantages of <%=vars.product_name%> over Redis - -<%=vars.product_name%>’s primary advantage is its **scalability**. While the Redis server is single threaded, <%=vars.product_name%> supports high concurrency. Many Redis clients can execute commands on the <%=vars.
[geode] 01/02: GEODE-9883 Update Geode for Redis docs file (#7274)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git commit 49367309e65b5b9710cac0646fe950173af2e1bc Author: Eric Zoerner AuthorDate: Wed Jan 26 16:05:17 2022 -0800 GEODE-9883 Update Geode for Redis docs file (#7274) Co-authored-by: Dave Barnes --- .../source/subnavs/geode-subnav.erb| 24 +- .../tools_modules/geode_for_redis.html.md.erb | 292 +++-- 2 files changed, 158 insertions(+), 158 deletions(-) diff --git a/geode-book/master_middleman/source/subnavs/geode-subnav.erb b/geode-book/master_middleman/source/subnavs/geode-subnav.erb index 094959b..372a42a 100644 --- a/geode-book/master_middleman/source/subnavs/geode-subnav.erb +++ b/geode-book/master_middleman/source/subnavs/geode-subnav.erb @@ -2105,28 +2105,8 @@ limitations under the License. - -<%=vars.product_name%> for Redis - - -Using <%=vars.product_name%> for Redis - - -Supported Redis Commands - - -Advantages of <%=vars.product_name%> over Redis - - -Expiration Accuracy - - - High Availability Model - - - Loss of Connections - - + +Geode for Redis Gemcached diff --git a/geode-docs/tools_modules/geode_for_redis.html.md.erb b/geode-docs/tools_modules/geode_for_redis.html.md.erb index 9451dc7..482d817 100644 --- a/geode-docs/tools_modules/geode_for_redis.html.md.erb +++ b/geode-docs/tools_modules/geode_for_redis.html.md.erb @@ -25,213 +25,233 @@ optional password authentication. -## Using <%=vars.product_name%> for Redis +## Using <%=vars.product_name%> for Redis The <%=vars.product_name%> cluster must have at least one server that is set up to handle the incoming Redis commands. -Use gfsh to start at least one server with a command of the form: +Prerequisites for running the examples: -```pre -start server \ - --name= \ - --locators= \ - --J=-Dgemfire.geode-for-redis-enabled=true \ - --J=-Dgemfire.geode-for-redis-port= \ - --J=-Dgemfire.geode-for-redis-bind-address= -``` - -If the gemfire property `geode-for-redis-enabled`, is set to `true`, a <%=vars.product_name%> -server with <%=vars.product_name%> for Redis will be started. +1. **Install <%=vars.product_name%>** +Using the instructions in the `README.md` file in the root of the <%=vars.product_name%> checkout directory, build and install <%=vars.product_name%>. +2. **Install the Redis CLI** +Follow installation instructions at https://redis.io/download -Replace `` with the name of your server. +Use `gfsh` to start a locator for managing a <%=vars.product_name%> cluster: -Replace `` with your locator port. +```commandLine +gfsh> start locator +``` -Replace `` with the port that the <%=vars.product_name%> server - listens on for Redis commands. The typical port used with a cluster compatible with Redis is 6379. +Use `gfsh` to start at least one server with a command of the form: -Replace `` with the address of the server host. +```commandLine +gfsh> start server --J=-Dgemfire.geode-for-redis-enabled=true --J=-Dgemfire.geode-for-redis-port=6379 +``` -Replace `` with the password clients use to authenticate. +More information about the options when starting a server is given in the section [Start Server Options](#redis-start-server-options) below. -To confirm the server is listening, run: +To confirm the server is listening, in a separate terminal run: -``` pre -redis-cli -h -p -a ping +```commandLine +$ redis-cli -c ping ``` -Replace ``,``, and `` with the same values as the server. +The `-c` option enables cluster mode in the redis-cli, which is necessary since +<%=vars.product_name%> for Redis runs as a Redis Cluster. If the server is functioning properly, you should see a response of `PONG`. -## Supported Redis Commands +### Add an additional server +If you’re interested in testing <%=vars.product_name%> scalability, in gfsh run the `start server` command again. -<%=vars.product_name%> for Redis supports the following Redis commands. - - - - APPEND
[geode] branch support/1.15 updated (b2c7782 -> 73026a0)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git. from b2c7782 GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) new 4936730 GEODE-9883 Update Geode for Redis docs file (#7274) new 73026a0 remove stray markdown file (#7314) The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .../source/subnavs/geode-subnav.erb| 24 +- geode-docs/tools_modules/geode_for_redis.html.md | 242 - .../tools_modules/geode_for_redis.html.md.erb | 292 +++-- 3 files changed, 158 insertions(+), 400 deletions(-) delete mode 100644 geode-docs/tools_modules/geode_for_redis.html.md
[geode] branch develop updated: remove stray markdown file (#7314)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/develop by this push: new b33021f remove stray markdown file (#7314) b33021f is described below commit b33021fcbde1e92480e8759c1ed79fc1a467f2cf Author: Dave Barnes AuthorDate: Wed Jan 26 17:51:09 2022 -0800 remove stray markdown file (#7314) --- geode-docs/tools_modules/geode_for_redis.html.md | 242 --- 1 file changed, 242 deletions(-) diff --git a/geode-docs/tools_modules/geode_for_redis.html.md b/geode-docs/tools_modules/geode_for_redis.html.md deleted file mode 100644 index 735c5d1..000 --- a/geode-docs/tools_modules/geode_for_redis.html.md +++ /dev/null @@ -1,242 +0,0 @@ - - -<% set_title(product_name, "for Redis") %> - -<%=vars.product_name%> for Redis allows <%=vars.product_name%> to function as a drop-in replacement for a -highly-available Redis data store, letting Redis applications take advantage of -<%=vars.product_name%>’s scaling capabilities without changing their client code. Redis clients connect to a <%=vars.product_name%> -server in the same way they connect to a Redis server, using a hostname and a port number, with -optional password authentication. - - - -## Using <%=vars.product_name%> for Redis - -The <%=vars.product_name%> cluster must have at least one server that is set up to handle the incoming Redis commands. - -Use gfsh to start at least one server with a command of the form: - -```pre -start server \ - --name= \ - --locators= \ - --geode-for-redis-port= \ - --geode-for-redis-bind-address= \ - --geode-for-redis-password= -``` - -If any of the options `geode-for-redis-bind-address`, `geode-for-redis-password`, or `geode-for-redis-port` -are included, a <%=vars.product_name%> server with <%=vars.product_name%> for Redis will be started. - -Replace `` with the name of your server. - -Replace `` with your locator port. - -Replace `` with the port that the <%=vars.product_name%> server - listens on for Redis commands. The typical port used with a cluster compatible with Redis is 6379. - -Replace `` with the address of the server host. - -Replace `` with the password clients use to authenticate. - -To confirm the server is listening, run: - -``` pre -redis-cli -h -p -a ping -``` - -Replace ``,``, and `` with the same values as the server. - -If the server is functioning properly, you should see a response of `PONG`. - -## Supported Redis Commands - -<%=vars.product_name%> for Redis supports the following Redis commands. - - - - APPEND - - AUTH - - DECR - - DECRBY - - DEL - - EXISTS - - EXPIRE - - EXPIREAT - - GET - - GETRANGE - - HDEL - - HEXISTS - - HGET - - HGETALL - - HINCRBY - - HINCRBYFLOAT - - HLEN - - HMGET - - HMSET - - HSCAN **[1]** - - HSET - - HSETNX - - HSTRLEN - - HVALS - - HKEYS - - INCR - - INCRBY - - INCRBYFLOAT - - INFO **[2]** - - KEYS - - MGET - - PERSIST - - PEXPIRE - - PEXPIREAT - - PING - - PSUBSCRIBE - - PTTL - - PUBLISH - - PUNSUBSCRIBE - - QUIT - - RENAME - - SADD - - SCARD - - SDIFF - - SDIFFSTORE - - SISMEMBER - - SET - - SETNX - - SLOWLOG **[3]** - - SMEMBERS - - SREM - - STRLEN - - SUBSCRIBE - - TTL - - TYPE - - UNSUBSCRIBE - - -Commands not listed above are **not implemented**. - - -**NOTES:** - -These commands are supported for Redis 5. - -**[1]** Redis accepts 64-bit signed integers for the HSCAN cursor and COUNT parameters. - <%=vars.product_name%> for Redis is limited to 32-bit integer values for these parameters. - -**[2]** INFO is implemented for the sections and fields listed below: - - - clients - -- connected_clients - -- blocked_clients (always returns 0) - - - cluster - -- cluster_enables (always returns 0) - - - keyspace - -- returns stats for db: 0 - - - memory - -- maxmemory - -- used_memory - -- mem_fragmentation_ratio (always reports 1.00) - - - persistence - -- loading (always returns 0) - -- rdb_changes_since_last_save (always returns 0) - -- rdb_last_save_time (always returns 0) - - - replication - -- role - -- connected_slaves (always returns 0) - - - server - - - redis_version - - - redis_mode - - - tcp_port - - - uptime_in_seconds - - - uptime_in_days - - - stats - -- total_commands_processed - -- instantaneous_ops_per_sec - -- total_net_input_bytes - -- instantaneous_input_kbps - -- total_connections_received - -- keyspace_hits - -- keyspace_misses - -- evicted_keys (always returns 0) - -- rejected_connections (always returns 0) - -**[3]** SLOWLOG is implemented as a NoOp. - -## Advantages of <%=vars.product_name%> over Redis - -<%=vars.product_name%>’s primary advantage is its **scalability**. While the
[geode] branch support/1.12 updated: GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.12 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.12 by this push: new f574632 GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) f574632 is described below commit f574632746e44dc283b91c98b867c82487172a19 Author: Donal Evans AuthorDate: Wed Jan 26 14:17:23 2022 -0800 GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) --- .../monitor_tune/socket_communication_have_enough_sockets.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb b/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb index 1c52ed5..f2ec5e8 100644 --- a/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb +++ b/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb @@ -39,7 +39,7 @@ recommend that you set `conserve-sockets` to `false`. You can force the release of an idle socket connection for peer-to-peer and client-to-server connections: -- **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. +- **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 closes that socket. The next time the thread needs a socket, it creates a new socket. - **Client**. For client connections, you can affect the same lease-time behavior by setting the pool `idle-timeout`. ## Calculating Connection Requirements
[geode] branch support/1.13 updated: GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.13 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.13 by this push: new d259570 GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) d259570 is described below commit d2595701d1c7c905cf676b6eb233dc569537c654 Author: Donal Evans AuthorDate: Wed Jan 26 14:17:23 2022 -0800 GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) --- .../monitor_tune/socket_communication_have_enough_sockets.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb b/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb index 1c52ed5..f2ec5e8 100644 --- a/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb +++ b/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb @@ -39,7 +39,7 @@ recommend that you set `conserve-sockets` to `false`. You can force the release of an idle socket connection for peer-to-peer and client-to-server connections: -- **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. +- **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 closes that socket. The next time the thread needs a socket, it creates a new socket. - **Client**. For client connections, you can affect the same lease-time behavior by setting the pool `idle-timeout`. ## Calculating Connection Requirements
[geode] branch support/1.14 updated: GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.14 by this push: new 0162fed GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) 0162fed is described below commit 0162fed255cc7708ea6e476ff3e0f9300660d4f4 Author: Donal Evans AuthorDate: Wed Jan 26 14:17:23 2022 -0800 GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) --- .../monitor_tune/socket_communication_have_enough_sockets.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb b/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb index 644c0f3..5caf93d 100644 --- a/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb +++ b/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb @@ -39,7 +39,7 @@ recommend that you use the default value of `false`. You can force the release of an idle socket connection for peer-to-peer and client-to-server connections: -- **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. +- **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 closes that socket. The next time the thread needs a socket, it creates a new socket. - **Client**. For client connections, you can affect the same lease-time behavior by setting the pool `idle-timeout`. ## Calculating Connection Requirements
[geode] branch support/1.15 updated: GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.15 by this push: new b2c7782 GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) b2c7782 is described below commit b2c77825ff1280d679b1d289afcf8913d6d509f8 Author: Donal Evans AuthorDate: Wed Jan 26 14:17:23 2022 -0800 GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) --- .../monitor_tune/socket_communication_have_enough_sockets.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb b/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb index 644c0f3..5caf93d 100644 --- a/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb +++ b/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb @@ -39,7 +39,7 @@ recommend that you use the default value of `false`. You can force the release of an idle socket connection for peer-to-peer and client-to-server connections: -- **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. +- **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 closes that socket. The next time the thread needs a socket, it creates a new socket. - **Client**. For client connections, you can affect the same lease-time behavior by setting the pool `idle-timeout`. ## Calculating Connection Requirements
[geode] branch support/1.14 updated: GEODE-9923: Add log message troubleshooting info from support team community (#7296)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.14 in repository https://gitbox.apache.org/repos/asf/geode.git The following commit(s) were added to refs/heads/support/1.14 by this push: new 5a55011 GEODE-9923: Add log message troubleshooting info from support team community (#7296) 5a55011 is described below commit 5a550110defaffcff2daff0becfc8740a448ca60 Author: Dave Barnes AuthorDate: Mon Jan 24 10:40:19 2022 -0800 GEODE-9923: Add log message troubleshooting info from support team community (#7296) --- .../source/subnavs/geode-subnav.erb|3 + .../troubleshooting/chapter_overview.html.md.erb |3 + .../log_messages_and_solutions.html.md.erb | 1564 3 files changed, 1570 insertions(+) diff --git a/geode-book/master_middleman/source/subnavs/geode-subnav.erb b/geode-book/master_middleman/source/subnavs/geode-subnav.erb index 7f261e1..6dbec0b 100644 --- a/geode-book/master_middleman/source/subnavs/geode-subnav.erb +++ b/geode-book/master_middleman/source/subnavs/geode-subnav.erb @@ -851,6 +851,9 @@ limitations under the License. Understanding and Recovering from Network Outages + +Log Messages and Solutions + diff --git a/geode-docs/managing/troubleshooting/chapter_overview.html.md.erb b/geode-docs/managing/troubleshooting/chapter_overview.html.md.erb index 1f533dc..2a17d32 100644 --- a/geode-docs/managing/troubleshooting/chapter_overview.html.md.erb +++ b/geode-docs/managing/troubleshooting/chapter_overview.html.md.erb @@ -57,4 +57,7 @@ This section provides strategies for handling common errors and failure situatio The safest response to a network outage is to restart all the processes and bring up a fresh data set. +- **[Log Messages and Solutions](log_messages_and_solutions.html)** + +This section provides strategies for responding to a variety of system log messages. diff --git a/geode-docs/managing/troubleshooting/log_messages_and_solutions.html.md.erb b/geode-docs/managing/troubleshooting/log_messages_and_solutions.html.md.erb new file mode 100644 index 000..764b285 --- /dev/null +++ b/geode-docs/managing/troubleshooting/log_messages_and_solutions.html.md.erb @@ -0,0 +1,1564 @@ +--- +title: Log Messages and Solutions +--- + + + +This section provides explanations of <%=vars.product_name%> Log messages with potential resolutions. + +Depending on how your system is configured, log files can be found in a number of locations. +See [Log File Locations](../security/security-audit.html#topic_5B6DF783A14241399DC25C6EE8D0048A) and +[Naming, Searching, and Creating Log Files](../logging/logging_whats_next.html) for more information. + +## above heap eviction threshold + +**Log Message:** + +``` +[info 2021/03/23 16:00:13.721 EDT xxx-server01 tid=0x5d] Member: +xxx(xxx-server01:29847):11096 above heap eviction threshold +``` + +**Log Level:** info + +**Category:** Heap GC + +**Meaning:** + +This message requires action to remain healthy. The live objects are driving heap consumption above +your threshold for collecting heap. This is not a good state, as you will either be prematurely +destroying data or overflowing it to disk, which can overwhelm the disk. + +**Potential Resolutions:** + +NOTE: <%=vars.product_name%> eviction is not truly compatible with G1GC given how G1GC behaves and how eviction assumes that garbage will be collected. + +You should consider increasing the total heap. This will increase tenured space, and potentially eliminate these messages. You can also increase your eviction-threshold percentage, but this can risk growing heap to the point where you encounter heap fragmentation issues. + + +## below heap eviction threshold + +**Log Message:** + +``` +[info 2021/03/23 16:00:43.438 EDT xxx-server01 tid=0x5d] Member: +xxx(xxx-server01:29847):11096 below heap eviction threshold +``` + +**Log Level:** info + +**Category:** Heap GC + +**Meaning:** + + You are now below the eviction threshold, after having been above the threshold. + +**Potential Resolutions:** + + Follow the guidance provided in the ["above heap eviction threshold"](#aboveheapevictionthreshold) message. + + +## above heap critical threshold + +**Log Message:** + +``` +[error 2020/06/23 03:43:48.796 EDT tid=0xa4] Member: +xxx(xxx-server-2:119506):10102 above heap critical threshold. Event generated via +polling. Used bytes: 26508001280. Memory thresholds: MemoryThresholds@[2041517395 +maxMemoryBytes:26843545600, criticalThreshold:95.0, +criticalThresholdBytes:25501368320, criticalThresholdClearBytes:24964497408, +evictionThreshold:85.0, evictionThre
[geode] branch develop updated (0ec7f48 -> d690f7b)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git. from 0ec7f48 roll develop to 1.16.0 now that support/1.15 has been created (#7309) add d690f7b GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) No new revisions were added by this update. Summary of changes: .../monitor_tune/socket_communication_have_enough_sockets.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
[geode] branch develop updated (4b5b30e -> 67d7725)
This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a change to branch develop in repository https://gitbox.apache.org/repos/asf/geode.git. from 4b5b30e GEODE-9969: Fix unescaping the region name with underscore (#7282) add 67d7725 Revert "GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7294)" (#7306) No new revisions were added by this update. Summary of changes: .../monitor_tune/socket_communication_have_enough_sockets.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
