geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From echobravopapa <...@git.apache.org>
Subject [GitHub] geode-native pull request #49: GEODE-2513 Unbrand docs section on Preserving...
Date Thu, 09 Mar 2017 19:59:51 GMT
Github user echobravopapa commented on a diff in the pull request:

    https://github.com/apache/geode-native/pull/49#discussion_r105257135
  
    --- Diff: docs/geode-native-docs/preserving-data/configuring-durable-nc.html.md.erb ---
    @@ -19,19 +19,19 @@ See the License for the specific language governing permissions and
     limitations under the License.
     -->
     
    -The durable native client can be configured in the `gfcpp.properties` file, or in the
`CacheFactory::set(name,             value)` call.
    +The durable client can be configured in the `gfcpp.properties` file, or in the `CacheFactory::set(name,
            value)` call.
     
    --   **Durable client ID**—You indicate that the client is durable by giving it a `durable-client-ID`.
The servers use this ID to identify the client. For a non-durable client, the `durable-client-ID`
is an empty string. The ID can be any number that is unique among the clients attached to
servers in the same distributed system.
    +-   **Durable client ID**—Indicate that the client is durable by giving it a `durable-client-ID`.
The servers use this ID to identify the client. For a non-durable client, the `durable-client-ID`
is an empty string. The ID can be any number that is unique among the clients attached to
servers in the same distributed system.
     
     -   **Durable timeout**—The `durable-timeout` setting specifies how long this client’s
servers should wait after the client disconnects before terminating its message queue. During
that time, the servers consider the client alive and continue to accumulate messages for it.
The default is 300 seconds.
     
     The `durable-timeout` setting is a tuning parameter. When setting the timeout, take into
account the normal activity of your application, the average size of your messages, and the
level of risk you can handle. Assuming that no messages are being removed from the queue,
how long can the application run before the queue reaches the maximum message count? In addition,
how long can it run before the queued messages consume all the memory on the client host?
How serious is each of those failures to your operation?
     
    -To assist with tuning, Geode provides statistics that track message queues for durable
clients through the disconnect and reconnect cycles. For statistics documentation, see [Statistics](geodeman/managing/statistics/chapter_overview.html).
    +To assist with tuning, Geode statistics track message queues for durable clients through
the disconnect and reconnect cycles.
     
    -When the queue is full, it blocks further operations that add messages until the queue
size drops to an acceptable level. The action to take is specified on the server. For details
on configuring the queue, see [Implementing Durable Client/Server Messaging](geodeman/developing/events/implementing_durable_client_server_messaging.html).
    +When the queue is full, it blocks further operations that add messages until the queue
size drops to an acceptable level. Server configuration sets the action to take. See details
on server configuration of the queue in the server documentation section [Implementing Durable
Client/Server Messaging](geodeman/developing/events/implementing_durable_client_server_messaging.html).
     
    -## Configuring a Durable Native Client Using gfcpp.properties
    +## Configuring a Durable Client Using gfcpp.properties
    --- End diff --
    
    works for me


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message