[jira] [Commented] (AMBARI-19527) Downgrade executes section if is not defined
[
https://issues.apache.org/jira/browse/AMBARI-19527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822724#comment-15822724
]
Hadoop QA commented on AMBARI-19527:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847476/AMBARI-19527_1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10058//console
This message is automatically generated.
> Downgrade executes section if is not defined
> --
>
> Key: AMBARI-19527
> URL: https://issues.apache.org/jira/browse/AMBARI-19527
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19527_1.patch
>
>
> When creating the initial upgrade packs, an effort was made to make them as
> least-verbose as possible. In that, we assumed that all tasks that occurred
> during an Upgrade would also occur on a Downgrade. That assumption led to
> some sneaky bugs that are difficult to troubleshoot.
> The real fix is to make the XSD enforce "sibling" elements, such that when
> PRE-UPGRADE tasks are defined, you can enforce that a PRE-DOWNGRADE element
> exist. Unfortunately, the JDK (even 1.8) doesn't support that version of XSD
> in JAXB.
> The interim solution was to use the afterUnmarshal secret sauce to validate
> that the elements exist. Allow a pre-downgrade or post-downgrade element to
> indicate that it can reuse the (pre-post)upgrade element definitions.
> Many of the changes here are in upgrade packs to add the new required
> elements, and the unit test that parses all upgrade packs passes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19276) Reset UI State does not clear ongoing wizard data
[ https://issues.apache.org/jira/browse/AMBARI-19276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-19276: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to 2.5 and trunk > Reset UI State does not clear ongoing wizard data > - > > Key: AMBARI-19276 > URL: https://issues.apache.org/jira/browse/AMBARI-19276 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-19276.patch > > > *STR:* > # Log into ambari-web and start "Add Service Wizard" > # Close the browser (simulate the scenario of browser crash) > # Log in from another credentials to ambari-web > # A message that add service wizard is ongoing will appear > # Got to ambari-web experimental page and reset ui state > *Expected:* The label should disappear showing for all users and the user who > started add service wizard should *not* renavigate to add service wizard on > logging in back > *Actual:* The labe ldoes not disappear for other users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19527) Downgrade executes section if is not defined
[ https://issues.apache.org/jira/browse/AMBARI-19527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-19527: --- Attachment: AMBARI-19527_1.patch > Downgrade executes section if is not defined > -- > > Key: AMBARI-19527 > URL: https://issues.apache.org/jira/browse/AMBARI-19527 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19527_1.patch > > > When creating the initial upgrade packs, an effort was made to make them as > least-verbose as possible. In that, we assumed that all tasks that occurred > during an Upgrade would also occur on a Downgrade. That assumption led to > some sneaky bugs that are difficult to troubleshoot. > The real fix is to make the XSD enforce "sibling" elements, such that when > PRE-UPGRADE tasks are defined, you can enforce that a PRE-DOWNGRADE element > exist. Unfortunately, the JDK (even 1.8) doesn't support that version of XSD > in JAXB. > The interim solution was to use the afterUnmarshal secret sauce to validate > that the elements exist. Allow a pre-downgrade or post-downgrade element to > indicate that it can reuse the (pre-post)upgrade element definitions. > Many of the changes here are in upgrade packs to add the new required > elements, and the unit test that parses all upgrade packs passes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-19527) Downgrade executes section if is not defined
[ https://issues.apache.org/jira/browse/AMBARI-19527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole reopened AMBARI-19527: > Downgrade executes section if is not defined > -- > > Key: AMBARI-19527 > URL: https://issues.apache.org/jira/browse/AMBARI-19527 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19527_1.patch > > > When creating the initial upgrade packs, an effort was made to make them as > least-verbose as possible. In that, we assumed that all tasks that occurred > during an Upgrade would also occur on a Downgrade. That assumption led to > some sneaky bugs that are difficult to troubleshoot. > The real fix is to make the XSD enforce "sibling" elements, such that when > PRE-UPGRADE tasks are defined, you can enforce that a PRE-DOWNGRADE element > exist. Unfortunately, the JDK (even 1.8) doesn't support that version of XSD > in JAXB. > The interim solution was to use the afterUnmarshal secret sauce to validate > that the elements exist. Allow a pre-downgrade or post-downgrade element to > indicate that it can reuse the (pre-post)upgrade element definitions. > Many of the changes here are in upgrade packs to add the new required > elements, and the unit test that parses all upgrade packs passes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19527) Downgrade executes section if is not defined
[ https://issues.apache.org/jira/browse/AMBARI-19527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-19527: --- Status: Patch Available (was: Reopened) > Downgrade executes section if is not defined > -- > > Key: AMBARI-19527 > URL: https://issues.apache.org/jira/browse/AMBARI-19527 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19527_1.patch > > > When creating the initial upgrade packs, an effort was made to make them as > least-verbose as possible. In that, we assumed that all tasks that occurred > during an Upgrade would also occur on a Downgrade. That assumption led to > some sneaky bugs that are difficult to troubleshoot. > The real fix is to make the XSD enforce "sibling" elements, such that when > PRE-UPGRADE tasks are defined, you can enforce that a PRE-DOWNGRADE element > exist. Unfortunately, the JDK (even 1.8) doesn't support that version of XSD > in JAXB. > The interim solution was to use the afterUnmarshal secret sauce to validate > that the elements exist. Allow a pre-downgrade or post-downgrade element to > indicate that it can reuse the (pre-post)upgrade element definitions. > Many of the changes here are in upgrade packs to add the new required > elements, and the unit test that parses all upgrade packs passes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19527) Downgrade executes section if is not defined
[ https://issues.apache.org/jira/browse/AMBARI-19527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-19527. Resolution: Fixed > Downgrade executes section if is not defined > -- > > Key: AMBARI-19527 > URL: https://issues.apache.org/jira/browse/AMBARI-19527 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > > When creating the initial upgrade packs, an effort was made to make them as > least-verbose as possible. In that, we assumed that all tasks that occurred > during an Upgrade would also occur on a Downgrade. That assumption led to > some sneaky bugs that are difficult to troubleshoot. > The real fix is to make the XSD enforce "sibling" elements, such that when > PRE-UPGRADE tasks are defined, you can enforce that a PRE-DOWNGRADE element > exist. Unfortunately, the JDK (even 1.8) doesn't support that version of XSD > in JAXB. > The interim solution was to use the afterUnmarshal secret sauce to validate > that the elements exist. Allow a pre-downgrade or post-downgrade element to > indicate that it can reuse the (pre-post)upgrade element definitions. > Many of the changes here are in upgrade packs to add the new required > elements, and the unit test that parses all upgrade packs passes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19522) Hive View 2.0: Saving worksheet as saved query
[
https://issues.apache.org/jira/browse/AMBARI-19522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822681#comment-15822681
]
Hadoop QA commented on AMBARI-19522:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847473/AMBARI-19522-v3_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:red}-1 core tests{color}. The test build failed in
contrib/views/hive20
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10057//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10057//console
This message is automatically generated.
> Hive View 2.0: Saving worksheet as saved query
> --
>
> Key: AMBARI-19522
> URL: https://issues.apache.org/jira/browse/AMBARI-19522
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19522-v3_trunk.patch
>
>
> - Saving worksheet as saved query.
> - Ability to delete the saved query
> - Ability to open the save query as worksheet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19522) Hive View 2.0: Saving worksheet as saved query
[ https://issues.apache.org/jira/browse/AMBARI-19522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19522: - Attachment: AMBARI-19522-v3_trunk.patch > Hive View 2.0: Saving worksheet as saved query > -- > > Key: AMBARI-19522 > URL: https://issues.apache.org/jira/browse/AMBARI-19522 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-19522-v3_trunk.patch > > > - Saving worksheet as saved query. > - Ability to delete the saved query > - Ability to open the save query as worksheet. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19522) Hive View 2.0: Saving worksheet as saved query
[ https://issues.apache.org/jira/browse/AMBARI-19522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19522: - Attachment: (was: AMBARI-19522-v2_trunk.patch) > Hive View 2.0: Saving worksheet as saved query > -- > > Key: AMBARI-19522 > URL: https://issues.apache.org/jira/browse/AMBARI-19522 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > > - Saving worksheet as saved query. > - Ability to delete the saved query > - Ability to open the save query as worksheet. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19540) Possibly too frequent calls to stack advisor as user changes sliders
[
https://issues.apache.org/jira/browse/AMBARI-19540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822637#comment-15822637
]
Hadoop QA commented on AMBARI-19540:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847453/AMBARI-19540.v1.branch-2.5.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10056//console
This message is automatically generated.
> Possibly too frequent calls to stack advisor as user changes sliders
>
>
> Key: AMBARI-19540
> URL: https://issues.apache.org/jira/browse/AMBARI-19540
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19540.v0.patch, AMBARI-19540.v1.branch-2.5.patch
>
>
> As you can see 3 calls are made while changing from 1024 to 2048 and
> similarly 3 calls when coming back to 1024.
> Beyond performance concern, multiple calls have a functional issue. The call
> includes previous value of the changed property - see the values. I would
> have expected the old value to be the value that was the original/saved
> value. However, it is wherever UI makes the stack advisor calls.
> [root@smq1-1 stack-recommendations]# find . -name services.json | xargs grep
> -A 3 changed
> ./55/services.json: "changed-configurations" : [ {
> ./55/services.json-"type" : "yarn-site",
> ./55/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./55/services.json-"old_value" : "1024"
> ./56/services.json: "changed-configurations" : [ {
> ./56/services.json-"type" : "yarn-site",
> ./56/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./56/services.json-"old_value" : "1280"
> ./57/services.json: "changed-configurations" : [ {
> ./57/services.json-"type" : "yarn-site",
> ./57/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./57/services.json-"old_value" : "1792"
> ./58/services.json: "changed-configurations" : [ {
> ./58/services.json-"type" : "yarn-site",
> ./58/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./58/services.json-"old_value" : "2048"
> ./59/services.json: "changed-configurations" : [ {
> ./59/services.json-"type" : "yarn-site",
> ./59/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./59/services.json-"old_value" : "1792"
> ./60/services.json: "changed-configurations" : [ {
> ./60/services.json-"type" : "yarn-site",
> ./60/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./60/services.json-"old_value" : "1280"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS
[
https://issues.apache.org/jira/browse/AMBARI-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822636#comment-15822636
]
Hadoop QA commented on AMBARI-19097:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847464/AMBARI-19097.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10055//console
This message is automatically generated.
> HDP 3.0 TP - create Service Advisor for HDFS
>
>
> Key: AMBARI-19097
> URL: https://issues.apache.org/jira/browse/AMBARI-19097
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19097.patch
>
>
> Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten
> from HDP 2.0.6 through HDP 2.6
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19543) Re-order rows in HDFS-TopN Grafana Dashboard
[ https://issues.apache.org/jira/browse/AMBARI-19543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822621#comment-15822621 ] Yusaku Sako commented on AMBARI-19543: -- +1'd on ReviewBoard. Committed to trunk and branch-2.5. > Re-order rows in HDFS-TopN Grafana Dashboard > > > Key: AMBARI-19543 > URL: https://issues.apache.org/jira/browse/AMBARI-19543 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19543.v0.patch > > > Move the first row of graphs to the last in HDFS TopN Grafana Dashboard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19543) Re-order rows in HDFS-TopN Grafana Dashboard
[ https://issues.apache.org/jira/browse/AMBARI-19543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-19543: - Issue Type: Task (was: Bug) > Re-order rows in HDFS-TopN Grafana Dashboard > > > Key: AMBARI-19543 > URL: https://issues.apache.org/jira/browse/AMBARI-19543 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19543.v0.patch > > > Move the first row of graphs to the last in HDFS TopN Grafana Dashboard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19543) Re-order rows in HDFS-TopN Grafana Dashboard
[ https://issues.apache.org/jira/browse/AMBARI-19543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-19543: - Resolution: Fixed Status: Resolved (was: Patch Available) > Re-order rows in HDFS-TopN Grafana Dashboard > > > Key: AMBARI-19543 > URL: https://issues.apache.org/jira/browse/AMBARI-19543 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19543.v0.patch > > > Move the first row of graphs to the last in HDFS TopN Grafana Dashboard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS
[ https://issues.apache.org/jira/browse/AMBARI-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19097: - Attachment: AMBARI-19097.patch > HDP 3.0 TP - create Service Advisor for HDFS > > > Key: AMBARI-19097 > URL: https://issues.apache.org/jira/browse/AMBARI-19097 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19097.patch > > > Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS
[ https://issues.apache.org/jira/browse/AMBARI-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19097: - Status: Patch Available (was: Open) > HDP 3.0 TP - create Service Advisor for HDFS > > > Key: AMBARI-19097 > URL: https://issues.apache.org/jira/browse/AMBARI-19097 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19097.patch > > > Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (AMBARI-19544) HDP 3.0 Tech Preview in Ambari 3.0
[ https://issues.apache.org/jira/browse/AMBARI-19544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez deleted AMBARI-19544: - > HDP 3.0 Tech Preview in Ambari 3.0 > -- > > Key: AMBARI-19544 > URL: https://issues.apache.org/jira/browse/AMBARI-19544 > Project: Ambari > Issue Type: Epic >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > > HDP 3.0 Tech Preview for Ambari 2.5 in January > Services: HDFS, YARN, MR, ZK > Plan: > # HDP 3.0 bits for Hadoop core > # New stack definition in Ambari > # Flatten configs, metrics, widgets, kerberos for the services listed above > # Break up Stack Advisor into Service Advisor per service listed above > # Testing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19544) HDP 3.0 Tech Preview in Ambari 3.0
Alejandro Fernandez created AMBARI-19544: Summary: HDP 3.0 Tech Preview in Ambari 3.0 Key: AMBARI-19544 URL: https://issues.apache.org/jira/browse/AMBARI-19544 Project: Ambari Issue Type: Epic Components: stacks Affects Versions: 3.0.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 3.0.0 HDP 3.0 Tech Preview for Ambari 2.5 in January Services: HDFS, YARN, MR, ZK Plan: # HDP 3.0 bits for Hadoop core # New stack definition in Ambari # Flatten configs, metrics, widgets, kerberos for the services listed above # Break up Stack Advisor into Service Advisor per service listed above # Testing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19543) Re-order rows in HDFS-TopN Grafana Dashboard
[ https://issues.apache.org/jira/browse/AMBARI-19543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19543: Status: Patch Available (was: In Progress) > Re-order rows in HDFS-TopN Grafana Dashboard > > > Key: AMBARI-19543 > URL: https://issues.apache.org/jira/browse/AMBARI-19543 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19543.v0.patch > > > Move the first row of graphs to the last in HDFS TopN Grafana Dashboard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19543) Re-order rows in HDFS-TopN Grafana Dashboard
[ https://issues.apache.org/jira/browse/AMBARI-19543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19543: Attachment: AMBARI-19543.v0.patch > Re-order rows in HDFS-TopN Grafana Dashboard > > > Key: AMBARI-19543 > URL: https://issues.apache.org/jira/browse/AMBARI-19543 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19543.v0.patch > > > Move the first row of graphs to the last in HDFS TopN Grafana Dashboard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19543) Re-order rows in HDFS-TopN Grafana Dashboard
Vivek Ratnavel Subramanian created AMBARI-19543: --- Summary: Re-order rows in HDFS-TopN Grafana Dashboard Key: AMBARI-19543 URL: https://issues.apache.org/jira/browse/AMBARI-19543 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.5.0 Move the first row of graphs to the last in HDFS TopN Grafana Dashboard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19540) Possibly too frequent calls to stack advisor as user changes sliders
[
https://issues.apache.org/jira/browse/AMBARI-19540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822578#comment-15822578
]
Hadoop QA commented on AMBARI-19540:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847453/AMBARI-19540.v1.branch-2.5.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10054//console
This message is automatically generated.
> Possibly too frequent calls to stack advisor as user changes sliders
>
>
> Key: AMBARI-19540
> URL: https://issues.apache.org/jira/browse/AMBARI-19540
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19540.v0.patch, AMBARI-19540.v1.branch-2.5.patch
>
>
> As you can see 3 calls are made while changing from 1024 to 2048 and
> similarly 3 calls when coming back to 1024.
> Beyond performance concern, multiple calls have a functional issue. The call
> includes previous value of the changed property - see the values. I would
> have expected the old value to be the value that was the original/saved
> value. However, it is wherever UI makes the stack advisor calls.
> [root@smq1-1 stack-recommendations]# find . -name services.json | xargs grep
> -A 3 changed
> ./55/services.json: "changed-configurations" : [ {
> ./55/services.json-"type" : "yarn-site",
> ./55/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./55/services.json-"old_value" : "1024"
> ./56/services.json: "changed-configurations" : [ {
> ./56/services.json-"type" : "yarn-site",
> ./56/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./56/services.json-"old_value" : "1280"
> ./57/services.json: "changed-configurations" : [ {
> ./57/services.json-"type" : "yarn-site",
> ./57/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./57/services.json-"old_value" : "1792"
> ./58/services.json: "changed-configurations" : [ {
> ./58/services.json-"type" : "yarn-site",
> ./58/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./58/services.json-"old_value" : "2048"
> ./59/services.json: "changed-configurations" : [ {
> ./59/services.json-"type" : "yarn-site",
> ./59/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./59/services.json-"old_value" : "1792"
> ./60/services.json: "changed-configurations" : [ {
> ./60/services.json-"type" : "yarn-site",
> ./60/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./60/services.json-"old_value" : "1280"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19540) Possibly too frequent calls to stack advisor as user changes sliders
[
https://issues.apache.org/jira/browse/AMBARI-19540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated AMBARI-19540:
Attachment: AMBARI-19540.v1.branch-2.5.patch
> Possibly too frequent calls to stack advisor as user changes sliders
>
>
> Key: AMBARI-19540
> URL: https://issues.apache.org/jira/browse/AMBARI-19540
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19540.v0.patch, AMBARI-19540.v1.branch-2.5.patch
>
>
> As you can see 3 calls are made while changing from 1024 to 2048 and
> similarly 3 calls when coming back to 1024.
> Beyond performance concern, multiple calls have a functional issue. The call
> includes previous value of the changed property - see the values. I would
> have expected the old value to be the value that was the original/saved
> value. However, it is wherever UI makes the stack advisor calls.
> [root@smq1-1 stack-recommendations]# find . -name services.json | xargs grep
> -A 3 changed
> ./55/services.json: "changed-configurations" : [ {
> ./55/services.json-"type" : "yarn-site",
> ./55/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./55/services.json-"old_value" : "1024"
> ./56/services.json: "changed-configurations" : [ {
> ./56/services.json-"type" : "yarn-site",
> ./56/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./56/services.json-"old_value" : "1280"
> ./57/services.json: "changed-configurations" : [ {
> ./57/services.json-"type" : "yarn-site",
> ./57/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./57/services.json-"old_value" : "1792"
> ./58/services.json: "changed-configurations" : [ {
> ./58/services.json-"type" : "yarn-site",
> ./58/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./58/services.json-"old_value" : "2048"
> ./59/services.json: "changed-configurations" : [ {
> ./59/services.json-"type" : "yarn-site",
> ./59/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./59/services.json-"old_value" : "1792"
> ./60/services.json: "changed-configurations" : [ {
> ./60/services.json-"type" : "yarn-site",
> ./60/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./60/services.json-"old_value" : "1280"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19539) Spark2 Service check fails on WE enabled cluster
[
https://issues.apache.org/jira/browse/AMBARI-19539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822557#comment-15822557
]
Hadoop QA commented on AMBARI-19539:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847434/AMBARI-19539.1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10052//console
This message is automatically generated.
> Spark2 Service check fails on WE enabled cluster
>
>
> Key: AMBARI-19539
> URL: https://issues.apache.org/jira/browse/AMBARI-19539
> Project: Ambari
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Bikas Saha
> Attachments: AMBARI-19539.1.patch
>
>
> Spark2 service check tries to connect to spark2 History server using http
> port.
> When Wire Encryption is enabled, spark2 service check should use https port
> to connect to Spark2 HS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19338) AM sizing for LLAP - min container size changes
[ https://issues.apache.org/jira/browse/AMBARI-19338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822551#comment-15822551 ] Siddharth Seth commented on AMBARI-19338: - More comments on the code review. Please don't commit yet. > AM sizing for LLAP - min container size changes > --- > > Key: AMBARI-19338 > URL: https://issues.apache.org/jira/browse/AMBARI-19338 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Dmytro Sen >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19338_2.patch, AMBARI-19338_3.patch > > > Currently, AMs are sized too big for LLAP (especially with small setups). > Better defaults are needed, but min container size has to change for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19542) Cannot change group/user privileges in list view if the user has VIEW.USER privilege
[
https://issues.apache.org/jira/browse/AMBARI-19542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeeta Ravindran updated AMBARI-19542:
Attachment: AMBARI-19542.patch
> Cannot change group/user privileges in list view if the user has VIEW.USER
> privilege
>
>
> Key: AMBARI-19542
> URL: https://issues.apache.org/jira/browse/AMBARI-19542
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19542.patch
>
>
> 1. Create a view for e.g. Capacity Scheduler view and grant a group / user
> permissions for the view.
> 2. Go to Roles list view. Try to assign the group / user a different role via
> the List view.
> There is no response in the UI and the role is not updated. On the browser
> console, the following erorr can be seen.
> DELETE
> http://9.30.56.80:8081/api/v1/clusters/C1/privileges?PrivilegeInfo/privilege_id.in(416)
> 500 (Internal Server Error)
> In the ambari-server.log, the following exception is seen:
> Caused by: org.apache.ambari.server.AmbariException: Can't remove VIEW
> permission from a CAPACITY-SCHEDULER{1.0.0} resource.
> at
> org.apache.ambari.server.controller.internal.PrivilegeResourceProvider$2.invoke(PrivilegeResourceProvider.java:460)
> This does not happen when roles are assigned via the Block view.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19542) Cannot change group/user privileges in list view if the user has VIEW.USER privilege
[
https://issues.apache.org/jira/browse/AMBARI-19542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeeta Ravindran updated AMBARI-19542:
Fix Version/s: 2.5.0
Status: Patch Available (was: In Progress)
> Cannot change group/user privileges in list view if the user has VIEW.USER
> privilege
>
>
> Key: AMBARI-19542
> URL: https://issues.apache.org/jira/browse/AMBARI-19542
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19542.patch
>
>
> 1. Create a view for e.g. Capacity Scheduler view and grant a group / user
> permissions for the view.
> 2. Go to Roles list view. Try to assign the group / user a different role via
> the List view.
> There is no response in the UI and the role is not updated. On the browser
> console, the following erorr can be seen.
> DELETE
> http://9.30.56.80:8081/api/v1/clusters/C1/privileges?PrivilegeInfo/privilege_id.in(416)
> 500 (Internal Server Error)
> In the ambari-server.log, the following exception is seen:
> Caused by: org.apache.ambari.server.AmbariException: Can't remove VIEW
> permission from a CAPACITY-SCHEDULER{1.0.0} resource.
> at
> org.apache.ambari.server.controller.internal.PrivilegeResourceProvider$2.invoke(PrivilegeResourceProvider.java:460)
> This does not happen when roles are assigned via the Block view.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19542) Cannot change group/user privileges in list view if the user has VIEW.USER privilege
Sangeeta Ravindran created AMBARI-19542:
---
Summary: Cannot change group/user privileges in list view if the
user has VIEW.USER privilege
Key: AMBARI-19542
URL: https://issues.apache.org/jira/browse/AMBARI-19542
Project: Ambari
Issue Type: Bug
Components: ambari-admin
Affects Versions: 2.5.0
Reporter: Sangeeta Ravindran
Assignee: Sangeeta Ravindran
Priority: Minor
1. Create a view for e.g. Capacity Scheduler view and grant a group / user
permissions for the view.
2. Go to Roles list view. Try to assign the group / user a different role via
the List view.
There is no response in the UI and the role is not updated. On the browser
console, the following erorr can be seen.
DELETE
http://9.30.56.80:8081/api/v1/clusters/C1/privileges?PrivilegeInfo/privilege_id.in(416)
500 (Internal Server Error)
In the ambari-server.log, the following exception is seen:
Caused by: org.apache.ambari.server.AmbariException: Can't remove VIEW
permission from a CAPACITY-SCHEDULER{1.0.0} resource.
at
org.apache.ambari.server.controller.internal.PrivilegeResourceProvider$2.invoke(PrivilegeResourceProvider.java:460)
This does not happen when roles are assigned via the Block view.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19541) Add log rotation settings - handle HDP upgrade scenario
Madhuvanthi Radhakrishnan created AMBARI-19541: -- Summary: Add log rotation settings - handle HDP upgrade scenario Key: AMBARI-19541 URL: https://issues.apache.org/jira/browse/AMBARI-19541 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan This jira will have the upgrade pack work for the following services YARN HDFS HBASE ZOOKEEPER OOZIE FALCON ATLAS RANGER RANGER-KMS KAFKA KNOX -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19540) Possibly too frequent calls to stack advisor as user changes sliders
[
https://issues.apache.org/jira/browse/AMBARI-19540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated AMBARI-19540:
Attachment: AMBARI-19540.v0.patch
> Possibly too frequent calls to stack advisor as user changes sliders
>
>
> Key: AMBARI-19540
> URL: https://issues.apache.org/jira/browse/AMBARI-19540
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19540.v0.patch
>
>
> As you can see 3 calls are made while changing from 1024 to 2048 and
> similarly 3 calls when coming back to 1024.
> Beyond performance concern, multiple calls have a functional issue. The call
> includes previous value of the changed property - see the values. I would
> have expected the old value to be the value that was the original/saved
> value. However, it is wherever UI makes the stack advisor calls.
> [root@smq1-1 stack-recommendations]# find . -name services.json | xargs grep
> -A 3 changed
> ./55/services.json: "changed-configurations" : [ {
> ./55/services.json-"type" : "yarn-site",
> ./55/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./55/services.json-"old_value" : "1024"
> ./56/services.json: "changed-configurations" : [ {
> ./56/services.json-"type" : "yarn-site",
> ./56/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./56/services.json-"old_value" : "1280"
> ./57/services.json: "changed-configurations" : [ {
> ./57/services.json-"type" : "yarn-site",
> ./57/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./57/services.json-"old_value" : "1792"
> ./58/services.json: "changed-configurations" : [ {
> ./58/services.json-"type" : "yarn-site",
> ./58/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./58/services.json-"old_value" : "2048"
> ./59/services.json: "changed-configurations" : [ {
> ./59/services.json-"type" : "yarn-site",
> ./59/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./59/services.json-"old_value" : "1792"
> ./60/services.json: "changed-configurations" : [ {
> ./60/services.json-"type" : "yarn-site",
> ./60/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./60/services.json-"old_value" : "1280"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19540) Possibly too frequent calls to stack advisor as user changes sliders
[
https://issues.apache.org/jira/browse/AMBARI-19540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated AMBARI-19540:
Status: Patch Available (was: In Progress)
> Possibly too frequent calls to stack advisor as user changes sliders
>
>
> Key: AMBARI-19540
> URL: https://issues.apache.org/jira/browse/AMBARI-19540
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19540.v0.patch
>
>
> As you can see 3 calls are made while changing from 1024 to 2048 and
> similarly 3 calls when coming back to 1024.
> Beyond performance concern, multiple calls have a functional issue. The call
> includes previous value of the changed property - see the values. I would
> have expected the old value to be the value that was the original/saved
> value. However, it is wherever UI makes the stack advisor calls.
> [root@smq1-1 stack-recommendations]# find . -name services.json | xargs grep
> -A 3 changed
> ./55/services.json: "changed-configurations" : [ {
> ./55/services.json-"type" : "yarn-site",
> ./55/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./55/services.json-"old_value" : "1024"
> ./56/services.json: "changed-configurations" : [ {
> ./56/services.json-"type" : "yarn-site",
> ./56/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./56/services.json-"old_value" : "1280"
> ./57/services.json: "changed-configurations" : [ {
> ./57/services.json-"type" : "yarn-site",
> ./57/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./57/services.json-"old_value" : "1792"
> ./58/services.json: "changed-configurations" : [ {
> ./58/services.json-"type" : "yarn-site",
> ./58/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./58/services.json-"old_value" : "2048"
> ./59/services.json: "changed-configurations" : [ {
> ./59/services.json-"type" : "yarn-site",
> ./59/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./59/services.json-"old_value" : "1792"
> ./60/services.json: "changed-configurations" : [ {
> ./60/services.json-"type" : "yarn-site",
> ./60/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./60/services.json-"old_value" : "1280"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19539) Spark2 Service check fails on WE enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-19539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19539: --- Reporter: Yesha Vora (was: Bikas Saha) > Spark2 Service check fails on WE enabled cluster > > > Key: AMBARI-19539 > URL: https://issues.apache.org/jira/browse/AMBARI-19539 > Project: Ambari > Issue Type: Bug >Reporter: Yesha Vora >Assignee: Bikas Saha > Attachments: AMBARI-19539.1.patch > > > Spark2 service check tries to connect to spark2 History server using http > port. > When Wire Encryption is enabled, spark2 service check should use https port > to connect to Spark2 HS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19540) Possibly too frequent calls to stack advisor as user changes sliders
Vivek Ratnavel Subramanian created AMBARI-19540:
---
Summary: Possibly too frequent calls to stack advisor as user
changes sliders
Key: AMBARI-19540
URL: https://issues.apache.org/jira/browse/AMBARI-19540
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.0
Reporter: Vivek Ratnavel Subramanian
Assignee: Vivek Ratnavel Subramanian
Fix For: 2.5.0
As you can see 3 calls are made while changing from 1024 to 2048 and similarly
3 calls when coming back to 1024.
Beyond performance concern, multiple calls have a functional issue. The call
includes previous value of the changed property - see the values. I would have
expected the old value to be the value that was the original/saved value.
However, it is wherever UI makes the stack advisor calls.
[root@smq1-1 stack-recommendations]# find . -name services.json | xargs grep -A
3 changed
./55/services.json: "changed-configurations" : [ {
./55/services.json-"type" : "yarn-site",
./55/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
./55/services.json-"old_value" : "1024"
./56/services.json: "changed-configurations" : [ {
./56/services.json-"type" : "yarn-site",
./56/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
./56/services.json-"old_value" : "1280"
./57/services.json: "changed-configurations" : [ {
./57/services.json-"type" : "yarn-site",
./57/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
./57/services.json-"old_value" : "1792"
./58/services.json: "changed-configurations" : [ {
./58/services.json-"type" : "yarn-site",
./58/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
./58/services.json-"old_value" : "2048"
./59/services.json: "changed-configurations" : [ {
./59/services.json-"type" : "yarn-site",
./59/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
./59/services.json-"old_value" : "1792"
./60/services.json: "changed-configurations" : [ {
./60/services.json-"type" : "yarn-site",
./60/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
./60/services.json-"old_value" : "1280"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19538) Add log rotation settings to Hive, Druid, Storm
[
https://issues.apache.org/jira/browse/AMBARI-19538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822494#comment-15822494
]
Hadoop QA commented on AMBARI-19538:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847425/AMBARI-19538.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 4 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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10051//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10051//console
This message is automatically generated.
> Add log rotation settings to Hive, Druid, Storm
> ---
>
> Key: AMBARI-19538
> URL: https://issues.apache.org/jira/browse/AMBARI-19538
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Attachments: AMBARI-19538.patch
>
>
> This jira is for log4j rotation settings for hive, druid and storm
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-19539) Spark2 Service check fails on WE enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-19539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822474#comment-15822474 ] Bikas Saha edited comment on AMBARI-19539 at 1/13/17 10:50 PM: --- [~sumitmohanty] I think this patch should fix it. https://reviews.apache.org/r/55526 was (Author: bikassaha): [~sumitmohanty] I think this patch should fix it. > Spark2 Service check fails on WE enabled cluster > > > Key: AMBARI-19539 > URL: https://issues.apache.org/jira/browse/AMBARI-19539 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: AMBARI-19539.1.patch > > > Spark2 service check tries to connect to spark2 History server using http > port. > When Wire Encryption is enabled, spark2 service check should use https port > to connect to Spark2 HS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
[ https://issues.apache.org/jira/browse/AMBARI-19390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822471#comment-15822471 ] Aravindan Vijayan commented on AMBARI-19390: Manually tested Unit tests passed. Got +1 in Reviewboard. Pushed to branch-2.5 and trunk. > AMS Collector works in HTTP mode after setting > ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY > - > > Key: AMBARI-19390 > URL: https://issues.apache.org/jira/browse/AMBARI-19390 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19390.patch > > > AMS Collector works in HTTP mode after setting > ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19539) Spark2 Service check fails on WE enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-19539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822474#comment-15822474 ] Bikas Saha commented on AMBARI-19539: - [~sumitmohanty] I think this patch should fix it. > Spark2 Service check fails on WE enabled cluster > > > Key: AMBARI-19539 > URL: https://issues.apache.org/jira/browse/AMBARI-19539 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: AMBARI-19539.1.patch > > > Spark2 service check tries to connect to spark2 History server using http > port. > When Wire Encryption is enabled, spark2 service check should use https port > to connect to Spark2 HS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19539) Spark2 Service check fails on WE enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-19539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated AMBARI-19539: Status: Patch Available (was: Open) > Spark2 Service check fails on WE enabled cluster > > > Key: AMBARI-19539 > URL: https://issues.apache.org/jira/browse/AMBARI-19539 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: AMBARI-19539.1.patch > > > Spark2 service check tries to connect to spark2 History server using http > port. > When Wire Encryption is enabled, spark2 service check should use https port > to connect to Spark2 HS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
[ https://issues.apache.org/jira/browse/AMBARI-19390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19390: --- Resolution: Fixed Status: Resolved (was: Patch Available) > AMS Collector works in HTTP mode after setting > ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY > - > > Key: AMBARI-19390 > URL: https://issues.apache.org/jira/browse/AMBARI-19390 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19390.patch > > > AMS Collector works in HTTP mode after setting > ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19539) Spark2 Service check fails on WE enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-19539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated AMBARI-19539: Attachment: AMBARI-19539.1.patch > Spark2 Service check fails on WE enabled cluster > > > Key: AMBARI-19539 > URL: https://issues.apache.org/jira/browse/AMBARI-19539 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Attachments: AMBARI-19539.1.patch > > > Spark2 service check tries to connect to spark2 History server using http > port. > When Wire Encryption is enabled, spark2 service check should use https port > to connect to Spark2 HS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
[ https://issues.apache.org/jira/browse/AMBARI-19390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19390: --- Status: Patch Available (was: Open) > AMS Collector works in HTTP mode after setting > ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY > - > > Key: AMBARI-19390 > URL: https://issues.apache.org/jira/browse/AMBARI-19390 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19390.patch > > > AMS Collector works in HTTP mode after setting > ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
[ https://issues.apache.org/jira/browse/AMBARI-19390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-19390: -- Assignee: Aravindan Vijayan > AMS Collector works in HTTP mode after setting > ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY > - > > Key: AMBARI-19390 > URL: https://issues.apache.org/jira/browse/AMBARI-19390 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19390.patch > > > AMS Collector works in HTTP mode after setting > ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
[ https://issues.apache.org/jira/browse/AMBARI-19390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19390: --- Attachment: AMBARI-19390.patch > AMS Collector works in HTTP mode after setting > ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY > - > > Key: AMBARI-19390 > URL: https://issues.apache.org/jira/browse/AMBARI-19390 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19390.patch > > > AMS Collector works in HTTP mode after setting > ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19539) Spark2 Service check fails on WE enabled cluster
Bikas Saha created AMBARI-19539: --- Summary: Spark2 Service check fails on WE enabled cluster Key: AMBARI-19539 URL: https://issues.apache.org/jira/browse/AMBARI-19539 Project: Ambari Issue Type: Bug Reporter: Bikas Saha Assignee: Bikas Saha Spark2 service check tries to connect to spark2 History server using http port. When Wire Encryption is enabled, spark2 service check should use https port to connect to Spark2 HS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-15936) Cluster CPU widget is wrong
[ https://issues.apache.org/jira/browse/AMBARI-15936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-15936. Resolution: Invalid > Cluster CPU widget is wrong > --- > > Key: AMBARI-15936 > URL: https://issues.apache.org/jira/browse/AMBARI-15936 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: Cyril Scetbon >Assignee: Aravindan Vijayan >Priority: Minor > > I'm using HDP 2.4 to run Yarn applications. When I look at my current > NodeManagers CPU, the consumption is low. However on Ambari interface, the > default "Cluster CPU“ widget displays a high CPU (91%). When I check the > expression used, it uses cpu_idle._sum (see > http://picpaste.com/Screen_Shot_2016-04-16_at_22.13.43-gS4XsIGb.png) which is > a metric that I can't find if I try to create a new widget > http://picpaste.com/Screen_Shot_2016-04-16_at_22.09.56-DJK3v4Wd.png > Can it be the reason why the CPU consumption displayed is totally wrong ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18915) Update AMS pom to use Apache hbase,hadoop,phoenix tarballs
[ https://issues.apache.org/jira/browse/AMBARI-18915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18915: --- Fix Version/s: (was: 2.5.0) 3.0.0 > Update AMS pom to use Apache hbase,hadoop,phoenix tarballs > -- > > Key: AMBARI-18915 > URL: https://issues.apache.org/jira/browse/AMBARI-18915 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18915.patch > > > Ambari Metrics Service have a specific dependency on HDP tarballs. Ideally > this dependency is not desired. Apache should be self sufficient without > dependencies on a particular distribution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-17596. Resolution: Fixed > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch, AMBARI-17596-addendum.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822444#comment-15822444 ] Aravindan Vijayan commented on AMBARI-17596: Pushed to branch-2.5 and trunk. > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch, AMBARI-17596-addendum.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18915) Update AMS pom to use Apache hbase,hadoop,phoenix tarballs
[ https://issues.apache.org/jira/browse/AMBARI-18915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18915: --- Affects Version/s: (was: 2.5.0) 3.0.0 > Update AMS pom to use Apache hbase,hadoop,phoenix tarballs > -- > > Key: AMBARI-18915 > URL: https://issues.apache.org/jira/browse/AMBARI-18915 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18915.patch > > > Ambari Metrics Service have a specific dependency on HDP tarballs. Ideally > this dependency is not desired. Apache should be self sufficient without > dependencies on a particular distribution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17596: --- Attachment: AMBARI-17596-addendum.patch > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch, AMBARI-17596-addendum.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17596: --- Attachment: (was: AMBARI-17596-addendum.patch) > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822439#comment-15822439 ] Siddharth Wagle commented on AMBARI-17596: -- +1 LGTM > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch, AMBARI-17596-addendum.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17596: --- Attachment: AMBARI-17596-addendum.patch Adding small patch for changes in metrics.properties > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch, AMBARI-17596-addendum.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reopened AMBARI-17596: > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch, AMBARI-17596-addendum.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19537) Provide default value for yarn leveldb state store path
[
https://issues.apache.org/jira/browse/AMBARI-19537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822428#comment-15822428
]
Hadoop QA commented on AMBARI-19537:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847393/AMBARI-19537.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10050//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10050//console
This message is automatically generated.
> Provide default value for yarn leveldb state store path
> ---
>
> Key: AMBARI-19537
> URL: https://issues.apache.org/jira/browse/AMBARI-19537
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19537.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19538) Add log rotation settings to Hive, Druid, Storm
[ https://issues.apache.org/jira/browse/AMBARI-19538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-19538: --- Status: Patch Available (was: Open) > Add log rotation settings to Hive, Druid, Storm > --- > > Key: AMBARI-19538 > URL: https://issues.apache.org/jira/browse/AMBARI-19538 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Attachments: AMBARI-19538.patch > > > This jira is for log4j rotation settings for hive, druid and storm -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19538) Add log rotation settings to Hive, Druid, Storm
[ https://issues.apache.org/jira/browse/AMBARI-19538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-19538: --- Attachment: AMBARI-19538.patch > Add log rotation settings to Hive, Druid, Storm > --- > > Key: AMBARI-19538 > URL: https://issues.apache.org/jira/browse/AMBARI-19538 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Attachments: AMBARI-19538.patch > > > This jira is for log4j rotation settings for hive, druid and storm -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19476) Incorrect error message when trying to add a group to multiple roles
[
https://issues.apache.org/jira/browse/AMBARI-19476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822374#comment-15822374
]
Hadoop QA commented on AMBARI-19476:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847402/AMBARI-19476.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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
ambari-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10049//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10049//console
This message is automatically generated.
> Incorrect error message when trying to add a group to multiple roles
>
>
> Key: AMBARI-19476
> URL: https://issues.apache.org/jira/browse/AMBARI-19476
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19476.patch,
> ErrorMessageAddingGroupToMultipleRoles.jpg
>
>
> 1. Create a group and assign roles to the group.
> 2. If you add the same group to multiple roles, the error message says "Only
> 1 role allowed per user".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19528) Ambari views : Adding new FileSystem support to views should work without code changes
[
https://issues.apache.org/jira/browse/AMBARI-19528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822338#comment-15822338
]
Hadoop QA commented on AMBARI-19528:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847374/AMBARI-19528_branch-2.5.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10048//console
This message is automatically generated.
> Ambari views : Adding new FileSystem support to views should work without
> code changes
> --
>
> Key: AMBARI-19528
> URL: https://issues.apache.org/jira/browse/AMBARI-19528
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.5.0
>
> Attachments: AMBARI-19528_branch-2.5.patch
>
>
> Right now when new file-system support has to be added to views, we need to
> add code to include several more key value pairs into the conf to make it
> work.
> Usually these key value pairs are file-system class names, secret key and
> access key.
> following 2 changes are proposed.
> 1. load the complete core-site and hdfs-site into the conf for creating
> filesystem. This will load any secret key, access key configured. It will
> also load any other necessary parameters.
> 2. Create a new view setting's parameter per view which will have semi colon
> separated key=value pairs that needs to be loaded into conf for connecting to
> the filesystem. This will cover any extra parameters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19538) Add log rotation settings to Hive, Druid, Storm
Madhuvanthi Radhakrishnan created AMBARI-19538: -- Summary: Add log rotation settings to Hive, Druid, Storm Key: AMBARI-19538 URL: https://issues.apache.org/jira/browse/AMBARI-19538 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan This jira is for log4j rotation settings for hive, druid and storm -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19535) When viewing details of a group, the group type is sometimes empty
[
https://issues.apache.org/jira/browse/AMBARI-19535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822335#comment-15822335
]
Hadoop QA commented on AMBARI-19535:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847376/AMBARI-19535.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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
ambari-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10047//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10047//console
This message is automatically generated.
> When viewing details of a group, the group type is sometimes empty
> --
>
> Key: AMBARI-19535
> URL: https://issues.apache.org/jira/browse/AMBARI-19535
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-19535.patch, GrouptTypeEmpty.jpg
>
>
> When you click on a Group and view its details, sometimes the Type shows an
> empty value.
> The following error can be seen on the web console.
> vendor.js:22245 TypeError: Cannot read property 'LABEL_KEY' of undefined at
> main.js:2278 at wrappedCallback (vendor.js:23746) at vendor.js:23832 at
> Scope.$eval (vendor.js:24875) at Scope.$digest (vendor.js:24687) at
> Scope.$apply (vendor.js:24979) at done (vendor.js:20552) at completeRequest
> (vendor.js:20766) at XMLHttpRequest.xhr.onreadystatechange (vendor.js:20705)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19430) Use common property for principal name prefix to help with customization of unique principal names
[
https://issues.apache.org/jira/browse/AMBARI-19430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822318#comment-15822318
]
Hadoop QA commented on AMBARI-19430:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847382/AMBARI-19430_trunk_01.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 9 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
ambari-funtest ambari-server ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10046//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10046//console
This message is automatically generated.
> Use common property for principal name prefix to help with customization of
> unique principal names
> --
>
> Key: AMBARI-19430
> URL: https://issues.apache.org/jira/browse/AMBARI-19430
> Project: Ambari
> Issue Type: Bug
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
> Attachments: AMBARI-19430_branch-2.5_01.patch,
> AMBARI-19430_trunk_01.patch
>
>
> Use common property for principal name prefix to help with customization of
> unique principal names.
> All _headless_ Kerberos identities have a non-unique principal name (across
> clusters). To help this issue, the cluster name is appended to these
> principal names by adding "-$\{cluster-name|toLower()\}" after the principal
> name component. If the user wants to change this convention, they will need
> to find all _headless_ principals and make the change. On top of that, when
> adding new components, they will need to remember to make the change to new
> _headless_ principal names.
> A better solution is to provide a _global_ property named "principal_suffix"
> and use that in each _headless_ principal name. By default the value for this
> property will be
> {code}
> principal_suffix="-${cluster_name|toLower()}"
> {code}
> If the user would like not use a prefix (in the event there is only a single
> cluster connecting to the KDC), the value can be changed to
> {code}
> principal_suffix=""
> {code}
> Finally if the user would like to use some other randomizer, they can set the
> value to something else. For example
> {code}
> principal_suffix="_12345"
> {code}
> The property is set in the Kerberos descriptor's "properties" block. For
> example:
> {code}
> {
> "properties": {
> "realm": "${kerberos-env/realm}",
> ...,
> "principal_suffix": "${cluster_name|toLower()}"
> },
> "identities": [
> ...,
> {
> "name": "smokeuser",
> "principal": {
> "value": "${cluster-env/smokeuser}-${principal_suffix}@${realm}",
> "type": "user",
> "configuration": "cluster-env/smokeuser_principal_name",
> "local_username": "${cluster-env/smokeuser}"
> },
> ...
> }
> ],
> "services": [
> {
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822273#comment-15822273 ] Alejandro Fernandez commented on AMBARI-19248: -- Pushed addendum to trunk, commit 5a7623a56c6e43eacdd44ec35bd62a2dfc11a2ed branch-2.5, commit f0002ede18c623b3d3121c26ae534189f45459a0 > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.5.0 >Reporter: mingjie tang >Assignee: mingjie tang > Fix For: 2.5.0 > > Attachments: 19248_2.diff, AMBARI-19248.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (AMBARI-19508) Ambari Yarn Queue Manager allows two same queue name
[ https://issues.apache.org/jira/browse/AMBARI-19508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako deleted AMBARI-19508: - > Ambari Yarn Queue Manager allows two same queue name > > > Key: AMBARI-19508 > URL: https://issues.apache.org/jira/browse/AMBARI-19508 > Project: Ambari > Issue Type: Bug >Reporter: Akhil PB >Assignee: Akhil PB > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (AMBARI-19495) Ambari Yarn Queue Manager allows two same queue name
[ https://issues.apache.org/jira/browse/AMBARI-19495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako deleted AMBARI-19495: - > Ambari Yarn Queue Manager allows two same queue name > > > Key: AMBARI-19495 > URL: https://issues.apache.org/jira/browse/AMBARI-19495 > Project: Ambari > Issue Type: Bug >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (AMBARI-19485) Ambari Yarn Queue Manager allows 2 same queue name
[ https://issues.apache.org/jira/browse/AMBARI-19485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako deleted AMBARI-19485: - > Ambari Yarn Queue Manager allows 2 same queue name > -- > > Key: AMBARI-19485 > URL: https://issues.apache.org/jira/browse/AMBARI-19485 > Project: Ambari > Issue Type: Bug >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (AMBARI-19496) Ambari Yarn Queue Manager allows two same queue name
[ https://issues.apache.org/jira/browse/AMBARI-19496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako deleted AMBARI-19496: - > Ambari Yarn Queue Manager allows two same queue name > > > Key: AMBARI-19496 > URL: https://issues.apache.org/jira/browse/AMBARI-19496 > Project: Ambari > Issue Type: Bug >Reporter: Akhil PB >Assignee: Akhil PB > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (AMBARI-19486) Ambari Yarn Queue Manager allows 2 same queue name
[ https://issues.apache.org/jira/browse/AMBARI-19486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako deleted AMBARI-19486: - > Ambari Yarn Queue Manager allows 2 same queue name > -- > > Key: AMBARI-19486 > URL: https://issues.apache.org/jira/browse/AMBARI-19486 > Project: Ambari > Issue Type: Bug >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (AMBARI-19484) Ambari Yarn Queue Manager allows 2 same queue name
[ https://issues.apache.org/jira/browse/AMBARI-19484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako deleted AMBARI-19484: - > Ambari Yarn Queue Manager allows 2 same queue name > -- > > Key: AMBARI-19484 > URL: https://issues.apache.org/jira/browse/AMBARI-19484 > Project: Ambari > Issue Type: Bug >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822261#comment-15822261 ] Alejandro Fernandez commented on AMBARI-19248: -- +1 for addendum [^19248_2.diff] > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.5.0 >Reporter: mingjie tang >Assignee: mingjie tang > Fix For: 2.5.0 > > Attachments: 19248_2.diff, AMBARI-19248.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18615) Fix JSHint errors in Workflow Manager view
[ https://issues.apache.org/jira/browse/AMBARI-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18615: Resolution: Won't Fix Status: Resolved (was: Patch Available) > Fix JSHint errors in Workflow Manager view > -- > > Key: AMBARI-18615 > URL: https://issues.apache.org/jira/browse/AMBARI-18615 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-18615.patch > > > When you compile the Workflow Manager view, you see 94 JSHint errors. > app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: > 6'). > app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: > 6'). > app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: > 6'). > app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: > 6'). > app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or > Mozilla JS extensions (use moz). > app.js: line 30, col 3, 'object short notation' is available in ES6 (use > 'esversion: 6') or Mozilla JS extensions (use moz). > app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: > 6'). > 7 errors > components/action-credential-config.js: line 18, col 1, 'import' is only > available in ES6 (use 'esversion: 6'). > components/action-credential-config.js: line 20, col 1, 'export' is only > available in ES6 (use 'esversion: 6'). > components/action-credential-config.js: line 24, col 38, 'arrow function > syntax (=>)' is only available in ES6 (use 'esversion: 6'). > components/action-credential-config.js: line 30, col 5, 'concise methods' is > available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz). > components/action-credential-config.js: line 33, col 36, 'arrow function > syntax (=>)' is only available in ES6 (use 'esversion: 6'). > 5 errors > components/action-version-select.js: line 18, col 1, 'import' is only > available in ES6 (use 'esversion: 6'). > components/action-version-select.js: line 20, col 1, 'export' is only > available in ES6 (use 'esversion: 6'). > components/action-version-select.js: line 22, col 5, 'concise methods' is > available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz). > 3 errors > components/archive-config.js: line 18, col 1, 'import' is only available in > ES6 (use 'esversion: 6'). > components/archive-config.js: line 19, col 1, 'import' is only available in > ES6 (use 'esversion: 6'). > components/archive-config.js: line 21, col 1, 'export' is only available in > ES6 (use 'esversion: 6'). > components/archive-config.js: line 29, col 5, 'concise methods' is available > in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz). > components/archive-config.js: line 33, col 5, 'concise methods' is available > in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz). > components/archive-config.js: line 36, col 5, 'concise methods' is available > in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz). > 6 errors > components/arg-config.js: line 18, col 1, 'import' is only available in ES6 > (use 'esversion: 6'). > components/arg-config.js: line 20, col 1, 'export' is only available in ES6 > (use 'esversion: 6'). > components/arg-config.js: line 33, col 3, 'concise methods' is available in > ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz). > components/arg-config.js: line 38, col 5, 'concise methods' is available in > ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz). > components/arg-config.js: line 41, col 5, 'concise methods' is available in > ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz). > 5 errors > components/bundle-job-details.js: line 18, col 1, 'import' is only available > in ES6 (use 'esversion: 6'). > components/bundle-job-details.js: line 20, col 1, 'export' is only available > in ES6 (use 'esversion: 6'). > components/bundle-job-details.js: line 22, col 5, 'concise methods' is > available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz). > components/bundle-job-details.js: line 25, col 5, 'concise methods' is > available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz). > components/bundle-job-details.js: line 28, col 5, 'concise methods' is > available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz). > 5 errors > components/coord-job-details.js: line 18, col 1, 'import' is only available > in ES6 (use 'esversion: 6'). > components/coord-job-details.js: line 20, col 1, 'export' is only available > in ES6 (use 'esversion: 6'). > components/coord-job-details.js: line 22, col 5, 'concise methods' is > available in ES6
[jira] [Commented] (AMBARI-19524) Use stack-level Atlas conf directory instead of hard-coded /etc/atlas/conf path
[
https://issues.apache.org/jira/browse/AMBARI-19524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822232#comment-15822232
]
Hadoop QA commented on AMBARI-19524:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847360/AMBARI-19524_trunk.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 2 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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10045//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10045//console
This message is automatically generated.
> Use stack-level Atlas conf directory instead of hard-coded /etc/atlas/conf
> path
> ---
>
> Key: AMBARI-19524
> URL: https://issues.apache.org/jira/browse/AMBARI-19524
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: All
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19524_branch-2.5.patch, AMBARI-19524_trunk.patch
>
>
> This is a bug that should have been fixed in Ambari 2.4 but showed up too
> late in the release and has repercussions to test it.
> Basically, status_params.py for Atlas service in Ambari sets
> {code}
> conf_dir = os.environ['METADATA_CONF'] if 'METADATA_CONF' in os.environ else
> '/etc/atlas/conf'
> {code}
> This is technically incorrect since /etc/atlas/conf is a symlink to
> /usr/hdp/current/atlas-client/conf, which is then a symlink to
> /etc/atlas/$some_version/0
> During Rolling Upgrade,
> 1. Atlas Server is stopped, new configs are written to
> /etc/atlas/$new_version/0, then symlink is changed so that
> /usr/hdp/current/atlas-server points to new version, and Atlas Server is
> started
> At this point, /etc/atlas/conf -> /usr/hdp/current/atlas-client/conf (which
> is still using the old version) since the client has not yet been updated.
> 2. Atlas Client has new configs written to /etc/atlas/$new_version/0, then
> symlink is changed so that /usr/hdp/current/atlas-client points to new version
> Basically, we need to look at the usages of conf_dir and make sure it is
> correct during all scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19476) Incorrect error message when trying to add a group to multiple roles
[ https://issues.apache.org/jira/browse/AMBARI-19476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19476: Attachment: (was: AMBARI-19476.patch) > Incorrect error message when trying to add a group to multiple roles > > > Key: AMBARI-19476 > URL: https://issues.apache.org/jira/browse/AMBARI-19476 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19476.patch, > ErrorMessageAddingGroupToMultipleRoles.jpg > > > 1. Create a group and assign roles to the group. > 2. If you add the same group to multiple roles, the error message says "Only > 1 role allowed per user". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19476) Incorrect error message when trying to add a group to multiple roles
[ https://issues.apache.org/jira/browse/AMBARI-19476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19476: Status: Patch Available (was: Open) > Incorrect error message when trying to add a group to multiple roles > > > Key: AMBARI-19476 > URL: https://issues.apache.org/jira/browse/AMBARI-19476 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19476.patch, > ErrorMessageAddingGroupToMultipleRoles.jpg > > > 1. Create a group and assign roles to the group. > 2. If you add the same group to multiple roles, the error message says "Only > 1 role allowed per user". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19476) Incorrect error message when trying to add a group to multiple roles
[ https://issues.apache.org/jira/browse/AMBARI-19476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19476: Attachment: AMBARI-19476.patch > Incorrect error message when trying to add a group to multiple roles > > > Key: AMBARI-19476 > URL: https://issues.apache.org/jira/browse/AMBARI-19476 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19476.patch, > ErrorMessageAddingGroupToMultipleRoles.jpg > > > 1. Create a group and assign roles to the group. > 2. If you add the same group to multiple roles, the error message says "Only > 1 role allowed per user". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19476) Incorrect error message when trying to add a group to multiple roles
[ https://issues.apache.org/jira/browse/AMBARI-19476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19476: Status: Open (was: Patch Available) > Incorrect error message when trying to add a group to multiple roles > > > Key: AMBARI-19476 > URL: https://issues.apache.org/jira/browse/AMBARI-19476 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19476.patch, > ErrorMessageAddingGroupToMultipleRoles.jpg > > > 1. Create a group and assign roles to the group. > 2. If you add the same group to multiple roles, the error message says "Only > 1 role allowed per user". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19525) Unit Test failure during schema verification of configuration files
[
https://issues.apache.org/jira/browse/AMBARI-19525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19525:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Unit Test failure during schema verification of configuration files
> ---
>
> Key: AMBARI-19525
> URL: https://issues.apache.org/jira/browse/AMBARI-19525
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: rb55502.patch
>
>
> {code}
> validatePropertySchemaOfServiceXMLs(org.apache.ambari.server.state.ServicePropertiesTest)
> Time elapsed: 2.622 sec <<< ERROR!
> org.apache.ambari.server.AmbariException: File
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/common-services/OOZIE/4.2.0.2.3/configuration/oozie-site.xml
> didn't pass the validation. Error message is : cvc-complex-type.2.4.a:
> Invalid content was found starting with element 'keystore'. One of '{maximum,
> minimum, unit, delete, visible, empty-value-valid, ui-only-property,
> read-only, editable-only-at-install, show-property-name, increment-step,
> entries, hidden, entries_editable, selection-cardinality, property-file-name,
> property-file-type}' is expected.
> at
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs(ServicePropertiesTest.java:49)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19276) Reset UI State does not clear ongoing wizard data
[
https://issues.apache.org/jira/browse/AMBARI-19276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822174#comment-15822174
]
Hadoop QA commented on AMBARI-19276:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847362/AMBARI-19276.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10043//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10043//console
This message is automatically generated.
> Reset UI State does not clear ongoing wizard data
> -
>
> Key: AMBARI-19276
> URL: https://issues.apache.org/jira/browse/AMBARI-19276
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-19276.patch
>
>
> *STR:*
> # Log into ambari-web and start "Add Service Wizard"
> # Close the browser (simulate the scenario of browser crash)
> # Log in from another credentials to ambari-web
> # A message that add service wizard is ongoing will appear
> # Got to ambari-web experimental page and reset ui state
> *Expected:* The label should disappear showing for all users and the user who
> started add service wizard should *not* renavigate to add service wizard on
> logging in back
> *Actual:* The labe ldoes not disappear for other users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19536) Improve "Install Wizard step 2-10" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19536: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Improve "Install Wizard step 2-10" after new guidelines > --- > > Key: AMBARI-19536 > URL: https://issues.apache.org/jira/browse/AMBARI-19536 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > > Should do the following adjustments to integrate with the new style > guidelines: > Step 2, as for the contents inside of the white panel: > 1. Make the two radio buttons horizontally aligned. > 2. Browse file button should be consistent with other buttons > 3. Each section title should be readable. > Step 3, > 3. "Remove Selected" should be right aligned, also disappear if nothing > selected > Warning section should have some margin > Step 7, > 5. Advanced configs, collapse of each category should be consistent with > configs page after installed > Also, In general, the checkbox and radio buttons are not aligned with related > text. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19536) Improve "Install Wizard step 2-10" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19536: - Status: Patch Available (was: Open) > Improve "Install Wizard step 2-10" after new guidelines > --- > > Key: AMBARI-19536 > URL: https://issues.apache.org/jira/browse/AMBARI-19536 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > > Should do the following adjustments to integrate with the new style > guidelines: > Step 2, as for the contents inside of the white panel: > 1. Make the two radio buttons horizontally aligned. > 2. Browse file button should be consistent with other buttons > 3. Each section title should be readable. > Step 3, > 3. "Remove Selected" should be right aligned, also disappear if nothing > selected > Warning section should have some margin > Step 7, > 5. Advanced configs, collapse of each category should be consistent with > configs page after installed > Also, In general, the checkbox and radio buttons are not aligned with related > text. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19537) Provide default value for yarn leveldb state store path
[ https://issues.apache.org/jira/browse/AMBARI-19537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19537: --- Attachment: AMBARI-19537.patch > Provide default value for yarn leveldb state store path > --- > > Key: AMBARI-19537 > URL: https://issues.apache.org/jira/browse/AMBARI-19537 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-19537.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19537) Provide default value for yarn leveldb state store path
[ https://issues.apache.org/jira/browse/AMBARI-19537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19537: --- Status: Patch Available (was: Open) > Provide default value for yarn leveldb state store path > --- > > Key: AMBARI-19537 > URL: https://issues.apache.org/jira/browse/AMBARI-19537 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-19537.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19537) Provide default value for yarn leveldb state store path
Di Li created AMBARI-19537: -- Summary: Provide default value for yarn leveldb state store path Key: AMBARI-19537 URL: https://issues.apache.org/jira/browse/AMBARI-19537 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Di Li Assignee: Di Li Priority: Minor Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19529) Atlas service check should fail only if all metadata servers are down.
[
https://issues.apache.org/jira/browse/AMBARI-19529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822130#comment-15822130
]
Hadoop QA commented on AMBARI-19529:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847356/AMBARI-19529_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10042//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10042//console
This message is automatically generated.
> Atlas service check should fail only if all metadata servers are down.
> --
>
> Key: AMBARI-19529
> URL: https://issues.apache.org/jira/browse/AMBARI-19529
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19529_branch-2.5 .patch, AMBARI-19529_trunk.patch
>
>
> On Atlas-HA environments, Atlas service check fails even if one of the hosts
> is down, the service check should only fail when All the Atlas metadata
> servers are down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19533) Host-Ordered Upgrade packs are named incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-19533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-19533: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Host-Ordered Upgrade packs are named incorrectly > > > Key: AMBARI-19533 > URL: https://issues.apache.org/jira/browse/AMBARI-19533 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole > Fix For: 2.5.0 > > Attachments: AMBARI-19533.patch > > > The Host-Ordered upgrade packs are named incorrectly and inconsistently. > This will cause issues when creating new Upgrade Packs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19536) Improve "Install Wizard step 2-10" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822087#comment-15822087 ] Xi Wang commented on AMBARI-19536: -- 20236 passing (24s) 153 pending > Improve "Install Wizard step 2-10" after new guidelines > --- > > Key: AMBARI-19536 > URL: https://issues.apache.org/jira/browse/AMBARI-19536 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > > Should do the following adjustments to integrate with the new style > guidelines: > Step 2, as for the contents inside of the white panel: > 1. Make the two radio buttons horizontally aligned. > 2. Browse file button should be consistent with other buttons > 3. Each section title should be readable. > Step 3, > 3. "Remove Selected" should be right aligned, also disappear if nothing > selected > Warning section should have some margin > Step 7, > 5. Advanced configs, collapse of each category should be consistent with > configs page after installed > Also, In general, the checkbox and radio buttons are not aligned with related > text. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19536) Improve "Install Wizard step 2-10" after new guidelines
Xi Wang created AMBARI-19536: Summary: Improve "Install Wizard step 2-10" after new guidelines Key: AMBARI-19536 URL: https://issues.apache.org/jira/browse/AMBARI-19536 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Xi Wang Assignee: Xi Wang Fix For: 3.0.0 Should do the following adjustments to integrate with the new style guidelines: Step 2, as for the contents inside of the white panel: 1. Make the two radio buttons horizontally aligned. 2. Browse file button should be consistent with other buttons 3. Each section title should be readable. Step 3, 3. "Remove Selected" should be right aligned, also disappear if nothing selected Warning section should have some margin Step 7, 5. Advanced configs, collapse of each category should be consistent with configs page after installed Also, In general, the checkbox and radio buttons are not aligned with related text. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19430) Use common property for principal name prefix to help with customization of unique principal names
[
https://issues.apache.org/jira/browse/AMBARI-19430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19430:
--
Status: Patch Available (was: In Progress)
> Use common property for principal name prefix to help with customization of
> unique principal names
> --
>
> Key: AMBARI-19430
> URL: https://issues.apache.org/jira/browse/AMBARI-19430
> Project: Ambari
> Issue Type: Bug
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
> Attachments: AMBARI-19430_branch-2.5_01.patch,
> AMBARI-19430_trunk_01.patch
>
>
> Use common property for principal name prefix to help with customization of
> unique principal names.
> All _headless_ Kerberos identities have a non-unique principal name (across
> clusters). To help this issue, the cluster name is appended to these
> principal names by adding "-$\{cluster-name|toLower()\}" after the principal
> name component. If the user wants to change this convention, they will need
> to find all _headless_ principals and make the change. On top of that, when
> adding new components, they will need to remember to make the change to new
> _headless_ principal names.
> A better solution is to provide a _global_ property named "principal_suffix"
> and use that in each _headless_ principal name. By default the value for this
> property will be
> {code}
> principal_suffix="-${cluster_name|toLower()}"
> {code}
> If the user would like not use a prefix (in the event there is only a single
> cluster connecting to the KDC), the value can be changed to
> {code}
> principal_suffix=""
> {code}
> Finally if the user would like to use some other randomizer, they can set the
> value to something else. For example
> {code}
> principal_suffix="_12345"
> {code}
> The property is set in the Kerberos descriptor's "properties" block. For
> example:
> {code}
> {
> "properties": {
> "realm": "${kerberos-env/realm}",
> ...,
> "principal_suffix": "${cluster_name|toLower()}"
> },
> "identities": [
> ...,
> {
> "name": "smokeuser",
> "principal": {
> "value": "${cluster-env/smokeuser}-${principal_suffix}@${realm}",
> "type": "user",
> "configuration": "cluster-env/smokeuser_principal_name",
> "local_username": "${cluster-env/smokeuser}"
> },
> ...
> }
> ],
> "services": [
> {
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19430) Use common property for principal name prefix to help with customization of unique principal names
[
https://issues.apache.org/jira/browse/AMBARI-19430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19430:
--
Attachment: AMBARI-19430_trunk_01.patch
AMBARI-19430_branch-2.5_01.patch
> Use common property for principal name prefix to help with customization of
> unique principal names
> --
>
> Key: AMBARI-19430
> URL: https://issues.apache.org/jira/browse/AMBARI-19430
> Project: Ambari
> Issue Type: Bug
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
> Attachments: AMBARI-19430_branch-2.5_01.patch,
> AMBARI-19430_trunk_01.patch
>
>
> Use common property for principal name prefix to help with customization of
> unique principal names.
> All _headless_ Kerberos identities have a non-unique principal name (across
> clusters). To help this issue, the cluster name is appended to these
> principal names by adding "-$\{cluster-name|toLower()\}" after the principal
> name component. If the user wants to change this convention, they will need
> to find all _headless_ principals and make the change. On top of that, when
> adding new components, they will need to remember to make the change to new
> _headless_ principal names.
> A better solution is to provide a _global_ property named "principal_suffix"
> and use that in each _headless_ principal name. By default the value for this
> property will be
> {code}
> principal_suffix="-${cluster_name|toLower()}"
> {code}
> If the user would like not use a prefix (in the event there is only a single
> cluster connecting to the KDC), the value can be changed to
> {code}
> principal_suffix=""
> {code}
> Finally if the user would like to use some other randomizer, they can set the
> value to something else. For example
> {code}
> principal_suffix="_12345"
> {code}
> The property is set in the Kerberos descriptor's "properties" block. For
> example:
> {code}
> {
> "properties": {
> "realm": "${kerberos-env/realm}",
> ...,
> "principal_suffix": "${cluster_name|toLower()}"
> },
> "identities": [
> ...,
> {
> "name": "smokeuser",
> "principal": {
> "value": "${cluster-env/smokeuser}-${principal_suffix}@${realm}",
> "type": "user",
> "configuration": "cluster-env/smokeuser_principal_name",
> "local_username": "${cluster-env/smokeuser}"
> },
> ...
> }
> ],
> "services": [
> {
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19029) Atlas web UI inaccessible alert after enabling Namenode-HA
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822073#comment-15822073
]
Hadoop QA commented on AMBARI-19029:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847331/AMBARI-19029.3.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 2 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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10041//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10041//console
This message is automatically generated.
> Atlas web UI inaccessible alert after enabling Namenode-HA
> --
>
> Key: AMBARI-19029
> URL: https://issues.apache.org/jira/browse/AMBARI-19029
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Shreya Bhat
>Assignee: Vishal Suvagia
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19029.1.patch, AMBARI-19029.2.patch,
> AMBARI-19029.3.patch, AMBARI-19029.patch
>
>
> After enabling Namenode-HA, atlas had a critical alert that "This host-level
> alert is triggered if the Metadata Server Web UI is unreachable."
> From atlas logs I can see :
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:84)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
> at
[jira] [Updated] (AMBARI-19535) When viewing details of a group, the group type is sometimes empty
[ https://issues.apache.org/jira/browse/AMBARI-19535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19535: Fix Version/s: 2.5.0 Status: Patch Available (was: In Progress) > When viewing details of a group, the group type is sometimes empty > -- > > Key: AMBARI-19535 > URL: https://issues.apache.org/jira/browse/AMBARI-19535 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-19535.patch, GrouptTypeEmpty.jpg > > > When you click on a Group and view its details, sometimes the Type shows an > empty value. > The following error can be seen on the web console. > vendor.js:22245 TypeError: Cannot read property 'LABEL_KEY' of undefined at > main.js:2278 at wrappedCallback (vendor.js:23746) at vendor.js:23832 at > Scope.$eval (vendor.js:24875) at Scope.$digest (vendor.js:24687) at > Scope.$apply (vendor.js:24979) at done (vendor.js:20552) at completeRequest > (vendor.js:20766) at XMLHttpRequest.xhr.onreadystatechange (vendor.js:20705) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19535) When viewing details of a group, the group type is sometimes empty
[ https://issues.apache.org/jira/browse/AMBARI-19535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19535: Attachment: AMBARI-19535.patch > When viewing details of a group, the group type is sometimes empty > -- > > Key: AMBARI-19535 > URL: https://issues.apache.org/jira/browse/AMBARI-19535 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-19535.patch, GrouptTypeEmpty.jpg > > > When you click on a Group and view its details, sometimes the Type shows an > empty value. > The following error can be seen on the web console. > vendor.js:22245 TypeError: Cannot read property 'LABEL_KEY' of undefined at > main.js:2278 at wrappedCallback (vendor.js:23746) at vendor.js:23832 at > Scope.$eval (vendor.js:24875) at Scope.$digest (vendor.js:24687) at > Scope.$apply (vendor.js:24979) at done (vendor.js:20552) at completeRequest > (vendor.js:20766) at XMLHttpRequest.xhr.onreadystatechange (vendor.js:20705) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19535) When viewing details of a group, the group type is sometimes empty
[ https://issues.apache.org/jira/browse/AMBARI-19535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19535: Attachment: GrouptTypeEmpty.jpg > When viewing details of a group, the group type is sometimes empty > -- > > Key: AMBARI-19535 > URL: https://issues.apache.org/jira/browse/AMBARI-19535 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-19535.patch, GrouptTypeEmpty.jpg > > > When you click on a Group and view its details, sometimes the Type shows an > empty value. > The following error can be seen on the web console. > vendor.js:22245 TypeError: Cannot read property 'LABEL_KEY' of undefined at > main.js:2278 at wrappedCallback (vendor.js:23746) at vendor.js:23832 at > Scope.$eval (vendor.js:24875) at Scope.$digest (vendor.js:24687) at > Scope.$apply (vendor.js:24979) at done (vendor.js:20552) at completeRequest > (vendor.js:20766) at XMLHttpRequest.xhr.onreadystatechange (vendor.js:20705) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19535) When viewing details of a group, the group type is sometimes empty
Sangeeta Ravindran created AMBARI-19535: --- Summary: When viewing details of a group, the group type is sometimes empty Key: AMBARI-19535 URL: https://issues.apache.org/jira/browse/AMBARI-19535 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.5.0 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran When you click on a Group and view its details, sometimes the Type shows an empty value. The following error can be seen on the web console. vendor.js:22245 TypeError: Cannot read property 'LABEL_KEY' of undefined at main.js:2278 at wrappedCallback (vendor.js:23746) at vendor.js:23832 at Scope.$eval (vendor.js:24875) at Scope.$digest (vendor.js:24687) at Scope.$apply (vendor.js:24979) at done (vendor.js:20552) at completeRequest (vendor.js:20766) at XMLHttpRequest.xhr.onreadystatechange (vendor.js:20705) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19528) Ambari views : Adding new FileSystem support to views should work without code changes
[ https://issues.apache.org/jira/browse/AMBARI-19528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19528: --- Status: Patch Available (was: Open) patch contains : loading coresite and hdfssite and custom configs in view before creating hdfs connection. changed the view.xml of views for adding custom properties. updated pom.xml of hive-next, files, pig, hive20, wfmanager, utils and commons. > Ambari views : Adding new FileSystem support to views should work without > code changes > -- > > Key: AMBARI-19528 > URL: https://issues.apache.org/jira/browse/AMBARI-19528 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-19528_branch-2.5.patch > > > Right now when new file-system support has to be added to views, we need to > add code to include several more key value pairs into the conf to make it > work. > Usually these key value pairs are file-system class names, secret key and > access key. > following 2 changes are proposed. > 1. load the complete core-site and hdfs-site into the conf for creating > filesystem. This will load any secret key, access key configured. It will > also load any other necessary parameters. > 2. Create a new view setting's parameter per view which will have semi colon > separated key=value pairs that needs to be loaded into conf for connecting to > the filesystem. This will cover any extra parameters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19528) Ambari views : Adding new FileSystem support to views should work without code changes
[ https://issues.apache.org/jira/browse/AMBARI-19528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19528: --- Attachment: AMBARI-19528_branch-2.5.patch > Ambari views : Adding new FileSystem support to views should work without > code changes > -- > > Key: AMBARI-19528 > URL: https://issues.apache.org/jira/browse/AMBARI-19528 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-19528_branch-2.5.patch > > > Right now when new file-system support has to be added to views, we need to > add code to include several more key value pairs into the conf to make it > work. > Usually these key value pairs are file-system class names, secret key and > access key. > following 2 changes are proposed. > 1. load the complete core-site and hdfs-site into the conf for creating > filesystem. This will load any secret key, access key configured. It will > also load any other necessary parameters. > 2. Create a new view setting's parameter per view which will have semi colon > separated key=value pairs that needs to be loaded into conf for connecting to > the filesystem. This will cover any extra parameters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19522) Hive View 2.0: Saving worksheet as saved query
[
https://issues.apache.org/jira/browse/AMBARI-19522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822036#comment-15822036
]
Hadoop QA commented on AMBARI-19522:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847332/AMBARI-19522-v2_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:red}-1 core tests{color}. The test build failed in
contrib/views/hive20
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10040//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10040//console
This message is automatically generated.
> Hive View 2.0: Saving worksheet as saved query
> --
>
> Key: AMBARI-19522
> URL: https://issues.apache.org/jira/browse/AMBARI-19522
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19522-v2_trunk.patch
>
>
> - Saving worksheet as saved query.
> - Ability to delete the saved query
> - Ability to open the save query as worksheet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19533) Host-Ordered Upgrade packs are named incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-19533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-19533: --- Status: Patch Available (was: Open) > Host-Ordered Upgrade packs are named incorrectly > > > Key: AMBARI-19533 > URL: https://issues.apache.org/jira/browse/AMBARI-19533 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole > Fix For: 2.5.0 > > Attachments: AMBARI-19533.patch > > > The Host-Ordered upgrade packs are named incorrectly and inconsistently. > This will cause issues when creating new Upgrade Packs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19533) Host-Ordered Upgrade packs are named incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-19533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-19533: --- Attachment: AMBARI-19533.patch > Host-Ordered Upgrade packs are named incorrectly > > > Key: AMBARI-19533 > URL: https://issues.apache.org/jira/browse/AMBARI-19533 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole > Fix For: 2.5.0 > > Attachments: AMBARI-19533.patch > > > The Host-Ordered upgrade packs are named incorrectly and inconsistently. > This will cause issues when creating new Upgrade Packs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19338) AM sizing for LLAP - min container size changes
[
https://issues.apache.org/jira/browse/AMBARI-19338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822008#comment-15822008
]
Hadoop QA commented on AMBARI-19338:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847325/AMBARI-19338_3.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10039//console
This message is automatically generated.
> AM sizing for LLAP - min container size changes
> ---
>
> Key: AMBARI-19338
> URL: https://issues.apache.org/jira/browse/AMBARI-19338
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Reporter: Dmytro Sen
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19338_2.patch, AMBARI-19338_3.patch
>
>
> Currently, AMs are sized too big for LLAP (especially with small setups).
> Better defaults are needed, but min container size has to change for that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
