[jira] [Commented] (HAWQ-871) HAWQ CHECK looking for wrong YARN HA parameters

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/HAWQ-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15354405#comment-15354405
 ] 

ASF GitHub Bot commented on HAWQ-871:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-hawq/pull/755


> HAWQ CHECK looking for wrong YARN HA parameters
> ---
>
> Key: HAWQ-871
> URL: https://issues.apache.org/jira/browse/HAWQ-871
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Command Line Tools
>Reporter: Radar Lei
>Assignee: Radar Lei
>
> When YARN HA is enabled in HDP, the following four params don't actually 
> exist. However, hawq check has been hard-coded to look for them, causing a 
> failure. 
> yarn.resourcemanager.address.rm1
> yarn.resourcemanager.address.rm2
> yarn.resourcemanager.scheduler.address.rm1
> yarn.resourcemanager.scheduler.address.rm2 
> **Correct params:**
> yarn.resourcemanager.hostname.rm1
> yarn.resourcemanager.hostname.rm2
> yarn.resourcemanager.scheduler.address (apparently, there is no rm1/rm2 
> specified for scheduler)



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

[jira] [Commented] (HAWQ-871) HAWQ CHECK looking for wrong YARN HA parameters

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/HAWQ-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15354397#comment-15354397
 ] 

ASF GitHub Bot commented on HAWQ-871:
-

Github user yaoj2 commented on the issue:

https://github.com/apache/incubator-hawq/pull/755
  
LGTM


> HAWQ CHECK looking for wrong YARN HA parameters
> ---
>
> Key: HAWQ-871
> URL: https://issues.apache.org/jira/browse/HAWQ-871
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Command Line Tools
>Reporter: Radar Lei
>Assignee: Radar Lei
>
> When YARN HA is enabled in HDP, the following four params don't actually 
> exist. However, hawq check has been hard-coded to look for them, causing a 
> failure. 
> yarn.resourcemanager.address.rm1
> yarn.resourcemanager.address.rm2
> yarn.resourcemanager.scheduler.address.rm1
> yarn.resourcemanager.scheduler.address.rm2 
> **Correct params:**
> yarn.resourcemanager.hostname.rm1
> yarn.resourcemanager.hostname.rm2
> yarn.resourcemanager.scheduler.address (apparently, there is no rm1/rm2 
> specified for scheduler)



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

[jira] [Commented] (HAWQ-871) HAWQ CHECK looking for wrong YARN HA parameters

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/HAWQ-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15354388#comment-15354388
 ] 

ASF GitHub Bot commented on HAWQ-871:
-

Github user linwen commented on the issue:

https://github.com/apache/incubator-hawq/pull/755
  
LGTM +1


> HAWQ CHECK looking for wrong YARN HA parameters
> ---
>
> Key: HAWQ-871
> URL: https://issues.apache.org/jira/browse/HAWQ-871
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Command Line Tools
>Reporter: Radar Lei
>Assignee: Radar Lei
>
> When YARN HA is enabled in HDP, the following four params don't actually 
> exist. However, hawq check has been hard-coded to look for them, causing a 
> failure. 
> yarn.resourcemanager.address.rm1
> yarn.resourcemanager.address.rm2
> yarn.resourcemanager.scheduler.address.rm1
> yarn.resourcemanager.scheduler.address.rm2 
> **Correct params:**
> yarn.resourcemanager.hostname.rm1
> yarn.resourcemanager.hostname.rm2
> yarn.resourcemanager.scheduler.address (apparently, there is no rm1/rm2 
> specified for scheduler)



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

[jira] [Commented] (HAWQ-871) HAWQ CHECK looking for wrong YARN HA parameters

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/HAWQ-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352384#comment-15352384
 ] 

ASF GitHub Bot commented on HAWQ-871:
-

GitHub user radarwave opened a pull request:

https://github.com/apache/incubator-hawq/pull/755

HAWQ-871. HAWQ CHECK looking for wrong YARN HA parameters

When YARN HA is enabled in HDP, the following four params don't actually 
exist. However, hawq check has been hard-coded to look for them, causing a 
failure. 
yarn.resourcemanager.address.rm1
yarn.resourcemanager.address.rm2
yarn.resourcemanager.scheduler.address.rm1
yarn.resourcemanager.scheduler.address.rm2
*Correct params:*
yarn.resourcemanager.hostname.rm1
yarn.resourcemanager.hostname.rm2
yarn.resourcemanager.scheduler.address (apparently, there is no rm1/rm2 
specified for scheduler)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/radarwave/incubator-hawq yarncheck

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-hawq/pull/755.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 #755


commit c3cdf2e8f9cdc5690576ef6f6f8e2ea59eb56f1d
Author: rlei 
Date:   2016-06-28T03:14:28Z

HAWQ-871. HAWQ CHECK looking for wrong YARN HA parameters




> HAWQ CHECK looking for wrong YARN HA parameters
> ---
>
> Key: HAWQ-871
> URL: https://issues.apache.org/jira/browse/HAWQ-871
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Command Line Tools
>Reporter: Radar Lei
>Assignee: Radar Lei
>
> When YARN HA is enabled in HDP, the following four params don't actually 
> exist. However, hawq check has been hard-coded to look for them, causing a 
> failure. 
> yarn.resourcemanager.address.rm1
> yarn.resourcemanager.address.rm2
> yarn.resourcemanager.scheduler.address.rm1
> yarn.resourcemanager.scheduler.address.rm2 
> **Correct params:**
> yarn.resourcemanager.hostname.rm1
> yarn.resourcemanager.hostname.rm2
> yarn.resourcemanager.scheduler.address (apparently, there is no rm1/rm2 
> specified for scheduler)



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