Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/97#discussion_r105208124
--- Diff: markdown/admin/ambari-admin.html.md.erb ---
@@ -182,20 +182,22 @@ First ensure that the new node(s) has been configured
per the instructions found
4. Click **Confirm Add** to acknowledge the component to add. Click
**OK** when the task completes.
5. In the Components summary, select **Add > PXF**.
6. Click **Confirm Add** to acknowledge the component to add. Click
**OK** when the task completes.
-17. (Optional) If you are using hash tables, adjust the **Default buckets
for Hash Distributed tables** setting (`default_hash_table_bucket_number`) on
the HAWQ service's **Configs > Settings** tab. Update this property's value by
multiplying the new number of nodes in the cluster by the appropriate number
indicated below.
-
- |Number of Nodes After Expansion|Suggested
default\_hash\_table\_bucket\_number value|
- |---------------|------------------------------------------|
- |<= 85|6 \* \#nodes|
- |\> 85 and <= 102|5 \* \#nodes|
- |\> 102 and <= 128|4 \* \#nodes|
- |\> 128 and <= 170|3 \* \#nodes|
- |\> 170 and <= 256|2 \* \#nodes|
- |\> 256 and <= 512|1 \* \#nodes|
- |\> 512|512|
-18. Ambari requires the HAWQ service to be restarted in order to apply
the configuration changes. If you need to apply the configuration *without*
restarting HAWQ (for dynamic cluster expansion), then you can use the HAWQ CLI
commands described in [Manually Updating the HAWQ
Configuration](#manual-config-steps) *instead* of following this step.
- <br/><br/>Stop and then start the HAWQ service to apply your
configuration changes via Ambari. Select **Service Actions > Stop**, followed
by **Service Actions > Start** to ensure that the HAWQ Master starts before the
newly-added segment. During the HAWQ startup, Ambari exchanges ssh keys for the
`gpadmin` user, and applies the new configuration.
- >**Note:** Do not use the **Restart All** service action to complete
this step.
+17. (Optional) If you are using hash tables, adjust the **Default buckets
for Hash Distributed tables** setting (`default_hash_table_bucket_number`).
+
+ 1. Open the HAWQ service's **Configs > Settings** tab. Update the
`default_hash_table_bucket_number` property's value by multiplying the new
number of nodes in the cluster by the appropriate number indicated below.
+
+ |Number of Nodes After Expansion|Suggested
default\_hash\_table\_bucket\_number value|
+ |---------------|------------------------------------------|
+ |<= 85|6 \* \#nodes|
+ |\> 85 and <= 102|5 \* \#nodes|
+ |\> 102 and <= 128|4 \* \#nodes|
+ |\> 128 and <= 170|3 \* \#nodes|
+ |\> 170 and <= 256|2 \* \#nodes|
+ |\> 256 and <= 512|1 \* \#nodes|
+ |\> 512|512|
+ 18. Ambari requires that the HAWQ service be restarted in order to
apply the configuration changes. If you need to apply the configuration
*without* restarting HAWQ (for dynamic cluster expansion), then use the
procedure described in [Cluster Expansion Workaround](#manual-config-steps)
*instead* of following this step.
--- End diff --
Reword this to "Ambari requires you to restart the HAWQ service in order to
apply the configuration changes."
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
