[jira] [Commented] (AMBARI-12910) Ambari Views Framework - need support for accessing RM running under HA

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718449#comment-14718449 ] 

Hadoop QA commented on AMBARI-12910:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12752943/AMBARI-12910_branch-2.1.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in contrib/views/hive contrib/views/utils.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/3664//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3664//console

This message is automatically generated.

> Ambari Views Framework - need support for accessing RM running under HA
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-12910
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12910
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.1.0
>            Reporter: DIPAYAN BHOWMICK
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-12910_branch-2.1.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Currently all views like the Tez view, YARN cluster view and YARN admin views that need to access YARN RMs running HA don't handle this scenario correctly.
> We need support in the views framework to enable this (note, if both RMs are running the RMs handle redirecting from the standby RM to the active one, but it has to be tested to work with the Ambari proxy. If one of the RMs is actually down, things are broken today).
> The Hive view might also need this.
> The following changes need to be considered:
> 1. The property that used to specify the RM location has to be extended to take a list of RM locations
> 2. The Ambari proxy has to cycle through the locations until it find one that works
> 3. For auto-created view instances, based on the cluster configuration, the multi-RM property in (1) has to be set correctly without user intervention



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