diff --git a/docs/EN_US/ConfiguringHPCC/ConfiguringHPCC.xml b/docs/EN_US/ConfiguringHPCC/ConfiguringHPCC.xml
index 511ce4dabfe..3dff4ff3f4e 100644
--- a/docs/EN_US/ConfiguringHPCC/ConfiguringHPCC.xml
+++ b/docs/EN_US/ConfiguringHPCC/ConfiguringHPCC.xml
@@ -37,7 +37,7 @@
similarity to actual persons, living or dead, is purely
coincidental.
-
+ If it is running, stop the HPCC system using this command on
every node:
-
-
+
@@ -469,7 +468,7 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
fileref="images/OSSgr3.png" />
You can use this command to confirm HPCC processes
- are stopped: sudo /etc/init.d/hpcc-init status
+ are stopped: sudo systemctl status hpccsystems-platform.target
@@ -1790,8 +1789,8 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
In the kibanaEntryPointURI field,
- enter the Kibana URI pointing to your shared Kibana dashboard.
-
+ enter the Kibana URI pointing to your shared Kibana
+ dashboard.
For example: /app/kibana#/dashboard/etc. (obtained from
the "share" tab in Kibana)
@@ -2556,22 +2555,27 @@ sudo -u hpcc cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/envi
+
Redundancy
+
Roxie can be configured to utilize a few different redundancy
models. Simple Redundancy - One channel per slave. Most commonly
used for a single node Roxie.
+
Full Redundancy - More slaves than the number of
channels. Multiple slaves host each channel.
+
Overloaded Redundancy - There are multiple channels per
slave.
+
Cyclic Redundancy - Each node hosts multiple channels in
rotation. The most commonly used configuration.
diff --git a/docs/EN_US/DynamicESDL/DynamicESDL_Includer.xml b/docs/EN_US/DynamicESDL/DynamicESDL_Includer.xml
index ef4da578ee3..8a4f92c4a95 100644
--- a/docs/EN_US/DynamicESDL/DynamicESDL_Includer.xml
+++ b/docs/EN_US/DynamicESDL/DynamicESDL_Includer.xml
@@ -37,7 +37,7 @@
similarity to actual persons, living or dead, is purely
coincidental.
-
+ If it is running, stop the HPCC system, using this command in
a terminal window:
-
-
+
@@ -240,7 +239,7 @@
fileref="images/OSSgr3.png" />
You can use this command to confirm HPCC processes
- are stopped:sudo /etc/init.d/hpcc-init status
+ are stopped:sudo systemctl status hpccsystems-platform.target
@@ -392,10 +391,9 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
role="bold">every node. The following command starts the
HPCC system on an individual node:
-
-
+
@@ -414,10 +412,10 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
You may want to create a script to push this
command out to every node. A sample script is provided with
HPCC. Use the following command to start HPCC on all
- nodes:
-
+ nodes:
@@ -655,10 +653,11 @@ ds_out := ROW ({res},MathService.MathService.t_AddThisResponse);
OUTPUT(ds_out, NAMED('AddThisResponse'));
-
- Using the Target drop list, select
- Roxie as the Target cluster.
+
+
+
+ Using the Target drop list,
+ select Roxie as the Target cluster.