GEODE-3395 Variable-ize product version and name in user guide - Managing
Project: http://git-wip-us.apache.org/repos/asf/geode/repo Commit: http://git-wip-us.apache.org/repos/asf/geode/commit/1b84ecbe Tree: http://git-wip-us.apache.org/repos/asf/geode/tree/1b84ecbe Diff: http://git-wip-us.apache.org/repos/asf/geode/diff/1b84ecbe Branch: refs/heads/develop Commit: 1b84ecbe4d942d843cb0d0fa8c2e03eb55f07f39 Parents: 6f7667d Author: Dave Barnes <[email protected]> Authored: Wed Aug 23 09:47:36 2017 -0700 Committer: Dave Barnes <[email protected]> Committed: Wed Aug 23 10:35:48 2017 -0700 ---------------------------------------------------------------------- .../source/subnavs/geode-subnav.erb | 14 +- .../running/running_the_cacheserver.html.md.erb | 2 +- .../running/running_the_locator.html.md.erb | 2 +- .../autoreconnect/member-reconnect.html.md.erb | 83 ------- geode-docs/managing/book_intro.html.md.erb | 40 ++-- .../chapter_overview.html.md.erb | 14 +- .../exporting_a_snapshot.html.md.erb | 4 +- .../importing_a_snapshot.html.md.erb | 4 +- .../disk_storage/chapter_overview.html.md.erb | 22 +- .../compacting_disk_stores.html.md.erb | 12 +- .../disk_store_configuration_params.html.md.erb | 2 +- .../how_disk_stores_work.html.md.erb | 10 +- ...eping_offline_disk_store_in_sync.html.md.erb | 2 +- .../managing_disk_buffer_flushes.html.md.erb | 10 +- .../managing_disk_stores.html.md.erb | 16 +- .../disk_storage/operation_logs.html.md.erb | 16 +- ...ize_availability_and_performance.html.md.erb | 2 +- .../overview_using_disk_stores.html.md.erb | 8 +- ...starting_system_with_disk_stores.html.md.erb | 2 +- .../disk_storage/using_disk_stores.html.md.erb | 8 +- .../using_the_default_disk_store.html.md.erb | 4 +- .../heap_use/heap_management.html.md.erb | 28 +-- .../managing/heap_use/lock_memory.html.md.erb | 6 +- .../heap_use/off_heap_management.html.md.erb | 12 +- .../logging/configuring_log4j2.html.md.erb | 26 +-- .../logging/how_logging_works.html.md.erb | 20 +- geode-docs/managing/logging/logging.html.md.erb | 14 +- .../logging/logging_categories.html.md.erb | 12 +- .../logging/setting_up_logging.html.md.erb | 2 +- .../configuring_rmi_connector.html.md.erb | 10 +- .../gfsh_and_management_api.html.md.erb | 2 +- .../management/jmx_manager_node.html.md.erb | 4 +- .../jmx_manager_operations.html.md.erb | 22 +- .../list_of_mbean_notifications.html.md.erb | 2 +- .../management/list_of_mbeans.html.md.erb | 8 +- .../management/list_of_mbeans_full.html.md.erb | 10 +- .../management_and_monitoring.html.md.erb | 30 ++- ...nagement_and_monitoring_features.html.md.erb | 12 +- .../management_system_overview.html.md.erb | 34 +-- .../management/mbean_architecture.html.md.erb | 24 +- .../management/mbean_notifications.html.md.erb | 8 +- .../management/mbeans_jconsole.html.md.erb | 10 +- .../managing/management/mm_overview.html.md.erb | 48 ++-- ...tification_federation_and_alerts.html.md.erb | 2 +- .../managing/member-reconnect.html.md.erb | 83 +++++++ .../monitor_tune/cache_consistency.html.md.erb | 8 +- .../monitor_tune/chapter_overview.html.md.erb | 28 +-- .../multicast_communication.html.md.erb | 14 +- ...ication_configuring_speed_limits.html.md.erb | 2 +- ...unication_runtime_considerations.html.md.erb | 6 +- ...n_testing_multicast_speed_limits.html.md.erb | 2 +- .../performance_controls.html.md.erb | 14 +- ...ance_controls_data_serialization.html.md.erb | 4 +- .../performance_on_vsphere.html.md.erb | 38 ++-- .../monitor_tune/slow_messages.html.md.erb | 2 +- .../monitor_tune/slow_receivers.html.md.erb | 6 +- .../slow_receivers_managing.html.md.erb | 6 +- ...ow_receivers_preventing_problems.html.md.erb | 8 +- .../socket_communication.html.md.erb | 18 +- ...ommunication_have_enough_sockets.html.md.erb | 4 +- ...tion_setting_socket_buffer_sizes.html.md.erb | 2 +- .../socket_tcp_keepalive.html.md.erb | 4 +- .../sockets_and_gateways.html.md.erb | 2 +- .../system_member_performance.html.md.erb | 8 +- ...ber_performance_jvm_mem_settings.html.md.erb | 2 +- .../monitor_tune/udp_communication.html.md.erb | 12 +- .../chapter_overview.html.md.erb | 18 +- .../failure_detection.html.md.erb | 2 +- .../handling_network_partitioning.html.md.erb | 6 +- ...rk_partitioning_management_works.html.md.erb | 4 +- ...ators_lead_members_and_weighting.html.md.erb | 2 +- .../preventing_network_partitions.html.md.erb | 2 +- .../managing/region_compression.html.md.erb | 226 +++++++++++++++++++ .../region_compression.html.md.erb | 226 ------------------- .../authentication_examples.html.md.erb | 4 +- .../authentication_overview.html.md.erb | 10 +- .../security/authorization_example.html.md.erb | 2 +- .../security/authorization_overview.html.md.erb | 4 +- .../security/chapter_overview.html.md.erb | 14 +- .../security/encrypting_passwords.html.md.erb | 2 +- .../encrypting_with_diffie_hellman.html.md.erb | 66 ++++++ .../encrypting_with_diffie_helman.html.md.erb | 66 ------ .../security/implementing_ssl.html.md.erb | 8 +- .../security/properties_file.html.md.erb | 2 +- .../security/security-audit.html.md.erb | 8 +- .../security_audit_overview.html.md.erb | 4 +- .../managing/security/ssl_example.html.md.erb | 2 +- .../managing/security/ssl_overview.html.md.erb | 10 +- .../application_defined_statistics.html.md.erb | 4 +- .../statistics/chapter_overview.html.md.erb | 16 +- .../statistics/how_statistics_work.html.md.erb | 2 +- .../setting_up_statistics.html.md.erb | 2 +- ...ient_region_and_entry_statistics.html.md.erb | 6 +- .../chapter_overview.html.md.erb | 24 +- .../diagnosing_system_probs.html.md.erb | 24 +- ...ent_and_recover_disk_full_errors.html.md.erb | 4 +- ...ring_conflicting_data_exceptions.html.md.erb | 14 +- .../recovering_from_app_crashes.html.md.erb | 4 +- .../recovering_from_cs_crashes.html.md.erb | 2 +- .../recovering_from_machine_crashes.html.md.erb | 6 +- .../recovering_from_network_outages.html.md.erb | 2 +- .../recovering_from_p2p_crashes.html.md.erb | 4 +- .../topics/gemfire_properties.html.md.erb | 2 +- .../gfsh/command-pages/create.html.md.erb | 2 +- 104 files changed, 842 insertions(+), 860 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-book/master_middleman/source/subnavs/geode-subnav.erb ---------------------------------------------------------------------- diff --git a/geode-book/master_middleman/source/subnavs/geode-subnav.erb b/geode-book/master_middleman/source/subnavs/geode-subnav.erb index 838b265..788923d 100644 --- a/geode-book/master_middleman/source/subnavs/geode-subnav.erb +++ b/geode-book/master_middleman/source/subnavs/geode-subnav.erb @@ -516,20 +516,20 @@ limitations under the License. </ul> </li> <li class="has_submenu"> - <a href="/docs/guide/12/managing/region_compression/region_compression.html">Region Compression</a> + <a href="/docs/guide/12/managing/region_compression.html">Region Compression</a> <ul> <li> - <a href="/docs/guide/12/managing/region_compression/region_compression.html#concept_a2c_rhc_gl">Guidelines on Using Compression</a> + <a href="/docs/guide/12/managing/region_compression.html#concept_a2c_rhc_gl">Guidelines on Using Compression</a> </li> <li> - <a href="/docs/guide/12/managing/region_compression/region_compression.html#topic_inm_whc_gl">How to Enable Compression in a Region</a> + <a href="/docs/guide/12/managing/region_compression.html#topic_inm_whc_gl">How to Enable Compression in a Region</a> </li> <li> - <a href="/docs/guide/12/managing/region_compression/region_compression.html#topic_hqf_syj_g4">Working with Compressors + <a href="/docs/guide/12/managing/region_compression.html#topic_hqf_syj_g4">Working with Compressors </a> </li> <li> - <a href="/docs/guide/12/managing/region_compression/region_compression.html#topic_omw_j3c_gl">Comparing Performance of Compressed and Non-Compressed Regions</a> + <a href="/docs/guide/12/managing/region_compression.html#topic_omw_j3c_gl">Comparing Performance of Compressed and Non-Compressed Regions</a> </li> </ul> </li> @@ -592,7 +592,7 @@ limitations under the License. <a href="/docs/guide/12/managing/security/encrypting_passwords.html">Encrypting Passwords for Use in cache.xml</a> </li> <li> - <a href="/docs/guide/12/managing/security/encrypting_with_diffie_helman.html">Encrypt Credentials with Diffie-Hellman</a> + <a href="/docs/guide/12/managing/security/encrypting_with_diffie_hellman.html">Encrypt Credentials with Diffie-Hellman</a> </li> <li> <a href="/docs/guide/12/managing/security/authentication_examples.html">Authentication Example</a> @@ -798,7 +798,7 @@ limitations under the License. <a href="/docs/guide/12/managing/troubleshooting/system_failure_and_recovery.html">System Failure and Recovery</a> </li> <li> - <a href="/docs/guide/12/managing/autoreconnect/member-reconnect.html">Handling Forced Cache Disconnection Using Autoreconnect</a> + <a href="/docs/guide/12/managing/member-reconnect.html">Handling Forced Cache Disconnection Using Autoreconnect</a> </li> <li class="has_submenu"> <a href="/docs/guide/12/managing/troubleshooting/recovering_from_app_crashes.html">Recovering from Application and Cache Server Crashes</a> http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/configuring/running/running_the_cacheserver.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/configuring/running/running_the_cacheserver.html.md.erb b/geode-docs/configuring/running/running_the_cacheserver.html.md.erb index 2d43f59..578326a 100644 --- a/geode-docs/configuring/running/running_the_cacheserver.html.md.erb +++ b/geode-docs/configuring/running/running_the_cacheserver.html.md.erb @@ -40,7 +40,7 @@ The `gfsh` utility uses a working directory for its configuration files and log - If you are using the Spring Framework, you can specify a Spring ApplicationContext XML file when starting up your server in `gfsh` by using the `--spring-xml-location` command-line option. This option allows you to bootstrap your Geode server process with your Spring application's configuration. See [Spring documentation](http://docs.spring.io/spring/docs/3.2.x/spring-framework-reference/html/resources.html#resources-app-ctx) for more information on this file. - For logging output, log file output defaults to `server_name.log` in the cache server's working directory. If you restart a server with the same server name, the existing *server\_name*.log file is automatically renamed for you (for example, `server1-01-01.log` or `server1-02-01.log`). You can modify the level of logging details in this file by specifying a level in the `--log-level` argument when starting up the server. - By default, the server will start in a subdirectory (named after the server's specified `--name`) under the directory where `gfsh` is executed. This subdirectory is considered the current working directory. You can also specify a different working directory when starting the cache server in `gfsh`. -- By default, a server process that has been shutdown and disconnected due to a network partition event or member unresponsiveness will restart itself and automatically try to reconnect to the existing distributed system. See [Handling Forced Cache Disconnection Using Autoreconnect](../../managing/autoreconnect/member-reconnect.html#concept_22EE6DDE677F4E8CAF5786E17B4183A9) for more details. +- By default, a server process that has been shutdown and disconnected due to a network partition event or member unresponsiveness will restart itself and automatically try to reconnect to the existing distributed system. See [Handling Forced Cache Disconnection Using Autoreconnect](../../managing/member-reconnect.html#concept_22EE6DDE677F4E8CAF5786E17B4183A9) for more details. - You can pass JVM parameters to the server's JVM by using the `--J=-Dproperty.name=value` upon server startup. These parameters can be Java properties or Geode configuration properties such as `gemfire.jmx-manager`. For example: ``` pre http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/configuring/running/running_the_locator.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/configuring/running/running_the_locator.html.md.erb b/geode-docs/configuring/running/running_the_locator.html.md.erb index 6e3a49f..853cb64 100644 --- a/geode-docs/configuring/running/running_the_locator.html.md.erb +++ b/geode-docs/configuring/running/running_the_locator.html.md.erb @@ -55,7 +55,7 @@ Locator configuration and log files have the following properties: - There is no cache configuration specific to locators. - For logging output, the locator creates a log file in its current working directory. Log file output defaults to `locator_name.log` in the locator's working directory. If you restart a locator with a previously used locator name, the existing *locator\_name*.log file is automatically renamed for you (for example, `locator1-01-01.log` or `locator1-02-01.log`). You can modify the level of logging details in this file by specifying a level in the `--log-level` argument when starting up the locator. - By default, a locator will start in a subdirectory (named after the locator) under the directory where `gfsh` is executed. This subdirectory is considered the current working directory. You can also specify a different working directory when starting the locator in `gfsh`. -- By default, a locator that has been shutdown and disconnected due to a network partition event or member unresponsiveness will restart itself and automatically try to reconnect to the existing distributed system. When a locator is in the reconnecting state, it provides no discovery services for the distributed system. See [Handling Forced Cache Disconnection Using Autoreconnect](../../managing/autoreconnect/member-reconnect.html) for more details. +- By default, a locator that has been shutdown and disconnected due to a network partition event or member unresponsiveness will restart itself and automatically try to reconnect to the existing distributed system. When a locator is in the reconnecting state, it provides no discovery services for the distributed system. See [Handling Forced Cache Disconnection Using Autoreconnect](../../managing/member-reconnect.html) for more details. ## <a id="running_the_locator__section_wst_ykb_rr" class="no-quick-link"></a>Locators and the Cluster Configuration Service http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb b/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb deleted file mode 100644 index 8d59c0a..0000000 --- a/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Handling Forced Cache Disconnection Using Autoreconnect ---- - -<!-- -Licensed to the Apache Software Foundation (ASF) under one or more -contributor license agreements. See the NOTICE file distributed with -this work for additional information regarding copyright ownership. -The ASF licenses this file to You under the Apache License, Version 2.0 -(the "License"); you may not use this file except in compliance with -the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. ---> - -A Geode member may be forcibly disconnected from a Geode distributed system if the member is unresponsive for a period of time, or if a network partition separates one or more members into a group that is too small to act as the distributed system. - -## How the Autoreconnection Process Works - -After being disconnected from a distributed system, -a Geode member shuts down and, by default, automatically restarts into -a "reconnecting" state, -while periodically attempting to rejoin the distributed system -by contacting a list of known locators. -If the member succeeds in reconnecting to a known locator, the member rebuilds its view of the distributed system from existing members and receives a new distributed member ID. - -If the member cannot connect to a known locator, the member will then check to see if it itself is a locator (or hosting an embedded locator process). If the member is a locator, then the member does a quorum-based reconnect; it will attempt to contact a quorum of the members that were in the membership view just before it became disconnected. If a quorum of members can be contacted, then startup of the distributed system is allowed to begin. Since the reconnecting member does not know which members survived the network partition event, all members that are in a reconnecting state will keep their UDP unicast ports open and respond to ping requests. - -Membership quorum is determined using the same member weighting system used in network partition detection. See [Membership Coordinators, Lead Members and Member Weighting](../network_partitioning/membership_coordinators_lead_members_and_weighting.html#concept_23C2606D59754106AFBFE17515DF4330). - -Note that when a locator is in the reconnecting state, -it provides no discovery services for the distributed system. - -The default settings for reconfiguration of the cache once -reconnected assume that the cluster configuration service has -a valid (XML) configuration. -This will not be the case if the cluster was configured using -API calls. -To handle this case, -either disable autoreconnect by setting the property to - -``` -disable-auto-reconnect = true -``` - -or, disable the cluster configuration service by setting the property to - -``` -enable-cluster-configuration = false -``` - -After the cache has reconnected, applications must fetch a reference to the new Cache, Regions, DistributedSystem and other artifacts. Old references will continue to throw cancellation exceptions like `CacheClosedException(cause=ForcedDisconnectException)`. - -See the Geode `DistributedSystem` and `Cache` Java API documentation for more information. - -## Managing the Autoreconnection Process - -By default a Geode member will try to reconnect until it is told to stop by using the `DistributedSystem.stopReconnecting()` or `Cache.stopReconnecting()` method. You can disable automatic reconnection entirely by setting `disable-auto-reconnect` Geode property to "true." - -You can use `DistributedSystem` and `Cache` callback methods to perform actions during the reconnect process, or to cancel the reconnect process if necessary. - -The `DistributedSystem` and `Cache` API provide several methods you can use to take actions while a member is reconnecting to the distributed system: - -- `DistributedSystem.isReconnecting()` returns true if the member is in the process of reconnecting and recreating the cache after having been removed from the system by other members. -- `DistributedSystem.waitUntilReconnected(long, TimeUnit)` waits for a period of time, and then returns a boolean value to indicate whether the member has reconnected to the DistributedSystem. Use a value of -1 seconds to wait indefinitely until the reconnect completes or the member shuts down. Use a value of 0 seconds as a quick probe to determine if the member has reconnected. -- `DistributedSystem.getReconnectedSystem()` returns the reconnected DistributedSystem. -- `DistributedSystem.stopReconnecting()` stops the reconnection process and ensures that the DistributedSystem stays in a disconnected state. -- `Cache.isReconnecting()` returns true if the cache is attempting to reconnect to a distributed system. -- `Cache.waitForReconnect(long, TimeUnit)` waits for a period of time, and then returns a boolean value to indicate whether the DistributedSystem has reconnected. Use a value of -1 seconds to wait indefinitely until the reconnect completes or the cache shuts down. Use a value of 0 seconds as a quick probe to determine if the member has reconnected. -- `Cache.getReconnectedCache()` returns the reconnected Cache. -- `Cache.stopReconnecting()` stops the reconnection process and ensures that the DistributedSystem stays in a disconnected state. - -## Operator Intervention - -You may need to intervene in the autoreconnection process if processes or hardware have crashed or are otherwise shut down before the network connection is healed. In this case the members in a "reconnecting" state will not be able to find the lost processes through UDP probes and will not rejoin the system until they are able to contact a locator. - - http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/book_intro.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/book_intro.html.md.erb b/geode-docs/managing/book_intro.html.md.erb index d7929f2..de2dc67 100644 --- a/geode-docs/managing/book_intro.html.md.erb +++ b/geode-docs/managing/book_intro.html.md.erb @@ -1,6 +1,4 @@ ---- -title: Managing Apache Geode ---- +<% set_title("Managing", product_name_long)%> <!-- Licensed to the Apache Software Foundation (ASF) under one or more @@ -19,50 +17,50 @@ See the License for the specific language governing permissions and limitations under the License. --> -*Managing Apache Geode* describes how to plan and implement tasks associated with managing, monitoring, and troubleshooting Apache Geode. +*Managing <%=vars.product_name_long%>* describes how to plan and implement tasks associated with managing, monitoring, and troubleshooting <%=vars.product_name_long%>. -- **[Apache Geode Management and Monitoring](../managing/management/management_and_monitoring.html)** +- **[<%=vars.product_name_long%> Management and Monitoring](management/management_and_monitoring.html)** - Apache Geode provides APIs and tools for managing your distributed system and monitoring the health of your distributed system members. + <%=vars.product_name_long%> provides APIs and tools for managing your distributed system and monitoring the health of your distributed system members. -- **[Managing Heap and Off-heap Memory](../managing/heap_use/heap_management.html)** +- **[Managing Heap and Off-heap Memory](heap_use/heap_management.html)** - By default, Apache Geode uses the JVM heap. Apache Geode also offers an option to store data off heap. This section describes how to manage heap and off-heap memory to best support your application. + By default, <%=vars.product_name_long%> uses the JVM heap. <%=vars.product_name_long%> also offers an option to store data off heap. This section describes how to manage heap and off-heap memory to best support your application. -- **[Disk Storage](../managing/disk_storage/chapter_overview.html)** +- **[Disk Storage](disk_storage/chapter_overview.html)** - With Apache Geode disk stores, you can persist data to disk as a backup to your in-memory copy and overflow data to disk when memory use gets too high. + With <%=vars.product_name_long%> disk stores, you can persist data to disk as a backup to your in-memory copy and overflow data to disk when memory use gets too high. -- **[Cache and Region Snapshots](../managing/cache_snapshots/chapter_overview.html)** +- **[Cache and Region Snapshots](cache_snapshots/chapter_overview.html)** Snapshots allow you to save region data and reload it later. A typical use case is loading data from one environment into another, such as capturing data from a production system and moving it into a smaller QA or development system. -- **[Region Compression](../managing/region_compression/region_compression.html)** +- **[Region Compression](region_compression.html)** This section describes region compression, its benefits and usage. -- **[Network Partitioning](../managing/network_partitioning/chapter_overview.html)** +- **[Network Partitioning](network_partitioning/chapter_overview.html)** - Apache Geode architecture and management features help detect and resolve network partition problems. + <%=vars.product_name_long%> architecture and management features help detect and resolve network partition problems. -- **[Security](../managing/security/chapter_overview.html)** +- **[Security](security/chapter_overview.html)** The security framework establishes trust by authenticating components and members upon connection. It facilitates the authorization of operations. -- **[Performance Tuning and Configuration](../managing/monitor_tune/chapter_overview.html)** +- **[Performance Tuning and Configuration](monitor_tune/chapter_overview.html)** - A collection of tools and controls allow you to monitor and adjust Apache Geode performance. + A collection of tools and controls allow you to monitor and adjust <%=vars.product_name_long%> performance. -- **[Logging](../managing/logging/logging.html)** +- **[Logging](logging/logging.html)** Comprehensive logging messages help you confirm system configuration and debug problems in configuration and code. -- **[Statistics](../managing/statistics/chapter_overview.html)** +- **[Statistics](statistics/chapter_overview.html)** - Every application and server in a distributed system can access statistical data about Apache Geode operations. You can configure the gathering of statistics by using the `alter runtime` command of `gfsh` or in the `gemfire.properties` file to facilitate system analysis and troubleshooting. + Every application and server in a distributed system can access statistical data about <%=vars.product_name_long%> operations. You can configure the gathering of statistics by using the `alter runtime` command of `gfsh` or in the `gemfire.properties` file to facilitate system analysis and troubleshooting. -- **[Troubleshooting and System Recovery](../managing/troubleshooting/chapter_overview.html)** +- **[Troubleshooting and System Recovery](troubleshooting/chapter_overview.html)** This section provides strategies for handling common errors and failure situations. http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/cache_snapshots/chapter_overview.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/cache_snapshots/chapter_overview.html.md.erb b/geode-docs/managing/cache_snapshots/chapter_overview.html.md.erb index 1439348..1fae438 100644 --- a/geode-docs/managing/cache_snapshots/chapter_overview.html.md.erb +++ b/geode-docs/managing/cache_snapshots/chapter_overview.html.md.erb @@ -28,23 +28,23 @@ The snapshot file is a binary file that contains all data from a particular regi **Note:** The previous `Region.loadSnapshot` and `Region.saveSnapshot` APIs have been deprecated. Data written in this format is not compatible with the new APIs. -- **[Usage and Performance Notes](../../managing/cache_snapshots/using_cache_and_region_snapshots.html)** +- **[Usage and Performance Notes](using_cache_and_region_snapshots.html)** Optimize the cache and region snapshot feature by understanding how it performs. -- **[Exporting Cache and Region Snapshots](../../managing/cache_snapshots/exporting_a_snapshot.html)** +- **[Exporting Cache and Region Snapshots](exporting_a_snapshot.html)** - To save Geode cache or region data to a snapshot that you can later load into another distributed system or region, use the `cache.getSnapshotService.save` API, `region.getSnapshotService.save` API, or the `gfsh` command-line interface (`export data`). + To save <%=vars.product_name%> cache or region data to a snapshot that you can later load into another distributed system or region, use the `cache.getSnapshotService.save` API, `region.getSnapshotService.save` API, or the `gfsh` command-line interface (`export data`). -- **[Importing Cache and Region Snapshots](../../managing/cache_snapshots/importing_a_snapshot.html)** +- **[Importing Cache and Region Snapshots](importing_a_snapshot.html)** - To import a Geode cache or region data snapshot that you previously exported into another distributed system or region, use the `cache.getSnapshotService.load` API, `region.getSnapshotService.load` API, or the `gfsh` command-line interface (`import data`). + To import a <%=vars.product_name%> cache or region data snapshot that you previously exported into another distributed system or region, use the `cache.getSnapshotService.load` API, `region.getSnapshotService.load` API, or the `gfsh` command-line interface (`import data`). -- **[Filtering Entries During Import or Export](../../managing/cache_snapshots/filtering_snapshot_entries.html)** +- **[Filtering Entries During Import or Export](filtering_snapshot_entries.html)** You can customize your snapshot by filtering entries during the import or export of a region or a cache. -- **[Reading Snapshots Programmatically](../../managing/cache_snapshots/read_snapshots_programmatically.html)** +- **[Reading Snapshots Programmatically](read_snapshots_programmatically.html)** You can read a snapshot entry-by-entry for further processing or transformation into other formats. http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb ---------------------------------------------------------------------- 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 eaddd41..0963c6a 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 @@ -19,7 +19,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -To save Geode cache or region data to a snapshot that you can later load into another distributed system or region, use the `cache.getSnapshotService.save` API, `region.getSnapshotService.save` API, or the `gfsh` command-line interface (`export data`). +To save <%=vars.product_name%> cache or region data to a snapshot that you can later load into another distributed system or region, use the `cache.getSnapshotService.save` API, `region.getSnapshotService.save` API, or the `gfsh` command-line interface (`export data`). If an error occurs during export, the export halts and the snapshot operation is canceled. Typical errors that halt an export include scenarios such as full disk, problems with file permissions, and network partitioning. @@ -57,7 +57,7 @@ region.getSnapshotService().save(mySnapshot, SnapshotFormat.GEMFIRE); **gfsh:** -Open a gfsh prompt. After connecting to a Geode distributed system, at the prompt type: +Open a gfsh prompt. After connecting to a <%=vars.product_name%> distributed system, at the prompt type: ``` pre gfsh>export data --region=Region --file=filename.gfd http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/cache_snapshots/importing_a_snapshot.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/cache_snapshots/importing_a_snapshot.html.md.erb b/geode-docs/managing/cache_snapshots/importing_a_snapshot.html.md.erb index f8296a8..b3670bf 100644 --- a/geode-docs/managing/cache_snapshots/importing_a_snapshot.html.md.erb +++ b/geode-docs/managing/cache_snapshots/importing_a_snapshot.html.md.erb @@ -19,7 +19,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -To import a Geode cache or region data snapshot that you previously exported into another distributed system or region, use the `cache.getSnapshotService.load` API, `region.getSnapshotService.load` API, or the `gfsh` command-line interface (`import data`). +To import a <%=vars.product_name%> cache or region data snapshot that you previously exported into another distributed system or region, use the `cache.getSnapshotService.load` API, `region.getSnapshotService.load` API, or the `gfsh` command-line interface (`import data`). ## <a id="concept_62B1E24DA7F342E9BB16C0818F7A7B70__section_4B2C73CA1A734D9D96693A52BF99D75A" class="no-quick-link"></a>Import Requirements @@ -62,7 +62,7 @@ region.getSnapshotService().load(mySnapshot, SnapshotFormat.GEMFIRE); **gfsh:** -Open a gfsh prompt. After connecting to a Geode distributed system, at the prompt type: +Open a gfsh prompt. After connecting to a <%=vars.product_name%> distributed system, at the prompt type: ``` pre gfsh>import data --region=Region --file=filename.gfd http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/chapter_overview.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/chapter_overview.html.md.erb b/geode-docs/managing/disk_storage/chapter_overview.html.md.erb index 68e089f..49fd6b8 100644 --- a/geode-docs/managing/disk_storage/chapter_overview.html.md.erb +++ b/geode-docs/managing/disk_storage/chapter_overview.html.md.erb @@ -19,37 +19,37 @@ See the License for the specific language governing permissions and limitations under the License. --> -With Apache Geode disk stores, you can persist data to disk as a backup to your in-memory copy and overflow data to disk when memory use gets too high. +With <%=vars.product_name_long%> disk stores, you can persist data to disk as a backup to your in-memory copy and overflow data to disk when memory use gets too high. -- **[How Disk Stores Work](../../managing/disk_storage/how_disk_stores_work.html)** +- **[How Disk Stores Work](how_disk_stores_work.html)** Overflow and persistence use disk stores individually or together to store data. -- **[Disk Store File Names and Extensions](../../managing/disk_storage/file_names_and_extensions.html)** +- **[Disk Store File Names and Extensions](file_names_and_extensions.html)** Disk store files include store management files, access control files, and the operation log, or oplog, files, consisting of one file for deletions and another for all other operations. -- **[Disk Store Operation Logs](../../managing/disk_storage/operation_logs.html)** +- **[Disk Store Operation Logs](operation_logs.html)** - At creation, each operation log is initialized at the disk store's `max-oplog-size`, with the size divided between the `crf` and `drf` files. When the oplog is closed, Apache Geode shrinks the files to the space used in each file. + At creation, each operation log is initialized at the disk store's `max-oplog-size`, with the size divided between the `crf` and `drf` files. When the oplog is closed, <%=vars.product_name_long%> shrinks the files to the space used in each file. -- **[Configuring Disk Stores](../../managing/disk_storage/overview_using_disk_stores.html)** +- **[Configuring Disk Stores](overview_using_disk_stores.html)** - In addition to the disk stores you specify, Apache Geode has a default disk store that it uses when disk use is configured with no disk store name specified. You can modify default disk store behavior. + In addition to the disk stores you specify, <%=vars.product_name_long%> has a default disk store that it uses when disk use is configured with no disk store name specified. You can modify default disk store behavior. -- **[Optimizing a System with Disk Stores](../../managing/disk_storage/optimize_availability_and_performance.html)** +- **[Optimizing a System with Disk Stores](optimize_availability_and_performance.html)** Optimize availability and performance by following the guidelines in this section. -- **[Start Up and Shut Down with Disk Stores](../../managing/disk_storage/starting_system_with_disk_stores.html)** +- **[Start Up and Shut Down with Disk Stores](starting_system_with_disk_stores.html)** This section describes what happens during startup and shutdown and provides procedures for those operations. -- **[Disk Store Management](../../managing/disk_storage/managing_disk_stores.html)** +- **[Disk Store Management](managing_disk_stores.html)** The `gfsh` command-line tool has a number of options for examining and managing your disk stores. The `gfsh` tool, the `cache.xml` file and the DiskStore APIs are your management tools for online and offline disk stores. -- **[Creating Backups for System Recovery and Operational Management](../../managing/disk_storage/backup_restore_disk_store.html)** +- **[Creating Backups for System Recovery and Operational Management](backup_restore_disk_store.html)** A backup is a copy of persisted data from a disk store. A backup is used to restore the disk store to the state it was in when the backup was made. The appropriate back up and restore procedures differ based upon whether the distributed system is online or offline. An online system has currently running members. An offline system does not have any running members. http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/compacting_disk_stores.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/compacting_disk_stores.html.md.erb b/geode-docs/managing/disk_storage/compacting_disk_stores.html.md.erb index 0a88811..17910b5 100644 --- a/geode-docs/managing/disk_storage/compacting_disk_stores.html.md.erb +++ b/geode-docs/managing/disk_storage/compacting_disk_stores.html.md.erb @@ -20,9 +20,9 @@ limitations under the License. --> <a id="compacting_disk_stores__section_64BA304595364E38A28098EB09494531"></a> -When a cache operation is added to a disk store, any preexisting operation record for the same entry becomes obsolete, and Apache Geode marks it as garbage. For example, when you create an entry, the create operation is added to the store. If you update the entry later, the update operation is added and the create operation becomes garbage. Geode does not remove garbage records as it goes, but it tracks the percentage of garbage in each operation log, and provides mechanisms for removing garbage to compact your log files. +When a cache operation is added to a disk store, any preexisting operation record for the same entry becomes obsolete, and <%=vars.product_name_long%> marks it as garbage. For example, when you create an entry, the create operation is added to the store. If you update the entry later, the update operation is added and the create operation becomes garbage. <%=vars.product_name%> does not remove garbage records as it goes, but it tracks the percentage of garbage in each operation log, and provides mechanisms for removing garbage to compact your log files. -Geode compacts an old operation log by copying all non-garbage records into the current log and discarding the old files. As with logging, oplogs are rolled as needed during compaction to stay within the max oplog setting. +<%=vars.product_name%> compacts an old operation log by copying all non-garbage records into the current log and discarding the old files. As with logging, oplogs are rolled as needed during compaction to stay within the max oplog setting. You can configure the system to automatically compact any closed operation log when its garbage content reaches a certain percentage. You can also manually request compaction for online and offline disk stores. For the online disk store, the current operation log is not available for compaction, no matter how much garbage it contains. @@ -36,10 +36,10 @@ Offline compaction runs essentially in the same way, but without the incoming ca Old log files become eligible for online compaction when their garbage content surpasses a configured percentage of the total file. A record is garbage when its operation is superseded by a more recent operation for the same object. During compaction, the non-garbage records are added to the current log along with new cache operations. Online compaction does not block current system operations. -- **Automatic compaction**. When `auto-compact` is true, Geode automatically compacts each oplog when its garbage content surpasses the `compaction-threshold`. This takes cycles from your other operations, so you may want to disable this and only do manual compaction, to control the timing. +- **Automatic compaction**. When `auto-compact` is true, <%=vars.product_name%> automatically compacts each oplog when its garbage content surpasses the `compaction-threshold`. This takes cycles from your other operations, so you may want to disable this and only do manual compaction, to control the timing. - **Manual compaction**. To run manual compaction: - - Set the disk store attribute `allow-force-compaction` to true. This causes Geode to maintain extra data about the files so it can compact on demand. This is disabled by default to save space. You can run manual online compaction at any time while the system is running. Oplogs eligible for compaction based on the `compaction-threshold` are compacted into the current oplog. - - Run manual compaction as needed. Geode has two types of manual compaction: + - Set the disk store attribute `allow-force-compaction` to true. This causes <%=vars.product_name%> to maintain extra data about the files so it can compact on demand. This is disabled by default to save space. You can run manual online compaction at any time while the system is running. Oplogs eligible for compaction based on the `compaction-threshold` are compacted into the current oplog. + - Run manual compaction as needed. <%=vars.product_name%> has two types of manual compaction: - 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: ``` pre @@ -73,7 +73,7 @@ gfsh>compact offline-disk-store --name=Disk2 --disk-dirs=/Disks/Disk2 **Note:** Do not perform offline compaction on the baseline directory of an incremental backup. -You must provide all of the directories in the disk store. If no oplog max size is specified, Geode uses the system default. +You must provide all of the directories in the disk store. If no oplog max size is specified, <%=vars.product_name%> uses the system default. Offline compaction can take a lot of memory. If you get a `java.lang.OutOfMemory` error while running this, you may need to increase your heap size with the `-J=-Xmx` parameter. http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/disk_store_configuration_params.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/disk_store_configuration_params.html.md.erb b/geode-docs/managing/disk_storage/disk_store_configuration_params.html.md.erb index 939028e..25f2083 100644 --- a/geode-docs/managing/disk_storage/disk_store_configuration_params.html.md.erb +++ b/geode-docs/managing/disk_storage/disk_store_configuration_params.html.md.erb @@ -118,6 +118,6 @@ Example: ``` **Note:** -The directories must exist when the disk store is created or the system throws an exception. Geode does not create directories. +The directories must exist when the disk store is created or the system throws an exception. <%=vars.product_name%> does not create directories. Use different disk-dir specifications for different disk stores. You cannot use the same directory for the same named disk store in two different members. http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/how_disk_stores_work.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/how_disk_stores_work.html.md.erb b/geode-docs/managing/disk_storage/how_disk_stores_work.html.md.erb index ee75b98..5d8a89e 100644 --- a/geode-docs/managing/disk_storage/how_disk_stores_work.html.md.erb +++ b/geode-docs/managing/disk_storage/how_disk_stores_work.html.md.erb @@ -27,7 +27,7 @@ Disk storage is available for these items: - **Regions**. Persist and/or overflow data from regions. - **Serverâs client subscription queues**. Overflow the messaging queues to control memory use. - **Gateway sender queues**. Persist these for high availability. These queues always overflow. -- **PDX serialization metadata**. Persist metadata about objects you serialize using Geode PDX serialization. +- **PDX serialization metadata**. Persist metadata about objects you serialize using <%=vars.product_name%> PDX serialization. Each member has its own set of disk stores, and they are completely separate from the disk stores of any other member. For each disk store, define where and how the data is stored to disk. You can store data from multiple regions and queues in a single disk store. @@ -35,9 +35,9 @@ This figure shows a member with disk stores D through R defined. The member has <img src="../../images/diskStores-1.gif" id="how_disk_stores_work__image_CB7972998C4A40B2A02550B97A723536" class="image" /> -## <a id="how_disk_stores_work__section_433EEEA1560D40DD9842200181EB1D0A" class="no-quick-link"></a>What Geode Writes to the Disk Store +## <a id="how_disk_stores_work__section_433EEEA1560D40DD9842200181EB1D0A" class="no-quick-link"></a>What <%=vars.product_name%> Writes to the Disk Store -This list describes the items that Geode comprise the disk store: +This list describes the items that <%=vars.product_name%> comprise the disk store: - The members that host the store, and information on their status, such as which members are online and which members are offline and time stamps. - A disk store identifier. @@ -45,11 +45,11 @@ This list describes the items that Geode comprise the disk store: - Colocated regions that the regions in the disk store are dependent upon. - A set of files that specify all keys for the regions, as well as all operations on the regions. Given both keys and operations, a region can be recreated when a member is restarted. -Geode does not write indexes to disk. +<%=vars.product_name%> does not write indexes to disk. ## <a id="how_disk_stores_work__section_C1A047CD5518499D94A0E9A0328F6DB8" class="no-quick-link"></a>Disk Store State -The files for a disk store are used by Geode as a group. Treat them as a single entity. If you copy them, copy them all together. Do not change the file names. +The files for a disk store are used by <%=vars.product_name%> as a group. Treat them as a single entity. If you copy them, copy them all together. Do not change the file names. Disk store access and management differs according to whether the member is online or offline. http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/keeping_offline_disk_store_in_sync.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/keeping_offline_disk_store_in_sync.html.md.erb b/geode-docs/managing/disk_storage/keeping_offline_disk_store_in_sync.html.md.erb index 1d32d8c..cd1bce4 100644 --- a/geode-docs/managing/disk_storage/keeping_offline_disk_store_in_sync.html.md.erb +++ b/geode-docs/managing/disk_storage/keeping_offline_disk_store_in_sync.html.md.erb @@ -79,4 +79,4 @@ You can remove the region from the disk store in one of two ways: --disk-dirs=/firstDiskStoreDir,/secondDiskStoreDir,/thirdDiskStoreDir --remove ``` -To guard against unintended data loss, Geode maintains the region in the disk store until you manually remove it. Regions in the disk stores that are not associated with any region in your application are still loaded into temporary regions in memory and kept there for the life of the member. The system has no way of detecting whether the cache region will be created by your API at some point, so it keeps the temporary region loaded and available. +To guard against unintended data loss, <%=vars.product_name%> maintains the region in the disk store until you manually remove it. Regions in the disk stores that are not associated with any region in your application are still loaded into temporary regions in memory and kept there for the life of the member. The system has no way of detecting whether the cache region will be created by your API at some point, so it keeps the temporary region loaded and available. http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/managing_disk_buffer_flushes.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/managing_disk_buffer_flushes.html.md.erb b/geode-docs/managing/disk_storage/managing_disk_buffer_flushes.html.md.erb index 7238843..87076f7 100644 --- a/geode-docs/managing/disk_storage/managing_disk_buffer_flushes.html.md.erb +++ b/geode-docs/managing/disk_storage/managing_disk_buffer_flushes.html.md.erb @@ -19,19 +19,19 @@ See the License for the specific language governing permissions and limitations under the License. --> -You can configure Geode to write immediately to disk and you may be able to modify your operating system behavior to perform buffer flushes more frequently. +You can configure <%=vars.product_name%> to write immediately to disk and you may be able to modify your operating system behavior to perform buffer flushes more frequently. -Typically, Geode writes disk data into the operating system's disk buffers and the operating system periodically flushes the buffers to disk. Increasing the frequency of writes to disk decreases the likelihood of data loss from application or machine crashes, but it impacts performance. Your other option, which may give you better performance, is to use Geode's in-memory data backups. Do this by storing your data in multiple replicated regions or in partitioned regions that are configured with redundant copies. See [Region Types](../../developing/region_options/region_types.html#region_types). +Typically, <%=vars.product_name%> writes disk data into the operating system's disk buffers and the operating system periodically flushes the buffers to disk. Increasing the frequency of writes to disk decreases the likelihood of data loss from application or machine crashes, but it impacts performance. Your other option, which may give you better performance, is to use <%=vars.product_name%>'s in-memory data backups. Do this by storing your data in multiple replicated regions or in partitioned regions that are configured with redundant copies. See [Region Types](../../developing/region_options/region_types.html#region_types). ## <a id="disk_buffer_flushes__section_448348BD28B14F478D81CC2EDC6C7049" class="no-quick-link"></a>Modifying Disk Flushes for the Operating System You may be able to change the operating system settings for periodic flushes. You may also be able to perform explicit disk flushes from your application code. For information on these options, see your operating system's documentation. For example, in Linux you can change the disk flush interval by modifying the setting `/proc/sys/vm/dirty_expire_centiseconds`. It defaults to 30 seconds. To alter this setting, see the Linux documentation for `dirty_expire_centiseconds`. -## <a id="disk_buffer_flushes__section_D1068505581A43EE8395DBE97297C60F" class="no-quick-link"></a>Modifying Geode to Flush Buffers on Disk Writes +## <a id="disk_buffer_flushes__section_D1068505581A43EE8395DBE97297C60F" class="no-quick-link"></a>Modifying <%=vars.product_name%> to Flush Buffers on Disk Writes -You can have Geode flush the disk buffers on every disk write. Do this by setting the system property `gemfire.syncWrites` to true at the command line when you start your Geode member. You can only modify this setting when you start a member. When this is set, Geode uses a Java `RandomAccessFile` with the flags "rwd", which causes every file update to be written synchronously to the storage device. This only guarantees your data if your disk stores are on a local device. See the Java documentation for `java.IO.RandomAccessFile`. +You can have <%=vars.product_name%> flush the disk buffers on every disk write. Do this by setting the system property `gemfire.syncWrites` to true at the command line when you start your <%=vars.product_name%> member. You can only modify this setting when you start a member. When this is set, <%=vars.product_name%> uses a Java `RandomAccessFile` with the flags "rwd", which causes every file update to be written synchronously to the storage device. This only guarantees your data if your disk stores are on a local device. See the Java documentation for `java.IO.RandomAccessFile`. -To modify the setting for a Geode application, add this to the java command line when you start the member: +To modify the setting for a <%=vars.product_name%> application, add this to the java command line when you start the member: ``` pre -Dgemfire.syncWrites=true http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/managing_disk_stores.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/managing_disk_stores.html.md.erb b/geode-docs/managing/disk_storage/managing_disk_stores.html.md.erb index 5262be1..138ca25 100644 --- a/geode-docs/managing/disk_storage/managing_disk_stores.html.md.erb +++ b/geode-docs/managing/disk_storage/managing_disk_stores.html.md.erb @@ -23,20 +23,20 @@ The `gfsh` command-line tool has a number of options for examining and managing See [Disk Store Commands](../../tools_modules/gfsh/quick_ref_commands_by_area.html#topic_1ACC91B493EE446E89EC7DBFBBAE00EA) for a list of available commands. -- **[Disk Store Management Commands and Operations](../../managing/disk_storage/managing_disk_stores_cmds.html)** +- **[Disk Store Management Commands and Operations](managing_disk_stores_cmds.html)** -- **[Validating a Disk Store](../../managing/disk_storage/validating_disk_store.html)** +- **[Validating a Disk Store](validating_disk_store.html)** -- **[Running Compaction on Disk Store Log Files](../../managing/disk_storage/compacting_disk_stores.html)** +- **[Running Compaction on Disk Store Log Files](compacting_disk_stores.html)** -- **[Keeping a Disk Store Synchronized with the Cache](../../managing/disk_storage/keeping_offline_disk_store_in_sync.html)** +- **[Keeping a Disk Store Synchronized with the Cache](keeping_offline_disk_store_in_sync.html)** -- **[Configuring Disk Free Space Monitoring](../../managing/disk_storage/disk_free_space_monitoring.html)** +- **[Configuring Disk Free Space Monitoring](disk_free_space_monitoring.html)** -- **[Handling Missing Disk Stores](../../managing/disk_storage/handling_missing_disk_stores.html)** +- **[Handling Missing Disk Stores](handling_missing_disk_stores.html)** -- **[Altering When Buffers Are Flushed to Disk](../../managing/disk_storage/managing_disk_buffer_flushes.html)** +- **[Altering When Buffers Are Flushed to Disk](managing_disk_buffer_flushes.html)** - You can configure Geode to write immediately to disk and you may be able to modify your operating system behavior to perform buffer flushes more frequently. + You can configure <%=vars.product_name%> to write immediately to disk and you may be able to modify your operating system behavior to perform buffer flushes more frequently. http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/operation_logs.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/operation_logs.html.md.erb b/geode-docs/managing/disk_storage/operation_logs.html.md.erb index b8d4211..db0fd09 100644 --- a/geode-docs/managing/disk_storage/operation_logs.html.md.erb +++ b/geode-docs/managing/disk_storage/operation_logs.html.md.erb @@ -19,15 +19,15 @@ See the License for the specific language governing permissions and limitations under the License. --> -At creation, each operation log is initialized at the disk store's `max-oplog-size`, with the size divided between the `crf` and `drf` files. When the oplog is closed, Apache Geode shrinks the files to the space used in each file. +At creation, each operation log is initialized at the disk store's `max-oplog-size`, with the size divided between the `crf` and `drf` files. When the oplog is closed, <%=vars.product_name_long%> shrinks the files to the space used in each file. <a id="operation_logs__section_C0B1391492394A908577C29772902A42"></a> -After the oplog is closed, Geode also attempts to create a `krf` file, which contains the key names as well as the offset for the value within the `crf` file. Although this file is not required for startup, if it is available, it will improve startup performance by allowing Geode to load the entry values in the background after the entry keys are loaded. +After the oplog is closed, <%=vars.product_name%> also attempts to create a `krf` file, which contains the key names as well as the offset for the value within the `crf` file. Although this file is not required for startup, if it is available, it will improve startup performance by allowing <%=vars.product_name%> to load the entry values in the background after the entry keys are loaded. -When an operation log is full, Geode automatically closes it and creates a new log with the next sequence number. This is called *oplog rolling*. You can also request an oplog rolling through the API call `DiskStore.forceRoll`. You may want to do this immediately before compacting your disk stores, so the latest oplog is available for compaction. +When an operation log is full, <%=vars.product_name%> automatically closes it and creates a new log with the next sequence number. This is called *oplog rolling*. You can also request an oplog rolling through the API call `DiskStore.forceRoll`. You may want to do this immediately before compacting your disk stores, so the latest oplog is available for compaction. **Note:** -Log compaction can change the names of the disk store files. File number sequencing is usually altered, with some existing logs removed or replaced by newer logs with higher numbering. Geode always starts a new log at a number higher than any existing number. +Log compaction can change the names of the disk store files. File number sequencing is usually altered, with some existing logs removed or replaced by newer logs with higher numbering. <%=vars.product_name%> always starts a new log at a number higher than any existing number. This example listing shows the logs in a system with only one disk directory specified for the store. The first log (`BACKUPCacheOverflow_1.crf` and `BACKUPCacheOverflow_1.drf`) has been closed and the system is writing to the second log. @@ -47,9 +47,9 @@ The system rotates through all available disk directories to write its logs. The ## <a id="operation_logs__section_8431984F4E6644D79292850CCA60E6E3" class="no-quick-link"></a>When Disk Store Oplogs Reach the Configured Disk Capacity -If no directory exists that is within its capacity limits, how Geode handles this depends on whether automatic compaction is enabled. +If no directory exists that is within its capacity limits, how <%=vars.product_name%> handles this depends on whether automatic compaction is enabled. -- If auto-compaction is enabled, Geode creates a new oplog in one of the directories, going over the limit, and logs a warning that reports: +- If auto-compaction is enabled, <%=vars.product_name%> creates a new oplog in one of the directories, going over the limit, and logs a warning that reports: ``` pre Even though the configured directory size limit has been exceeded a @@ -58,9 +58,9 @@ If no directory exists that is within its capacity limits, how Geode handles thi ``` **Note:** - When auto-compaction is enabled, `dir-size` does not limit how much disk space is used. Geode will perform auto-compaction, which should free space, but the system may go over the configured disk limits. + When auto-compaction is enabled, `dir-size` does not limit how much disk space is used. <%=vars.product_name%> will perform auto-compaction, which should free space, but the system may go over the configured disk limits. -- If auto-compaction is disabled, Geode does not create a new oplog, operations in the regions attached to the disk store block, and Geode logs this error: +- If auto-compaction is disabled, <%=vars.product_name%> does not create a new oplog, operations in the regions attached to the disk store block, and <%=vars.product_name%> logs this error: ``` pre Disk is full and rolling is disabled. No space can be created http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/optimize_availability_and_performance.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/optimize_availability_and_performance.html.md.erb b/geode-docs/managing/disk_storage/optimize_availability_and_performance.html.md.erb index 5443d93..f8f93d4 100644 --- a/geode-docs/managing/disk_storage/optimize_availability_and_performance.html.md.erb +++ b/geode-docs/managing/disk_storage/optimize_availability_and_performance.html.md.erb @@ -21,7 +21,7 @@ limitations under the License. Optimize availability and performance by following the guidelines in this section. -1. Apache Geode recommends the use of `ext4` filesystems when operating on Linux or Solaris platforms. The `ext4` filesystem supports preallocation, which benefits disk startup performance. If you are using `ext3` filesystems in latency-sensitive environments with high write throughput, you can improve disk startup performance by setting the `maxOplogSize` (see the `DiskStoreFactory.setMaxOplogSize`) to a value lower than the default 1 GB and by disabling preallocation by specifying the system property `gemfire.preAllocateDisk=false` upon Geode process startup. +1. <%=vars.product_name_long%> recommends the use of `ext4` filesystems when operating on Linux or Solaris platforms. The `ext4` filesystem supports preallocation, which benefits disk startup performance. If you are using `ext3` filesystems in latency-sensitive environments with high write throughput, you can improve disk startup performance by setting the `maxOplogSize` (see the `DiskStoreFactory.setMaxOplogSize`) to a value lower than the default 1 GB and by disabling preallocation by specifying the system property `gemfire.preAllocateDisk=false` upon <%=vars.product_name%> process startup. 2. When you start your system, start all the members that have persistent regions at roughly the same time. Create and use startup scripts for consistency and completeness. 3. Shut down your system using the gfsh `shutdown` command. This is an ordered shutdown that positions your disk stores for a faster startup. 4. Configure critical usage thresholds (`disk-usage-warning-percentage` and `disk-usage-critical-percentage`) for the disk. By default, these are set to 80% for warning and 99% for errors that will shut down the cache. http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/overview_using_disk_stores.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/overview_using_disk_stores.html.md.erb b/geode-docs/managing/disk_storage/overview_using_disk_stores.html.md.erb index 74c1b96..ce5e2cf 100644 --- a/geode-docs/managing/disk_storage/overview_using_disk_stores.html.md.erb +++ b/geode-docs/managing/disk_storage/overview_using_disk_stores.html.md.erb @@ -19,17 +19,17 @@ See the License for the specific language governing permissions and limitations under the License. --> -In addition to the disk stores you specify, Apache Geode has a default disk store that it uses when disk use is configured with no disk store name specified. You can modify default disk store behavior. +In addition to the disk stores you specify, <%=vars.product_name_long%> has a default disk store that it uses when disk use is configured with no disk store name specified. You can modify default disk store behavior. -- **[Designing and Configuring Disk Stores](../../managing/disk_storage/using_disk_stores.html)** +- **[Designing and Configuring Disk Stores](using_disk_stores.html)** You define disk stores in your cache, then you assign them to your regions and queues by setting the `disk-store-name` attribute in your region and queue configurations. -- **[Disk Store Configuration Parameters](../../managing/disk_storage/disk_store_configuration_params.html)** +- **[Disk Store Configuration Parameters](disk_store_configuration_params.html)** You define your disk stores by using the `gfsh create disk-store` command or in `<disk-store>` subelements of your cache declaration in `cache.xml`. All disk stores are available for use by all of your regions and queues. -- **[Modifying the Default Disk Store](../../managing/disk_storage/using_the_default_disk_store.html)** +- **[Modifying the Default Disk Store](using_the_default_disk_store.html)** You can modify the behavior of the default disk store by specifying the attributes you want for the disk store named "DEFAULT". http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/starting_system_with_disk_stores.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/starting_system_with_disk_stores.html.md.erb b/geode-docs/managing/disk_storage/starting_system_with_disk_stores.html.md.erb index d4a8cbc..977185b 100644 --- a/geode-docs/managing/disk_storage/starting_system_with_disk_stores.html.md.erb +++ b/geode-docs/managing/disk_storage/starting_system_with_disk_stores.html.md.erb @@ -58,7 +58,7 @@ If the member's disk store has data for a region that is never created, the data Each memberâs persistent regions load and go online as quickly as possible, not waiting unnecessarily for other members to complete. For performance reasons, these actions occur asynchronously: - Once at least one copy of each and every bucket is recovered from disk, the region is available. Secondary buckets will load asynchronously. -- Entry keys are loaded from the key file in the disk store before considering entry values. Once all keys are loaded, Geode loads the entry values asynchronously. If a value is requested before it has loaded, the value will immediately be fetched from the disk store. +- Entry keys are loaded from the key file in the disk store before considering entry values. Once all keys are loaded, <%=vars.product_name%> loads the entry values asynchronously. If a value is requested before it has loaded, the value will immediately be fetched from the disk store. ## <a id="starting_system_with_disk_stores__section_D0A7403707B847749A22BF9221A2C823" class="no-quick-link"></a>Start Up Procedure http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/using_disk_stores.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/using_disk_stores.html.md.erb b/geode-docs/managing/disk_storage/using_disk_stores.html.md.erb index 4835533..bcf7b5b 100644 --- a/geode-docs/managing/disk_storage/using_disk_stores.html.md.erb +++ b/geode-docs/managing/disk_storage/using_disk_stores.html.md.erb @@ -22,7 +22,7 @@ limitations under the License. You define disk stores in your cache, then you assign them to your regions and queues by setting the `disk-store-name` attribute in your region and queue configurations. **Note:** -Besides the disk stores you specify, Apache Geode has a default disk store that it uses when disk use is configured with no disk store name specified. By default, this disk store is saved to the applicationâs working directory. You can change its behavior, as indicated in [Create and Configure Your Disk Stores](using_disk_stores.html#defining_disk_stores__section_37BC5A4D84B34DB49E489DD4141A4884) and [Modifying the Default Disk Store](using_the_default_disk_store.html#using_the_default_disk_store). +Besides the disk stores you specify, <%=vars.product_name_long%> has a default disk store that it uses when disk use is configured with no disk store name specified. By default, this disk store is saved to the applicationâs working directory. You can change its behavior, as indicated in [Create and Configure Your Disk Stores](using_disk_stores.html#defining_disk_stores__section_37BC5A4D84B34DB49E489DD4141A4884) and [Modifying the Default Disk Store](using_the_default_disk_store.html#using_the_default_disk_store). - [Design Your Disk Stores](using_disk_stores.html#defining_disk_stores__section_0CD724A12EE4418587046AAD9EEC59C5) - [Create and Configure Your Disk Stores](using_disk_stores.html#defining_disk_stores__section_37BC5A4D84B34DB49E489DD4141A4884) @@ -31,11 +31,11 @@ Besides the disk stores you specify, Apache Geode has a default disk store that ## <a id="defining_disk_stores__section_0CD724A12EE4418587046AAD9EEC59C5" class="no-quick-link"></a>Design Your Disk Stores -Before you begin, you should understand Geode [Basic Configuration and Programming](../../basic_config/book_intro.html). +Before you begin, you should understand <%=vars.product_name%> [Basic Configuration and Programming](../../basic_config/book_intro.html). 1. Work with your system designers and developers to plan for anticipated disk storage requirements in your testing and production caching systems. Take into account space and functional requirements. - For efficiency, separate data that is only overflowed in separate disk stores from data that is persisted or persisted and overflowed. Regions can be overflowed, persisted, or both. Server subscription queues are only overflowed. - - When calculating your disk requirements, figure in your data modification patterns and your compaction strategy. Geode creates each oplog file at the max-oplog-size, which defaults to 1 GB. Obsolete operations are only removed from the oplogs during compaction, so you need enough space to store all operations that are done between compactions. For regions where you are doing a mix of updates and deletes, if you use automatic compaction, a good upper bound for the required disk space is + - When calculating your disk requirements, figure in your data modification patterns and your compaction strategy. <%=vars.product_name%> creates each oplog file at the max-oplog-size, which defaults to 1 GB. Obsolete operations are only removed from the oplogs during compaction, so you need enough space to store all operations that are done between compactions. For regions where you are doing a mix of updates and deletes, if you use automatic compaction, a good upper bound for the required disk space is ``` pre (1 / (1 - (compaction_threshold/100)) ) * data size @@ -49,7 +49,7 @@ Before you begin, you should understand Geode [Basic Configuration and Programmi ## <a id="defining_disk_stores__section_37BC5A4D84B34DB49E489DD4141A4884" class="no-quick-link"></a>Create and Configure Your Disk Stores -1. In the locations you have chosen, create all directories you will specify for your disk stores to use. Geode throws an exception if the specified directories are not available when a disk store is created. You do not need to populate these directories with anything. +1. In the locations you have chosen, create all directories you will specify for your disk stores to use. <%=vars.product_name%> throws an exception if the specified directories are not available when a disk store is created. You do not need to populate these directories with anything. 2. Open a `gfsh` prompt and connect to the distributed system. 3. At the `gfsh` prompt, create and configure a disk store: - Specify the name (`--name`) of the disk-store. http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/disk_storage/using_the_default_disk_store.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/disk_storage/using_the_default_disk_store.html.md.erb b/geode-docs/managing/disk_storage/using_the_default_disk_store.html.md.erb index 2618290..b2f37de 100644 --- a/geode-docs/managing/disk_storage/using_the_default_disk_store.html.md.erb +++ b/geode-docs/managing/disk_storage/using_the_default_disk_store.html.md.erb @@ -22,7 +22,7 @@ limitations under the License. You can modify the behavior of the default disk store by specifying the attributes you want for the disk store named "DEFAULT". <a id="using_the_default_disk_store__section_7D6E1A05D28840AC8606EF0D88E9B373"></a> -Whenever you use disk stores without specifying the disk store to use, Geode uses the disk store named "DEFAULT". +Whenever you use disk stores without specifying the disk store to use, <%=vars.product_name%> uses the disk store named "DEFAULT". For example, these region and queue configurations specify persistence and/or overflow, but do not specify the disk-store-name. Because no disk store is specified, these use the disk store named "DEFAULT". @@ -50,7 +50,7 @@ Example of using the default disk store for server subscription queue overflow ( ## <a id="using_the_default_disk_store__section_671AED6EAFEE485D837411DEBE0C6BC6" class="no-quick-link"></a>Change the Behavior of the Default Disk Store -Geode initializes the default disk store with the default disk store configuration settings. You can modify the behavior of the default disk store by specifying the attributes you want for the disk store named "DEFAULT". The only thing you canât change about the default disk store is the name. +<%=vars.product_name%> initializes the default disk store with the default disk store configuration settings. You can modify the behavior of the default disk store by specifying the attributes you want for the disk store named "DEFAULT". The only thing you canât change about the default disk store is the name. The following example changes the default disk store to allow manual compaction and to use multiple, non-default directories: http://git-wip-us.apache.org/repos/asf/geode/blob/1b84ecbe/geode-docs/managing/heap_use/heap_management.html.md.erb ---------------------------------------------------------------------- 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 7fab249..f4d934d 100644 --- a/geode-docs/managing/heap_use/heap_management.html.md.erb +++ b/geode-docs/managing/heap_use/heap_management.html.md.erb @@ -19,17 +19,17 @@ See the License for the specific language governing permissions and limitations under the License. --> -By default, Apache Geode uses the JVM heap. Apache Geode also offers an option to store data off heap. This section describes how to manage heap and off-heap memory to best support your application. +By default, <%=vars.product_name_long%> uses the JVM heap. <%=vars.product_name_long%> also offers an option to store data off heap. This section describes how to manage heap and off-heap memory to best support your application. ## <a id="section_590DA955523246ED980E4E351FF81F71" class="no-quick-link"></a>Tuning the JVM's Garbage Collection Parameters -Because Apache Geode is specifically designed to manipulate data held in memory, you can optimize your application's performance by tuning the way Apache Geode uses the JVM heap. +Because <%=vars.product_name_long%> is specifically designed to manipulate data held in memory, you can optimize your application's performance by tuning the way <%=vars.product_name_long%> uses the JVM heap. See your JVM documentation for all JVM-specific settings that can be used to improve garbage collection (GC) response. At a minimum, do the following: 1. Set the initial and maximum heap switches, `-Xms` and `-Xmx`, to the same values. The `gfsh start server` options `--initial-heap` and `--max-heap` accomplish the same purpose, with the added value of providing resource manager defaults such as eviction threshold and critical threshold. 2. Configure your JVM for concurrent mark-sweep (CMS) garbage collection. -3. If your JVM allows, configure it to initiate CMS collection when heap use is at least 10% lower than your setting for the resource manager `eviction-heap-percentage`. You want the collector to be working when Geode is evicting or the evictions will not result in more free memory. For example, if the `eviction-heap-percentage` is set to 65, set your garbage collection to start when the heap use is no higher than 55%. +3. If your JVM allows, configure it to initiate CMS collection when heap use is at least 10% lower than your setting for the resource manager `eviction-heap-percentage`. You want the collector to be working when <%=vars.product_name%> is evicting or the evictions will not result in more free memory. For example, if the `eviction-heap-percentage` is set to 65, set your garbage collection to start when the heap use is no higher than 55%. | JVM | CMS switch flag | CMS initiation (begin at heap % N) | |-------------|---------------------------|----------------------------------------| @@ -54,12 +54,12 @@ $ gfsh start server --name=app.MyApplication --initial-heap=30m --max-heap=30m \ --J=-XX:+UseConcMarkSweepGC --J=-XX:CMSInitiatingOccupancyFraction=60 ``` -## <a id="how_the_resource_manager_works" class="no-quick-link"></a>Using the Geode Resource Manager +## <a id="how_the_resource_manager_works" class="no-quick-link"></a>Using the <%=vars.product_name%> Resource Manager -The Geode resource manager works with your JVM's tenured garbage collector to control heap use and protect your member from hangs and crashes due to memory overload. +The <%=vars.product_name%> resource manager works with your JVM's tenured garbage collector to control heap use and protect your member from hangs and crashes due to memory overload. <a id="how_the_resource_manager_works__section_53E80B61991447A2915E8A754383B32D"></a> -The Geode resource manager prevents the cache from consuming too much memory by evicting old data. If the garbage collector is unable to keep up, the resource manager refuses additions to the cache until the collector has freed an adequate amount of memory. +The <%=vars.product_name%> resource manager prevents the cache from consuming too much memory by evicting old data. If the garbage collector is unable to keep up, the resource manager refuses additions to the cache until the collector has freed an adequate amount of memory. The resource manager has two threshold settings, each expressed as a percentage of the total tenured heap. Both are disabled by default. @@ -75,7 +75,7 @@ The resource manager has two threshold settings, each expressed as a percentage When heap use passes the eviction threshold in either direction, the manager logs an info-level message. -When heap use exceeds the critical threshold, the manager logs an error-level message. Avoid exceeding the critical threshold. Once identified as critical, the Geode member becomes a read-only member that refuses cache updates for all of its regions, including incoming distributed updates. +When heap use exceeds the critical threshold, the manager logs an error-level message. Avoid exceeding the critical threshold. Once identified as critical, the <%=vars.product_name%> member becomes a read-only member that refuses cache updates for all of its regions, including incoming distributed updates. For more information, see `org.apache.geode.cache.control.ResourceManager` in the online API documentation. @@ -98,13 +98,13 @@ Resource manager behavior is closely tied to the triggering of Garbage Collectio <a id="configuring_resource_manager__section_B47A78E7BA0048C89FBBDB7441C308BE"></a> The recommendations provided here for using the manager assume you have a solid understanding of your Java VM's heap management and garbage collection service. -The resource manager is available for use in any Apache Geode member, but you may not want to activate it everywhere. For some members it might be better to occasionally restart after a hang or OME crash than to evict data and/or refuse distributed caching activities. Also, members that do not risk running past their memory limits would not benefit from the overhead the resource manager consumes. Cache servers are often configured to use the manager because they generally host more data and have more data activity than other members, requiring greater responsiveness in data cleanup and collection. +The resource manager is available for use in any <%=vars.product_name_long%> member, but you may not want to activate it everywhere. For some members it might be better to occasionally restart after a hang or OME crash than to evict data and/or refuse distributed caching activities. Also, members that do not risk running past their memory limits would not benefit from the overhead the resource manager consumes. Cache servers are often configured to use the manager because they generally host more data and have more data activity than other members, requiring greater responsiveness in data cleanup and collection. For the members where you want to activate the resource manager: -1. Configure Geode for heap LRU management. +1. Configure <%=vars.product_name%> for heap LRU management. -2. Set the JVM GC tuning parameters to handle heap and garbage collection in conjunction with the Geode manager. +2. Set the JVM GC tuning parameters to handle heap and garbage collection in conjunction with the <%=vars.product_name%> manager. 3. Monitor and tune heap LRU configurations and your GC configurations. @@ -112,7 +112,7 @@ For the members where you want to activate the resource manager: 5. In production, keep monitoring and tuning to meet changing needs. -## <a id="configuring_resource_manager__section_4949882892DA46F6BB8588FA97037F45" class="no-quick-link"></a>Configure Geode for Heap LRU Management +## <a id="configuring_resource_manager__section_4949882892DA46F6BB8588FA97037F45" class="no-quick-link"></a>Configure <%=vars.product_name%> for Heap LRU Management The configuration terms used here are `cache.xml` elements and attributes, but you can also configure through `gfsh` and the `org.apache.geode.cache.control.ResourceManager` and `Region` APIs. @@ -149,15 +149,15 @@ cache.xml example: ## <a id="set_jvm_gc_tuning_params" class="no-quick-link"></a>Set the JVM GC Tuning Parameters -If your JVM allows, configure it to initiate concurrent mark-sweep (CMS) garbage collection when heap use is at least 10% lower than your setting for the resource manager `eviction-heap-percentage`. You want the collector to be working when Geode is evicting or the evictions will not result in more free memory. For example, if the `eviction-heap-percentage` is set to 65, set your garbage collection to start when the heap use is no higher than 55%. +If your JVM allows, configure it to initiate concurrent mark-sweep (CMS) garbage collection when heap use is at least 10% lower than your setting for the resource manager `eviction-heap-percentage`. You want the collector to be working when <%=vars.product_name%> is evicting or the evictions will not result in more free memory. For example, if the `eviction-heap-percentage` is set to 65, set your garbage collection to start when the heap use is no higher than 55%. ## <a id="configuring_resource_manager__section_DE1CC494C2B547B083AA00821250972A" class="no-quick-link"></a>Monitor and Tune Heap LRU Configurations -In tuning the resource manager, your central focus should be keeping the member below the critical threshold. The critical threshold is provided to avoid member hangs and crashes, but because of its exception-throwing behavior for distributed updates, the time spent in critical negatively impacts the entire distributed system. To stay below critical, tune so that the Geode eviction and the JVM's GC respond adequately when the eviction threshold is reached. +In tuning the resource manager, your central focus should be keeping the member below the critical threshold. The critical threshold is provided to avoid member hangs and crashes, but because of its exception-throwing behavior for distributed updates, the time spent in critical negatively impacts the entire distributed system. To stay below critical, tune so that the <%=vars.product_name%> eviction and the JVM's GC respond adequately when the eviction threshold is reached. Use the statistics provided by your JVM to make sure your memory and GC settings are sufficient for your needs. -The Geode `ResourceManagerStats` provide information about memory use and the manager thresholds and eviction activities. +The <%=vars.product_name%> `ResourceManagerStats` provide information about memory use and the manager thresholds and eviction activities. If your application spikes above the critical threshold on a regular basis, try lowering the eviction threshold. If the application never goes near critical, you might raise the eviction threshold to gain more usable memory without the overhead of unneeded evictions or GC cycles.
