Docs: Updating/removing "experimental" status for resource groups feature (#3705)

* Docs - editing resource groups warning for RHEL 6 * removing most RG experiental warnings; addressing remaining SuSE issue and experimental status on that platform

Docs: Updating/removing "experimental" status for resource groups feature (#3705)
* Docs - editing resource groups warning for RHEL 6 * removing most RG experiental warnings; addressing remaining SuSE issue and experimental status on that platform
7a0415ba · David Yozie · GitHub · 0854d2c7 · 7a0415ba · 7a0415ba
9 changed file
--- a/gpdb-doc/dita/admin_guide/wlmgmt.xml
+++ b/gpdb-doc/dita/admin_guide/wlmgmt.xml
@@ -11,14 +11,14 @@
      amount of memory used to execute a query, and the relative amount of CPU devoted to processing
      a query. Greenplum Database provides two schemes to manage resources - Resource Queues and
      Resource Groups.</p>
-    <note type="warning">Resource groups are an experimental feature and are not intended for use in
-      a production environment. Experimental features are subject to change without notice in future
-        releases.<p>Significant Greenplum Database performance degradation has been observed when
-        enabling resource group-based workload management on RedHat 6.x, CentOS 6.x, and SuSE 11
-        systems. This issue is caused by a Linux cgroup kernel bug. This kernel bug has been fixed
-        in CentOS 7.x and Red Hat 7.x systems, and in Red Hat 6 systems that use kernel version
-        2.6.32-696 or higher. SuSE 11 does not have a kernel version that resolves this
-      issue.</p></note>
+    <note type="warning">Significant Greenplum Database performance degradation has been observed
+      when enabling resource group-based workload management on RedHat 6.x, CentOS 6.x, and SuSE 11
+      systems. This issue is caused by a Linux cgroup kernel bug. This kernel bug has been fixed in
+      CentOS 7.x and Red Hat 7.x systems. The performance problem is mitigated in Red Hat 6 systems
+      that use kernel version 2.6.32-696 or higher. <p>SuSE 11 does not have a kernel version that
+        resolves this issue; resource groups are considered to be an experimental feature on this platform. <ph
+          otherprops="pivotal">Resource groups are not supported on SuSE 11 for production
+        use.</ph></p></note>
    <p>Either the resource queue or the resource group management scheme can be active in Greenplum
      Database; both schemes cannot be active at the same time.</p>
    <p>Resource queues are enabled by default when you install your Greenplum Database cluster.

--- a/gpdb-doc/dita/admin_guide/workload_mgmt_resgroups.xml
+++ b/gpdb-doc/dita/admin_guide/workload_mgmt_resgroups.xml
@@ -4,9 +4,6 @@
 <topic id="topic1" xml:lang="en">
  <title id="iz173472">Using Resource Groups</title>
  <body>
-    <note type="warning">Resource groups are an experimental feature and are not intended for use in
-      a production environment. Experimental features are subject to change without notice in future
-      releases.</note>
    <p>You can use resource groups to manage the number of active queries that may execute
      concurrently in your Greenplum Database cluster. With resource groups, you can also manage the
      amount of CPU and memory resources Greenplum allocates to each query.</p>
@@ -199,9 +196,11 @@
      <note type="warning">Significant Greenplum Database performance degradation has been observed
        when enabling resource group-based workload management on RedHat 6.x, CentOS 6.x, and SuSE
        11 systems. This issue is caused by a Linux cgroup kernel bug. This kernel bug has been
-        fixed in CentOS 7.x and Red Hat 7.x systems, and in Red Hat 6 systems that use kernel
-        version 2.6.32-696 or higher. SuSE 11 does not have a kernel version that resolves this
-        issue.</note>
+        fixed in CentOS 7.x and Red Hat 7.x systems. The performance problem is mitigated in Red Hat
+        6 systems that use kernel version 2.6.32-696 or higher. <p>SuSE 11 does not have a kernel
+          version that resolves this issue; resource groups are considered to be an experimental
+          feature on this platform. <ph otherprops="pivotal">Resource groups are not supported on
+            SuSE 11 for production use.</ph></p></note>
      <section id="topic833" xml:lang="en">
        <title>Prerequisite</title>
        <p>Greenplum Database resource groups use Linux Control Groups (cgroups) to manage CPU

--- a/gpdb-doc/dita/ref_guide/config_params/guc-list.xml
+++ b/gpdb-doc/dita/ref_guide/config_params/guc-list.xml
@@ -4887,9 +4887,6 @@
  <topic id="gp_resgroup_memory_policy">
    <title>gp_resgroup_memory_policy</title>
    <body>
-      <note type="warning">Resource groups are an experimental feature and
-        are not intended for use in a production environment. Experimental features are subject to
-        change without notice in future releases.</note>
      <p>Used by a resource group to manage memory allocation to query operators.</p>
      <p>When set to <codeph>auto</codeph>, Greenplum Database uses resource group memory limits to distribute memory across query operators, allocating a fixed size of memory to non-memory-intensive operators and the rest to memory-intensive operators.</p>
      <p>When you specify <codeph>eager_free</codeph>, Greenplum Database distributes memory among operators more optimally by re-allocating memory released by operators that have completed their processing to operators in a later query stage.</p>
@@ -4919,9 +4916,6 @@
  <topic id="gp_resource_group_cpu_limit">
    <title>gp_resource_group_cpu_limit</title>
    <body>
-      <note type="warning">Resource groups are an experimental feature and are not intended for use
-        in a production environment. Experimental features are subject to change without notice in
-        future releases.</note>
      <p>Identifies the maximum percentage of system CPU resources to allocate to resource groups on
        each Greenplum Database segment node.</p>
      <table id="gp_resource_group_cpu_limit_table">
@@ -4950,9 +4944,6 @@
  <topic id="gp_resource_group_memory_limit">
    <title>gp_resource_group_memory_limit</title>
    <body>
-      <note type="warning">Resource groups are an experimental feature and are not intended for use
-        in a production environment. Experimental features are subject to change without notice in
-        future releases.</note>
      <p>Identifies the maximum percentage of system memory resources to allocate to resource groups
        on each Greenplum Database segment node.</p>
      <table id="gp_resource_group_memory_limit_table">
@@ -4981,9 +4972,6 @@
  <topic id="gp_resource_manager">
    <title>gp_resource_manager</title>
    <body>
-      <note type="warning">Resource groups are an experimental feature and are not intended for use
-        in a production environment. Experimental features are subject to change without notice in
-        future releases.</note>
      <p>Identifies the resource management scheme currently enabled in the Greenplum Database
        cluster. The default scheme is to use resource queues.</p>
      <table id="gp_resource_manager_table">
@@ -7260,9 +7248,6 @@
  <topic id="max_resource_groups">
    <title>max_resource_groups</title>
    <body>
-      <note type="warning">Resource groups are an experimental feature and are not intended for use
-        in a production environment. Experimental features are subject to change without notice in
-        future releases.</note>
      <p>Sets the maximum number of resource groups that you can create in a Greenplum Database
        system. Resource groups are defined system-wide.</p>
      <table id="max_resource_queues_table">
@@ -7390,9 +7375,6 @@
  <topic id="memory_spill_ratio">
    <title>memory_spill_ratio</title>
    <body>
-      <note type="warning">Resource groups are an experimental feature and are not intended for use
-        in a production environment. Experimental features are subject to change without notice in
-        future releases.</note>
      <p>Sets the memory usage threshold for memory-intensive operators in a transaction. When a
        transaction reaches this threshold, it spills to disk.</p>
      <p>The default <codeph>memory_spill_ratio</codeph> is the value defined for the resource group

--- a/gpdb-doc/dita/ref_guide/config_params/guc_category-list.xml
+++ b/gpdb-doc/dita/ref_guide/config_params/guc_category-list.xml
@@ -1196,9 +1196,6 @@
  <topic id="topic444" xml:lang="en">
    <title id="kh1550694">Resource Management Parameters (Resource Groups)</title>
    <body>
-      <note type="warning">Resource groups are an experimental feature and are not intended for use
-        in a production environment. Experimental features are subject to change without notice in
-        future releases.</note>
      <p>The following parameters configure the Greenplum Database resource group workload
        management feature. </p>
      <simpletable id="kh1571613" frame="none">

--- a/gpdb-doc/dita/ref_guide/sql_commands/ALTER_RESOURCE_GROUP.xml
+++ b/gpdb-doc/dita/ref_guide/sql_commands/ALTER_RESOURCE_GROUP.xml
@@ -4,7 +4,6 @@
 <topic id="topic1">
  <title id="au20941">ALTER RESOURCE GROUP</title>
  <body>
-    <note type="warning">Resource groups are an experimental feature and are not intended for use in a production environment. Experimental features are subject to change without notice in future releases.</note>
    <p id="sql_command_desc">Changes the limits of a resource group.</p>
    <section id="section2">
      <title>Synopsis</title>

--- a/gpdb-doc/dita/ref_guide/sql_commands/ALTER_ROLE.xml
+++ b/gpdb-doc/dita/ref_guide/sql_commands/ALTER_ROLE.xml
@@ -67,8 +67,7 @@ ALTER ROLE <varname>name</varname> [ [WITH] <varname>option</varname> [ ... ] ]<
          would then be subject to the concurrent transaction, memory, and CPU limits configured for
          the resource group. You can assign a single resource group to one or more roles. See
              <codeph><xref href="./CREATE_RESOURCE_GROUP.xml#topic1" type="topic" format="dita"
-            /></codeph> for additional information.
-            <note type="warning">Resource groups are an experimental feature and are not intended for use in a production environment. Experimental features are subject to change without notice in future releases.</note> </li>
+            /></codeph> for additional information.  </li>
        <li id="av137061"><b>WITH <varname>option</varname></b> — Changes many of the role
          attributes that can be specified in <codeph><xref href="./CREATE_ROLE.xml#topic1"
              type="topic" format="dita"/></codeph>. Attributes not mentioned in the command retain

--- a/gpdb-doc/dita/ref_guide/sql_commands/CREATE_RESOURCE_GROUP.xml
+++ b/gpdb-doc/dita/ref_guide/sql_commands/CREATE_RESOURCE_GROUP.xml
@@ -4,7 +4,6 @@
 <topic id="topic1">
  <title id="by20941">CREATE RESOURCE GROUP</title>
  <body>
-    <note type="warning">Resource groups are an experimental feature and are not intended for use in a production environment. Experimental features are subject to change without notice in future releases.</note>
    <p id="sql_command_desc">Defines a new resource group.</p>
    <section id="section2">
      <title>Synopsis</title>

--- a/gpdb-doc/dita/ref_guide/sql_commands/CREATE_ROLE.xml
+++ b/gpdb-doc/dita/ref_guide/sql_commands/CREATE_ROLE.xml
@@ -179,7 +179,6 @@
                        having the <codeph>SUPERUSER</codeph> attribute.</pd>
                    <pd>You can assign the <codeph>default_group</codeph> resource group to any
                        role.</pd>
-                    <pd><note type="warning">Resource groups are an experimental feature and are not intended for use in a production environment. Experimental features are subject to change without notice in future releases.</note></pd>
                </plentry>
                <plentry>
                    <pt>RESOURCE QUEUE <varname>queue_name</varname></pt>

--- a/gpdb-doc/dita/ref_guide/sql_commands/DROP_RESOURCE_GROUP.xml
+++ b/gpdb-doc/dita/ref_guide/sql_commands/DROP_RESOURCE_GROUP.xml
@@ -2,7 +2,6 @@
 <!DOCTYPE topic
  PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
 <topic id="topic1"><title id="dc20941">DROP RESOURCE GROUP</title><body>
-    <note type="warning">Resource groups are an experimental feature and are not intended for use in a production environment. Experimental features are subject to change without notice in future releases.</note>
    <p id="sql_command_desc">Removes a resource group.</p><section id="section2"><title>Synopsis</title><codeblock id="sql_command_synopsis">DROP RESOURCE GROUP <varname>group_name</varname></codeblock></section><section id="section3"><title>Description</title><p>This command removes a resource group from Greenplum
 Database. Only a superuser
 can drop a resource group.</p><p>To drop a resource group, the group cannot be assigned to any roles,