[jira] [Commented] (AMBARI-19372) Disable FileCache update for parallel_execution
[
https://issues.apache.org/jira/browse/AMBARI-19372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799903#comment-15799903
]
Hadoop QA commented on AMBARI-19372:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845634/AMBARI-19372.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-agent
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9902//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9902//console
This message is automatically generated.
> Disable FileCache update for parallel_execution
> ---
>
> Key: AMBARI-19372
> URL: https://issues.apache.org/jira/browse/AMBARI-19372
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19372.patch
>
>
> Ambari agent's {{FileCache}} is not thread-safe, hence needs to be disabled
> if {{parallel_execution}} is enabled. The server's
> {{agent.auto.cache.update=false}} setting is not enough to prevent all
> subprocesses from using the file cache, because they are started before the
> setting is received from the server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Attachment: No graph if uppercase agent hostname .png > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19357.patch, No graph if uppercase agent hostname > .png, uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowercase hostname used in > ambari ,but the hostname in METRIC_RECORD is not lowercase (see attached > picture),so we will not get any records.This patch amis to convert hostname > of metric record of flume to lowercase before inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19365) Executing ambari-server unit tests with JDK 1.8 results in unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19365:
--
Status: Patch Available (was: In Progress)
> Executing ambari-server unit tests with JDK 1.8 results in unit test failures
> -
>
> Key: AMBARI-19365
> URL: https://issues.apache.org/jira/browse/AMBARI-19365
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: jdk1_8, unit-test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19365_branch-2.5_01.patch,
> AMBARI-19365_trunk_01.patch
>
>
> Following unit tests fails when executed with JDK 1.8
> {code}
> mvn test -Dtest=DataStoreImplTest
> mvn clean test -Dtest=UpgradeCatalog222Test
> mvn test -Dtest=KerberosCheckerTest,AmbariBasicAuthenticationFilterTest
> {code}
> Same unit tests passes if the environment is switched to use JDK 1.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19365) Executing ambari-server unit tests with JDK 1.8 results in unit test failures
[
https://issues.apache.org/jira/browse/AMBARI-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19365:
--
Attachment: AMBARI-19365_trunk_01.patch
AMBARI-19365_branch-2.5_01.patch
> Executing ambari-server unit tests with JDK 1.8 results in unit test failures
> -
>
> Key: AMBARI-19365
> URL: https://issues.apache.org/jira/browse/AMBARI-19365
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: jdk1_8, unit-test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19365_branch-2.5_01.patch,
> AMBARI-19365_trunk_01.patch
>
>
> Following unit tests fails when executed with JDK 1.8
> {code}
> mvn test -Dtest=DataStoreImplTest
> mvn clean test -Dtest=UpgradeCatalog222Test
> mvn test -Dtest=KerberosCheckerTest,AmbariBasicAuthenticationFilterTest
> {code}
> Same unit tests passes if the environment is switched to use JDK 1.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19374) solr_cloud_util.py should update solr data in ZK if it has changed
Miklos Gergely created AMBARI-19374: --- Summary: solr_cloud_util.py should update solr data in ZK if it has changed Key: AMBARI-19374 URL: https://issues.apache.org/jira/browse/AMBARI-19374 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.4.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.5.0 solr_cloud_util.py updates only solrconfig.xml changes in the zookeeper, it should update any kind of solr data change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19374) solr_cloud_util.py should update solr data in ZK if it has changed
[ https://issues.apache.org/jira/browse/AMBARI-19374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19374: Attachment: AMBARI-19374.patch > solr_cloud_util.py should update solr data in ZK if it has changed > -- > > Key: AMBARI-19374 > URL: https://issues.apache.org/jira/browse/AMBARI-19374 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19374.patch > > > solr_cloud_util.py updates only solrconfig.xml changes in the zookeeper, it > should update any kind of solr data change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19374) solr_cloud_util.py should update solr data in ZK if it has changed
[ https://issues.apache.org/jira/browse/AMBARI-19374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19374: Status: Patch Available (was: In Progress) > solr_cloud_util.py should update solr data in ZK if it has changed > -- > > Key: AMBARI-19374 > URL: https://issues.apache.org/jira/browse/AMBARI-19374 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19374.patch > > > solr_cloud_util.py updates only solrconfig.xml changes in the zookeeper, it > should update any kind of solr data change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-19367) Not able to save FS action node after populating job xml value
[
https://issues.apache.org/jira/browse/AMBARI-19367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkat reassigned AMBARI-19367:
---
Assignee: venkat
> Not able to save FS action node after populating job xml value
> --
>
> Key: AMBARI-19367
> URL: https://issues.apache.org/jira/browse/AMBARI-19367
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: venkat
>Priority: Blocker
> Labels: WFD
> Fix For: 2.5.0
>
>
> Not able to save FS action node after populating job xml value. When user
> tries to save the action node settings, UI is throwing below error :
> {code}
> oozie-designer-b34005a….js:2 Uncaught TypeError: Cannot read property
> 'pushObject' of undefined
> at n.addFile
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:2:24866)
> at n.bindInputPlaceholder
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:2:24794)
> at n.trigger
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:16:24070)
> at n [as trigger]
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:11:18800)
> at
> http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:6:727
> at Map.forEach (native)
> at n.processMultivaluedComponents
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:6:683)
> at n.save
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:6:1177)
> at n.send
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:15:25559)
> at n [as send]
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:11:18800)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19375) Update the execution mode for hive interactive in HDP 2.6 stack
Siddharth Seth created AMBARI-19375: --- Summary: Update the execution mode for hive interactive in HDP 2.6 stack Key: AMBARI-19375 URL: https://issues.apache.org/jira/browse/AMBARI-19375 Project: Ambari Issue Type: Task Components: stacks Reporter: Siddharth Seth Assignee: Siddharth Seth -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19375) Update the execution mode for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19375: Attachment: AMBARI-19375.01.patch The intent is to change the value to only. Also to update the value to only from the old value of 'all' in the 2.5 stack on upgrade. cc [~sumitmohanty] for review. > Update the execution mode for hive interactive in HDP 2.6 stack > --- > > Key: AMBARI-19375 > URL: https://issues.apache.org/jira/browse/AMBARI-19375 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Attachments: AMBARI-19375.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19376) translation from English to Chinese
xlsong created AMBARI-19376: --- Summary: translation from English to Chinese Key: AMBARI-19376 URL: https://issues.apache.org/jira/browse/AMBARI-19376 Project: Ambari Issue Type: Task Components: ambari-admin, ambari-web Affects Versions: trunk, 2.2.1 Reporter: xlsong Fix For: 2.2.1 translation of pages from English to Chinese -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19375) Update the execution mode for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19375: Status: Patch Available (was: Open) > Update the execution mode for hive interactive in HDP 2.6 stack > --- > > Key: AMBARI-19375 > URL: https://issues.apache.org/jira/browse/AMBARI-19375 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Attachments: AMBARI-19375.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19375) Update the execution mode for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19375: Fix Version/s: 2.5.0 > Update the execution mode for hive interactive in HDP 2.6 stack > --- > > Key: AMBARI-19375 > URL: https://issues.apache.org/jira/browse/AMBARI-19375 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19375.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17512) Failed to Check Ambari Metrics
[
https://issues.apache.org/jira/browse/AMBARI-17512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xing resolved AMBARI-17512.
---
Resolution: Won't Fix
> Failed to Check Ambari Metrics
> --
>
> Key: AMBARI-17512
> URL: https://issues.apache.org/jira/browse/AMBARI-17512
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-metrics, ambari-server
>Affects Versions: 2.2.2
>Reporter: Xing
>
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py",
> line 172, in
> AMSServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py",
> line 100, in service_check
> raise Fail("Metrics were not saved. Service check has failed. "
> resource_management.core.exceptions.Fail: Metrics were not saved. Service
> check has failed.
> Connection failed.
> stdout:
> 2016-06-30 07:15:36,288 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-06-30 07:15:36,297 - Ambari Metrics service check was started.
> 2016-06-30 07:15:36,304 - Generated metrics:
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host-172-16-1-204",
> "timestamp": 1467285336000,
> "starttime": 1467285336000,
> "metrics": {
> "1467285336000": 0.415144595584,
> "1467285337000": 1467285336000
> }
> }
> ]
> }
> 2016-06-30 07:15:36,304 - Connecting (POST) to
> host-172-16-1-204:6188/ws/v1/timeline/metrics/
> 2016-06-30 07:15:51,319 - Connection failed. Next retry in 15 seconds.
> 2016-06-30 07:15:51,322 - Generated metrics:
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host-172-16-1-204",
> "timestamp": 1467285351000,
> "starttime": 1467285351000,
> "metrics": {
> "1467285351000": 0.415144595584,
> "1467285352000": 1467285351000
> }
> }
> ]
> }
> 2016-06-30 07:15:51,323 - Connecting (POST) to
> host-172-16-1-204:6188/ws/v1/timeline/metrics/
> 2016-06-30 07:16:06,338 - Connection failed. Next retry in 15 seconds.
> 2016-06-30 07:16:06,341 - Generated metrics:
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host-172-16-1-204",
> "timestamp": 1467285366000,
> "starttime": 1467285366000,
> "metrics": {
> "1467285366000": 0.415144595584,
> "1467285367000": 1467285366000
> }
> }
> ]
> }
> 2016-06-30 07:16:06,341 - Connecting (POST) to
> host-172-16-1-204:6188/ws/v1/timeline/metrics/
> 2016-06-30 07:16:21,350 - Connection failed. Next retry in 15 seconds.
> 2016-06-30 07:16:21,353 - Generated metrics:
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host-172-16-1-204",
> "timestamp": 1467285381000,
> "starttime": 1467285381000,
> "metrics": {
> "1467285381000": 0.415144595584,
> "1467285382000": 1467285381000
> }
> }
> ]
> }
> 2016-06-30 07:16:21,353 - Connecting (POST) to
> host-172-16-1-204:6188/ws/v1/timeline/metrics/
> 2016-06-30 07:16:36,369 - Connection failed. Next retry in 15 seconds.
> 2016-06-30 07:16:36,372 - Generated metrics:
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host-172-16-1-204",
> "timestamp": 1467285396000,
> "starttime": 1467285396000,
> "metrics": {
> "1467285396000": 0.415144595584,
> "1467285397000": 1467285396000
> }
> }
> ]
> }
> 2016-06-30 07:16:36,372 - Connecting (POST) to
> host-172-16-1-204:6188/ws/v1/timeline/metrics/
> 2016-06-30 07:16:51,388 - Connection failed. Next retry in 15 seconds.
> 2016-06-30 07:16:51,391 - Generated metrics:
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host-172-16-1-204",
> "timestamp": 1467285411000,
> "starttime": 1467285411000,
> "metrics": {
> "1467285411000": 0.415144595584,
> "1467285412000": 1467285411000
> }
> }
> ]
> }
> 2016-06-30 07:16:51,391 - Connecting (POST) to
> host-172-
[jira] [Updated] (AMBARI-19367) Not able to save FS action node after populating job xml value
[
https://issues.apache.org/jira/browse/AMBARI-19367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkat updated AMBARI-19367:
Status: Patch Available (was: In Progress)
> Not able to save FS action node after populating job xml value
> --
>
> Key: AMBARI-19367
> URL: https://issues.apache.org/jira/browse/AMBARI-19367
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: venkat
>Priority: Blocker
> Labels: WFD
> Fix For: 2.5.0
>
>
> Not able to save FS action node after populating job xml value. When user
> tries to save the action node settings, UI is throwing below error :
> {code}
> oozie-designer-b34005a….js:2 Uncaught TypeError: Cannot read property
> 'pushObject' of undefined
> at n.addFile
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:2:24866)
> at n.bindInputPlaceholder
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:2:24794)
> at n.trigger
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:16:24070)
> at n [as trigger]
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:11:18800)
> at
> http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:6:727
> at Map.forEach (native)
> at n.processMultivaluedComponents
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:6:683)
> at n.save
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:6:1177)
> at n.send
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:15:25559)
> at n [as send]
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:11:18800)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19352) Designer should always pick latest version for an action node
[ https://issues.apache.org/jira/browse/AMBARI-19352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB updated AMBARI-19352: - Resolution: Fixed Status: Resolved (was: Patch Available) > Designer should always pick latest version for an action node > - > > Key: AMBARI-19352 > URL: https://issues.apache.org/jira/browse/AMBARI-19352 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19352_trunk.patch > > > Designer should always pick latest version for an action node and the actin > node settings should be specific to each workflow tab. > But as of now, designer is picking up old settings even for a new tab. > Steps to reproduce: > 1) Import a workflow with hive node and hive node version as 0.2. > 2) Open a new tab and add a hive node to the new workflow. > 3) Preview the xml for new workflow. Even the new workflow has hive version > as 0.2. Ideally it should be the latest version 0.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19367) Not able to save FS action node after populating job xml value
[
https://issues.apache.org/jira/browse/AMBARI-19367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkat updated AMBARI-19367:
Attachment: AMBARI-19367_branch-2.5.patch
> Not able to save FS action node after populating job xml value
> --
>
> Key: AMBARI-19367
> URL: https://issues.apache.org/jira/browse/AMBARI-19367
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: venkat
>Priority: Blocker
> Labels: WFD
> Fix For: 2.5.0
>
> Attachments: AMBARI-19367_branch-2.5.patch
>
>
> Not able to save FS action node after populating job xml value. When user
> tries to save the action node settings, UI is throwing below error :
> {code}
> oozie-designer-b34005a….js:2 Uncaught TypeError: Cannot read property
> 'pushObject' of undefined
> at n.addFile
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:2:24866)
> at n.bindInputPlaceholder
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:2:24794)
> at n.trigger
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:16:24070)
> at n [as trigger]
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:11:18800)
> at
> http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:6:727
> at Map.forEach (native)
> at n.processMultivaluedComponents
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:6:683)
> at n.save
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-b34005a588d596541889745a2e518025.js:6:1177)
> at n.send
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:15:25559)
> at n [as send]
> (http://172.27.21.64:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-5ac0512ea25105f32859ade26812f863.js:11:18800)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19291) User should be shown proper error message in file browser page
[ https://issues.apache.org/jira/browse/AMBARI-19291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB updated AMBARI-19291: - Resolution: Fixed Status: Resolved (was: Patch Available) > User should be shown proper error message in file browser page > -- > > Key: AMBARI-19291 > URL: https://issues.apache.org/jira/browse/AMBARI-19291 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19291_trunk.patch > > > User should be shown proper error message when user tries to navigate to a > hdfs folder and he doesn't have access on that folder. > Steps to reproduce : > 1) Try to import workflow from HDFS . > 2) In the file browser, click on a folder on which user doesn't have > permission > 3) Though api > /api/v1/views/Workflow%20Manager/versions/1.0.0/instances/WFD/resources/proxy/fileServices/fileops/listdir?path=%2Ftmp%2Fhive > fails with appropriate error, UI keeps on loading. > UI should handle this error and show appropriate message to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19306) User is not able to validate/submit the workflow after browsing workflow path
[ https://issues.apache.org/jira/browse/AMBARI-19306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB updated AMBARI-19306: - Resolution: Fixed Status: Resolved (was: Patch Available) > User is not able to validate/submit the workflow after browsing workflow path > - > > Key: AMBARI-19306 > URL: https://issues.apache.org/jira/browse/AMBARI-19306 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy >Priority: Critical > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19306_trunk.patch > > > User is not able to validate/submit the workflow after browsing workflow path. > Steps to reproduce : > 1) Import the workflow. (attaching the workflow) > 2) Click on submit. > 3) Browse the 'workflow path' using file browser. > 4) After selecting the workflow path, UI scrolling is not functional and > footer elements become non accessible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19368) Add common log rotation settings to ranger, ranger-kms, falcon
[ https://issues.apache.org/jira/browse/AMBARI-19368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-19368: --- Attachment: AMBARI-19368.patch > Add common log rotation settings to ranger, ranger-kms, falcon > -- > > Key: AMBARI-19368 > URL: https://issues.apache.org/jira/browse/AMBARI-19368 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19368.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19377) Update HDP-2.6 stack versions to match actual versions
Dmytro Grinenko created AMBARI-19377: Summary: Update HDP-2.6 stack versions to match actual versions Key: AMBARI-19377 URL: https://issues.apache.org/jira/browse/AMBARI-19377 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Priority: Critical Fix For: 2.5.0 On the stack definition, we should match the versions on-disk to match the versions that are in VDF Also, change the HDP-2.6/Spark2 description to: “Apache Spark 2.1 is a fast and general engine for large-scale data processing. This service is Technical Preview.” -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19377) Update HDP-2.6 stack versions to match actual versions
[ https://issues.apache.org/jira/browse/AMBARI-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-19377: - Status: Patch Available (was: In Progress) > Update HDP-2.6 stack versions to match actual versions > -- > > Key: AMBARI-19377 > URL: https://issues.apache.org/jira/browse/AMBARI-19377 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19377.patch > > > On the stack definition, we should match the versions on-disk to match the > versions that are in VDF > Also, change the HDP-2.6/Spark2 description to: > “Apache Spark 2.1 is a fast and general engine for large-scale data > processing. This service is Technical Preview.” -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19377) Update HDP-2.6 stack versions to match actual versions
[ https://issues.apache.org/jira/browse/AMBARI-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-19377: - Attachment: AMBARI-19377.patch > Update HDP-2.6 stack versions to match actual versions > -- > > Key: AMBARI-19377 > URL: https://issues.apache.org/jira/browse/AMBARI-19377 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19377.patch > > > On the stack definition, we should match the versions on-disk to match the > versions that are in VDF > Also, change the HDP-2.6/Spark2 description to: > “Apache Spark 2.1 is a fast and general engine for large-scale data > processing. This service is Technical Preview.” -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19377) Update HDP-2.6 stack versions to match actual versions
[ https://issues.apache.org/jira/browse/AMBARI-19377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-19377: - Fix Version/s: trunk > Update HDP-2.6 stack versions to match actual versions > -- > > Key: AMBARI-19377 > URL: https://issues.apache.org/jira/browse/AMBARI-19377 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19377.patch > > > On the stack definition, we should match the versions on-disk to match the > versions that are in VDF > Also, change the HDP-2.6/Spark2 description to: > “Apache Spark 2.1 is a fast and general engine for large-scale data > processing. This service is Technical Preview.” -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19352) Designer should always pick latest version for an action node
[ https://issues.apache.org/jira/browse/AMBARI-19352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15800621#comment-15800621 ] Hudson commented on AMBARI-19352: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #640 (See [https://builds.apache.org/job/Ambari-branch-2.5/640/]) AMBARI-19352. Designer should always pick latest version for an action (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6379b6e0bfe2e6cee91667c2f61721ee8097f48a]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow-json-importer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-config.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-version-settings.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow-importer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-version-settings.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow-xml-generator.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-errors.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/version-settings.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/design.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/coord-config.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/coord-version-settings.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/actionjob_hanlder.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/flow-designer.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/version-settings.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/bundle/bundle-xml-importer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/coordinator/coordinator-xml-importer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/schema-versions.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-version-settings.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/routes/design.js > Designer should always pick latest version for an action node > - > > Key: AMBARI-19352 > URL: https://issues.apache.org/jira/browse/AMBARI-19352 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19352_trunk.patch > > > Designer should always pick latest version for an action node and the actin > node settings should be specific to each workflow tab. > But as of now, designer is picking up old settings even for a new tab. > Steps to reproduce: > 1) Import a workflow with hive node and hive node version as 0.2. > 2) Open a new tab and add a hive node to the new workflow. > 3) Preview the xml for new workflow. Even the new workflow has hive version > as 0.2. Ideally it should be the latest version 0.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19352) Designer should always pick latest version for an action node
[ https://issues.apache.org/jira/browse/AMBARI-19352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15800632#comment-15800632 ] Hudson commented on AMBARI-19352: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6357 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6357/]) AMBARI-19352. Designer should always pick latest version for an action (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dcffaeda04ff0348bcb1927f4e1de6a045ddf93a]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-config.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/coord-config.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/bundle/bundle-xml-importer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/design.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/version-settings.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/flow-designer.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/schema-versions.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow-xml-generator.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/routes/design.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-version-settings.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/coord-version-settings.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/coordinator/coordinator-xml-importer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow-importer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-errors.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow-json-importer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/version-settings.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-config.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-version-settings.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/actionjob_hanlder.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-version-settings.js > Designer should always pick latest version for an action node > - > > Key: AMBARI-19352 > URL: https://issues.apache.org/jira/browse/AMBARI-19352 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19352_trunk.patch > > > Designer should always pick latest version for an action node and the actin > node settings should be specific to each workflow tab. > But as of now, designer is picking up old settings even for a new tab. > Steps to reproduce: > 1) Import a workflow with hive node and hive node version as 0.2. > 2) Open a new tab and add a hive node to the new workflow. > 3) Preview the xml for new workflow. Even the new workflow has hive version > as 0.2. Ideally it should be the latest version 0.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19376) translation from English to Chinese
[ https://issues.apache.org/jira/browse/AMBARI-19376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xlsong updated AMBARI-19376: Attachment: messages.patch Committed to branch-2.2.1 in ambari-web/app/ > translation from English to Chinese > --- > > Key: AMBARI-19376 > URL: https://issues.apache.org/jira/browse/AMBARI-19376 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-web >Affects Versions: trunk, 2.2.1 >Reporter: xlsong > Labels: features > Fix For: 2.2.1 > > Attachments: messages.patch > > > translation of pages from English to Chinese -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19376) translation from English to Chinese
[ https://issues.apache.org/jira/browse/AMBARI-19376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15800677#comment-15800677 ] Yao Lei commented on AMBARI-19376: -- 个人觉得可以保留原始的message.js文件，同时提供一份汉化的message.zh.js文件，让程序能够自由切换语言比较好 > translation from English to Chinese > --- > > Key: AMBARI-19376 > URL: https://issues.apache.org/jira/browse/AMBARI-19376 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-web >Affects Versions: trunk, 2.2.1 >Reporter: xlsong > Labels: features > Fix For: 2.2.1 > > Attachments: messages.patch > > > translation of pages from English to Chinese -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17470) Refactor Ambari service def configurations for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-17470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797528#comment-15797528 ] Hudson commented on AMBARI-17470: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #630 (See [https://builds.apache.org/job/Ambari-branch-2.5/630/]) AMBARI-17470 Refactor Ambari service def configurations for Zeppelin (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8542c5c47fdb20441aff7a9a0f9e451709a1f2b7]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/metainfo.xml * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-log4j-properties.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/ZEPPELIN/configuration/zeppelin-env.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-shiro-ini.xml Revert "AMBARI-17470 Refactor Ambari service def configurations for (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f9d54855d3162d534b0baecdf0cb196e6bc0e01d]) * (delete) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-shiro-ini.xml * (delete) ambari-server/src/main/resources/stacks/HDP/2.6/services/ZEPPELIN/configuration/zeppelin-env.xml * (delete) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml * (delete) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-log4j-properties.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py > Refactor Ambari service def configurations for Zeppelin > --- > > Key: AMBARI-17470 > URL: https://issues.apache.org/jira/browse/AMBARI-17470 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Yesha Vora >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-17470-branch-2.5-v1.patch, > AMBARI-17470-branch-2.5-v2.patch > > > Zeppelin has below configuration files : > * zeppelin-env.sh > * zeppelin-site.xml > * log4j.properties > Amabri UI shows zeppelin-env.sh and zeppelin-site.xml in config page. It > should also add log4j.properties file in Ambari config page. > - Move shiro.ini and log4j.properties out of zeppelin-env configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19334) Need to highlight XML tags in preview xml viewer
[ https://issues.apache.org/jira/browse/AMBARI-19334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797527#comment-15797527 ] Hudson commented on AMBARI-19334: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #630 (See [https://builds.apache.org/job/Ambari-branch-2.5/630/]) AMBARI-19334 XML formatting while workflow preview (Venkata Sairam via (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dcb96e93a42dfb27c1a7fed52ae1106299d1ed60]) * (edit) contrib/views/wfmanager/src/main/resources/ui/ember-cli-build.js > Need to highlight XML tags in preview xml viewer > > > Key: AMBARI-19334 > URL: https://issues.apache.org/jira/browse/AMBARI-19334 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19334_branch_2.5.patch > > > Need to highlight XML tags in preview xml viewer. As of now only xml > structure is maintained. Highlighting individual tags would provide better > insight for the preview xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19335) Need to support permission in string format for FS action node
[ https://issues.apache.org/jira/browse/AMBARI-19335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797526#comment-15797526 ] Hudson commented on AMBARI-19335: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #630 (See [https://builds.apache.org/job/Ambari-branch-2.5/630/]) AMBARI-19335 To support permission in string format for FS action node (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a6fedf46efb54139c9d4b2dffeef8e8b95ec058c]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/actionjob_hanlder.js > Need to support permission in string format for FS action node > -- > > Key: AMBARI-19335 > URL: https://issues.apache.org/jira/browse/AMBARI-19335 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19335_branch_2.5.patch > > > Need to add support for FS action nodes for identifying permission in string > format. Currently only number format is supported. > If user imports a workflow with action node where permission is in string > format, then permission is not set in the workflow designer view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19335) Need to support permission in string format for FS action node
[ https://issues.apache.org/jira/browse/AMBARI-19335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797566#comment-15797566 ] Hudson commented on AMBARI-19335: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6348 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6348/]) AMBARI-19335 To support permission in string format for FS action node (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=34bc40ece5b0dc6eed311ecccf7a29f822db1879]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/actionjob_hanlder.js > Need to support permission in string format for FS action node > -- > > Key: AMBARI-19335 > URL: https://issues.apache.org/jira/browse/AMBARI-19335 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19335_branch_2.5.patch > > > Need to add support for FS action nodes for identifying permission in string > format. Currently only number format is supported. > If user imports a workflow with action node where permission is in string > format, then permission is not set in the workflow designer view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19334) Need to highlight XML tags in preview xml viewer
[ https://issues.apache.org/jira/browse/AMBARI-19334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797567#comment-15797567 ] Hudson commented on AMBARI-19334: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6348 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6348/]) AMBARI-19334 XML formatting while workflow preview (Venkata Sairam via (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4c12e5de8040d0a32f6d0b0eb8f574ba10d5144b]) * (edit) contrib/views/wfmanager/src/main/resources/ui/ember-cli-build.js > Need to highlight XML tags in preview xml viewer > > > Key: AMBARI-19334 > URL: https://issues.apache.org/jira/browse/AMBARI-19334 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19334_branch_2.5.patch > > > Need to highlight XML tags in preview xml viewer. As of now only xml > structure is maintained. Highlighting individual tags would provide better > insight for the preview xml. -- 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=15797592#comment-15797592 ] Dmytro Sen commented on AMBARI-19338: - The failures aren't related to this patch > 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: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19338_2.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-19352) Designer should always pick latest version for an action node
[ https://issues.apache.org/jira/browse/AMBARI-19352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19352: - Attachment: AMBARI-19352_trunk.patch > Designer should always pick latest version for an action node > - > > Key: AMBARI-19352 > URL: https://issues.apache.org/jira/browse/AMBARI-19352 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19352_trunk.patch > > > Designer should always pick latest version for an action node and the actin > node settings should be specific to each workflow tab. > But as of now, designer is picking up old settings even for a new tab. > Steps to reproduce: > 1) Import a workflow with hive node and hive node version as 0.2. > 2) Open a new tab and add a hive node to the new workflow. > 3) Preview the xml for new workflow. Even the new workflow has hive version > as 0.2. Ideally it should be the latest version 0.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19352) Designer should always pick latest version for an action node
[ https://issues.apache.org/jira/browse/AMBARI-19352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19352: - Status: Patch Available (was: Open) > Designer should always pick latest version for an action node > - > > Key: AMBARI-19352 > URL: https://issues.apache.org/jira/browse/AMBARI-19352 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19352_trunk.patch > > > Designer should always pick latest version for an action node and the actin > node settings should be specific to each workflow tab. > But as of now, designer is picking up old settings even for a new tab. > Steps to reproduce: > 1) Import a workflow with hive node and hive node version as 0.2. > 2) Open a new tab and add a hive node to the new workflow. > 3) Preview the xml for new workflow. Even the new workflow has hive version > as 0.2. Ideally it should be the latest version 0.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-19354) Invalid message is shown after saving the workflow
[ https://issues.apache.org/jira/browse/AMBARI-19354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj reassigned AMBARI-19354: Assignee: Padma Priya Nagaraj > Invalid message is shown after saving the workflow > -- > > Key: AMBARI-19354 > URL: https://issues.apache.org/jira/browse/AMBARI-19354 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > > Invalid message is shown after saving the workflow. The message "Transition > deleted Undo" is shown even when no changes are made to the workflow. > Steps to reproduce : > 1) Import a workflow. > 2) Click on one of the action nodes and open settings. > 3) Without making any change, click on 'Save' > After saving, message "Transition deleted Undo" is shown to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19345) Storm REST metrics are not available when Storm UI is running in HTTPS
[
https://issues.apache.org/jira/browse/AMBARI-19345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797699#comment-15797699
]
Rahul Pathak commented on AMBARI-19345:
---
I was able to workaround STORM_UI_SERVER and Storm Server Process by setting
ui.port to same as ui.https.port and modifying AlertDefinition for
STORM_UI_SERVER as below.
{code}
{
"AlertDefinition" : {
"cluster_name" : "h1",
"component_name" : "STORM_UI_SERVER",
"description" : null,
"enabled" : true,
"help_url" : null,
"id" : 153,
"ignore_host" : false,
"interval" : 1,
"label" : "Storm Web UI",
"name" : "storm_webui",
"repeat_tolerance" : 1,
"repeat_tolerance_enabled" : false,
"scope" : "ANY",
"service_name" : "STORM",
"source" : {
"reporting" : {
"critical" : {
"text" : "Connection failed to {1} ({3})"
},
"warning" : {
"text" : "HTTP {0} response from {1} in {2:.3f}s ({3})"
},
"ok" : {
"text" : "HTTP {0} response in {2:.3f}s"
}
},
"type" : "WEB",
"uri" : {
"kerberos_principal" : "{{storm-env/storm_ui_principal_name}}",
"connection_timeout" : 5.0,
"kerberos_keytab" : "{{storm-env/storm_ui_keytab}}",
"http" : "{{storm-site/ui.port}}",
"https_property_value" : "HTTPS_ONLY",
"default_port" : 0.0,
"https" : "{{storm-site/ui.https.port}}"
}
}
}
}
{code}
For REST metrics I tried changing
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/STORM/0.10.0/metrics.json
however I am not sure how to add truststore password and file.
> Storm REST metrics are not available when Storm UI is running in HTTPS
> --
>
> Key: AMBARI-19345
> URL: https://issues.apache.org/jira/browse/AMBARI-19345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.1, 2.4.2
>Reporter: Rahul Pathak
> Attachments: storm summary.png
>
>
> Enable storm ui for https as per below document.
> http://storm.apache.org/releases/1.0.1/SECURITY.html
> Storm UI works fine and connect successfully using https.
> However ambari alert for storm UI breaks, also ambari server keeps trying to
> fetch REST metrics using http instead of https.
> !storm summary.png!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19345) Storm REST metrics are not available when Storm UI is running in HTTPS
[
https://issues.apache.org/jira/browse/AMBARI-19345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797701#comment-15797701
]
Rahul Pathak commented on AMBARI-19345:
---
I was able to workaround STORM_UI_SERVER and Storm Server Process by setting
ui.port to same as ui.https.port and modifying AlertDefinition for
STORM_UI_SERVER as below.
{code}
{
"AlertDefinition" : {
"cluster_name" : "h1",
"component_name" : "STORM_UI_SERVER",
"description" : null,
"enabled" : true,
"help_url" : null,
"id" : 153,
"ignore_host" : false,
"interval" : 1,
"label" : "Storm Web UI",
"name" : "storm_webui",
"repeat_tolerance" : 1,
"repeat_tolerance_enabled" : false,
"scope" : "ANY",
"service_name" : "STORM",
"source" : {
"reporting" : {
"critical" : {
"text" : "Connection failed to {1} ({3})"
},
"warning" : {
"text" : "HTTP {0} response from {1} in {2:.3f}s ({3})"
},
"ok" : {
"text" : "HTTP {0} response in {2:.3f}s"
}
},
"type" : "WEB",
"uri" : {
"kerberos_principal" : "{{storm-env/storm_ui_principal_name}}",
"connection_timeout" : 5.0,
"kerberos_keytab" : "{{storm-env/storm_ui_keytab}}",
"http" : "{{storm-site/ui.port}}",
"https_property_value" : "HTTPS_ONLY",
"default_port" : 0.0,
"https" : "{{storm-site/ui.https.port}}"
}
}
}
}
{code}
For REST metrics I tried changing
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/STORM/0.10.0/metrics.json
however I am not sure how to add truststore password and file.
> Storm REST metrics are not available when Storm UI is running in HTTPS
> --
>
> Key: AMBARI-19345
> URL: https://issues.apache.org/jira/browse/AMBARI-19345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.1, 2.4.2
>Reporter: Rahul Pathak
> Attachments: storm summary.png
>
>
> Enable storm ui for https as per below document.
> http://storm.apache.org/releases/1.0.1/SECURITY.html
> Storm UI works fine and connect successfully using https.
> However ambari alert for storm UI breaks, also ambari server keeps trying to
> fetch REST metrics using http instead of https.
> !storm summary.png!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-19345) Storm REST metrics are not available when Storm UI is running in HTTPS
[
https://issues.apache.org/jira/browse/AMBARI-19345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797699#comment-15797699
]
Rahul Pathak edited comment on AMBARI-19345 at 1/4/17 9:08 AM:
---
I was able to workaround STORM_UI_SERVER and Storm Server Process alert by
setting ui.port to same as ui.https.port and modifying AlertDefinition for
STORM_UI_SERVER as below.
{code}
{
"AlertDefinition" : {
"cluster_name" : "h1",
"component_name" : "STORM_UI_SERVER",
"description" : null,
"enabled" : true,
"help_url" : null,
"id" : 153,
"ignore_host" : false,
"interval" : 1,
"label" : "Storm Web UI",
"name" : "storm_webui",
"repeat_tolerance" : 1,
"repeat_tolerance_enabled" : false,
"scope" : "ANY",
"service_name" : "STORM",
"source" : {
"reporting" : {
"critical" : {
"text" : "Connection failed to {1} ({3})"
},
"warning" : {
"text" : "HTTP {0} response from {1} in {2:.3f}s ({3})"
},
"ok" : {
"text" : "HTTP {0} response in {2:.3f}s"
}
},
"type" : "WEB",
"uri" : {
"kerberos_principal" : "{{storm-env/storm_ui_principal_name}}",
"connection_timeout" : 5.0,
"kerberos_keytab" : "{{storm-env/storm_ui_keytab}}",
"http" : "{{storm-site/ui.port}}",
"https_property_value" : "HTTPS_ONLY",
"default_port" : 0.0,
"https" : "{{storm-site/ui.https.port}}"
}
}
}
}
{code}
For REST metrics I tried changing
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/STORM/0.10.0/metrics.json
however I am not sure how to add trust store password and file.
was (Author: rahulp):
I was able to workaround STORM_UI_SERVER and Storm Server Process by setting
ui.port to same as ui.https.port and modifying AlertDefinition for
STORM_UI_SERVER as below.
{code}
{
"AlertDefinition" : {
"cluster_name" : "h1",
"component_name" : "STORM_UI_SERVER",
"description" : null,
"enabled" : true,
"help_url" : null,
"id" : 153,
"ignore_host" : false,
"interval" : 1,
"label" : "Storm Web UI",
"name" : "storm_webui",
"repeat_tolerance" : 1,
"repeat_tolerance_enabled" : false,
"scope" : "ANY",
"service_name" : "STORM",
"source" : {
"reporting" : {
"critical" : {
"text" : "Connection failed to {1} ({3})"
},
"warning" : {
"text" : "HTTP {0} response from {1} in {2:.3f}s ({3})"
},
"ok" : {
"text" : "HTTP {0} response in {2:.3f}s"
}
},
"type" : "WEB",
"uri" : {
"kerberos_principal" : "{{storm-env/storm_ui_principal_name}}",
"connection_timeout" : 5.0,
"kerberos_keytab" : "{{storm-env/storm_ui_keytab}}",
"http" : "{{storm-site/ui.port}}",
"https_property_value" : "HTTPS_ONLY",
"default_port" : 0.0,
"https" : "{{storm-site/ui.https.port}}"
}
}
}
}
{code}
For REST metrics I tried changing
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/STORM/0.10.0/metrics.json
however I am not sure how to add truststore password and file.
> Storm REST metrics are not available when Storm UI is running in HTTPS
> --
>
> Key: AMBARI-19345
> URL: https://issues.apache.org/jira/browse/AMBARI-19345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.1, 2.4.2
>Reporter: Rahul Pathak
> Attachments: storm summary.png
>
>
> Enable storm ui for https as per below document.
> http://storm.apache.org/releases/1.0.1/SECURITY.html
> Storm UI works fine and connect successfully using https.
> However ambari alert for storm UI breaks, also ambari server keeps trying to
> fetch REST metrics using http instead of https.
> !storm summary.png!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-19345) Storm REST metrics are not available when Storm UI is running in HTTPS
[
https://issues.apache.org/jira/browse/AMBARI-19345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Pathak updated AMBARI-19345:
--
Comment: was deleted
(was: I was able to workaround STORM_UI_SERVER and Storm Server Process by
setting ui.port to same as ui.https.port and modifying AlertDefinition for
STORM_UI_SERVER as below.
{code}
{
"AlertDefinition" : {
"cluster_name" : "h1",
"component_name" : "STORM_UI_SERVER",
"description" : null,
"enabled" : true,
"help_url" : null,
"id" : 153,
"ignore_host" : false,
"interval" : 1,
"label" : "Storm Web UI",
"name" : "storm_webui",
"repeat_tolerance" : 1,
"repeat_tolerance_enabled" : false,
"scope" : "ANY",
"service_name" : "STORM",
"source" : {
"reporting" : {
"critical" : {
"text" : "Connection failed to {1} ({3})"
},
"warning" : {
"text" : "HTTP {0} response from {1} in {2:.3f}s ({3})"
},
"ok" : {
"text" : "HTTP {0} response in {2:.3f}s"
}
},
"type" : "WEB",
"uri" : {
"kerberos_principal" : "{{storm-env/storm_ui_principal_name}}",
"connection_timeout" : 5.0,
"kerberos_keytab" : "{{storm-env/storm_ui_keytab}}",
"http" : "{{storm-site/ui.port}}",
"https_property_value" : "HTTPS_ONLY",
"default_port" : 0.0,
"https" : "{{storm-site/ui.https.port}}"
}
}
}
}
{code}
For REST metrics I tried changing
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/STORM/0.10.0/metrics.json
however I am not sure how to add truststore password and file.)
> Storm REST metrics are not available when Storm UI is running in HTTPS
> --
>
> Key: AMBARI-19345
> URL: https://issues.apache.org/jira/browse/AMBARI-19345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.1, 2.4.2
>Reporter: Rahul Pathak
> Attachments: storm summary.png
>
>
> Enable storm ui for https as per below document.
> http://storm.apache.org/releases/1.0.1/SECURITY.html
> Storm UI works fine and connect successfully using https.
> However ambari alert for storm UI breaks, also ambari server keeps trying to
> fetch REST metrics using http instead of https.
> !storm summary.png!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19354) Invalid message is shown after saving the workflow
[ https://issues.apache.org/jira/browse/AMBARI-19354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19354: - Attachment: AMBARI-19354_trunk.patch > Invalid message is shown after saving the workflow > -- > > Key: AMBARI-19354 > URL: https://issues.apache.org/jira/browse/AMBARI-19354 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19354_trunk.patch > > > Invalid message is shown after saving the workflow. The message "Transition > deleted Undo" is shown even when no changes are made to the workflow. > Steps to reproduce : > 1) Import a workflow. > 2) Click on one of the action nodes and open settings. > 3) Without making any change, click on 'Save' > After saving, message "Transition deleted Undo" is shown to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19354) Invalid message is shown after saving the workflow
[ https://issues.apache.org/jira/browse/AMBARI-19354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19354: - Status: Patch Available (was: Open) > Invalid message is shown after saving the workflow > -- > > Key: AMBARI-19354 > URL: https://issues.apache.org/jira/browse/AMBARI-19354 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19354_trunk.patch > > > Invalid message is shown after saving the workflow. The message "Transition > deleted Undo" is shown even when no changes are made to the workflow. > Steps to reproduce : > 1) Import a workflow. > 2) Click on one of the action nodes and open settings. > 3) Without making any change, click on 'Save' > After saving, message "Transition deleted Undo" is shown to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19336) User should be prompted to enter valid workflow xml file name while Submit/Validate
[
https://issues.apache.org/jira/browse/AMBARI-19336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Belliraj HB updated AMBARI-19336:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> User should be prompted to enter valid workflow xml file name while
> Submit/Validate
> ---
>
> Key: AMBARI-19336
> URL: https://issues.apache.org/jira/browse/AMBARI-19336
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
> Labels: WFD
> Fix For: 2.5.0
>
> Attachments: AMBARI-19336_trunk.patch
>
>
> User should be prompted to enter valid workflow xml file name while
> Submit/Validate
> As of now user can provide any file name. Also user is not restricted even if
> he provides a directory structure.
> For example if user provides xml file as /tmp/testPath, a file 'testPath' is
> getting created under directory /tmp/
> This file has permission : '-rw-r--r--'
> Due to this restricted permission, below issues are faced :
> Issue 1 : User is not able to import the saved workflow.
> Issue 2 : From the dashboard, if user selects any instance of the workflow
> and decides to edit the workflow, user is shown with below error :
> {code}
> There is some problem while importing.Please try again. Hide Log
> org.apache.hadoop.security.AccessControlException: Permission denied:
> user=admin, access=EXECUTE,
> inode="/oozieex/mr-ex1/workflow.xml":admin:hadoop:-rw-r--r--
> at sun.reflect.GeneratedConstructorAccessor263.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
> at
> org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.toIOException(WebHdfsFileSystem.java:390)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.access$600(WebHdfsFileSystem.java:90)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.shouldRetry(WebHdfsFileSystem.java:661)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.runWithRetry(WebHdfsFileSystem.java:627)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.access$100(WebHdfsFileSystem.java:463)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner$1.run(WebHdfsFileSystem.java:492)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.run(WebHdfsFileSystem.java:488)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$UnresolvedUrlOpener.connect(WebHdfsFileSystem.java:1217)
> at
> org.apache.hadoop.hdfs.web.ByteRangeInputStream.openInputStream(ByteRangeInputStream.java:121)
> at
> org.apache.hadoop.hdfs.web.ByteRangeInputStream.getInputStream(ByteRangeInputStream.java:105)
> at
> org.apache.hadoop.hdfs.web.ByteRangeInputStream.(ByteRangeInputStream.java:90)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$OffsetUrlInputStream.(WebHdfsFileSystem.java:1274)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.open(WebHdfsFileSystem.java:1188)
> at org.apache.hadoop.fs.FileSystem.open(FileSystem.java:767)
> at org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:324)
> at org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:322)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:397)
> at org.apache.ambari.view.utils.hdfs.HdfsApi.open(HdfsApi.java:322)
> at org.apache.oozie.ambari.view.HDFSFileUtils.read(HDFSFileUtils.java:57)
> at
> org.apache.oozie.ambari.view.WorkflowFilesService.readWorkflowXml(WorkflowFilesService.java:54)
> at
> org.apache.oozie.ambari.view.OozieProxyImpersonator.readWorkflowXxml(OozieProxyImpersonator.java:400)
> at sun.reflect.GeneratedMethodAccessor373.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(
[jira] [Created] (AMBARI-19356) Change type of fields for Ambari SNMP alert trap
Dmytro Sen created AMBARI-19356: --- Summary: Change type of fields for Ambari SNMP alert trap Key: AMBARI-19356 URL: https://issues.apache.org/jira/browse/AMBARI-19356 Project: Ambari Issue Type: Bug Components: alerts Affects Versions: 2.5.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.5.0 SNMPv2-SMI::enterprises.18060.16.1.1.1.1 = STRING: "6" - This needs to be sent as an INTEGER SNMPv2-SMI::enterprises.18060.16.1.1.1.6 = STRING: "3" - This needs to be sent as an INTEGER -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19356) Change type of fields for Ambari SNMP alert trap
[ https://issues.apache.org/jira/browse/AMBARI-19356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19356: Status: Patch Available (was: Open) > Change type of fields for Ambari SNMP alert trap > > > Key: AMBARI-19356 > URL: https://issues.apache.org/jira/browse/AMBARI-19356 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.5.0 > > Attachments: AMBARI-19356.patch > > > SNMPv2-SMI::enterprises.18060.16.1.1.1.1 = STRING: "6" - This needs to be > sent as an INTEGER > SNMPv2-SMI::enterprises.18060.16.1.1.1.6 = STRING: "3" - This needs to be > sent as an INTEGER -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19356) Change type of fields for Ambari SNMP alert trap
[ https://issues.apache.org/jira/browse/AMBARI-19356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19356: Attachment: AMBARI-19356.patch > Change type of fields for Ambari SNMP alert trap > > > Key: AMBARI-19356 > URL: https://issues.apache.org/jira/browse/AMBARI-19356 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.5.0 > > Attachments: AMBARI-19356.patch > > > SNMPv2-SMI::enterprises.18060.16.1.1.1.1 = STRING: "6" - This needs to be > sent as an INTEGER > SNMPv2-SMI::enterprises.18060.16.1.1.1.6 = STRING: "3" - This needs to be > sent as an INTEGER -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-7811) Integrate ElasticSearch, LogStash and Kibana with Ambari
[ https://issues.apache.org/jira/browse/AMBARI-7811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798000#comment-15798000 ] Phakin Cheangkrachange commented on AMBARI-7811: May I ask how did you integrate elasticsearch to Ambari? Did you use any public Ambari's elasticsearch services on Github? > Integrate ElasticSearch, LogStash and Kibana with Ambari > > > Key: AMBARI-7811 > URL: https://issues.apache.org/jira/browse/AMBARI-7811 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Mingjiang Shi > > A hadoop cluster has many nodes, many services and many components, which > generates many logs on different machines. It would be a good idea to search > and view those logs at a central place. > The ELK stack (elastic search, logstash and kibana) is the one of the best > open source log collection, storage and search solution. By integrating ELK > with Ambari, user could optionally install ELK when deploying a cluster. > This will enable user to search and view all the logs at free. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19357) Flume metrics can't show if host name of flume agent is not lowercase
Yao Lei created AMBARI-19357: Summary: Flume metrics can't show if host name of flume agent is not lowercase Key: AMBARI-19357 URL: https://issues.apache.org/jira/browse/AMBARI-19357 Project: Ambari Issue Type: Bug Affects Versions: 2.4.2 Reporter: Yao Lei -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19358) UI to add config ...2.6/HIVE/configuration/hive-env.xml 'enable_heap_dump' config in smart configs page.
Aleksandr Kovalenko created AMBARI-19358: Summary: UI to add config ...2.6/HIVE/configuration/hive-env.xml 'enable_heap_dump' config in smart configs page. Key: AMBARI-19358 URL: https://issues.apache.org/jira/browse/AMBARI-19358 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.4.1 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.5.0 UI needs to add the config 'enable_heap_dump' in Smart configs panel, so that its easy for user to enable/disable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Summary: Flume metrics can't show if hostname of flume agent is not lowercase (was: Flume metrics can't show if host name of flume agent is not lowercase) > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19340) Infra Solr Client logging is not working
[
https://issues.apache.org/jira/browse/AMBARI-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-19340.
---
Resolution: Fixed
> Infra Solr Client logging is not working
>
>
> Key: AMBARI-19340
> URL: https://issues.apache.org/jira/browse/AMBARI-19340
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19340.patch
>
>
> If we run any command for infra-solr-client, we got the following output:
> {code:java}
> log4j:WARN Failed to set property [maxBackupIndex] to value "".
> log4j:ERROR [] is not in proper int form.
> log4j:ERROR [MB] not in expected format.
> java.lang.NumberFormatException: For input string: ""
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Long.parseLong(Long.java:601)
> at java.lang.Long.valueOf(Long.java:803)
> at
> org.apache.log4j.helpers.OptionConverter.toFileSize(OptionConverter.java:280)
> at
> org.apache.log4j.RollingFileAppender.setMaxFileSize(RollingFileAppender.java:260)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.java:245)
> at
> org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.java:204)
> at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:169)
> at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
> at
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
> at
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
> at
> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
> at
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)
> at org.apache.log4j.LogManager.(LogManager.java:127)
> at
> org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:64)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:270)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281)
> at
> org.apache.ambari.logsearch.solr.AmbariSolrCloudCLI.(AmbariSolrCloudCLI.java:38)
> {code}
> therefore logging is not working for infra-solr-client.
> This is regression for AMBARI-19323
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19340) Infra Solr Client logging is not working
[
https://issues.apache.org/jira/browse/AMBARI-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798033#comment-15798033
]
Olivér Szabó commented on AMBARI-19340:
---
committed to trunk:
{code:java}
commit ff222441e75c2feff3b93aee12560f1e624d3189
Author: oleewere
Date: Tue Jan 3 17:59:57 2017 +0100
AMBARI-19340. Infra Solr Client logging is not working (oleewere)
Change-Id: I404ffdaf5b95cd28b0f992dc859376dec9f1bd33
{code}
committed to branch-2.5:
{code:java}
commit c7c207d9764d1b501c111ec166592835b70c45bb
Author: oleewere
Date: Tue Jan 3 17:59:57 2017 +0100
AMBARI-19340. Infra Solr Client logging is not working (oleewere)
Change-Id: I404ffdaf5b95cd28b0f992dc859376dec9f1bd33
{code}
> Infra Solr Client logging is not working
>
>
> Key: AMBARI-19340
> URL: https://issues.apache.org/jira/browse/AMBARI-19340
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19340.patch
>
>
> If we run any command for infra-solr-client, we got the following output:
> {code:java}
> log4j:WARN Failed to set property [maxBackupIndex] to value "".
> log4j:ERROR [] is not in proper int form.
> log4j:ERROR [MB] not in expected format.
> java.lang.NumberFormatException: For input string: ""
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Long.parseLong(Long.java:601)
> at java.lang.Long.valueOf(Long.java:803)
> at
> org.apache.log4j.helpers.OptionConverter.toFileSize(OptionConverter.java:280)
> at
> org.apache.log4j.RollingFileAppender.setMaxFileSize(RollingFileAppender.java:260)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.java:245)
> at
> org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.java:204)
> at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:169)
> at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
> at
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
> at
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
> at
> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
> at
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)
> at org.apache.log4j.LogManager.(LogManager.java:127)
> at
> org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:64)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:270)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281)
> at
> org.apache.ambari.logsearch.solr.AmbariSolrCloudCLI.(AmbariSolrCloudCLI.java:38)
> {code}
> therefore logging is not working for infra-solr-client.
> This is regression for AMBARI-19323
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: For example, > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > > For example, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19358) UI to add config ...2.6/HIVE/configuration/hive-env.xml 'enable_heap_dump' config in smart configs page.
[ https://issues.apache.org/jira/browse/AMBARI-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-19358: - Attachment: AMBARI-19358.patch > UI to add config ...2.6/HIVE/configuration/hive-env.xml 'enable_heap_dump' > config in smart configs page. > > > Key: AMBARI-19358 > URL: https://issues.apache.org/jira/browse/AMBARI-19358 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19358.patch > > > UI needs to add the config 'enable_heap_dump' in Smart configs panel, so that > its easy for user to enable/disable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. (was: For example,) > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19356) Change type of fields for Ambari SNMP alert trap
[
https://issues.apache.org/jira/browse/AMBARI-19356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798060#comment-15798060
]
Hadoop QA commented on AMBARI-19356:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845512/AMBARI-19356.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9881//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9881//console
This message is automatically generated.
> Change type of fields for Ambari SNMP alert trap
>
>
> Key: AMBARI-19356
> URL: https://issues.apache.org/jira/browse/AMBARI-19356
> Project: Ambari
> Issue Type: Bug
> Components: alerts
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-19356.patch
>
>
> SNMPv2-SMI::enterprises.18060.16.1.1.1.1 = STRING: "6" - This needs to be
> sent as an INTEGER
> SNMPv2-SMI::enterprises.18060.16.1.1.1.6 = STRING: "3" - This needs to be
> sent as an INTEGER
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19358) UI to add config ...2.6/HIVE/configuration/hive-env.xml 'enable_heap_dump' config in smart configs page.
[ https://issues.apache.org/jira/browse/AMBARI-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798064#comment-15798064 ] Aleksandr Kovalenko commented on AMBARI-19358: -- Tested manually, results of running UI unit tests: 19859 passing (20s) 153 pending > UI to add config ...2.6/HIVE/configuration/hive-env.xml 'enable_heap_dump' > config in smart configs page. > > > Key: AMBARI-19358 > URL: https://issues.apache.org/jira/browse/AMBARI-19358 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19358.patch > > > UI needs to add the config 'enable_heap_dump' in Smart configs panel, so that > its easy for user to enable/disable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19358) UI to add config ...2.6/HIVE/configuration/hive-env.xml 'enable_heap_dump' config in smart configs page.
[ https://issues.apache.org/jira/browse/AMBARI-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798066#comment-15798066 ] Aleksandr Kovalenko commented on AMBARI-19358: -- committed to trunk and branch-2.5 > UI to add config ...2.6/HIVE/configuration/hive-env.xml 'enable_heap_dump' > config in smart configs page. > > > Key: AMBARI-19358 > URL: https://issues.apache.org/jira/browse/AMBARI-19358 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19358.patch > > > UI needs to add the config 'enable_heap_dump' in Smart configs panel, so that > its easy for user to enable/disable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally for the reason that hostnames are displayed in Ambari is was:If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally for the reason that hostnames are displayed in > Ambari is -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase,so we will not get any record. was: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally for the reason that hostnames are displayed in Ambari is > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname displayed in > ambari ,but the hostname in METRIC_RECORD is not lowcase,so we will not get > any record. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19359) UI elements misalignment in dashboard screen of WFD
venkat created AMBARI-19359: --- Summary: UI elements misalignment in dashboard screen of WFD Key: AMBARI-19359 URL: https://issues.apache.org/jira/browse/AMBARI-19359 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: venkat Fix For: 2.5.0 Checkboxes alignment in dashboard screen for workflows, coordinators, bundles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record. was: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase,so we will not get any record. > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname displayed in > ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached > picture),so we will not get any record. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-19359) UI elements misalignment in dashboard screen of WFD
[ https://issues.apache.org/jira/browse/AMBARI-19359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat reassigned AMBARI-19359: --- Assignee: venkat > UI elements misalignment in dashboard screen of WFD > --- > > Key: AMBARI-19359 > URL: https://issues.apache.org/jira/browse/AMBARI-19359 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > > Checkboxes alignment in dashboard screen for workflows, coordinators, bundles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Attachment: uppercase agent hostname .png > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Attachments: uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname displayed in > ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached > picture),so we will not get any record. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19359) UI elements misalignment in dashboard screen of WFD
[ https://issues.apache.org/jira/browse/AMBARI-19359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19359: Status: Patch Available (was: In Progress) > UI elements misalignment in dashboard screen of WFD > --- > > Key: AMBARI-19359 > URL: https://issues.apache.org/jira/browse/AMBARI-19359 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > > Checkboxes alignment in dashboard screen for workflows, coordinators, bundles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19340) Infra Solr Client logging is not working
[
https://issues.apache.org/jira/browse/AMBARI-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798114#comment-15798114
]
Hudson commented on AMBARI-19340:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #631 (See
[https://builds.apache.org/job/Ambari-branch-2.5/631/])
AMBARI-19340. Infra Solr Client logging is not working (oleewere) (oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c7c207d9764d1b501c111ec166592835b70c45bb])
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/properties/solr-client-log4j.properties.j2
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/solr_cloud_util.py
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/scripts/setup_infra_solr.py
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/scripts/params.py
> Infra Solr Client logging is not working
>
>
> Key: AMBARI-19340
> URL: https://issues.apache.org/jira/browse/AMBARI-19340
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19340.patch
>
>
> If we run any command for infra-solr-client, we got the following output:
> {code:java}
> log4j:WARN Failed to set property [maxBackupIndex] to value "".
> log4j:ERROR [] is not in proper int form.
> log4j:ERROR [MB] not in expected format.
> java.lang.NumberFormatException: For input string: ""
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Long.parseLong(Long.java:601)
> at java.lang.Long.valueOf(Long.java:803)
> at
> org.apache.log4j.helpers.OptionConverter.toFileSize(OptionConverter.java:280)
> at
> org.apache.log4j.RollingFileAppender.setMaxFileSize(RollingFileAppender.java:260)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.java:245)
> at
> org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.java:204)
> at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:169)
> at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
> at
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
> at
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
> at
> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
> at
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)
> at org.apache.log4j.LogManager.(LogManager.java:127)
> at
> org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:64)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:270)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281)
> at
> org.apache.ambari.logsearch.solr.AmbariSolrCloudCLI.(AmbariSolrCloudCLI.java:38)
> {code}
> therefore logging is not working for infra-solr-client.
> This is regression for AMBARI-19323
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19359) UI elements misalignment in dashboard screen of WFD
[ https://issues.apache.org/jira/browse/AMBARI-19359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19359: Attachment: AMBARI-19339_branch_2.5.patch > UI elements misalignment in dashboard screen of WFD > --- > > Key: AMBARI-19359 > URL: https://issues.apache.org/jira/browse/AMBARI-19359 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-19339_branch_2.5.patch > > > Checkboxes alignment in dashboard screen for workflows, coordinators, bundles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19360) Ranger policies not syncing for storm, kafka and knox
Vishal Suvagia created AMBARI-19360: --- Summary: Ranger policies not syncing for storm, kafka and knox Key: AMBARI-19360 URL: https://issues.apache.org/jira/browse/AMBARI-19360 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Environment: On enabling Namenode-HA and one-way SSL for Ranger, plugins for storm kafka and knox are not able to communicate to Ranger. Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 On Enabling Namenode-HA, and One-way SSL for Ranger, plugins are not able to fetch latest policies as authorization does not work for Storm, knox and Kafka plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record. This patch amis to convert hostname of metric record to lowcase before inserting into ams hbase. was: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record. > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Attachments: uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname displayed in > ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached > picture),so we will not get any record. > This patch amis to convert hostname of metric record to lowcase before > inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record.This patch amis to convert hostname of metric record to lowcase before inserting into ams hbase. was: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record. This patch amis to convert hostname of metric record to lowcase before inserting into ams hbase. > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Attachments: uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname displayed in > ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached > picture),so we will not get any record.This patch amis to convert hostname of > metric record to lowcase before inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record.This patch amis to convert hostname of flume agent metric record to lowcase before inserting into ams hbase. was: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record.This patch amis to convert hostname of metric record to lowcase before inserting into ams hbase. > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Attachments: uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname displayed in > ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached > picture),so we will not get any record.This patch amis to convert hostname of > flume agent metric record to lowcase before inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any records.This patch amis to convert hostname of flume agent metric record to lowcase before inserting into ams hbase. was: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record.This patch amis to convert hostname of flume agent metric record to lowcase before inserting into ams hbase. > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Attachments: uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname displayed in > ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached > picture),so we will not get any records.This patch amis to convert hostname > of flume agent metric record to lowcase before inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname used in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any records.This patch amis to convert hostname of flume agent metric record to lowcase before inserting into ams hbase. was: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any records.This patch amis to convert hostname of flume agent metric record to lowcase before inserting into ams hbase. > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Attachments: uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname used in > ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached > picture),so we will not get any records.This patch amis to convert hostname > of flume agent metric record to lowcase before inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Attachment: AMBARI-19357.patch > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Attachments: AMBARI-19357.patch, uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname used in > ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached > picture),so we will not get any records.This patch amis to convert hostname > of flume agent metric record to lowcase before inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19333) Store LogSearch truststore/keystore passwords in file
[
https://issues.apache.org/jira/browse/AMBARI-19333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-19333.
---
Resolution: Fixed
committed to trunk:
{code:java}
commit 4a4a16aa9bd0d07e20e683dd9d428227e23f076f
Author: oleewere
Date: Wed Jan 4 13:19:17 2017 +0100
AMBARI-19333. Store LogSearch truststore/keystore passwords in file
(oleewere)
Change-Id: Ifbf2b1c72df7f20f31ce0e4ef8bf7f5fa4d5ac55
{code}
committed to branch-2.5:
{code:java}
commit a29343fc944ac0e07142ab256ac2cac73d2d5ad3
Author: oleewere
Date: Wed Jan 4 13:19:17 2017 +0100
AMBARI-19333. Store LogSearch truststore/keystore passwords in file
(oleewere)
Change-Id: Ifbf2b1c72df7f20f31ce0e4ef8bf7f5fa4d5ac55
{code}
> Store LogSearch truststore/keystore passwords in file
> -
>
> Key: AMBARI-19333
> URL: https://issues.apache.org/jira/browse/AMBARI-19333
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19333.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowercase hostname used in ambari ,but the hostname in METRIC_RECORD is not lowercase (see attached picture),so we will not get any records.This patch amis to convert hostname of metric record of flume to lowercase before inserting into ams hbase. was: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname used in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any records.This patch amis to convert hostname of flume agent metric record to lowcase before inserting into ams hbase. > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Attachments: AMBARI-19357.patch, uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowercase hostname used in > ambari ,but the hostname in METRIC_RECORD is not lowercase (see attached > picture),so we will not get any records.This patch amis to convert hostname > of metric record of flume to lowercase before inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19331) Setup correct authentication and authorization mechanism between Yarn and Zookeeper
[ https://issues.apache.org/jira/browse/AMBARI-19331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-19331: --- Fix Version/s: 2.5.0 Status: Patch Available (was: Open) > Setup correct authentication and authorization mechanism between Yarn and > Zookeeper > --- > > Key: AMBARI-19331 > URL: https://issues.apache.org/jira/browse/AMBARI-19331 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.5.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 2.5.0 > > > Setup the correct authentication (jaas conf files) and authorization > (per-component ACLs) mechanisms between YARN and ZooKeeper when kerberos is > enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19361) Cover JournalNode HA wizard with unit tests
Andrii Tkach created AMBARI-19361: - Summary: Cover JournalNode HA wizard with unit tests Key: AMBARI-19361 URL: https://issues.apache.org/jira/browse/AMBARI-19361 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19361) Cover JournalNode HA wizard with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-19361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19361: -- Status: Patch Available (was: Open) > Cover JournalNode HA wizard with unit tests > --- > > Key: AMBARI-19361 > URL: https://issues.apache.org/jira/browse/AMBARI-19361 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19361.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13038) Define ephemeral port range for Ambari agents
[ https://issues.apache.org/jira/browse/AMBARI-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-13038: -- Fix Version/s: (was: 2.5.0) 3.0.0 > Define ephemeral port range for Ambari agents > - > > Key: AMBARI-13038 > URL: https://issues.apache.org/jira/browse/AMBARI-13038 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.1.0 > Environment: All >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > Attachments: AMBARI-13038.patch, EphemeralPortRange.pdf > > > Problem: > When Ambari agent starts,it tries to use an ephemeral port that is already in > use by another component. > Steps to Reproduce: > 1. Install a cluster with Ambari > 2. Restart the Ambari agent until it takes a port in use by another service > Solution: > Range of ephemeral ports used by Ambari should be narrowed. (configurable) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19361) Cover JournalNode HA wizard with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-19361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19361: -- Attachment: AMBARI-19361.patch > Cover JournalNode HA wizard with unit tests > --- > > Key: AMBARI-19361 > URL: https://issues.apache.org/jira/browse/AMBARI-19361 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19361.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Fix Version/s: 2.5.0 > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19357.patch, uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowercase hostname used in > ambari ,but the hostname in METRIC_RECORD is not lowercase (see attached > picture),so we will not get any records.This patch amis to convert hostname > of metric record of flume to lowercase before inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19361) Cover JournalNode HA wizard with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-19361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798175#comment-15798175 ] Andrii Tkach commented on AMBARI-19361: --- 19935 passing (28s) 153 pending > Cover JournalNode HA wizard with unit tests > --- > > Key: AMBARI-19361 > URL: https://issues.apache.org/jira/browse/AMBARI-19361 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19361.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Fix Version/s: trunk > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19357.patch, uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowercase hostname used in > ambari ,but the hostname in METRIC_RECORD is not lowercase (see attached > picture),so we will not get any records.This patch amis to convert hostname > of metric record of flume to lowercase before inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19362) Hive View 2.0 : add REST endpoint for renaming a table
Nitiraj Singh Rathore created AMBARI-19362: -- Summary: Hive View 2.0 : add REST endpoint for renaming a table Key: AMBARI-19362 URL: https://issues.apache.org/jira/browse/AMBARI-19362 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Status: Patch Available (was: Open) > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19357.patch, uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowercase hostname used in > ambari ,but the hostname in METRIC_RECORD is not lowercase (see attached > picture),so we will not get any records.This patch amis to convert hostname > of metric record of flume to lowercase before inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19358) UI to add config ...2.6/HIVE/configuration/hive-env.xml 'enable_heap_dump' config in smart configs page.
[ https://issues.apache.org/jira/browse/AMBARI-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798191#comment-15798191 ] Hudson commented on AMBARI-19358: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #632 (See [https://builds.apache.org/job/Ambari-branch-2.5/632/]) AMBARI-19358. UI to add config ...2.6/HIVE/configuration/hive-env.xml (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0c5bae7e214beda6eeffc98763d7875d4f9d5234]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/metainfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/themes/theme.json > UI to add config ...2.6/HIVE/configuration/hive-env.xml 'enable_heap_dump' > config in smart configs page. > > > Key: AMBARI-19358 > URL: https://issues.apache.org/jira/browse/AMBARI-19358 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19358.patch > > > UI needs to add the config 'enable_heap_dump' in Smart configs panel, so that > its easy for user to enable/disable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19360) Ranger policies not syncing for storm, kafka and knox
[ https://issues.apache.org/jira/browse/AMBARI-19360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19360: Attachment: AMBARI-19360.patch > Ranger policies not syncing for storm, kafka and knox > - > > Key: AMBARI-19360 > URL: https://issues.apache.org/jira/browse/AMBARI-19360 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 > Environment: On enabling Namenode-HA and one-way SSL for Ranger, > plugins for storm kafka and knox are not able to communicate to Ranger. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19360.patch > > > On Enabling Namenode-HA, and One-way SSL for Ranger, plugins are not able to > fetch latest policies as authorization does not work for Storm, knox and > Kafka plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19362) Hive View 2.0 : add REST endpoint for renaming a table
[ https://issues.apache.org/jira/browse/AMBARI-19362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19362: --- Status: Patch Available (was: Open) > Hive View 2.0 : add REST endpoint for renaming a table > -- > > Key: AMBARI-19362 > URL: https://issues.apache.org/jira/browse/AMBARI-19362 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19362) Hive View 2.0 : add REST endpoint for renaming a table
[ https://issues.apache.org/jira/browse/AMBARI-19362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19362: --- Attachment: AMBARI-19362_branch-2.5.patch > Hive View 2.0 : add REST endpoint for renaming a table > -- > > Key: AMBARI-19362 > URL: https://issues.apache.org/jira/browse/AMBARI-19362 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-19362_branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19331) Setup correct authentication and authorization mechanism between Yarn and Zookeeper
[ https://issues.apache.org/jira/browse/AMBARI-19331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-19331: --- Attachment: AMBARI-19331_trunk.patch > Setup correct authentication and authorization mechanism between Yarn and > Zookeeper > --- > > Key: AMBARI-19331 > URL: https://issues.apache.org/jira/browse/AMBARI-19331 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.5.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 2.5.0 > > Attachments: AMBARI-19331_trunk.patch > > > Setup the correct authentication (jaas conf files) and authorization > (per-component ACLs) mechanisms between YARN and ZooKeeper when kerberos is > enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19331) Setup correct authentication and authorization mechanism between Yarn and Zookeeper
[ https://issues.apache.org/jira/browse/AMBARI-19331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-19331: --- Attachment: AMBARI-19331_branch-2.5.patch > Setup correct authentication and authorization mechanism between Yarn and > Zookeeper > --- > > Key: AMBARI-19331 > URL: https://issues.apache.org/jira/browse/AMBARI-19331 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.5.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 2.5.0 > > Attachments: AMBARI-19331_branch-2.5.patch, AMBARI-19331_trunk.patch > > > Setup the correct authentication (jaas conf files) and authorization > (per-component ACLs) mechanisms between YARN and ZooKeeper when kerberos is > enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19361) Cover JournalNode HA wizard with unit tests
[
https://issues.apache.org/jira/browse/AMBARI-19361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798249#comment-15798249
]
Hadoop QA commented on AMBARI-19361:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845530/AMBARI-19361.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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9882//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9882//console
This message is automatically generated.
> Cover JournalNode HA wizard with unit tests
> ---
>
> Key: AMBARI-19361
> URL: https://issues.apache.org/jira/browse/AMBARI-19361
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-19361.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19333) Store LogSearch truststore/keystore passwords in file
[ https://issues.apache.org/jira/browse/AMBARI-19333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798269#comment-15798269 ] Hudson commented on AMBARI-19333: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #633 (See [https://builds.apache.org/job/Ambari-branch-2.5/633/]) AMBARI-19333. Store LogSearch truststore/keystore passwords in file (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a29343fc944ac0e07142ab256ac2cac73d2d5ad3]) * (edit) ambari-server/src/test/python/stacks/2.4/LOGSEARCH/test_logsearch.py * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/scripts/run.sh * (edit) ambari-server/src/test/python/stacks/2.4/configs/default.json * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/params.py * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/util/SSLUtil.java * (edit) ambari-logsearch/docker/test-config/logsearch/logsearch-env.sh * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/setup_logsearch.py * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logsearch-env.sh.j2 * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/LogSearch.java > Store LogSearch truststore/keystore passwords in file > - > > Key: AMBARI-19333 > URL: https://issues.apache.org/jira/browse/AMBARI-19333 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19333.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19360) Ranger policies not syncing for storm, kafka and knox
[ https://issues.apache.org/jira/browse/AMBARI-19360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19360: Status: Patch Available (was: In Progress) > Ranger policies not syncing for storm, kafka and knox > - > > Key: AMBARI-19360 > URL: https://issues.apache.org/jira/browse/AMBARI-19360 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 > Environment: On enabling Namenode-HA and one-way SSL for Ranger, > plugins for storm kafka and knox are not able to communicate to Ranger. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19360.patch > > > On Enabling Namenode-HA, and One-way SSL for Ranger, plugins are not able to > fetch latest policies as authorization does not work for Storm, knox and > Kafka plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19363) Log Search: external authentication roles are hard coded
Olivér Szabó created AMBARI-19363: - Summary: Log Search: external authentication roles are hard coded Key: AMBARI-19363 URL: https://issues.apache.org/jira/browse/AMBARI-19363 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.5.0 By default AMBARI.ADMINISTRATOR (logsearch.roles.allowed) role is used for LogSearch users (with external ambari server authentication) these roles should be editable on ambari UI (not only with adding as custom property) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19363) Log Search: external authentication roles are hard coded
[ https://issues.apache.org/jira/browse/AMBARI-19363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19363: -- Attachment: AMBARI-19363.patch > Log Search: external authentication roles are hard coded > > > Key: AMBARI-19363 > URL: https://issues.apache.org/jira/browse/AMBARI-19363 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19363.patch > > > By default AMBARI.ADMINISTRATOR (logsearch.roles.allowed) role is used for > LogSearch users (with external ambari server authentication) > these roles should be editable on ambari UI (not only with adding as custom > property) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19363) Log Search: external authentication roles are hard coded
[ https://issues.apache.org/jira/browse/AMBARI-19363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19363: -- Attachment: AMBARI-19363_branch-2.5.patch > Log Search: external authentication roles are hard coded > > > Key: AMBARI-19363 > URL: https://issues.apache.org/jira/browse/AMBARI-19363 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19363.patch, AMBARI-19363_branch-2.5.patch > > > By default AMBARI.ADMINISTRATOR (logsearch.roles.allowed) role is used for > LogSearch users (with external ambari server authentication) > these roles should be editable on ambari UI (not only with adding as custom > property) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19331) Setup correct authentication and authorization mechanism between Yarn and Zookeeper
[ https://issues.apache.org/jira/browse/AMBARI-19331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-19331: --- Attachment: (was: AMBARI-19331_branch-2.5.patch) > Setup correct authentication and authorization mechanism between Yarn and > Zookeeper > --- > > Key: AMBARI-19331 > URL: https://issues.apache.org/jira/browse/AMBARI-19331 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.5.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 2.5.0 > > > Setup the correct authentication (jaas conf files) and authorization > (per-component ACLs) mechanisms between YARN and ZooKeeper when kerberos is > enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
