[
https://issues.apache.org/jira/browse/HAWQ-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086742#comment-15086742
]
zharui commented on HAWQ-323:
-----------------------------
The results of "select * from gp_segment_configuration" as follows
template1=# select * from gp_segment_configuration;
registration_order | role | status | port | hostname | address
--------------------+------+--------+-------+---------------+---------------
0 | m | u | 5432 | ws01.mzhen.cn | ws01.mzhen.cn
1 | p | u | 40000 | ws02.mzhen.cn | 192.168.3.3
There's no information of the segment which located on the same node with the
master instance.
And I am quite sure that network is not the reason of this issue because the
segment in trouble is located on the same node with the master.
> Cannot query when cluster include more than 1 segment
> -----------------------------------------------------
>
> Key: HAWQ-323
> URL: https://issues.apache.org/jira/browse/HAWQ-323
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Core, Resource Manager
> Affects Versions: 2.0.0-beta-incubating
> Reporter: zharui
> Assignee: Lei Chang
>
> The version I use is 2.0.0-beta-RC2. I can query data normally when cluster
> just have 1 segment. Once the cluster have more then 1 segments online, I
> cannot finish any query and being informed that "ERROR: failed to acquire
> resource from resource manager, 7 of 8 segments are unavailable
> (pquery.c:788)".
> I have read the segment logs and the source code about resource manager. I
> guess this issue is because of the communication failure between segment
> instance and resource manager server. I can find the logs of the segment
> connect to resource manager successfully such as "AsyncComm framework
> receives message 518 from FD5" and "Resource enforcer increases memory quota
> to: total memory quota=65536 MB, delta memory quota = 65536 MB", but the
> other online segments have no these log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)