You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by huor <gi...@git.apache.org> on 2015/11/26 11:00:59 UTC
[GitHub] incubator-hawq pull request: HAWQ-196: Refine GUCs in hawq-site.xm...
GitHub user huor opened a pull request:
https://github.com/apache/incubator-hawq/pull/138
HAWQ-196: Refine GUCs in hawq-site.xml and template-hawq-site.xml
Please review the unification of GUCs in hawq-site.xml and template-hawq-site.xml
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/huor/incubator-hawq github_huor_guc
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/138.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #138
----
commit 99e1e07df1fd68145ab7426626a85c6a91dc7cce
Author: Ruilong Huo <rh...@pivotal.io>
Date: 2015-11-26T09:08:32Z
HAWQ-196: Refine GUCs in hawq-site.xml and template-hawq-site.xml
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq pull request: HAWQ-196: Refine GUCs in hawq-site.xm...
Posted by radarwave <gi...@git.apache.org>.
Github user radarwave commented on a diff in the pull request:
https://github.com/apache/incubator-hawq/pull/138#discussion_r45961973
--- Diff: src/backend/utils/misc/etc/template-hawq-site.xml ---
@@ -20,131 +20,133 @@ under the License.
-->
<configuration>
- <property>
- <name>hawq_master_address_host</name>
- <value>%master.host%</value>
- </property>
-
- <property>
- <name>hawq_master_address_port</name>
- <value>%master.port%</value>
- </property>
-
- <property>
- <name>hawq_standby_address_host</name>
- <value>%standby.host%</value>
- </property>
-
- <property>
- <name>hawq_segment_address_port</name>
- <value>%segment.port%</value>
- </property>
-
- <property>
- <name>hawq_dfs_url</name>
- <value>%namenode.host%:%namenode.port%/%hawq.file.space%</value>
- </property>
-
- <property>
- <name>hawq_master_directory</name>
- <value>%master.directory%</value>
- </property>
-
- <property>
- <name>hawq_segment_directory</name>
- <value>%segment.directory%</value>
- </property>
-
- <property>
- <name>hawq_master_temp_directory</name>
- <value>%master.temp.directory%</value>
- </property>
-
- <property>
- <name>hawq_segment_temp_directory</name>
- <value>%segment.temp.directory%</value>
- </property>
+ <property>
+ <name>hawq_master_address_host</name>
+ <value>%master.host%</value>
+ <description>The host name of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_address_port</name>
+ <value>%master.port%</value>
+ <description>The port of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_standby_address_host</name>
+ <value>%standby.host%</value>
+ <description>The host name of hawq standby master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_address_port</name>
+ <value>%segment.port%</value>
+ <description>The port of hawq segment.</description>
+ </property>
+
+ <property>
+ <name>hawq_dfs_url</name>
+ <value>%namenode.host%:%namenode.port%/%hawq.file.space%</value>
+ <description>URL for accessing HDFS.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_directory</name>
+ <value>%master.directory%</value>
+ <description>The directory of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_directory</name>
+ <value>%segment.directory%</value>
+ <description>The directory of hawq segment.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_temp_directory</name>
+ <value>%master.temp.directory%</value>
+ <description>The temporary directory reserved for hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_temp_directory</name>
+ <value>%segment.temp.directory%</value>
+ <description>The temporary directory reserved for hawq segment.</description>
+ </property>
- <!-- HAWQ resource manager parameters -->
- <property>
- <name>hawq_rm_yarn_address</name>
- <value>%master.host%:9980</value>
--- End diff --
The port number better to be consist between hawq-site.xml, template-hawq-site.xml and yarn-client.xml.
8032 <--> 9080
8030 <--> 9081
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq pull request: HAWQ-196: Refine GUCs in hawq-site.xm...
Posted by radarwave <gi...@git.apache.org>.
Github user radarwave commented on the pull request:
https://github.com/apache/incubator-hawq/pull/138#issuecomment-160566666
Looks good to me. +1
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq pull request: HAWQ-196: Refine GUCs in hawq-site.xm...
Posted by huor <gi...@git.apache.org>.
Github user huor commented on the pull request:
https://github.com/apache/incubator-hawq/pull/138#issuecomment-159865640
@radarwave , @jiny2 , @yaoj2, @changleicn , please review.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq pull request: HAWQ-196: Refine GUCs in hawq-site.xm...
Posted by huor <gi...@git.apache.org>.
Github user huor commented on a diff in the pull request:
https://github.com/apache/incubator-hawq/pull/138#discussion_r46233696
--- Diff: src/backend/utils/misc/etc/hawq-site.xml ---
@@ -20,103 +20,133 @@ under the License.
-->
<configuration>
- <property>
- <name>hawq_master_address_host</name>
- <value>localhost</value>
- <description>The host name of hawq master.</description>
- </property>
-
- <property>
- <name>hawq_master_address_port</name>
- <value>5432</value>
- <description>The port of hawq master.</description>
- </property>
-
- <property>
- <name>hawq_segment_address_port</name>
- <value>40000</value>
- <description>The port of hawq segment.</description>
- </property>
-
- <property>
- <name>hawq_dfs_url</name>
- <value>localhost:8020/hawq_default</value>
- <description>URL for accessing HDFS.</description>
- </property>
-
- <property>
- <name>hawq_master_directory</name>
- <value>~/hawq-data-directory/masterdd</value>
- <description>The directory of hawq master.</description>
- </property>
-
- <property>
- <name>hawq_segment_directory</name>
- <value>~/hawq-data-directory/segmentdd</value>
- <description>The directory of hawq segment.</description>
- </property>
-
- <property>
- <name>hawq_master_temp_directory</name>
- <value>/tmp</value>
- <description>The temporary directory reserved for hawq master.</description>
- </property>
-
- <property>
- <name>hawq_segment_temp_directory</name>
- <value>/tmp</value>
- <description>The temporary directory reserved for hawq segment.</description>
- </property>
+ <property>
+ <name>hawq_master_address_host</name>
+ <value>localhost</value>
+ <description>The host name of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_address_port</name>
+ <value>5432</value>
+ <description>The port of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_standby_address_host</name>
+ <value>none</value>
+ <description>The host name of hawq standby master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_address_port</name>
+ <value>40000</value>
+ <description>The port of hawq segment.</description>
+ </property>
+
+ <property>
+ <name>hawq_dfs_url</name>
+ <value>localhost:8020/hawq_default</value>
+ <description>URL for accessing HDFS.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_directory</name>
+ <value>~/hawq-data-directory/masterdd</value>
+ <description>The directory of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_directory</name>
+ <value>~/hawq-data-directory/segmentdd</value>
+ <description>The directory of hawq segment.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_temp_directory</name>
+ <value>/tmp</value>
+ <description>The temporary directory reserved for hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_temp_directory</name>
+ <value>/tmp</value>
+ <description>The temporary directory reserved for hawq segment.</description>
+ </property>
- <!-- HAWQ resource manager parameters -->
- <property>
- <name>hawq_global_rm_type</name>
- <value>none</value>
- <description>The resource manager type to start for allocating resource.
- 'none' means hawq resource manager exclusively uses whole
- cluster; 'yarn' means hawq resource manager contacts YARN
- resource manager to negotiate resource.
- </description>
- </property>
-
- <property>
- <name>hawq_rm_memory_limit_perseg</name>
- <value>64GB</value>
- <description>The limit of memory usage in a hawq segment when
- hawq_global_rm_type is set 'none'.
- </description>
- </property>
-
- <property>
- <name>hawq_rm_nvcore_limit_perseg</name>
- <value>16</value>
- <description>The limit of virtual core usage in a hawq segment when
- hawq_global_rm_type is set 'none'.
- </description>
- </property>
-
- <property>
- <name>hawq_rm_yarn_address</name>
- <value>localhost:8032</value>
- <description>The address of YARN resource manager server.</description>
- </property>
-
- <property>
- <name>hawq_rm_yarn_scheduler_address</name>
- <value>localhost:8030</value>
- <description>The address of YARN scheduler server.</description>
- </property>
-
- <property>
- <name>hawq_rm_yarn_queue_name</name>
- <value>default</value>
- <description>The YARN queue name to register hawq resource manager.</description>
- </property>
-
- <property>
- <name>hawq_rm_yarn_app_name</name>
- <value>hawq</value>
- <description>The application name to register hawq resource manager in YARN.</description>
- </property>
-
+ <!-- HAWQ resource manager parameters -->
+ <property>
+ <name>hawq_global_rm_type</name>
+ <value>none</value>
+ <description>The resource manager type to start for allocating resource.
+ 'none' means hawq resource manager exclusively uses whole
+ cluster; 'yarn' means hawq resource manager contacts YARN
+ resource manager to negotiate resource.
+ </description>
+ </property>
+
+ <property>
+ <name>hawq_rm_memory_limit_perseg</name>
+ <value>64GB</value>
+ <description>The limit of memory usage in a hawq segment when
+ hawq_global_rm_type is set 'none'.
+ </description>
+ </property>
+
+ <property>
+ <name>hawq_rm_nvcore_limit_perseg</name>
+ <value>16</value>
+ <description>The limit of virtual core usage in a hawq segment when
+ hawq_global_rm_type is set 'none'.
+ </description>
+ </property>
+
+ <property>
+ <name>hawq_rm_yarn_address</name>
+ <value>localhost:8032</value>
+ <description>The address of YARN resource manager server.</description>
+ </property>
+
+ <property>
+ <name>hawq_rm_yarn_scheduler_address</name>
+ <value>localhost:8030</value>
+ <description>The address of YARN scheduler server.</description>
+ </property>
+
+ <property>
+ <name>hawq_rm_yarn_queue_name</name>
+ <value>default</value>
+ <description>The YARN queue name to register hawq resource manager.</description>
+ </property>
+
+ <property>
+ <name>hawq_rm_yarn_app_name</name>
+ <value>hawq</value>
+ <description>The application name to register hawq resource manager in YARN.</description>
+ </property>
+ <!-- HAWQ resource manager parameters end here. -->
+
+ <!-- HAWQ resource enforcement parameters -->
+ <property>
+ <name>hawq_re_cpu_enable</name>
+ <value>false</value>
+ <description>The control to enable/disable CPU resource enforcement.</description>
+ </property>
+
+ <property>
+ <name>hawq_re_cgroup_mount_point</name>
+ <value>/sys/fs/cgroup</value>
+ <description>The mount point of CGroup file system for resource enforcement.
+ For example, /sys/fs/cgroup/cpu/hawq for CPU sub-system.
+ </description>
+ </property>
+
+ <property>
+ <name>hawq_re_cgroup_hierarchy_name</name>
+ <value>hawq</value>
--- End diff --
The previous value for "hawq_re_cgroup_hierarchy_name" is "hadoop-yarn". In the unification of properties, we changed it to "hawq" which is more meaningful. Please update it to "hawq" in Ambari accordingly. Thanks.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq pull request: HAWQ-196: Refine GUCs in hawq-site.xm...
Posted by denalex <gi...@git.apache.org>.
Github user denalex commented on a diff in the pull request:
https://github.com/apache/incubator-hawq/pull/138#discussion_r46176605
--- Diff: src/backend/utils/misc/etc/hawq-site.xml ---
@@ -20,103 +20,133 @@ under the License.
-->
<configuration>
- <property>
- <name>hawq_master_address_host</name>
- <value>localhost</value>
- <description>The host name of hawq master.</description>
- </property>
-
- <property>
- <name>hawq_master_address_port</name>
- <value>5432</value>
- <description>The port of hawq master.</description>
- </property>
-
- <property>
- <name>hawq_segment_address_port</name>
- <value>40000</value>
- <description>The port of hawq segment.</description>
- </property>
-
- <property>
- <name>hawq_dfs_url</name>
- <value>localhost:8020/hawq_default</value>
- <description>URL for accessing HDFS.</description>
- </property>
-
- <property>
- <name>hawq_master_directory</name>
- <value>~/hawq-data-directory/masterdd</value>
- <description>The directory of hawq master.</description>
- </property>
-
- <property>
- <name>hawq_segment_directory</name>
- <value>~/hawq-data-directory/segmentdd</value>
- <description>The directory of hawq segment.</description>
- </property>
-
- <property>
- <name>hawq_master_temp_directory</name>
- <value>/tmp</value>
- <description>The temporary directory reserved for hawq master.</description>
- </property>
-
- <property>
- <name>hawq_segment_temp_directory</name>
- <value>/tmp</value>
- <description>The temporary directory reserved for hawq segment.</description>
- </property>
+ <property>
+ <name>hawq_master_address_host</name>
+ <value>localhost</value>
+ <description>The host name of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_address_port</name>
+ <value>5432</value>
+ <description>The port of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_standby_address_host</name>
+ <value>none</value>
+ <description>The host name of hawq standby master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_address_port</name>
+ <value>40000</value>
+ <description>The port of hawq segment.</description>
+ </property>
+
+ <property>
+ <name>hawq_dfs_url</name>
+ <value>localhost:8020/hawq_default</value>
+ <description>URL for accessing HDFS.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_directory</name>
+ <value>~/hawq-data-directory/masterdd</value>
+ <description>The directory of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_directory</name>
+ <value>~/hawq-data-directory/segmentdd</value>
+ <description>The directory of hawq segment.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_temp_directory</name>
+ <value>/tmp</value>
+ <description>The temporary directory reserved for hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_temp_directory</name>
+ <value>/tmp</value>
+ <description>The temporary directory reserved for hawq segment.</description>
+ </property>
- <!-- HAWQ resource manager parameters -->
- <property>
- <name>hawq_global_rm_type</name>
- <value>none</value>
- <description>The resource manager type to start for allocating resource.
- 'none' means hawq resource manager exclusively uses whole
- cluster; 'yarn' means hawq resource manager contacts YARN
- resource manager to negotiate resource.
- </description>
- </property>
-
- <property>
- <name>hawq_rm_memory_limit_perseg</name>
- <value>64GB</value>
- <description>The limit of memory usage in a hawq segment when
- hawq_global_rm_type is set 'none'.
- </description>
- </property>
-
- <property>
- <name>hawq_rm_nvcore_limit_perseg</name>
- <value>16</value>
- <description>The limit of virtual core usage in a hawq segment when
- hawq_global_rm_type is set 'none'.
- </description>
- </property>
-
- <property>
- <name>hawq_rm_yarn_address</name>
- <value>localhost:8032</value>
- <description>The address of YARN resource manager server.</description>
- </property>
-
- <property>
- <name>hawq_rm_yarn_scheduler_address</name>
- <value>localhost:8030</value>
- <description>The address of YARN scheduler server.</description>
- </property>
-
- <property>
- <name>hawq_rm_yarn_queue_name</name>
- <value>default</value>
- <description>The YARN queue name to register hawq resource manager.</description>
- </property>
-
- <property>
- <name>hawq_rm_yarn_app_name</name>
- <value>hawq</value>
- <description>The application name to register hawq resource manager in YARN.</description>
- </property>
-
+ <!-- HAWQ resource manager parameters -->
+ <property>
+ <name>hawq_global_rm_type</name>
+ <value>none</value>
+ <description>The resource manager type to start for allocating resource.
+ 'none' means hawq resource manager exclusively uses whole
+ cluster; 'yarn' means hawq resource manager contacts YARN
+ resource manager to negotiate resource.
+ </description>
+ </property>
+
+ <property>
+ <name>hawq_rm_memory_limit_perseg</name>
+ <value>64GB</value>
+ <description>The limit of memory usage in a hawq segment when
+ hawq_global_rm_type is set 'none'.
+ </description>
+ </property>
+
+ <property>
+ <name>hawq_rm_nvcore_limit_perseg</name>
+ <value>16</value>
+ <description>The limit of virtual core usage in a hawq segment when
+ hawq_global_rm_type is set 'none'.
+ </description>
+ </property>
+
+ <property>
+ <name>hawq_rm_yarn_address</name>
+ <value>localhost:8032</value>
+ <description>The address of YARN resource manager server.</description>
+ </property>
+
+ <property>
+ <name>hawq_rm_yarn_scheduler_address</name>
+ <value>localhost:8030</value>
+ <description>The address of YARN scheduler server.</description>
+ </property>
+
+ <property>
+ <name>hawq_rm_yarn_queue_name</name>
+ <value>default</value>
+ <description>The YARN queue name to register hawq resource manager.</description>
+ </property>
+
+ <property>
+ <name>hawq_rm_yarn_app_name</name>
+ <value>hawq</value>
+ <description>The application name to register hawq resource manager in YARN.</description>
+ </property>
+ <!-- HAWQ resource manager parameters end here. -->
+
+ <!-- HAWQ resource enforcement parameters -->
+ <property>
+ <name>hawq_re_cpu_enable</name>
+ <value>false</value>
+ <description>The control to enable/disable CPU resource enforcement.</description>
+ </property>
+
+ <property>
+ <name>hawq_re_cgroup_mount_point</name>
+ <value>/sys/fs/cgroup</value>
+ <description>The mount point of CGroup file system for resource enforcement.
+ For example, /sys/fs/cgroup/cpu/hawq for CPU sub-system.
+ </description>
+ </property>
+
+ <property>
+ <name>hawq_re_cgroup_hierarchy_name</name>
+ <value>hawq</value>
--- End diff --
Ambari currently sets this value as hadoop-yarn: https://github.com/Pivotal-Hadoop/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-site.xml#L169
Is this a problem ? Which value should be used ?
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq pull request: HAWQ-196: Refine GUCs in hawq-site.xm...
Posted by huor <gi...@git.apache.org>.
Github user huor closed the pull request at:
https://github.com/apache/incubator-hawq/pull/138
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq pull request: HAWQ-196: Refine GUCs in hawq-site.xm...
Posted by huor <gi...@git.apache.org>.
Github user huor commented on a diff in the pull request:
https://github.com/apache/incubator-hawq/pull/138#discussion_r46112116
--- Diff: src/backend/utils/misc/etc/template-hawq-site.xml ---
@@ -20,131 +20,133 @@ under the License.
-->
<configuration>
- <property>
- <name>hawq_master_address_host</name>
- <value>%master.host%</value>
- </property>
-
- <property>
- <name>hawq_master_address_port</name>
- <value>%master.port%</value>
- </property>
-
- <property>
- <name>hawq_standby_address_host</name>
- <value>%standby.host%</value>
- </property>
-
- <property>
- <name>hawq_segment_address_port</name>
- <value>%segment.port%</value>
- </property>
-
- <property>
- <name>hawq_dfs_url</name>
- <value>%namenode.host%:%namenode.port%/%hawq.file.space%</value>
- </property>
-
- <property>
- <name>hawq_master_directory</name>
- <value>%master.directory%</value>
- </property>
-
- <property>
- <name>hawq_segment_directory</name>
- <value>%segment.directory%</value>
- </property>
-
- <property>
- <name>hawq_master_temp_directory</name>
- <value>%master.temp.directory%</value>
- </property>
-
- <property>
- <name>hawq_segment_temp_directory</name>
- <value>%segment.temp.directory%</value>
- </property>
+ <property>
+ <name>hawq_master_address_host</name>
+ <value>%master.host%</value>
+ <description>The host name of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_address_port</name>
+ <value>%master.port%</value>
+ <description>The port of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_standby_address_host</name>
+ <value>%standby.host%</value>
+ <description>The host name of hawq standby master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_address_port</name>
+ <value>%segment.port%</value>
+ <description>The port of hawq segment.</description>
+ </property>
+
+ <property>
+ <name>hawq_dfs_url</name>
+ <value>%namenode.host%:%namenode.port%/%hawq.file.space%</value>
+ <description>URL for accessing HDFS.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_directory</name>
+ <value>%master.directory%</value>
+ <description>The directory of hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_directory</name>
+ <value>%segment.directory%</value>
+ <description>The directory of hawq segment.</description>
+ </property>
+
+ <property>
+ <name>hawq_master_temp_directory</name>
+ <value>%master.temp.directory%</value>
+ <description>The temporary directory reserved for hawq master.</description>
+ </property>
+
+ <property>
+ <name>hawq_segment_temp_directory</name>
+ <value>%segment.temp.directory%</value>
+ <description>The temporary directory reserved for hawq segment.</description>
+ </property>
- <!-- HAWQ resource manager parameters -->
- <property>
- <name>hawq_rm_yarn_address</name>
- <value>%master.host%:9980</value>
--- End diff --
To make the ports consistent in hawq-site.xml, template-hawq-site.xml and yarn-client.xml, will use below settings:
hawq_rm_yarn_address: %master.host%:8032
hawq_rm_yarn_scheduler_address: %master.host%:8030
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---