Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/97#discussion_r105213393
--- Diff: markdown/admin/ambari-admin.html.md.erb ---
@@ -206,44 +208,22 @@ First ensure that the new node(s) has been configured
per the instructions found
23. (Optional.) If you enabled temporary password-based authentication
while preparing/configuring your HAWQ host systems, turn off password-based
authentication as described in [Apache HAWQ System
Requirements](../requirements/system-requirements.html#topic_pwdlessssh).
-#### <a id="manual-config-steps"></a>Manually Updating the HAWQ
Configuration
-If you need to expand your HAWQ cluster without restarting the HAWQ
service, follow these steps to manually apply the new HAWQ configuration. (Use
these steps *instead* of following Step 7 in the above procedure.):
+#### <a id="manual-config-steps"></a>Cluster Expansion Workaround
+If you need to expand your HAWQ cluster without restarting the HAWQ
service, follow this procedure to manually apply the HAWQ configuration changes
required for this operation. (Perform these steps *instead of* following Step
9b in the above procedure.)
-1. Update your configuration to use the new
`default_hash_table_bucket_number` value that you calculated:
- 1. SSH into the HAWQ master host as the `gpadmin` user:
- ```shell
- $ ssh gpadmin@<HAWQ_MASTER_HOST>
- ```
- 2. Source the `greenplum_path.sh` file to update the shell environment:
- ```shell
- $ source /usr/local/hawq/greenplum_path.sh
- ```
- 3. Verify the current value of `default_hash_table_bucket_number`:
- ```shell
- $ hawq config -s default_hash_table_bucket_number
- ```
- 4. Update `default_hash_table_bucket_number` to the new value that you
calculated:
- ```shell
- $ hawq config -c default_hash_table_bucket_number -v <new_value>
- ```
- 5. Reload the configuration without restarting the cluster:
- ```shell
- $ hawq stop cluster -u
- ```
- 6. Verify that the `default_hash_table_bucket_number` value was updated:
- ```shell
- $ hawq config -s default_hash_table_bucket_number
- ```
-2. Edit the `/usr/local/hawq/etc/slaves` file and add the new HAWQ
hostname(s) to the end of the file. Separate multiple hosts with new lines. For
example, after adding host4 and host5 to a cluster already contains hosts 1-3,
the updated file contents would be:
+1. Perform the procedure identified in [Updating HAWQ Configuration
Without Cluster Restart](#manual-cfg-norestart) to update your configuration to
use the new `default_hash_table_bucket_number` value that you calculated and
set via the Ambari UI. You may skip Step 1 of this procedure.
+
+2. Edit the `/usr/local/hawq/etc/slaves` file and add the new HAWQ
hostname(s) to the end of the file. Identify each host on a separate line. For
example, after adding host4 and host5 to a cluster already containing hosts
1-3, the `slaves` file would appear similar to the following:
```
host1
host2
host3
host4
host5
- ```
-3. Continue with Step 8 in the previous procedure, [Expanding the HAWQ
Cluster](#amb-expand). When the HAWQ service is ready to be restarted via
Ambari, Ambari will refresh the new configurations.
+ ```
+
+3. Continue with Step 10 in the previous procedure, [Expanding the HAWQ
Cluster](#amb-expand). When the HAWQ service is ready to be restarted via
Ambari, Ambari will refresh the new configurations.
--- End diff --
Let's insert and use an anchor to get them right back to step 10 here.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
