Docs - highlight vacuum after gpexpand (#9944)

* clarifying pg_upgrade note * adding VACUUM note for gpexpand * gpexpand edits * small edit * edits after review

Docs - highlight vacuum after gpexpand (#9944)
* clarifying pg_upgrade note * adding VACUUM note for gpexpand * gpexpand edits * small edit * edits after review
f656b50e · Lena Hunter · GitHub · 959364a1 · f656b50e · f656b50e
3 changed file
--- a/gpdb-doc/dita/admin_guide/expand/expand-initialize.xml
+++ b/gpdb-doc/dita/admin_guide/expand/expand-initialize.xml
@@ -210,35 +210,37 @@ sdw5|sdw5-1|60012|/gpdata/mirror/gp10|14|10|m</codeblock>
          the expansion schema. The <i>gpexpand</i> schema resides in the
            postgres database. For more information, see <xref
            href="expand-planning.xml#topic9" type="topic" format="dita"/>.</p>
+        <p>After segment initialization is complete,  <xref
+            href="expand-redistribute.xml#topic28/expand-redistribute">redistribute the
+            tables</xref> to balance existing data over the new segments.</p>
      </section>
    </body>
  </topic>
-  <topic id="topic27" xml:lang="en">
-    <title>Rolling Back a Failed Expansion Setup</title>
-    <body>
-      <p>You can roll back an expansion setup operation (adding segment instances and segment hosts)
-        only if the operation fails.</p>
-      <p>If the expansion fails during the initialization step, while the database is down, you must
-        first restart the database in master-only mode by running the <codeph>gpstart -m</codeph>
-        command. </p>
-      <p>Roll back the failed expansion with the following
-        command:<codeblock>gpexpand --rollback</codeblock></p>
-    </body>
-  </topic>
  <topic id="topic_wkv_kkd_chb">
    <title>Monitoring the Cluster Expansion State</title>
    <body>
      <p>At any time, you can check the state of cluster expansion by running the
          <codeph>gpstate</codeph> utility with the <codeph>-x</codeph> flag: </p>
      <codeblock>$ gpstate -x</codeblock>
-      <p>If the expansion schema exists in the postgres database, <codeph>gpstate
-          -x</codeph> reports on the progress of the expansion. During the first expansion phase,
-          <codeph>gpstate</codeph> reports on the progress of new segment initialization.  During the
+      <p>If the expansion schema exists in the postgres database, <codeph>gpstate -x</codeph>
+        reports on the progress of the expansion. During the first expansion phase,
+          <codeph>gpstate</codeph> reports on the progress of new segment initialization. During the
        second phase, <codeph>gpstate</codeph> reports on the progress of table redistribution, and
        whether redistribution is paused or active. </p>
      <p>You can also query the expansion schema to see expansion status. See <xref
          href="expand-redistribute.xml#topic31"/> for more information.</p>
-
+    </body>
+  </topic>
+  <topic id="topic27" xml:lang="en">
+    <title>Rolling Back a Failed Expansion Setup</title>
+    <body>
+      <p>You can roll back an expansion setup operation (adding segment instances and segment hosts)
+        only if the operation fails.</p>
+      <p>If the expansion fails during the initialization step, while the database is down, you must
+        first restart the database in master-only mode by running the <codeph>gpstart -m</codeph>
+        command. </p>
+      <p>Roll back the failed expansion with the following
+        command:<codeblock>gpexpand --rollback</codeblock></p>
    </body>
  </topic>
 </topic>
--- a/gpdb-doc/dita/admin_guide/expand/expand-planning.xml
+++ b/gpdb-doc/dita/admin_guide/expand/expand-planning.xml
@@ -164,9 +164,9 @@
                  <image href="../graphics/green-checkbox.jpg" width="29px" height="28px"
                    id="image_sk2_51m_2r"/>
                </entry>
-                <entry>Run <codeph>analyze</codeph> to update distribution statistics.<p>During the
-                    expansion, use <codeph>gpexpand -a</codeph>, and post-expansion, use
-                      <codeph>analyze</codeph>.</p></entry>
+                <entry><b>Important:</b> Run <codeph>analyze</codeph> to update distribution
+                    statistics.<p>During the expansion, use <codeph>gpexpand -a</codeph>, and
+                    post-expansion, use <codeph>analyze</codeph>.</p></entry>
              </row>
              <row>
                <entry namest="c1" nameend="c2"><p><b>Back Up Databases</b></p><ph>* System is up
@@ -208,7 +208,7 @@
          configuration in the particular site and environment. </li>
      </ul>
      <p>After selecting and adding new hardware to your network environment, ensure you perform the
-        burn-in tasks described in <xref href="expand-nodes.xml#topic19" type="topic" format="dita"
+        burn-in tasks described in <xref href="expand-nodes.xml#topic18" type="topic" format="dita"
        />.</p>
    </body>
  </topic>

--- a/gpdb-doc/dita/admin_guide/expand/expand-redistribute.xml
+++ b/gpdb-doc/dita/admin_guide/expand/expand-redistribute.xml
@@ -73,18 +73,32 @@
                  href="../../ref_guide/system_catalogs/gp_expansion_status.xml"
                  >gpexpand.status</xref></i> when a session starts and finishes.</p></li>
        </ol>
+        <note>After completing table redistribution, run the <codeph>VACUUM ANALYZE</codeph> and
+            <codeph>REINDEX</codeph>commands on the catalog tables to update table statistics, and
+          rebuild indexes. See <xref href="../managing/maintain.xml#topic2">Routine Vacuum and
+            Analyze</xref> in the <i>Administration Guide</i> and <xref
+            href="../../ref_guide/sql_commands/VACUUM.xml#topic1/er20941"
+            ><codeph>VACUUM</codeph></xref> in the <i>Reference Guide</i>. </note>
      </section>
    </body>
  </topic>
  <topic id="topic31" xml:lang="en">
    <title>Monitoring Table Redistribution</title>
    <body>
-      <p>You can query the expansion schema during the table redistribution process. The view
-            <i><xref href="../../ref_guide/system_catalogs/gpexpand_expansion_progress.xml"
-            >gpexpand.expansion_progress</xref></i> provides a current progress summary, including
-        the estimated rate of table redistribution and estimated time to completion. You can query
-        the table <i><xref href="../../ref_guide/system_catalogs/gp_expansion_tables.xml"
-            >gpexpand.status_detail</xref></i> for per-table status information.</p>
+      <p>During the table redistribution process you can query the expansion schema to view:</p> 
+      <ul
+          id="ul_tn2_xzr_jlb">
+          <li>a current progress summary, the estimated rate of table redistribution, and the
+          estimated time to completion. Use <i><xref
+              href="../../ref_guide/system_catalogs/gpexpand_expansion_progress.xml"
+              >gpexpand.expansion_progress</xref></i>, as described in <xref href="#topic32"
+            format="dita">Viewing Expansion Status</xref>.</li>
+          <li>per-table status information, using <i><xref
+              href="../../ref_guide/system_catalogs/gp_expansion_tables.xml"
+              >gpexpand.status_detail</xref></i>. See <xref href="#topic33" format="dita">Viewing
+            Table Status</xref>.</li>
+        </ul>
+     
      <p>See also <xref href="expand-initialize.xml#topic_wkv_kkd_chb"/> for information about
        monitoring the overall expansion progress with the <codeph>gpstate</codeph> utility.</p>
    </body>