[ https://issues.apache.org/jira/browse/HAWQ-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329208#comment-15329208 ]
ASF GitHub Bot commented on HAWQ-715: ------------------------------------- GitHub user linwen opened a pull request: https://github.com/apache/incubator-hawq/pull/710 HAWQ-715. fix libyarn HA configuration bug please review, thanks! You can merge this pull request into a Git repository by running: $ git pull https://github.com/linwen/incubator-hawq hawq-715 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/710.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 #710 ---- commit a70af8c32119a767c1f8d7116ce327230503084f Author: Wen Lin <w...@pivotal.io> Date: 2016-06-14T09:45:39Z HAWQ-715. fix libyarn HA configuration bug ---- > hawq_rm_yarn_address doesn't take effect if libyarn is in HA mode > ----------------------------------------------------------------- > > Key: HAWQ-715 > URL: https://issues.apache.org/jira/browse/HAWQ-715 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn > Reporter: Lin Wen > Assignee: Lin Wen > > Currently if libyarn is in HA mode, > hawq_rm_yarn_address/hawq_rm_yarn_scheduler_address doesn't take effect but > still need users configure them in haw-site.xml, hawq will iteratively use > the hosts listed in property > yarn.resourcemanager.ha/yarn.resourcemanager.scheudler.ha in yarn-client.xml, > until hawq finds out an active YARN Resource Manager. > A better way is, > hawq_rm_yarn_address/hawq_rm_yarn_scheduler_address in hawq-site.xml are > required to be configured in HA mode, and will be considered as active RM to > connect firstly, if failed, then HAWQ will connect the other hosts listed in > yarn.resourcemanager.ha/yarn.resourcemanager.scheudler.ha -- This message was sent by Atlassian JIRA (v6.3.4#6332)