geode-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kl...@apache.org
Subject [30/46] geode git commit: Update 15-min quickstart, replacing GemFire with Geode where feasible
Date Mon, 12 Dec 2016 22:36:33 GMT
Update 15-min quickstart, replacing GemFire with Geode where feasible


Project: http://git-wip-us.apache.org/repos/asf/geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/geode/commit/0b3d44c6
Tree: http://git-wip-us.apache.org/repos/asf/geode/tree/0b3d44c6
Diff: http://git-wip-us.apache.org/repos/asf/geode/diff/0b3d44c6

Branch: refs/heads/feature/GEODE-1930
Commit: 0b3d44c6c47ebaaf9b2d5738130e00e0c4f47119
Parents: b35f07a
Author: Dave Barnes <dbarnes@pivotal.io>
Authored: Wed Nov 23 09:48:49 2016 -0800
Committer: Dave Barnes <dbarnes@pivotal.io>
Committed: Wed Nov 23 10:12:47 2016 -0800

----------------------------------------------------------------------
 .../15_minute_quickstart_gfsh.html.md.erb       | 90 ++++++++++----------
 .../host_machine.html.md.erb                    |  2 +-
 2 files changed, 46 insertions(+), 46 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/geode/blob/0b3d44c6/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb b/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
index ec1606a..a5971ca 100644
--- a/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
+++ b/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
@@ -22,17 +22,17 @@ limitations under the License.
 
 Need a quick introduction to Apache Geode? Take this brief tour to try out basic features
and functionality.
 
-## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_ECE5170BAD9B454E875F13BEB5762DDD"
class="no-quick-link"></a>Step 1: Install Apache Geode.
+## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_ECE5170BAD9B454E875F13BEB5762DDD"
class="no-quick-link"></a>Step 1: Install Apache Geode
 
 See [How to Install](installation/install_standalone.html#concept_0129F6A1D0EB42C4A3D24861AF2C5425)
for instructions.
 
-## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_582F8CBBD99D42F1A55C07591E2E9E9E"
class="no-quick-link"></a>Step 2: Use gfsh to start a Locator.
+## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_582F8CBBD99D42F1A55C07591E2E9E9E"
class="no-quick-link"></a>Step 2: Use gfsh to start a locator
 
 In a terminal window, use the `gfsh` command line interface to start up a locator. Apache
Geode *gfsh* (pronounced "jee-fish") provides a single, intuitive command-line interface from
which you can launch, manage, and monitor Apache Geode processes, data, and applications.
See [gfsh (Geode SHell)](../tools_modules/gfsh/chapter_overview.html).
 
-The *locator* is a Geode process that tells new, connecting members where running members
are located and provides load balancing for server use. A locator, by default, starts up a
JMX Manager, which is used for monitoring and managing of a Geode cluster. The cluster configuration
service uses locators to persist and distribute cluster configurations to cluster members.
See [Running Geode Locator Processes](../configuring/running/running_the_locator.html) and
[Overview of the Cluster Configuration Service](../configuring/cluster_config/gfsh_persist.html).
+The *locator* is a Geode process that tells new, connecting members where running members
are located and provides load balancing for server use. A locator, by default, starts up a
JMX Manager, which is used for monitoring and managing a Geode cluster. The cluster configuration
service uses locators to persist and distribute cluster configurations to cluster members.
See [Running Geode Locator Processes](../configuring/running/running_the_locator.html) and
[Overview of the Cluster Configuration Service](../configuring/cluster_config/gfsh_persist.html).
 
-1.  Create a scratch working directory (for example, `my_gemfire`) and change directories
into it. `gfsh` saves locator and server working directories and log files in this location.
+1.  Create a scratch working directory (for example, `my_geode`) and change directories into
it. `gfsh` saves locator and server working directories and log files in this location.
 2.  Start gfsh by typing `gfsh` at the command line (or `gfsh.bat` if you are using Windows).
 
     ``` pre
@@ -40,36 +40,36 @@ The *locator* is a Geode process that tells new, connecting members where
runnin
        / _____/ ______/ ______/ /____/ /
       / /  __/ /___  /_____  / _____  /
      / /__/ / ____/  _____/ / /    / /
-    /______/_/      /______/_/    /_/    v8.2.0
+    /______/_/      /______/_/    /_/    1.0.0
 
-    Monitor and Manage GemFire
+    Monitor and Manage Geode
     gfsh>
     ```
 
-3.  At the `gfsh` prompt, type:
+3.  At the `gfsh` prompt, type the `start locator` command and specify a name for the locator:
 
     ``` pre
     gfsh>start locator --name=locator1
-    Starting a GemFire Locator in /home/username/my_gemfire/locator1...
+    Starting a Geode Locator in /home/username/my_geode/locator1...
     .................................
-    Locator in /home/username/my_gemfire/locator1 on ubuntu.local[10334] as locator1 is currently
online.
+    Locator in /home/username/my_geode/locator1 on ubuntu.local[10334] as locator1 is currently
online.
     Process ID: 3529
     Uptime: 18 seconds
-    GemFire Version: 8.2.0
-    Java Version: 1.8.0_60
-    Log File: /home/username/my_gemfire/locator1/locator1.log
+    Geode Version: 1.0.0
+    Java Version: 1.8.0_101
+    Log File: /home/username/my_geode/locator1/locator1.log
     JVM Arguments: -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/username/Pivotal_GemFire_820_b17919_Linux/lib/gemfire.jar:
-    /home/username/Pivotal_GemFire_820_b17919_Linux/lib/locator-dependencies.jar
+    Class-Path: /home/username/Apache_Geode_Linux/lib/geode-core-1.0.0.jar:
+    /home/username/Apache_Geode_Linux/lib/geode-dependencies.jar
 
-    Successfully connected to: [host=ubuntu.local, port=1099]
+    Successfully connected to: JMX Manager [host=10.118.33.169, port=1099]
 
     Cluster configuration service is up and running.
     ```
 
-## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_02C79BFFB5334E78A5856AE1EB1F1F84"
class="no-quick-link"></a>Step 3. Start Pulse.
+## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_02C79BFFB5334E78A5856AE1EB1F1F84"
class="no-quick-link"></a>Step 3: Start Pulse
 
 Start up the browser-based Pulse monitoring tool. Pulse is a Web Application that provides
a graphical dashboard for monitoring vital, real-time health and performance of Geode clusters,
members, and regions. See [Geode Pulse](../tools_modules/pulse/chapter_overview.html).
 
@@ -83,7 +83,7 @@ The Pulse application now displays the locator you just started (locator1):
 
 <img src="../images/pulse_locator.png" id="topic_FE3F28ED18E145F787431EC87B676A76__image_ign_ff5_t4"
class="image" />
 
-## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_C617BC1C70EB41B8BCA3691D6E3C891A"
class="no-quick-link"></a>Step 4: Start a server.
+## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_C617BC1C70EB41B8BCA3691D6E3C891A"
class="no-quick-link"></a>Step 4: Start a server
 
 A Geode server is a process that runs as a long-lived, configurable member of a cluster (also
called a *distributed system*). The Geode server is used primarily for hosting long-lived
data regions and for running standard Geode processes such as the server in a client/server
configuration. See [Running Geode Server Processes](../configuring/running/running_the_cacheserver.html).
 
@@ -98,7 +98,7 @@ This commands starts a cache server named "server1" on the specified port
of 404
 
 Observe the changes (new member and server) in Pulse. Try expanding the distributed system
icon to see the locator and cache server graphically.
 
-## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_3EA12E44B8394C6A9302DF4D14888AF4"
class="no-quick-link"></a>Step 5: Create a replicated, persistent region.
+## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_3EA12E44B8394C6A9302DF4D14888AF4"
class="no-quick-link"></a>Step 5: Create a replicated, persistent region
 
 In this step you create a region with the `gfsh` command line utility. Regions are the core
building blocks of the Geode cluster and provide the means for organizing your data. The region
you create for this exercise employs replication to replicate data across members of the cluster
and utilizes persistence to save the data to disk. See [Data Regions](../basic_config/data_regions/chapter_overview.html#data_regions).
 
@@ -152,7 +152,7 @@ In this step you create a region with the `gfsh` command line utility.
Regions a
 
 **Note:** Keep this `gfsh` prompt open for the next steps.
 
-## Step 6: Manipulate data in the region and demonstrate persistence.
+## Step 6: Manipulate data in the region and demonstrate persistence
 
 Apache Geode manages data as key/value pairs. In most applications, a Java program adds,
deletes and modifies stored data. You can also use gfsh commands to add and retrieve data.
See [Data Commands](../tools_modules/gfsh/quick_ref_commands_by_area.html#topic_C7DB8A800D6244AE8FF3ADDCF139DCE4).
 
@@ -199,9 +199,9 @@ Apache Geode manages data as key/value pairs. In most applications, a
Java progr
 
     ``` pre
     gfsh>stop server --name=server1
-    Stopping Cache Server running in /home/username/my_gemfire/server1 on ubuntu.local[40411]
as server1...
+    Stopping Cache Server running in /home/username/my_geode/server1 on ubuntu.local[40411]
as server1...
     Process ID: 3883
-    Log File: /home/username/my_gemfire/server1/server1.log
+    Log File: /home/username/my_geode/server1/server1.log
     ....
     ```
 
@@ -211,7 +211,7 @@ Apache Geode manages data as key/value pairs. In most applications, a
Java progr
     gfsh>start server --name=server1 --server-port=40411
     ```
 
-5.  Run the following command to retrieve data from the region again-- notice that the data
is still available:
+5.  Run the following command to retrieve data from the region again -- notice that the data
is still available:
 
     ``` pre
     gfsh>query --query="select * from /regionA"
@@ -227,13 +227,13 @@ Apache Geode manages data as key/value pairs. In most applications,
a Java progr
     one
     ```
 
-    Because regionA uses persistence, it writes a copy of the data to disk. When a server
hosting regionA starts, the data is populated into the cache. Note that the result displays
the values for the two data entries you created prior to stopping the server with the `put`
commands.
+    Because regionA uses persistence, it writes a copy of the data to disk. When a server
hosting regionA starts, the data is populated into the cache. Note that the result displays
the values for the two data entries you created with the `put` commands prior to stopping
the server≈.
 
     See [Data Entries](../basic_config/data_entries_custom_classes/chapter_overview.html).
 
     See [Data Regions](../basic_config/data_regions/chapter_overview.html#data_regions).
 
-## Step 7: Examine the effects of replication.
+## Step 7: Examine the effects of replication
 
 In this step, you start a second cache server. Because regionA is replicated, the data will
be available on any server hosting the region.
 
@@ -280,9 +280,9 @@ See [Data Regions](../basic_config/data_regions/chapter_overview.html#data_regio
 
     ``` pre
     gfsh>stop server --name=server1
-    Stopping Cache Server running in /home/username/my_gemfire/server1 on ubuntu.local[40411]
as server1...
+    Stopping Cache Server running in /home/username/my_geode/server1 on ubuntu.local[40411]
as server1...
     Process ID: 4064
-    Log File: /home/username/my_gemfire/server1/server1.log
+    Log File: /home/username/my_geode/server1/server1.log
     ....
     ```
 
@@ -336,13 +336,13 @@ See [Data Regions](../basic_config/data_regions/chapter_overview.html#data_regio
 
     ``` pre
     gfsh>stop server --name=server2
-    Stopping Cache Server running in /home/username/my_gemfire/server2 on ubuntu.local[40412]
as server2...
+    Stopping Cache Server running in /home/username/my_geode/server2 on ubuntu.local[40412]
as server2...
     Process ID: 4185
-    Log File: /home/username/my_gemfire/server2/server2.log
+    Log File: /home/username/my_geode/server2/server2.log
     .....
     ```
 
-## Step 8: Restart the cache servers in parallel.
+## Step 8: Restart the cache servers in parallel
 
 In this step you restart the cache servers in parallel. Because the data is persisted, the
data is available when the servers restart. Because the data is replicated, you must start
the servers in parallel so that they can synchronize their data before starting.
 
@@ -350,7 +350,7 @@ In this step you restart the cache servers in parallel. Because the data
is pers
 
     ``` pre
     gfsh>start server --name=server1 --server-port=40411
-    Starting a GemFire Server in /home/username/my_gemfire/server1...
+    Starting a Geode Server in /home/username/my_geode/server1...
     ............................................................................
     ............................................................................
     ```
@@ -364,29 +364,29 @@ In this step you restart the cache servers in parallel. Because the
data is pers
 
         DiskStore ID: 8e2d99a9-4725-47e6-800d-28a26e1d59b1
         Name: server1
-        Location: /192.0.2.0:/home/username/my_gemfire/server1/.
+        Location: /192.0.2.0:/home/username/my_geode/server1/.
 
       Members with potentially new data:
       [
         DiskStore ID: 2e91b003-8954-43f9-8ba9-3c5b0cdd4dfa
         Name: server2
-        Location: /192.0.2.0:/home/username/my_gemfire/server2/.
+        Location: /192.0.2.0:/home/username/my_geode/server2/.
       ]
-      Use the "gemfire list-missing-disk-stores" command to see all disk stores that
+      Use the "gfsh show missing-disk-stores" command to see all disk stores that
     are being waited on by other members.
     ```
 
-2.  In a second terminal window, change directories to the scratch working directory (for
example, `my_gemfire`) and start gfsh:
+2.  In a second terminal window, change directories to the scratch working directory (for
example, `my_geode`) and start gfsh:
 
     ``` pre
-    [username@localhost ~/my_gemfire]$ gfsh
+    [username@localhost ~/my_geode]$ gfsh
         _________________________     __
        / _____/ ______/ ______/ /____/ /
       / /  __/ /___  /_____  / _____  /
      / /__/ / ____/  _____/ / /    / /
-    /______/_/      /______/_/    /_/    v8.2.0
+    /______/_/      /______/_/    /_/    1.0.0
 
-    Monitor and Manage GemFire
+    Monitor and Manage Geode
     ```
 
 3.  Run the following command to connect to the cluster:
@@ -407,17 +407,17 @@ In this step you restart the cache servers in parallel. Because the
data is pers
     When server2 starts, note that **server1 completes its start up** in the first gfsh window:
 
     ``` pre
-    Server in /home/username/my_gemfire/server1 on ubuntu.local[40411] as server1 is currently
online.
+    Server in /home/username/my_geode/server1 on ubuntu.local[40411] as server1 is currently
online.
     Process ID: 3402
     Uptime: 1 minute 46 seconds
-    GemFire Version: 8.2.0
+    Geode Version: 1.0.0
     Java Version: 1.8.0_60
-    Log File: /home/username/my_gemfire/server1/server1.log
+    Log File: /home/username/my_geode/server1/server1.log
     JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334] -Dgemfire.use-cluster-configuration=true
     -XX:OnOutOfMemoryError=kill -KILL %p -Dgemfire.launcher.registerSignalHandlers=true
     -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
-    Class-Path: /home/username/Pivotal_GemFire_820_b17919_Linux/lib/gemfire.jar:
-    /home/username/Pivotal_GemFire_820_b17919_Linux/lib/server-dependencies.jar
+    Class-Path: /home/username/Apache_Geode_Linux/lib/gemfire.jar:
+    /home/username/Apache_Geode_Linux/lib/server-dependencies.jar
     ```
 
 5.  Verify that the locator and two servers are running:
@@ -455,9 +455,9 @@ In this step you restart the cache servers in parallel. Because the data
is pers
 
     ``` pre
     gfsh>stop server --dir=server2
-    Stopping Cache Server running in /home/username/my_gemfire/server2 on 192.0.2.0[40412]
as server2...
+    Stopping Cache Server running in /home/username/my_geode/server2 on 192.0.2.0[40412]
as server2...
     Process ID: 3992
-    Log File: /home/username/my_gemfire/server2/server2.log
+    Log File: /home/username/my_geode/server2/server2.log
     ....
     ```
 
@@ -481,7 +481,7 @@ In this step you restart the cache servers in parallel. Because the data
is pers
     NEXT_STEP_NAME : END
     ```
 
-## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_E417BEEC172B4E96A92A61DC7601E572"
class="no-quick-link"></a>Step 9: Shut down the system including your locators.
+## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_E417BEEC172B4E96A92A61DC7601E572"
class="no-quick-link"></a>Step 9: Shut down the system including your locators
 
 To shut down your cluster, do the following:
 

http://git-wip-us.apache.org/repos/asf/geode/blob/0b3d44c6/geode-docs/getting_started/system_requirements/host_machine.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/system_requirements/host_machine.html.md.erb b/geode-docs/getting_started/system_requirements/host_machine.html.md.erb
index b2379a9..ce00704 100644
--- a/geode-docs/getting_started/system_requirements/host_machine.html.md.erb
+++ b/geode-docs/getting_started/system_requirements/host_machine.html.md.erb
@@ -33,7 +33,7 @@ Each machine that will run Apache Geode must meet the following requirements:
 -   Many default Linux installations use SYN cookies to protect the 
 system against malicious attacks that flood TCP SYN packets.
 The use of SYN cookies dramatically reduces network bandwidth,
-and can be triggered by a running GemFire distributed system.
+and can be triggered by a running distributed system.
 
     To disable SYN cookies permanently:
     1. Edit the `/etc/sysctl.conf` file to include the following line:


Mime
View raw message