LATEST VERSION: 8.2.8 - CHANGELOG
Pivotal GemFire® v8.2

start

start

Start servers, locators, gateway senders and gateway receivers, and monitoring tools.

start gateway-receiver

Start the gateway receiver on a given member or group of members.

Note that you can only have one gateway receiver on each member, and unlike a gateway sender, you do not need to specify an identifier for the gateway receiver.

Availability: Online. You must be connected in gfsh to a JMX Manager member to use this command.

Syntax:
start gateway-receiver [--group=value(,value)*] [--member=value]
Table 1. Parameters
Name Description
--member Name or ID of the member on which to start the Gateway Receiver.
--group Group(s) of members on which to start the Gateway Receiver.
Example Commands:
start gateway-receiver
start gateway-receiver --member=member1
Sample Output:
gfsh>start gateway-receiver
      Member                | Result | Message
--------------------------- | -------| -----------------------------------------------------------------------
pc13(2266)<v6>:56852        | OK     | GatewayReceiver is started on member pc13(2266)<v6>:56852
pc13(Manager:2242)<v5>:57631| Error  | GatewayReceiver is not available on member pc13(Manager:2242)<v5>:57631
pc13(2275)<v7>:47480        | OK     | GatewayReceiver is started on member pc13(2275)<v7>:47480
pc13(2293)<v8>:55472        | OK     | GatewayReceiver is started on member pc13(2293)<v8>:55472

gfsh>start gateway-receiver --member=pc13(2266)<v14>:36579
GatewayReceiver is started on member pc13(2266)<v14>:36579

gfsh>start gateway-receiver --group=RG1
         Member      | Result | Message
-------------------- | -------| ----------------------------------------------------------
pc13(2275)<v23>:27484| OK     | GatewayReceiver is started on member pc13(2275)<v23>:27484
pc13(2293)<v24>:55810| OK     | GatewayReceiver is started on member pc13(2293)<v24>:55810
pc13(2266)<v22>:4522 | OK     | GatewayReceiver is started on member pc13(2266)<v22>:4522

start gateway-sender

Start the gateway sender on a member or members.

For information on how to configure a gateway sender, see Configure Gateway Senders.

Note: By default, gateway senders are configured to start automatically. Manual restart introduces a risk of data loss; it is not intended for production systems.

Availability: Online. You must be connected in gfsh to a JMX Manager member to use this command.

Syntax:
start gateway-sender --id=value [--group=value(,value)*] [--member=value]
Table 2. Parameters
Name Description
--id Required. ID of the GatewaySender.
--group Group(s) of members on which to start the Gateway Sender.
--member Member used to start the Gateway Sender
Example Commands:
start gateway-sender --id=sender1-NY
start gateway-sender --id=sender1-NY --member=server1
start gateway-sender --id=sender1-NY --group=MemberGroup1,MemberGroup2
Sample Output:
gfsh>start gateway-sender --id=ln
 Member                       |  Result |                   Message
------------------------------| ------- | -------------------------------------------------------------------------
pc13(30614)<v6>:63670         | OK      | GatewaySender ln is started on member pc13(30614)<v6>:63670
pc13(30621)<v7>:36015         | OK      | GatewaySender ln is started on member pc13(30621)<v7>:36015
pc13(30633)<v8>:13633         | OK      | GatewaySender ln is started on member pc13(30633)<v8>:13633
pc13(Manager:30588)<v5>:42792 | Error   | GatewaySender ln is not available on member pc13(Manager:30588)<v5>:42792

gfsh>start gateway-sender --id=ln --member=pc13(30614)<v14>:44519
GatewaySender ln is started on member pc13(30614)<v14>:44519
gfsh>start gateway-sender --id=ln --group=SenderGroup1
Member                 | Result| Message
---------------------- | ------| ------------------------------------------------------------
pc13(30614)<v18>:15201 | OK    | GatewaySender ln is started on member pc13(30614)<v18>:15201
pc13(30621)<v19>:61437 | OK    | GatewaySender ln is started on member pc13(30621)<v19>:61437
pc13(30633)<v20>:22567 | OK    | GatewaySender ln is started on member pc13(30633)<v20>:22567

start jconsole

Start the JDK JConsole monitoring application in a separate process.

JConsole automatically connects to a running JMX Manager node if one is available.

Note that you must have a JDK installed (not just a JRE) and the correct PATH and JAVA_HOME environment variables set.

See Browsing GemFire MBeans through JConsole for an example of using JConsole with the GemFireGemFire management and monitoring system.

Availability: Online or offline.

Syntax:
start jconsole [--interval=<seconds>] [--notile] [--version] 
[-J<jconsole JVM options>]
Table 3. Parameters
Name Description Default Value
--interval Set the update interval to n seconds (default is 4 seconds). (Equivalent to JConsole's -interval=n) 4
--notile Whether to initially tile windows for two or more connections. This parameter is passed as -notile to JConsole. false
--pluginpath "Directories or JAR files which are searched for JConsole plugins. The path should contain a provider-configuration file named:\n" + " META-INF/services/com.sun.tools.jconsole.JConsolePlugin\n" + "containing one line for each plugin specifying the fully qualified class name of the class implementing the com.sun.tools.jconsole.JConsolePlugin class."  
--version Display the JConsole version information. This parameter is passed as -version to JConsole. false
--J Arguments passed to the JVM on which JConsole runs  
Example Commands:
gfsh./> start jconsole --interval=8 --notile;
Running JDK JConsole

gfsh./> start jconsole --version;
JConsole version "1.6.0_31-b04-415"
Java(TM) SE Runtime Environment (build 1.6.0_31-b04-415-11M3646)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode)
Sample Output:
gfsh>start jconsole
Running JDK JConsole
The JConsole application appears and auto-connects to a JMX Manager node if one is available:



Error Messages:
An error occurred while launching JConsole = %1$s

Connecting by the GemFire member's name or ID is not currently supported.
Please specify the member as '<hostname|IP>[PORT].

An IO error occurred while launching JConsole.
Please ensure that JAVA_HOME is set to the JDK installation 
or the JDK bin directory is in the system PATH.

JConsole could not be found.\nPlease ensure that JAVA_HOME is set to the 
JDK installation or the JDK bin directory is in the system PATH.

start jvisualvm

Start the JDK's Java VisualVM monitoring application in a separate process.

Availability: Online or offline.

Syntax:
start jvisualvm [--J=value(,value)*]
Table 4. Parameters
Name Description
--J VM-option passed to the spawned CacheServer VM. For example: -J-Dfoo.bar=true for setting foo.bar to 'true'.
Example Commands:
start jvisualvm
Sample Output:

start locator

Start a locator.

The command creates a subdirectory and log file named after the locator. If the locator detects that no other JMX Manager exists, then the locator will automatically start an embedded JMX Manager and connect the current gfsh session to the JMX Manager.

Note: You must have JAVA_HOME set before starting gfsh to use this command.

In addition, if gfsh is not already connected to a JMX Manager, the gfsh console will automatically connect to the new embedded JMX Manager started by the new locator.

Note: When both --max-heap and --initial-heap are specified during locator startup, additional GC parameters are specified internally by GemFire's Resource Manager. If you do not want the additional default GC properties set by the Resource Manager, then use the-Xms and -Xmx JVM options. See Control Heap Use with the Resource Manager for more information.

Availability: Online or offline.

Syntax:
start locator --name=value [--bind-address=value] [--force(=value)?] [--group=value] [--hostname-for-clients=value]
 [--locators=value] [--log-level=value] [--mcast-address=value] [--mcast-port=value] [--port=value] [--dir=value] 
 [--properties-file=value] [--security-properties-file=value] [--initial-heap=value] [--max-heap=value] 
 [--connect(=value)?] [--enable-cluster-configuration(=value)?] [--load-from-cluster-configuration-dir(=value)?]
 [--cluster-config-dir=value] [--J=value(,value)*] 
Table 5. Parameters
Name Description Default Value
--name Required. Name to be used for this GemFireGemFire locator service.  
--bind-address IP address on which the locator will be bound. bound to all addresses
--force Whether to allow the PID file from a previous locator run to be overwritten. false
--group Group(s) the locator will be a part of.  
--hostname-for-clients Hostname or IP address that will be sent to clients so they can connect to this locator. uses the bind-address to which the locator is bound).
--locators List of locators used by this locator to join the appropriate GemFireGemFire cluster.  
--log-level Level of output logged to the locator log file. Possible values for log-level include: finest, finer, fine, config, info, warning, severe, none.  
--mcast-address IP address or hostname used to bind the UPD socket for multi-cast networking so the locator can locate other members in the GemFireGemFire cluster. If mcast-port is zero, then mcast-address is ignored.  
--mcast-port Port used for multi-cast networking so the locator can locate other members of the GemFire cluster. A zero value disables mcast.  
--port Port the locator will listen on. 10334
--dir Directory in which the Locator will be started and run. ./<locator-member-name>
--properties-file Specify the gemfire.properties file for configuring the locator's distributed system. The file's path should be absolute or relative to gfsh's working directory.  
--security-properties-file The gfsecurity.properties file for configuring the Locator's security configuration in the distributed system. The file's path can be absolute or relative to gfsh's working directory.  
--initial-heap Size has the same format as the -Xmx/-Xms JVM options.
Note: If you use the -J-Xms and -J-Xmx JVM properties instead of -initial-heap and -max-heap, then GemFireGemFire does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
 
--max-heap Size has the same format as the -Xmx/-Xms JVM options
Note: If you use the -J-Xms and -J-Xmx JVM properties instead of -initial-heap and -max-heap, then GemFireGemFire does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
 
--connect When connect is set to false, gfsh does not automatically connect to the locator which is started using this command. true
--enable-cluster-configuration Enables cluster configuration behavior where locators maintain configurations for all members of a distributed system. See Overview of the Cluster Configuration Service. true
--load-from-cluster-configuration-dir Loads the cluster configuration from the shared-config directory. (When set to false, the configuration is loaded from the disk store of the internal, persistent region used by the locator to persist the configuration.) false
--cluster-config-dir Directory used by the cluster configuration service to store the cluster configuration on the filesystem cluster-config
--J Argument passed to the JVM on which the Locator will run. For example, specifying --J=-Dfoo.bar=true sets property "foo.bar" to "true".
Note:
If the argument you are passing contains spaces or commas, enclose the option in single quotes. For example:
start locator --name=locator1 --port=9009 --mcast-port=0\
 --J='-Dgemfire.remote-locators=10.116.34.222[9009],10.116.35.225[9009]'
none
Example Commands:
start locator --name=locator1
Sample Output:
gfsh>start locator --name=locator3
Starting a GemFire Locator in /home/stymon/locator3...
................................
Locator in /home/stymon/locator3 on ubuntu.local[10334] as locator3 is currently online.
Process ID: 1898
Uptime: 19 seconds
GemFire Version: 8.0.0
Java Version: 1.7.0_65
Log File: /home/stymon/locator3/locator3.log
JVM Arguments: -Dgemfire.default.locators=192.168.129.145[40402] 
-Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false 
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /home/stymon/Pivotal_GemFire_800_b48258_Linux/lib/locator-dependencies.jar:
/usr/local/java/lib/tools.jar

Cluster configuration service is up and running.

start pulse

Launch the GemFire Pulse monitoring dashboard tool in the user's default system browser and navigates the user to the landing page (login page).

For more information on GemFire Pulse, see GemFire Pulse.

Availability: Online or offline.

Syntax:
start pulse [--url=value]
Table 6. Parameters
Name Description Default
--url URL of the Pulse Web application http://localhost:7070/pulse
Example Commands:
start pulse
start pulse --url=http://gemfire.mycompany.com:7070/pulse

Sample Output: See GemFire Pulse for examples of Pulse.

start server

Start a GemFire cache server process.

Note: When both --max-heap and --initial-heap are specified during locator startup, additional GC parameters are specified internally by GemFire's Resource Manager. If you do not want the additional default GC properties set by the Resource Manager, then use the -Xms and -Xmx JVM options. See Control Heap Use with the Resource Manager for more information.

Availability: Online or offline.

Syntax:
start server --name=value [--assign-buckets(=value)?] [--bind-address=value]
    [--cache-xml-file=value] [--classpath=value] [--disable-default-server(=value)?]
    [--disable-exit-when-out-of-memory(=value)?] [--enable-time-statistics(=value)?]
    [--force(=value)?] [--properties-file=value] [--security-properties-file=value]
    [--group=value] [--locators=value] [--locator-wait-time=value] [--log-level=value]
    [--mcast-address=value] [--mcast-port=value] [--memcached-port=value]
    [--memcached-protocol=value] [--rebalance(=value)?] [--server-bind-address=value]
    [--server-port=value] [--spring-xml-location=value]
    [--statistic-archive-file=value] [--dir=value] [--initial-heap=value]
    [--max-heap=value] [--use-cluster-configuration(=value)?] [--J=value(,value)*]
    [--critical-heap-percentage=value] [--eviction-heap-percentage=value]
    [--hostname-for-clients=value] [--max-connections=value]
    [--message-time-to-live=value] [--max-message-count=value] [--max-threads=value]
    [--socket-buffer-size=value]
Table 7. Parameters
Name Description Default Value
--name Required. Member name for this GemFire Cache Server service.  
--assign-buckets Whether to assign buckets to the partitioned regions of the cache on server start. false
--bind-address The IP address on which the Server will be bound. binds to all addresses
--cache-xml-file Specifies the name of the XML file or resource to initialize the cache with when it is created.  
--classpath Location of user classes required by the Cache Server. This path is appended to the current CLASSPATH.  
--disable-default-server Whether the cache server will be started by default. If the parameter is specified without a value, the value is set to true. If set to true, the cache server acts as a peer. false
--disable-exit-when-out-of-memory Prevents the JVM from exiting when an OutOfMemoryError occurs. false
--enable-time-statistics Causes additional time-based statistics to be gathered for GemFire operations. true
--properties-file The gemfire.properties file for configuring the Cache Server's distributed system. The file's path can be absolute or relative to the gfsh working directory.  
--security-properties-file The gfsecurity.properties file for configuring the Server's security configuration in the distributed system. The file's path can be absolute or relative to gfsh directory.  
--group Group(s) the Cache Server will be a part of.  
--force Whether to allow the PID file from a previous Cache Server run to be overwritten. false
--locators Sets the list of locators used by the Cache Server to join the appropriate GemFire cluster.  
--locator-wait-time Sets the number of seconds the server will wait for a locator to become available during startup before giving up. 0
--log-level Sets the level of output logged to the Cache Server log file. Possible values for log-level include: finest, finer, fine, config, info, warning, severe, none.  
--mcast-address The IP address or hostname used to bind the UDP socket for multi-cast networking so the Cache Server can locate other members in the GemFire cluster. If mcast-port is zero, then mcast-address is ignored.  
--mcast-port Sets the port used for multi-cast networking so the Cache Server can locate other members of the GemFire cluster. A zero value disables mcast.  
--memcached-port If specified and is non-zero, sets the port number for an embedded Gemcached server and starts the Gemcached server.  
--memcached-protocol Sets the protocol used by an embedded Gemcached server. Valid values are BINARY and ASCII. If you omit this property, the ASCII protocol is used.  
--server-bind-address IP address on which the Server will be bound. binds to all addresses
--server-port Port the Server will listen on for client connections. 40404
--spring-xml-location Specifies the location of a Spring XML configuration file(s) for bootstrapping and configuring a GemFire Server. This configuration file can exist on the CLASSPATH (default) or any location supported by Spring's Resource(Loader) location specifiers (for example, classpath:, file:, etc). ResourceLoader is described in the Spring documentation.  
--rebalance Whether to initiate rebalancing across the GemFire cluster. false
--dir Specify the directory in which the server will run in. This directory is written to the location where you started gfsh. If not specified, the directory is named after the server.
--statistic-archive-file The file that statistic samples are written to. An empty string (default) disables statistic archival.  
--initial-heap Initial size of the heap in the same format as the JVM -Xms parameter.
Note: If you use the --J=-Xms and --J=-Xmx JVM properties instead of --initial-heap and --max-heap, then GemFire does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
 
--max-heap Maximum size of the heap in the same format as the JVM -Xmx parameter.
Note: If you use the --J=-Xms and --J=-Xmx JVM properties instead of --initial-heap and --max-heap, then GemFire does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
 
--J Argument passed to the JVM on which the Cache Server will run. For example, --J=-Dfoo.bar=true will set the property "foo.bar" to "true".

If the argument you are passing contains spaces or commas, enclose the option in single quotes.

 
--use-cluster-configuration Specifies whether the server requests a cluster configuration from the locator. See Overview of the Cluster Configuration Service. true
--critical-heap-percentage Set the percentage of heap at or above which the cache is considered in danger of becoming inoperable due to garbage collection pauses or out of memory exceptions. This feature requires additional VM flags to perform properly; you must set --initial-heap and --max-heap or the corresponding JVM properties to use this threshold. You must also set --max-heap and --intial-heap to the same value.  
--eviction-heap-percentage Set the percentage of heap at or above which the eviction should begin on Regions configured for HeapLRU eviction. Changing this value may cause eviction to begin immediately. Only one change to this attribute or critical heap percentage will be allowed at any given time and its effect will be fully realized before the next change is allowed. This feature requires additional VM flags to perform properly; you must set --initial-heap and --max-heap or the corresponding JVM properties to use this threshold. You must also set --max-heap and --intial-heap to the same value.  
--hostname-for-clients Sets the ip address or host name that this cache server is to listen on for client connections. Setting a specific hostname-for-clients causes server locators to use this value when telling clients how to connect to this cache server. This is useful in the case where the cache server may refer to itself with one hostname, but the clients need to use a different hostname to find the cache server. The value "" causes the bind-address to be given to clients. A null value will be treated the same as the default "".  
--max-connections Sets the maxium number of client connections allowed. When the maximum is reached the cache server will stop accepting connections  
--message-time-to-live Sets the time (in seconds ) after which a message in the client queue will expire.  
--max-message-count Sets maximum number of messages that can be enqueued in a client-queue.  
--max-threads Sets the maxium number of threads allowed in this cache server to service client requests. The default of 0 causes the cache server to dedicate a thread for every client connection.  
--socket-buffer-size Sets the buffer size in bytes of the socket connection for this CacheServer. 32768

Examples

gfsh>start server --name=server1
gfsh>start server --name=server2 --server-port=40405
Sample Output:
gfsh>start server --name=server1 --server-port=40406
Starting a GemFire Server in /home/stymon/server1...
....................................................
Server in /home/stymon/server1 on ubuntu.local[40406] as server1 is currently online.
Process ID: 32209
Uptime: 47 seconds
GemFire Version: 8.0.0
Java Version: 1.7.0_65
Log File: /home/stymon/server1/server1.log
JVM Arguments: -Dgemfire.default.locators=192.168.129.145[40402] -Dgemfire.use-cluster-configuration=true 
-XX:OnOutOfMemoryError="kill -9 %p" -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /home/stymon/Pivotal_GemFire_800_b48258_Linux/lib/server-dependencies.jar:/usr/local/java/lib/tools.jar

start vsd

Launch GemFire Visual Statistics Display (VSD) in a separate process.

You can specify a comma delimited list of directories and specific GemFire statistics archive files (.gfs) to load into VSD upon start. A directory locations will be searched recursively for statistics archive (.gfs) files.

Availability: Online or offline.

Syntax:
start vsd [--file=value(nullvalue)*]
Table 8. Parameters
Name Description
--file File or directory from which to read the statistics archive(s).
Example Commands:
gfsh> start vsd /export/gemfire/node1,/export/gemfire/node2/statArchive.gfs,../../gemfire/nodeN;
Running GemFire Visual Statistics Display (VSD)

gfsh> start vsd;
Running GemFire Visual Statistics Display (VSD)

Sample Output: