[09/50] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb -- diff --git a/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb b/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb deleted file mode 100644 index 62e033b..000 --- a/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb +++ /dev/null @@ -1,156 +0,0 @@ -title: Pool Configuration Example and Settings - -Connection pools require standard client/server distributed system and cache configuration settings. You must also configure settings for the locator, server, and pool elements. - -- Locator. Host and port where a server locator is listening. -- Server. Host and port where a server is listening. -- Pool. Client/server connection pool. - -The example shows a declarative pool configuration. Following the example is a table that describes the attributes that can be configured. - -## ExampleâDeclarative Pool Configuration - -This example shows a declarative pool configuration. - -**Note:** -You create an instance of `PoolFactory` through `PoolManager`. - -``` pre - - - -``` - -## Pool Attributes - - - - - - - - - -Attribute Name -Description -Default - - - - -free-connection-timeout -Number of milliseconds (ms) that the client waits for a free connection if max-connections limit is configured and all connections are in use. -1 ms - - -idle-timeout -Number of milliseconds to wait for a connection to become idle for load balancing -5000 ms - - -load-conditioning-interval -Interval in which the pool checks to see if a connection to a specific server should be moved to a different server to improve the load balance. -30 ms (5 minutes) - - -max-connections -Maximum number of connections that the pool can create. If all connections are in use, an operation requiring a client-to server-connection is blocked until a connection is available or the free-connection-timeout is reached. If set to -1, there is no maximum. The setting must indicate a cap greater than min-connections. - -**Note:** -If you use this setting to cap your pool connections, disable the pool attribute pr-single-hop-enabled. Leaving single hop enabled can increase thrashing and lower performance. - --1 - - -min-connections -Number of connections that must be created initially. -5 - - -name -Pool name. - - - -ping-interval -Interval between pinging the server to show the client is alive, set in milliseconds. Pings are only sent when the ping-interval elapses between normal client messages. This must be set lower than the serverâs maximum-time-between-pings. -1 ms - - -pr-single-hop-enabled -Setting used for single-hop access to partitioned region data in the servers for some data operations. See PartitionResolver. See note in thread-local-connections below. -True - - -read-timeout -Number of milliseconds to wait for a response from a server before the connection times out. -1 - - -retry-attempts -Number of times to retry an operation after a time-out or exception for high availability. If set to -1, the pool tries every available server once until it succeeds or has tried all servers. --1 - - -server-group -Server group from which to select connections. If not specified, the global group of all connected servers is used. -empty - - -socket-buffer-size -Size of the socket buffer, in bytes, on each connection established. -32768 - - -statistic-interval -Default frequency, in milliseconds, with which the client statistics are sent to the server. A value of -1 indicates that the statistics are not sent to the server. --1 - - -subscription-ack-interval -Number of milliseconds to wait before sending an acknowledgment to the server about events received from the subscriptions. -100 - - -subscription-enabled -Whether to establish a server to client subscription. -False - - -subscription-message-tracking-timeout -Number of milliseconds for which messages sent from a server to a client are tracked. The tracking is done to minimize duplicate events. -9 - - -subscription-redundancy -Redundancy for servers that contain subscriptions established by the client. A value of -1 causes all available servers in the specified group to be made redundant. -0 - - -thread-local-connections -Whether the connections must have affinity to the thread that last used them. - -**Note:** -To set this to true, also set pr-single-hop-enabled to false. A true value in pr-single-hop-enabled automatically assigns a false value to thread-local-connections... - -False - - -update-locator-list-interval -An integer number of milliseconds defining the interval between locator list updates. If the value is less than or equal to 0, the update will be disabled. -5000 - -
[09/50] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb -- diff --git a/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb b/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb deleted file mode 100644 index d862004..000 --- a/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb +++ /dev/null @@ -1,34 +0,0 @@ -title: DiskPolicy - - -If the `lru-entries-limit` attribute is greater than zero, the optional `disk-policy` attribute determines how over-limit LRU entries are handled. LRU entries over the limit are either destroyed by default (`disk-policy` is none ) or written to disk (`overflows`). - -**Note:** -If `LruEntriesLimit` is `0`, or `CachingEnabled` is `false`, do not set the `disk-policy` attribute. An `IllegalStateException` is thrown if the attribute is set. - -This declaration causes LRU to overflow to disk: - -``` pre - - - -``` - -Overflow requires a persistence manager for cache-to-disk and disk-to-cache operations. See [PersistenceManager](persistence-manager.html#persistence-manager). - -## Overflowing Data to Disk - -Region data can be stored to disk using the overflow process to satisfy region capacity restrictions without completely destroying the local cache data. The storage mechanism uses disk files to hold region entry data. When an entry is overflowed, its value is written to disk but its key and entry object remain in the cache. This also uses the region attribute [DiskPolicy](disk-policy.html#disk-policy). - -Overflow allows you to keep the region within a user-specified size in memory by relegating the values of least recently used (LRU) entries to disk. Overflow essentially uses disk as a swap space for entry values. When the region size reaches the specified threshold, entry values are moved from memory to disk, as shown in the following figure. If an entry is requested whose value is only on disk, the value is copied back into memory, possibly causing the value of a different LRU entry to be overflowed to disk. - - - -Figure: Data Flow Between Overflow Region and Disk Files - - - -In this figure the value of the LRU entry X has been moved to disk to recover space in memory. The key for the entry remains in memory. From the distributed system perspective, the value on disk is as much a part of the region as the data in memory. A `get` performed on region B looks first in memory and then on disk as part of the local cache search. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/entries.html.md.erb -- diff --git a/geode-docs/nativeclient/client-cache/entries.html.md.erb b/geode-docs/nativeclient/client-cache/entries.html.md.erb deleted file mode 100644 index b5799f5..000 --- a/geode-docs/nativeclient/client-cache/entries.html.md.erb +++ /dev/null @@ -1,20 +0,0 @@ -title: Region Entries - -Region entries hold cached application data. Entries are automatically managed according to region attribute settings. - -You can create, update, invalidate, and destroy entries through explicit API calls or through operations distributed from other caches. - -When the number of entries is very large, a partitioned region can provide the required data management capacity if the total size of the data is greater than the heap in any single JVM. - -When an entry is created, a new object is instantiated in the region containing: - -- The entry key. -- The entry value. This is the application data object. The entry value may be set to `NULL`, which is the equivalent of an invalid value. - -Entry operations invoke callbacks to user-defined application plug-ins. In this chapter, the calls that may affect the entry operation itself (by providing a value or aborting the operation, for example) are highlighted, but all possible interactions are not listed. For details, see [Application Plug-Ins](application-plugins.html#application-plugins). - -`DateTime` objects must be stored in the cache in UTC, so that times correspond between client and server. If you use a date with a different time zone, convert it when storing into and retrieving from the cache. - - http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb -- diff --git a/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb b/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb deleted file mode 100644 index d154d62..000 --- a/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb +++ /dev/null @@ -1,65 +0,0 @@ -title: Specifying Expiration Attributes - - -Expiration
