[ 
https://issues.apache.org/jira/browse/HAWQ-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Biao Wu updated HAWQ-930:
-------------------------
    Affects Version/s: 2.0.1.0-incubating

> HAWQ RM can not work
> --------------------
>
>                 Key: HAWQ-930
>                 URL: https://issues.apache.org/jira/browse/HAWQ-930
>             Project: Apache HAWQ
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.1.0-incubating
>            Reporter: Biao Wu
>            Assignee: Lei Chang
>
> The HAWQ Version is "HAWQ version 2.0.1.0 build dev".
> segment number:17
> Run `hawq restart cluster`,
> the pg_log:
> 2016-07-18 14:04:42.799428 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 151",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:43.799498 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 152",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:44.799569 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 153",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:45.799639 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 154",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:46.799709 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 155",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:47.799780 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 156",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:48.799850 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 157",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:49.799918 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 158",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:50.799988 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 159",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:51.800056 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 160",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:52.800126 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 161",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:53.800195 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 162",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:54.800263 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 163",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:55.800331 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 164",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:56.800399 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 165",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:57.800466 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 166",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:58.800535 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 167",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:04:59.800602 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 168",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:00.800669 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 169",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:01.800736 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 170",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:02.800803 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 171",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:03.800870 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 172",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:04.800938 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 173",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:05.801004 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 174",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:06.801073 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 175",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:07.801132 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 176",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:08.801224 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 177",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:09.801294 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 178",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:10.801367 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"LOG","00000","Wait for HAWQ 
> RM 179",,,,,,,0,,"resourcemanager.c",421,
> 2016-07-18 14:05:10.808694 
> CST,,,p136927,th-1736828640,,,,0,,,seg-10000,,,,,"FATAL","XX000","HAWQ RM can 
> not work. Please check HAWQ RM log. 
> (resourcemanager.c:433)",,,,,,,0,,"resourcemanager.c",433,"Stack trace:
> 1    0x8bd698 postgres errstart + 0x288
> 2    0x8bf41b postgres elog_finish + 0xab
> 3    0x959c30 postgres ResManagerProcessStartup + 0x210
> 4    0x78c6b8 postgres <symbol not found> + 0x78c6b8
> 5    0x790cee postgres <symbol not found> + 0x790cee
> 6    0x792ef9 postgres PostmasterMain + 0x759
> 7    0x6c935f postgres main + 0x50f
> 8    0x3e5661ed5d libc.so.6 __libc_start_main + 0xfd
> 9    0x49f719 postgres <symbol not found> + 0x49f719
> "
> Where can view the HAWQ RM log?
> hawq-site.xml :
> <configuration>
>         <property>
>                 <name>hawq_master_address_host</name>
>                 <value>masterip</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>adhoc/user/hawq_default</value>
>                 <description>URL for accessing HDFS.</description>
>         </property>
>         <property>
>                 <name>hawq_master_directory</name>
>                 <value>/data0/hawq/hawq-data-directory/masterdd</value>
>                 <description>The directory of hawq master.</description>
>         </property>
>         <property>
>                 <name>hawq_segment_directory</name>
>                 <value>/data0/hawq/hawq-data-directory/segmentdd</value>
>                 <description>The directory of hawq segment.</description>
>         </property>
>         <property>
>                 <name>hawq_master_temp_directory</name>
>                 <value>/data0/hawq/tmp</value>
>                 <description>The temporary directory reserved for hawq 
> master.</description>
>         </property>
>         <property>
>                 <name>hawq_segment_temp_directory</name>
>                 <value>/data0/hawq/tmp</value>
>                 <description>The temporary directory reserved for hawq 
> segment.</description>
>         </property>
>         <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>64G</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_stmt_vseg_memory</name>
>                 <value>128</value>
>     </property>
>         <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>
>                 <description>The name of the hierarchy to accomodate CGroup 
> directories/files for resource enforcement.
>            For example, /sys/fs/cgroup/cpu/hawq for CPU sub-system.
>     </description>
>         </property>
>         <property>
>                 <name>default_hash_table_bucket_number</name>
>                 <value>6</value>
>         </property>
> </configuration>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to