Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5C37F200BB2 for ; Sat, 15 Oct 2016 00:17:41 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5ABF5160AE3; Fri, 14 Oct 2016 22:17:41 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DD12F160AFB for ; Sat, 15 Oct 2016 00:17:38 +0200 (CEST) Received: (qmail 42953 invoked by uid 500); 14 Oct 2016 22:17:38 -0000 Mailing-List: contact commits-help@geode.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.incubator.apache.org Delivered-To: mailing list commits@geode.incubator.apache.org Received: (qmail 42894 invoked by uid 99); 14 Oct 2016 22:17:38 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2016 22:17:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 7E4CB1A0385 for ; Fri, 14 Oct 2016 22:17:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.769 X-Spam-Level: X-Spam-Status: No, score=-4.769 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, KAM_LOTSOFHASH=0.25, KAM_MANYCOMMENTS=1.2, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id FDpayzHygz_H for ; Fri, 14 Oct 2016 22:17:19 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 8E3AC60E1C for ; Fri, 14 Oct 2016 22:17:03 +0000 (UTC) Received: (qmail 35877 invoked by uid 99); 14 Oct 2016 22:17:01 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2016 22:17:01 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id AABA7DFB78; Fri, 14 Oct 2016 22:17:01 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: kmiller@apache.org To: commits@geode.incubator.apache.org Date: Fri, 14 Oct 2016 22:18:05 -0000 Message-Id: <0c96ad4d9e0042ac9a47fa745017562f@git.apache.org> In-Reply-To: <4e5a8ffd52f143b79e70b1717c3838a1@git.apache.org> References: <4e5a8ffd52f143b79e70b1717c3838a1@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [67/94] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files archived-at: Fri, 14 Oct 2016 22:17:41 -0000 http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/management/programming_example.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/management/programming_example.html.md.erb b/geode-docs/managing/management/programming_example.html.md.erb index 45e4ac5..17cfcd4 100644 --- a/geode-docs/managing/management/programming_example.html.md.erb +++ b/geode-docs/managing/management/programming_example.html.md.erb @@ -2,6 +2,23 @@ title: Management and Monitoring Programming Examples --- + + One example demonstrates the use of an MBean server to manage and monitor a node in a distributed system, and the other example acts as the managed node. ## JMX Manager Node Example http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/cache_consistency.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/cache_consistency.html.md.erb b/geode-docs/managing/monitor_tune/cache_consistency.html.md.erb index 09f868b..adc10c9 100644 --- a/geode-docs/managing/monitor_tune/cache_consistency.html.md.erb +++ b/geode-docs/managing/monitor_tune/cache_consistency.html.md.erb @@ -2,6 +2,23 @@ title: Maintaining Cache Consistency --- + + Maintaining data consistency between caches in a distributed Geode system is vital for ensuring its functional integrity and preventing data loss. ## General Guidelines http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb ---------------------------------------------------------------------- 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 da69f00..db09945 100644 --- a/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb +++ b/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb @@ -2,6 +2,23 @@ title: Performance Tuning and Configuration --- + + A collection of tools and controls allow you to monitor and adjust Apache Geode performance. - **[Improving Geode Performance on vSphere](../../managing/monitor_tune/gemfire_performance_on_vsphere.html)** http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere.html.md.erb b/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere.html.md.erb index 249a7dd..2be5502 100644 --- a/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere.html.md.erb +++ b/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere.html.md.erb @@ -2,6 +2,23 @@ title: Improving Geode Performance on vSphere --- + + This topic provides guidelines for tuning vSphere virtualized environments that host Apache Geode deployments. Without tuning, Geode can suffer a performance drop in virtual environments, including the VMware vSphere virtual platform. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere_guidelines.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere_guidelines.html.md.erb b/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere_guidelines.html.md.erb index d8b7248..b5cb8a2 100644 --- a/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere_guidelines.html.md.erb +++ b/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere_guidelines.html.md.erb @@ -1,6 +1,23 @@ --- title: Operating System Guidelines --- + + http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/multicast_communication.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/multicast_communication.html.md.erb b/geode-docs/managing/monitor_tune/multicast_communication.html.md.erb index 3574cc7..ba823c6 100644 --- a/geode-docs/managing/monitor_tune/multicast_communication.html.md.erb +++ b/geode-docs/managing/monitor_tune/multicast_communication.html.md.erb @@ -2,6 +2,23 @@ title: Multicast Communication --- + + You can make configuration adjustments to improve the UDP multicast performance of peer-to-peer communication in your Geode system. Before you begin, you should understand Geode [Basic Configuration and Programming](../../basic_config/book_intro.html). See also the general communication tuning and UDP tuning covered in [Socket Communication](socket_communication.html) and [UDP Communication](udp_communication.html#udp_comm). http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/multicast_communication_configuring_speed_limits.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/multicast_communication_configuring_speed_limits.html.md.erb b/geode-docs/managing/monitor_tune/multicast_communication_configuring_speed_limits.html.md.erb index 8ef2894..a6cb090 100644 --- a/geode-docs/managing/monitor_tune/multicast_communication_configuring_speed_limits.html.md.erb +++ b/geode-docs/managing/monitor_tune/multicast_communication_configuring_speed_limits.html.md.erb @@ -2,6 +2,23 @@ title: Configuring Multicast Speed Limits --- + + After you determine the maximum transmission rate, configure and tune your production system. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/multicast_communication_provisioning_bandwidth.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/multicast_communication_provisioning_bandwidth.html.md.erb b/geode-docs/managing/monitor_tune/multicast_communication_provisioning_bandwidth.html.md.erb index d236823..402590f 100644 --- a/geode-docs/managing/monitor_tune/multicast_communication_provisioning_bandwidth.html.md.erb +++ b/geode-docs/managing/monitor_tune/multicast_communication_provisioning_bandwidth.html.md.erb @@ -2,6 +2,23 @@ title: Provisioning Bandwidth for Multicast --- + + Multicast installations require more planning and configuration than TCP installations. With IP multicast, you gain scalability but lose the administrative convenience of TCP. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb b/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb index b8445f2..77fd42b 100644 --- a/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb +++ b/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb @@ -2,6 +2,23 @@ title: Run-time Considerations for Multicast --- + + When you use multicast for messaging and data distribution, you need to understand how the health monitoring setting works and how to control memory use. **Multicast Health Monitor** http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb b/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb index d339a55..1e8faa7 100644 --- a/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb +++ b/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb @@ -2,6 +2,23 @@ title: Testing Multicast Speed Limits --- + + TCP automatically adjusts its speed to the capability of the processes using it and enforces bandwidth sharing so that every process gets a turn. With multicast, you must determine and explicitly set those limits. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/multicast_communication_troubleshooting.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/multicast_communication_troubleshooting.html.md.erb b/geode-docs/managing/monitor_tune/multicast_communication_troubleshooting.html.md.erb index 9e99981..c7f9c48 100644 --- a/geode-docs/managing/monitor_tune/multicast_communication_troubleshooting.html.md.erb +++ b/geode-docs/managing/monitor_tune/multicast_communication_troubleshooting.html.md.erb @@ -2,6 +2,23 @@ title: Troubleshooting the Multicast Tuning Process --- + + Several problems may arise during the initial testing and tuning process for multicasting. **Some or All Members Cannot Communicate** http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/performance_controls.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/performance_controls.html.md.erb b/geode-docs/managing/monitor_tune/performance_controls.html.md.erb index 79269a0..ddc713c 100644 --- a/geode-docs/managing/monitor_tune/performance_controls.html.md.erb +++ b/geode-docs/managing/monitor_tune/performance_controls.html.md.erb @@ -2,6 +2,23 @@ title: Performance Controls --- + + This topic provides tuning suggestions of particular interest to developers, primarily programming techniques and cache configuration. Before you begin, you should understand Apache Geode [Basic Configuration and Programming](../../basic_config/book_intro.html). http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/performance_controls_controlling_socket_use.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/performance_controls_controlling_socket_use.html.md.erb b/geode-docs/managing/monitor_tune/performance_controls_controlling_socket_use.html.md.erb index 4e04445..d4327eb 100644 --- a/geode-docs/managing/monitor_tune/performance_controls_controlling_socket_use.html.md.erb +++ b/geode-docs/managing/monitor_tune/performance_controls_controlling_socket_use.html.md.erb @@ -2,6 +2,23 @@ title: Controlling Socket Use --- + + For peer-to-peer communication, you can manage socket use at the system member level and at the thread level. The conserve-sockets setting indicates whether application threads share sockets with other threads or use their own sockets for distributed system member communication. This setting has no effect on communication between a server and its clients, but it does control the server’s communication with its peers or a gateway sender's communication with a gateway receiver. In client/server settings in particular, where there can be a large number of clients for each server, controlling peer-to-peer socket use is an important part of tuning server performance. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/performance_controls_data_serialization.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/performance_controls_data_serialization.html.md.erb b/geode-docs/managing/monitor_tune/performance_controls_data_serialization.html.md.erb index d393eb3..139f1bb 100644 --- a/geode-docs/managing/monitor_tune/performance_controls_data_serialization.html.md.erb +++ b/geode-docs/managing/monitor_tune/performance_controls_data_serialization.html.md.erb @@ -2,6 +2,23 @@ title: Data Serialization --- + + In addition to standard Java serialization, Geode offers serialization options that give you higher performance and greater flexibility for data storage, transfers, and language types. Under *Developing with Apache Geode*, see [Data Serialization](../../developing/data_serialization/chapter_overview.html#data_serialization). http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/performance_controls_increasing_cache_hits.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/performance_controls_increasing_cache_hits.html.md.erb b/geode-docs/managing/monitor_tune/performance_controls_increasing_cache_hits.html.md.erb index 58fcb27..c3a4d13 100644 --- a/geode-docs/managing/monitor_tune/performance_controls_increasing_cache_hits.html.md.erb +++ b/geode-docs/managing/monitor_tune/performance_controls_increasing_cache_hits.html.md.erb @@ -2,6 +2,23 @@ title: Increasing the Ratio of Cache Hits --- + + The more frequently a get fails to find a valid value in the first cache and has to try a second cache, the more the overall performance is affected. A common cause of misses is expiration or eviction of the entry. If you have a region’s entry expiration or eviction enabled, monitor the region and entry statistics. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/performance_controls_managing_slow_receivers.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/performance_controls_managing_slow_receivers.html.md.erb b/geode-docs/managing/monitor_tune/performance_controls_managing_slow_receivers.html.md.erb index fbbd329..30293d0 100644 --- a/geode-docs/managing/monitor_tune/performance_controls_managing_slow_receivers.html.md.erb +++ b/geode-docs/managing/monitor_tune/performance_controls_managing_slow_receivers.html.md.erb @@ -2,6 +2,23 @@ title: Management of Slow Receivers --- + + You have several options for handling slow members that receive data distribution. The slow receiver options control only to peer-to-peer communication between distributed regions using TCP/IP. This topic does not apply to client/server or multi-site communication, or to communication using the UDP unicast or IP multicast protocols. Most of the options for handling slow members are related to on-site configuration during system integration and tuning. For this information, see [Slow Receivers with TCP/IP](slow_receivers.html). http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/performance_controls_setting_cache_timeouts.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/performance_controls_setting_cache_timeouts.html.md.erb b/geode-docs/managing/monitor_tune/performance_controls_setting_cache_timeouts.html.md.erb index bb84a5f..ca69a49 100644 --- a/geode-docs/managing/monitor_tune/performance_controls_setting_cache_timeouts.html.md.erb +++ b/geode-docs/managing/monitor_tune/performance_controls_setting_cache_timeouts.html.md.erb @@ -2,6 +2,23 @@ title: Setting Cache Timeouts --- + + Cache timeout properties can modified through the gfsh `alter runtime` command (or declared in the `cache.xml` file) and can also be set through methods of the interface, `org.apache.geode.cache.Cache`. To modify cache timeout properties, you can issue the following `gfsh alter runtime` command. For example: http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/slow_messages.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/slow_messages.html.md.erb b/geode-docs/managing/monitor_tune/slow_messages.html.md.erb index 481c396..7150802 100644 --- a/geode-docs/managing/monitor_tune/slow_messages.html.md.erb +++ b/geode-docs/managing/monitor_tune/slow_messages.html.md.erb @@ -2,6 +2,23 @@ title: Slow distributed-ack Messages --- + + In systems with distributed-ack regions, a sudden large number of distributed-no-ack operations can cause distributed-ack operations to take a long time to complete. The `distributed-no-ack` operations can come from anywhere. They may be updates to `distributed-no-ack` regions or they may be other `distributed-no-ack` operations, like destroys, performed on any region in the cache, including the `distributed-ack` regions. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/slow_receivers.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/slow_receivers.html.md.erb b/geode-docs/managing/monitor_tune/slow_receivers.html.md.erb index 8960d913..5e4aebe 100644 --- a/geode-docs/managing/monitor_tune/slow_receivers.html.md.erb +++ b/geode-docs/managing/monitor_tune/slow_receivers.html.md.erb @@ -2,6 +2,23 @@ title: Slow Receivers with TCP/IP --- + + You have several options for preventing situations that can cause slow receivers of data distributions. The slow receiver options control only peer-to-peer communication using TCP/IP. This discussion does not apply to client/server or multi-site communication, or to communication using the UDP unicast or multicast protocols. Before you begin, you should understand Geode [Basic Configuration and Programming](../../basic_config/book_intro.html). http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/slow_receivers_managing.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/slow_receivers_managing.html.md.erb b/geode-docs/managing/monitor_tune/slow_receivers_managing.html.md.erb index 9bc4302..49e93c4 100644 --- a/geode-docs/managing/monitor_tune/slow_receivers_managing.html.md.erb +++ b/geode-docs/managing/monitor_tune/slow_receivers_managing.html.md.erb @@ -2,6 +2,23 @@ title: Managing Slow Receivers --- + + If the receiver fails to receive a message, the sender continues to attempt to deliver the message as long as the receiving member is still in the distributed system. During the retry cycle, Geode throws warnings that include this string: http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/slow_receivers_preventing_problems.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/slow_receivers_preventing_problems.html.md.erb b/geode-docs/managing/monitor_tune/slow_receivers_preventing_problems.html.md.erb index 1a6d256..ec0c199 100644 --- a/geode-docs/managing/monitor_tune/slow_receivers_preventing_problems.html.md.erb +++ b/geode-docs/managing/monitor_tune/slow_receivers_preventing_problems.html.md.erb @@ -2,6 +2,23 @@ title: Preventing Slow Receivers --- + + During system integration, you can identify and eliminate potential causes of slow receivers in peer-to-peer communication. Work with your network administrator to eliminate any problems you identify. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/socket_communication.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/socket_communication.html.md.erb b/geode-docs/managing/monitor_tune/socket_communication.html.md.erb index 99d2117..a97986a 100644 --- a/geode-docs/managing/monitor_tune/socket_communication.html.md.erb +++ b/geode-docs/managing/monitor_tune/socket_communication.html.md.erb @@ -2,6 +2,23 @@ title: Socket Communication --- + + Geode processes communicate using TCP/IP and UDP unicast and multicast protocols. In all cases, communication uses sockets that you can tune to optimize performance. The adjustments you make to tune your Geode communication may run up against operating system limits. If this happens, check with your system administrator about adjusting the operating system settings. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/socket_communication_ephemeral_tcp_port_limits.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/socket_communication_ephemeral_tcp_port_limits.html.md.erb b/geode-docs/managing/monitor_tune/socket_communication_ephemeral_tcp_port_limits.html.md.erb index e0dc158..3df570a 100644 --- a/geode-docs/managing/monitor_tune/socket_communication_ephemeral_tcp_port_limits.html.md.erb +++ b/geode-docs/managing/monitor_tune/socket_communication_ephemeral_tcp_port_limits.html.md.erb @@ -2,6 +2,23 @@ title: Ephemeral TCP Port Limits --- + + By default, Windows’ ephemeral ports are within the range 1024-4999, inclusive.You can increase the range. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb ---------------------------------------------------------------------- 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 fcc2416..a075e08 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 @@ -2,6 +2,23 @@ title: Making Sure You Have Enough Sockets --- + + The number of sockets available to your applications is governed by operating system limits. Sockets use file descriptors and the operating system’s view of your application’s socket use is expressed in terms of file descriptors. There are two limits, one on the maximum descriptors available to a single application and the other on the total number of descriptors available in the system. If you get error messages telling you that you have too many files open, you might be hitting the operating system limits with your use of sockets. Your system administrator might be able to increase the system limits so that you have more available. You can also tune your members to use fewer sockets for their outgoing connections. This section discusses socket use in Geode and ways to limit socket consumption in your Geode members. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/socket_communication_setting_socket_buffer_sizes.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/socket_communication_setting_socket_buffer_sizes.html.md.erb b/geode-docs/managing/monitor_tune/socket_communication_setting_socket_buffer_sizes.html.md.erb index 8af18c8..41884a2 100644 --- a/geode-docs/managing/monitor_tune/socket_communication_setting_socket_buffer_sizes.html.md.erb +++ b/geode-docs/managing/monitor_tune/socket_communication_setting_socket_buffer_sizes.html.md.erb @@ -2,6 +2,23 @@ title: Setting Socket Buffer Sizes --- + + When you determine buffer size settings, you try to strike a balance between communication needs and other processing. Larger socket buffers allow your members to distribute data and events more quickly, but they also take memory away from other things. If you store very large data objects in your cache, finding the right sizing for your buffers while leaving enough memory for the cached data can become critical to system performance. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/socket_communication_tcpip_p2p_handshake_timeouts.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/socket_communication_tcpip_p2p_handshake_timeouts.html.md.erb b/geode-docs/managing/monitor_tune/socket_communication_tcpip_p2p_handshake_timeouts.html.md.erb index e33dd9c..486c337 100644 --- a/geode-docs/managing/monitor_tune/socket_communication_tcpip_p2p_handshake_timeouts.html.md.erb +++ b/geode-docs/managing/monitor_tune/socket_communication_tcpip_p2p_handshake_timeouts.html.md.erb @@ -2,6 +2,23 @@ title: TCP/IP Peer-to-Peer Handshake Timeouts --- + + You can alleviate connection handshake timeouts for TCP/IP connections by increasing the connection handshake timeout interval with the system property p2p.handshakeTimeoutMs. The default setting is 59000 milliseconds. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/socket_tcp_keepalive.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/socket_tcp_keepalive.html.md.erb b/geode-docs/managing/monitor_tune/socket_tcp_keepalive.html.md.erb index b960fd4..f5512bf 100644 --- a/geode-docs/managing/monitor_tune/socket_tcp_keepalive.html.md.erb +++ b/geode-docs/managing/monitor_tune/socket_tcp_keepalive.html.md.erb @@ -2,6 +2,23 @@ title: TCP/IP KeepAlive Configuration --- + + Geode supports TCP KeepAlive to prevent socket connections from being timed out. The `gemfire.enableTcpKeepAlive` system property prevents connections that appear idle from being timed out (for example, by a firewall.) When configured to true, Geode enables the SO\_KEEPALIVE option for individual sockets. This operating system-level setting allows the socket to send verification checks (ACK requests) to remote systems in order to determine whether or not to keep the socket connection alive. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/sockets_and_gateways.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/sockets_and_gateways.html.md.erb b/geode-docs/managing/monitor_tune/sockets_and_gateways.html.md.erb index 4910453..ca20bf8 100644 --- a/geode-docs/managing/monitor_tune/sockets_and_gateways.html.md.erb +++ b/geode-docs/managing/monitor_tune/sockets_and_gateways.html.md.erb @@ -2,6 +2,23 @@ title: Configuring Sockets in Multi-Site (WAN) Deployments --- + + When you determine buffer size settings, you try to strike a balance between communication needs and other processing. This table lists the settings for gateway relationships and protocols, and tells where to set them. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/system_member_performance.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/system_member_performance.html.md.erb b/geode-docs/managing/monitor_tune/system_member_performance.html.md.erb index 72cfe8a..49b9f62 100644 --- a/geode-docs/managing/monitor_tune/system_member_performance.html.md.erb +++ b/geode-docs/managing/monitor_tune/system_member_performance.html.md.erb @@ -2,6 +2,23 @@ title: System Member Performance --- + + You can modify some configuration parameters to improve system member performance. Before doing so, you should understand [Basic Configuration and Programming](../../basic_config/book_intro.html). http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/system_member_performance_connection_thread_settings.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/system_member_performance_connection_thread_settings.html.md.erb b/geode-docs/managing/monitor_tune/system_member_performance_connection_thread_settings.html.md.erb index 0c13022..42aedb5 100644 --- a/geode-docs/managing/monitor_tune/system_member_performance_connection_thread_settings.html.md.erb +++ b/geode-docs/managing/monitor_tune/system_member_performance_connection_thread_settings.html.md.erb @@ -2,6 +2,23 @@ title: Connection Thread Settings and Performance --- + + When many peer processes are started concurrently, you can improve the distributed system connect time can by setting the p2p.HANDSHAKE\_POOL\_SIZE system property value to the expected number of members. This property controls the number of threads that can be used to establish new TCP/IP connections between peer caches. The threads are discarded if they are idle for 60 seconds. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/system_member_performance_distributed_system_member.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/system_member_performance_distributed_system_member.html.md.erb b/geode-docs/managing/monitor_tune/system_member_performance_distributed_system_member.html.md.erb index 6b885b9..2076c7a 100644 --- a/geode-docs/managing/monitor_tune/system_member_performance_distributed_system_member.html.md.erb +++ b/geode-docs/managing/monitor_tune/system_member_performance_distributed_system_member.html.md.erb @@ -2,6 +2,23 @@ title: Distributed System Member Properties --- + + Several performance-related properties apply to a cache server or application that connects to the distributed system. - **statistic-sampling-enabled**.Turning off statistics sampling saves resources, but it also takes away potentially valuable information for ongoing system tuning and unexpected system problems. If LRU eviction is configured, then statistics sampling must be on. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/system_member_performance_garbage.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/system_member_performance_garbage.html.md.erb b/geode-docs/managing/monitor_tune/system_member_performance_garbage.html.md.erb index b9231ce..ef23dff 100644 --- a/geode-docs/managing/monitor_tune/system_member_performance_garbage.html.md.erb +++ b/geode-docs/managing/monitor_tune/system_member_performance_garbage.html.md.erb @@ -2,6 +2,23 @@ title: Garbage Collection and System Performance --- + + If your application exhibits unacceptably high latencies, you might improve performance by modifying your JVM’s garbage collection behavior. Garbage collection, while necessary, introduces latency into your system by consuming resources that would otherwise be available to your application. You can reduce the impact of garbage collection in two ways: http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/system_member_performance_jvm_mem_settings.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/system_member_performance_jvm_mem_settings.html.md.erb b/geode-docs/managing/monitor_tune/system_member_performance_jvm_mem_settings.html.md.erb index 08d5700..4440b25 100644 --- a/geode-docs/managing/monitor_tune/system_member_performance_jvm_mem_settings.html.md.erb +++ b/geode-docs/managing/monitor_tune/system_member_performance_jvm_mem_settings.html.md.erb @@ -2,6 +2,23 @@ title: JVM Memory Settings and System Performance --- + + You configure JVM memory settings for the Java application by adding parameters to the java invocation. For the cache server, you add them to the command-line parameters for the gfsh `start server` command. - JVM heap size—Your JVM may require more memory than is allocated by default. For example, you may need to increase heap size for an application that stores a lot of data. You can set a maximum size and an initial size, so if you know you will be using the maximum (or close to it) for the life of the member, you can speed memory allocation time by setting the initial size to the maximum. This sets both the maximum and initial memory sizes to 1024 megabytes for a Java application: http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/udp_communication.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/monitor_tune/udp_communication.html.md.erb b/geode-docs/managing/monitor_tune/udp_communication.html.md.erb index 2f85709..4a5d3c0 100644 --- a/geode-docs/managing/monitor_tune/udp_communication.html.md.erb +++ b/geode-docs/managing/monitor_tune/udp_communication.html.md.erb @@ -2,6 +2,23 @@ title: UDP Communication --- + + You can make configuration adjustments to improve multicast and unicast UDP performance of peer-to-peer communication. You can tune your Geode UDP messaging to maximize throughput. There are two main tuning goals: to use the largest reasonable datagram packet sizes and to reduce retransmission rates. These actions reduce messaging overhead and overall traffic on your network while still getting your data where it needs to go. Geode also provides statistics to help you decide when to change your UDP messaging settings. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb b/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb index 62a10bf..98d3c0b 100644 --- a/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb +++ b/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb @@ -2,6 +2,23 @@ title: Network Partitioning --- + + Apache Geode architecture and management features help detect and resolve network partition problems. - **[How Network Partitioning Management Works](../../managing/network_partitioning/how_network_partitioning_management_works.html)** http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/network_partitioning/failure_detection.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/network_partitioning/failure_detection.html.md.erb b/geode-docs/managing/network_partitioning/failure_detection.html.md.erb index 055cc42..223b3d9 100644 --- a/geode-docs/managing/network_partitioning/failure_detection.html.md.erb +++ b/geode-docs/managing/network_partitioning/failure_detection.html.md.erb @@ -2,6 +2,23 @@ title: Failure Detection and Membership Views --- + + Geode uses failure detection to remove unresponsive members from membership views. ## Failure Detection http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/network_partitioning/handling_network_partitioning.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/network_partitioning/handling_network_partitioning.html.md.erb b/geode-docs/managing/network_partitioning/handling_network_partitioning.html.md.erb index 70e9668..61a2576 100644 --- a/geode-docs/managing/network_partitioning/handling_network_partitioning.html.md.erb +++ b/geode-docs/managing/network_partitioning/handling_network_partitioning.html.md.erb @@ -2,6 +2,23 @@ title: Configure Apache Geode to Handle Network Partitioning --- + + This section lists the configuration steps for network partition detection. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/network_partitioning/how_network_partitioning_management_works.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/network_partitioning/how_network_partitioning_management_works.html.md.erb b/geode-docs/managing/network_partitioning/how_network_partitioning_management_works.html.md.erb index 157864d..e971634 100644 --- a/geode-docs/managing/network_partitioning/how_network_partitioning_management_works.html.md.erb +++ b/geode-docs/managing/network_partitioning/how_network_partitioning_management_works.html.md.erb @@ -2,6 +2,23 @@ title: How Network Partitioning Management Works --- + + Geode handles network outages by using a weighting system to determine whether the remaining available members have a sufficient quorum to continue as a distributed system. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/network_partitioning/membership_coordinators_lead_members_and_weighting.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/network_partitioning/membership_coordinators_lead_members_and_weighting.html.md.erb b/geode-docs/managing/network_partitioning/membership_coordinators_lead_members_and_weighting.html.md.erb index cfade68..cb21f54 100644 --- a/geode-docs/managing/network_partitioning/membership_coordinators_lead_members_and_weighting.html.md.erb +++ b/geode-docs/managing/network_partitioning/membership_coordinators_lead_members_and_weighting.html.md.erb @@ -2,6 +2,23 @@ title: Membership Coordinators, Lead Members and Member Weighting --- + + Network partition detection uses a designated membership coordinator and a weighting system that accounts for a lead member to determine whether a network partition has occurred. ## Membership Coordinators and Lead Members http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/network_partitioning/network_partitioning_scenarios.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/network_partitioning/network_partitioning_scenarios.html.md.erb b/geode-docs/managing/network_partitioning/network_partitioning_scenarios.html.md.erb index 4009792..a90b3f1 100644 --- a/geode-docs/managing/network_partitioning/network_partitioning_scenarios.html.md.erb +++ b/geode-docs/managing/network_partitioning/network_partitioning_scenarios.html.md.erb @@ -2,6 +2,23 @@ title: Network Partitioning Scenarios --- + + This topic describes network partitioning scenarios and what happens to the partitioned sides of the distributed system. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/network_partitioning/preventing_network_partitions.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/network_partitioning/preventing_network_partitions.html.md.erb b/geode-docs/managing/network_partitioning/preventing_network_partitions.html.md.erb index b18b600..6a983f5 100644 --- a/geode-docs/managing/network_partitioning/preventing_network_partitions.html.md.erb +++ b/geode-docs/managing/network_partitioning/preventing_network_partitions.html.md.erb @@ -2,6 +2,23 @@ title: Preventing Network Partitions --- + + This section provides a short list of things you can do to prevent a network partition from occurring. To avoid a network partition: http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/region_compression/region_compression.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/region_compression/region_compression.html.md.erb b/geode-docs/managing/region_compression/region_compression.html.md.erb index d664a7b..c85d1e1 100644 --- a/geode-docs/managing/region_compression/region_compression.html.md.erb +++ b/geode-docs/managing/region_compression/region_compression.html.md.erb @@ -1,6 +1,23 @@ --- title: Region Compression --- + + http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/authentication_examples.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/security/authentication_examples.html.md.erb b/geode-docs/managing/security/authentication_examples.html.md.erb index 6e0d050..b7634c8 100644 --- a/geode-docs/managing/security/authentication_examples.html.md.erb +++ b/geode-docs/managing/security/authentication_examples.html.md.erb @@ -2,6 +2,23 @@ title: Authentication Example --- + + This example demonstrates the basics of an implementation of the `SecurityManager.authenticate` method. The remainder of the example may be found within the Apache Geode http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/authentication_overview.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/security/authentication_overview.html.md.erb b/geode-docs/managing/security/authentication_overview.html.md.erb index fe38e10..de8088e 100644 --- a/geode-docs/managing/security/authentication_overview.html.md.erb +++ b/geode-docs/managing/security/authentication_overview.html.md.erb @@ -2,6 +2,23 @@ title: Authentication --- + + Authentication verifies the identities of components within the distributed system such as peers, clients, and those connecting to a JMX manager. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/authorization_example.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/security/authorization_example.html.md.erb b/geode-docs/managing/security/authorization_example.html.md.erb index 9d03f65..2e725a1 100644 --- a/geode-docs/managing/security/authorization_example.html.md.erb +++ b/geode-docs/managing/security/authorization_example.html.md.erb @@ -2,6 +2,23 @@ title: Authorization Example --- + + This example demonstrates the basics of an implementation of the `SecurityManager.authorize` method. The remainder of the example may be found within the Apache Geode http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/authorization_overview.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/security/authorization_overview.html.md.erb b/geode-docs/managing/security/authorization_overview.html.md.erb index 6ca014a..beca4f2 100644 --- a/geode-docs/managing/security/authorization_overview.html.md.erb +++ b/geode-docs/managing/security/authorization_overview.html.md.erb @@ -2,6 +2,23 @@ title: Authorization --- + + Distributed system and cache operations can be restricted, intercepted and modifed, or completely blocked based on configured access rights set for the various distributed system entities. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/chapter_overview.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/security/chapter_overview.html.md.erb b/geode-docs/managing/security/chapter_overview.html.md.erb index 88df5d8..98990f6 100644 --- a/geode-docs/managing/security/chapter_overview.html.md.erb +++ b/geode-docs/managing/security/chapter_overview.html.md.erb @@ -2,6 +2,23 @@ title: Security --- + + The security framework permits authentication of connecting components and authorization of operations for all communicating components of the distributed system. - **[Security Implementation Introduction and Overview](../../managing/security/implementing_security.html)** http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/enable_security.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/security/enable_security.html.md.erb b/geode-docs/managing/security/enable_security.html.md.erb index c6b4e33..051180c 100644 --- a/geode-docs/managing/security/enable_security.html.md.erb +++ b/geode-docs/managing/security/enable_security.html.md.erb @@ -2,6 +2,23 @@ title: Enable Security with Property Definitions --- + + ## security-manager Property http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/encrypting_passwords.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/security/encrypting_passwords.html.md.erb b/geode-docs/managing/security/encrypting_passwords.html.md.erb index 8104c29..975727e 100644 --- a/geode-docs/managing/security/encrypting_passwords.html.md.erb +++ b/geode-docs/managing/security/encrypting_passwords.html.md.erb @@ -1,6 +1,23 @@ --- title: Encrypting Passwords for Use in cache.xml --- + + http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/encrypting_with_diffie_helman.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/security/encrypting_with_diffie_helman.html.md.erb b/geode-docs/managing/security/encrypting_with_diffie_helman.html.md.erb index bc44fd8..2dd91cb 100644 --- a/geode-docs/managing/security/encrypting_with_diffie_helman.html.md.erb +++ b/geode-docs/managing/security/encrypting_with_diffie_helman.html.md.erb @@ -2,6 +2,23 @@ title: Encrypt Credentials with Diffie-Hellman --- + + For secure transmission of sensitive information, like passwords, you can encrypt credentials using the Diffie-Hellman key exchange algorithm. This encryption applies only to client/server authentication - not peer-to-peer authentication. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/implementing_authentication.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/security/implementing_authentication.html.md.erb b/geode-docs/managing/security/implementing_authentication.html.md.erb index a605e1b..374a95e 100644 --- a/geode-docs/managing/security/implementing_authentication.html.md.erb +++ b/geode-docs/managing/security/implementing_authentication.html.md.erb @@ -2,6 +2,23 @@ title: Implementing Authentication --- + + Authentication lends a measure of security to a distributed system by verifying the identity of components as they connect to the system. All components use the same authentication mechanism. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/implementing_authorization.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/managing/security/implementing_authorization.html.md.erb b/geode-docs/managing/security/implementing_authorization.html.md.erb index 3fd4816..ec47133 100644 --- a/geode-docs/managing/security/implementing_authorization.html.md.erb +++ b/geode-docs/managing/security/implementing_authorization.html.md.erb @@ -2,6 +2,23 @@ title: Implementing Authorization --- + + ## How Authorization Works When a component requests an operation,