[jira] [Commented] (AMBARI-19438) Add enable delta sync property for Ranger
[
https://issues.apache.org/jira/browse/AMBARI-19438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837340#comment-15837340
]
Hudson commented on AMBARI-19438:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6537 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6537/])
AMBARI-19438 Add enable delta sync property for Ranger (mugdha) (mugdha:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ff4babbb776b6f7f53003a499d8677c9d79b5404])
* (add)
ambari-server/src/main/resources/common-services/RANGER/0.7.0/themes/theme_version_5.json
* (add)
ambari-server/src/main/resources/common-services/RANGER/0.7.0/configuration/ranger-ugsync-site.xml
* (edit)
ambari-server/src/main/resources/common-services/RANGER/0.7.0/metainfo.xml
> Add enable delta sync property for Ranger
> -
>
> Key: AMBARI-19438
> URL: https://issues.apache.org/jira/browse/AMBARI-19438
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19438.patch
>
>
> Add new property {{ranger.usersync.ldap.deltasync}} under ranger-ugsync-site
> config type to enable delta-sync. Need to show it under existing Smart Config
> Tab Ranger Usersync for LDAP/AD Sub Tab.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19438) Add enable delta sync property for Ranger
[
https://issues.apache.org/jira/browse/AMBARI-19438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837332#comment-15837332
]
Hudson commented on AMBARI-19438:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #795 (See
[https://builds.apache.org/job/Ambari-branch-2.5/795/])
AMBARI-19438 Add enable delta sync property for Ranger (mugdha) (mugdha:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3fe36a45799cd24e638e9a0764aaa64cc08cbaff])
* (add)
ambari-server/src/main/resources/common-services/RANGER/0.7.0/themes/theme_version_5.json
* (add)
ambari-server/src/main/resources/common-services/RANGER/0.7.0/configuration/ranger-ugsync-site.xml
* (edit)
ambari-server/src/main/resources/common-services/RANGER/0.7.0/metainfo.xml
> Add enable delta sync property for Ranger
> -
>
> Key: AMBARI-19438
> URL: https://issues.apache.org/jira/browse/AMBARI-19438
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19438.patch
>
>
> Add new property {{ranger.usersync.ldap.deltasync}} under ranger-ugsync-site
> config type to enable delta-sync. Need to show it under existing Smart Config
> Tab Ranger Usersync for LDAP/AD Sub Tab.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19603) Issue with delete action node operation
[ https://issues.apache.org/jira/browse/AMBARI-19603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB updated AMBARI-19603: - Assignee: Belliraj HB Status: Patch Available (was: Open) > Issue with delete action node operation > --- > > Key: AMBARI-19603 > URL: https://issues.apache.org/jira/browse/AMBARI-19603 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Belliraj HB >Priority: Critical > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19603_trunk.patch > > > Deleting decision node is deleting every other node proceeding it. > Steps to reproduce : > 1) Import the the workflow with decision node > 2) Delete the decision node. > 3) See that even the end node is getting deleted. > Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19603) Issue with delete action node operation
[ https://issues.apache.org/jira/browse/AMBARI-19603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB updated AMBARI-19603: - Attachment: AMBARI-19603_trunk.patch > Issue with delete action node operation > --- > > Key: AMBARI-19603 > URL: https://issues.apache.org/jira/browse/AMBARI-19603 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Priority: Critical > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19603_trunk.patch > > > Deleting decision node is deleting every other node proceeding it. > Steps to reproduce : > 1) Import the the workflow with decision node > 2) Delete the decision node. > 3) See that even the end node is getting deleted. > Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19438) Add enable delta sync property for Ranger
[
https://issues.apache.org/jira/browse/AMBARI-19438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-19438:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.5:
[3fe36a45799cd24e638e9a0764aaa64cc08cbaff|https://github.com/apache/ambari/commit/3fe36a45799cd24e638e9a0764aaa64cc08cbaff]
and trunk:
[ff4babbb776b6f7f53003a499d8677c9d79b5404|https://github.com/apache/ambari/commit/ff4babbb776b6f7f53003a499d8677c9d79b5404]
> Add enable delta sync property for Ranger
> -
>
> Key: AMBARI-19438
> URL: https://issues.apache.org/jira/browse/AMBARI-19438
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19438.patch
>
>
> Add new property {{ranger.usersync.ldap.deltasync}} under ranger-ugsync-site
> config type to enable delta-sync. Need to show it under existing Smart Config
> Tab Ranger Usersync for LDAP/AD Sub Tab.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19667) Hive View 2.0: Editor should be stretchable by dragging
[ https://issues.apache.org/jira/browse/AMBARI-19667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837204#comment-15837204 ] Hudson commented on AMBARI-19667: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #794 (See [https://builds.apache.org/job/Ambari-branch-2.5/794/]) AMBARI-19667. Hive View 2.0: Editor should be stretchable by dragging (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a5e008067ec31e526bd86d6efd80c3874a531711]) * (edit) contrib/views/hive20/src/main/resources/ui/bower.json * (edit) contrib/views/hive20/src/main/resources/ui/app/components/query-editor.js * (edit) contrib/views/hive20/src/main/resources/ui/package.json * (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss > Hive View 2.0: Editor should be stretchable by dragging > --- > > Key: AMBARI-19667 > URL: https://issues.apache.org/jira/browse/AMBARI-19667 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar > Fix For: 2.5.0 > > Attachments: AMBARI-19667_trunk.patch > > > User should be able to extend the height of editor by dragging -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-17589) Capture & visualize metrics for Ambari Server
[ https://issues.apache.org/jira/browse/AMBARI-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-17589: -- Assignee: Aravindan Vijayan (was: Li-Wei Tseng) > Capture & visualize metrics for Ambari Server > - > > Key: AMBARI-17589 > URL: https://issues.apache.org/jira/browse/AMBARI-17589 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > > Ambari's architectural design is based on having a single master server with > multiple agents. Each agent sends a heartbeat every X seconds to the server > to report its status; the server may reply with a list of commands to be run > by each agent. > An operational cluster may have up to 2000-4000 agents and Ambari needs to be > robust and performant at such scale. Often times, Ambari's overall > performance is subject to the cluster’s environment like network latency and > stability, Ambari database call latency, etc. In such environments, detecting > the cause of the Ambari’s sluggish performance and/or instability have proven > to be difficult in practice. > Ambari should intercept and store the time and resources taken for serving > requests. This information can be then presented to the end user on Ambari > Web and/or Grafana. > Optionally, this work can be extended to have Ambari Web persist time taken > to process the response of each API call and other performance > characteristics. Such performance data on Ambari Web can be again presented > to the end user via Ambari Web and/or Grafana. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17589) Capture & visualize metrics for Ambari Server
[ https://issues.apache.org/jira/browse/AMBARI-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-17589. Resolution: Fixed > Capture & visualize metrics for Ambari Server > - > > Key: AMBARI-17589 > URL: https://issues.apache.org/jira/browse/AMBARI-17589 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Li-Wei Tseng >Priority: Critical > Fix For: 2.5.0 > > > Ambari's architectural design is based on having a single master server with > multiple agents. Each agent sends a heartbeat every X seconds to the server > to report its status; the server may reply with a list of commands to be run > by each agent. > An operational cluster may have up to 2000-4000 agents and Ambari needs to be > robust and performant at such scale. Often times, Ambari's overall > performance is subject to the cluster’s environment like network latency and > stability, Ambari database call latency, etc. In such environments, detecting > the cause of the Ambari’s sluggish performance and/or instability have proven > to be difficult in practice. > Ambari should intercept and store the time and resources taken for serving > requests. This information can be then presented to the end user on Ambari > Web and/or Grafana. > Optionally, this work can be extended to have Ambari Web persist time taken > to process the response of each API call and other performance > characteristics. Such performance data on Ambari Web can be again presented > to the end user via Ambari Web and/or Grafana. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19701) Provide minimal call context from UI when making stack advisor calls
[
https://issues.apache.org/jira/browse/AMBARI-19701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837179#comment-15837179
]
Hadoop QA commented on AMBARI-19701:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849212/AMBARI-19701.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10237//console
This message is automatically generated.
> Provide minimal call context from UI when making stack advisor calls
>
>
> Key: AMBARI-19701
> URL: https://issues.apache.org/jira/browse/AMBARI-19701
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-19701.patch
>
>
> We need to identify if call is made when
> * Cluster is being created (first call)
> * Add service
> * Just landing on a page and only need config attributes
> Possible change to the json data send in POST -
> {code}
> {
> "recommend":"configurations",
> "user-context" : { "operation" : "ClusterCreate" } <== add this
> "hosts"
> {code}
> *Cluster create (first call):*
> {code}"user-context": {"operation" : "ClusterCreate"}{code}
> *Add service (first call):*
> {code}"user-context": {"operation" : "AddService", "operation_details" :
> "HDFS,YARN"}{code}
> *Landing on a config page:*
> {code}"user-context": {"operation" : "RecommendAttribute"}{code}
> *Config edit on a config page: (lower priority)*
> {code}"user-context": {"operation" : "EditConfig"}{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19671) Hive View 2.0: Incorrect behaviour on select of database
[ https://issues.apache.org/jira/browse/AMBARI-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837171#comment-15837171 ] Hudson commented on AMBARI-19671: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6536 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6536/]) AMBARI-19671. Hive View 2.0: Incorrect behaviour on select of database (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=72e02ab089b07246b2c79eb5e94825f1c19ad3cf]) * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query.hbs > Hive View 2.0: Incorrect behaviour on select of database > > > Key: AMBARI-19671 > URL: https://issues.apache.org/jira/browse/AMBARI-19671 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar > Fix For: 2.5.0 > > Attachments: AMBARI-19671_trunk.patch > > > On selecting a database from right panel, display does not change. Ideally > followings should happen: > 1. Move "checked" icon to selected database > 2. Hide tables related to unselected database and show tables for the > selected one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19671) Hive View 2.0: Incorrect behaviour on select of database
[ https://issues.apache.org/jira/browse/AMBARI-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837169#comment-15837169 ] Hudson commented on AMBARI-19671: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #793 (See [https://builds.apache.org/job/Ambari-branch-2.5/793/]) AMBARI-19671. Hive View 2.0: Incorrect behaviour on select of database (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5c9fc2e5d53435daca736cced9af94e5b009e993]) * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query.hbs > Hive View 2.0: Incorrect behaviour on select of database > > > Key: AMBARI-19671 > URL: https://issues.apache.org/jira/browse/AMBARI-19671 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar > Fix For: 2.5.0 > > Attachments: AMBARI-19671_trunk.patch > > > On selecting a database from right panel, display does not change. Ideally > followings should happen: > 1. Move "checked" icon to selected database > 2. Hide tables related to unselected database and show tables for the > selected one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19667) Hive View 2.0: Editor should be stretchable by dragging
[ https://issues.apache.org/jira/browse/AMBARI-19667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837170#comment-15837170 ] Hudson commented on AMBARI-19667: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6536 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6536/]) AMBARI-19667. Hive View 2.0: Editor should be stretchable by dragging (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0de31d6a59c2ec847fc060dffb9e69431eee4ebc]) * (edit) contrib/views/hive20/src/main/resources/ui/app/components/query-editor.js * (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss * (edit) contrib/views/hive20/src/main/resources/ui/package.json * (edit) contrib/views/hive20/src/main/resources/ui/bower.json > Hive View 2.0: Editor should be stretchable by dragging > --- > > Key: AMBARI-19667 > URL: https://issues.apache.org/jira/browse/AMBARI-19667 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar > Fix For: 2.5.0 > > Attachments: AMBARI-19667_trunk.patch > > > User should be able to extend the height of editor by dragging -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19667) Hive View 2.0: Editor should be stretchable by dragging
[ https://issues.apache.org/jira/browse/AMBARI-19667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19667: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > Hive View 2.0: Editor should be stretchable by dragging > --- > > Key: AMBARI-19667 > URL: https://issues.apache.org/jira/browse/AMBARI-19667 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar > Fix For: 2.5.0 > > Attachments: AMBARI-19667_trunk.patch > > > User should be able to extend the height of editor by dragging -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19671) Hive View 2.0: Incorrect behaviour on select of database
[ https://issues.apache.org/jira/browse/AMBARI-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19671: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > Hive View 2.0: Incorrect behaviour on select of database > > > Key: AMBARI-19671 > URL: https://issues.apache.org/jira/browse/AMBARI-19671 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar > Fix For: 2.5.0 > > Attachments: AMBARI-19671_trunk.patch > > > On selecting a database from right panel, display does not change. Ideally > followings should happen: > 1. Move "checked" icon to selected database > 2. Hide tables related to unselected database and show tables for the > selected one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19701) Provide minimal call context from UI when making stack advisor calls
[
https://issues.apache.org/jira/browse/AMBARI-19701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-19701:
--
Status: Patch Available (was: Open)
> Provide minimal call context from UI when making stack advisor calls
>
>
> Key: AMBARI-19701
> URL: https://issues.apache.org/jira/browse/AMBARI-19701
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-19701.patch
>
>
> We need to identify if call is made when
> * Cluster is being created (first call)
> * Add service
> * Just landing on a page and only need config attributes
> Possible change to the json data send in POST -
> {code}
> {
> "recommend":"configurations",
> "user-context" : { "operation" : "ClusterCreate" } <== add this
> "hosts"
> {code}
> *Cluster create (first call):*
> {code}"user-context": {"operation" : "ClusterCreate"}{code}
> *Add service (first call):*
> {code}"user-context": {"operation" : "AddService", "operation_details" :
> "HDFS,YARN"}{code}
> *Landing on a config page:*
> {code}"user-context": {"operation" : "RecommendAttribute"}{code}
> *Config edit on a config page: (lower priority)*
> {code}"user-context": {"operation" : "EditConfig"}{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19701) Provide minimal call context from UI when making stack advisor calls
[
https://issues.apache.org/jira/browse/AMBARI-19701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-19701:
--
Attachment: AMBARI-19701.patch
> Provide minimal call context from UI when making stack advisor calls
>
>
> Key: AMBARI-19701
> URL: https://issues.apache.org/jira/browse/AMBARI-19701
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-19701.patch
>
>
> We need to identify if call is made when
> * Cluster is being created (first call)
> * Add service
> * Just landing on a page and only need config attributes
> Possible change to the json data send in POST -
> {code}
> {
> "recommend":"configurations",
> "user-context" : { "operation" : "ClusterCreate" } <== add this
> "hosts"
> {code}
> *Cluster create (first call):*
> {code}"user-context": {"operation" : "ClusterCreate"}{code}
> *Add service (first call):*
> {code}"user-context": {"operation" : "AddService", "operation_details" :
> "HDFS,YARN"}{code}
> *Landing on a config page:*
> {code}"user-context": {"operation" : "RecommendAttribute"}{code}
> *Config edit on a config page: (lower priority)*
> {code}"user-context": {"operation" : "EditConfig"}{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17346) Dependent components should be shutdown before stopping hdfs
[ https://issues.apache.org/jira/browse/AMBARI-17346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-17346: Description: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. was: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. > Dependent components should be shutdown before stopping hdfs > > > Key: AMBARI-17346 > URL: https://issues.apache.org/jira/browse/AMBARI-17346 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu > > Sometimes admin shuts down hdfs first, then hbase. > By the time hbase is shutdown, no data can be persisted (including metadata). > This results in large number of inconsistencies when hbase cluster is brought > back up. > Before hdfs is shutdown, the components dependent on hdfs should be shutdown > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19701) Provide minimal call context from UI when making stack advisor calls
Richard Zang created AMBARI-19701:
-
Summary: Provide minimal call context from UI when making stack
advisor calls
Key: AMBARI-19701
URL: https://issues.apache.org/jira/browse/AMBARI-19701
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.0
Reporter: Richard Zang
Assignee: Richard Zang
Fix For: 2.5.0
We need to identify if call is made when
* Cluster is being created (first call)
* Add service
* Just landing on a page and only need config attributes
Possible change to the json data send in POST -
{code}
{
"recommend":"configurations",
"user-context" : { "operation" : "ClusterCreate" } <== add this
"hosts"
{code}
*Cluster create (first call):*
{code}"user-context": {"operation" : "ClusterCreate"}{code}
*Add service (first call):*
{code}"user-context": {"operation" : "AddService", "operation_details" :
"HDFS,YARN"}{code}
*Landing on a config page:*
{code}"user-context": {"operation" : "RecommendAttribute"}{code}
*Config edit on a config page: (lower priority)*
{code}"user-context": {"operation" : "EditConfig"}{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19098) HDP 3.0 TP - create Service Advisor for YARN/MR
[
https://issues.apache.org/jira/browse/AMBARI-19098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837083#comment-15837083
]
Hadoop QA commented on AMBARI-19098:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849208/AMBARI-19098.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10236//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10236//console
This message is automatically generated.
> HDP 3.0 TP - create Service Advisor for YARN/MR
> ---
>
> Key: AMBARI-19098
> URL: https://issues.apache.org/jira/browse/AMBARI-19098
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19098.patch
>
>
> Create a Service Advisor script for YARN/MR in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten
> from HDP 2.0.6 through HDP 2.6
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19098) HDP 3.0 TP - create Service Advisor for YARN/MR
[ https://issues.apache.org/jira/browse/AMBARI-19098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19098: - Status: Patch Available (was: Open) > HDP 3.0 TP - create Service Advisor for YARN/MR > --- > > Key: AMBARI-19098 > URL: https://issues.apache.org/jira/browse/AMBARI-19098 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19098.patch > > > Create a Service Advisor script for YARN/MR in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19098) HDP 3.0 TP - create Service Advisor for YARN/MR
[ https://issues.apache.org/jira/browse/AMBARI-19098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19098: - Attachment: AMBARI-19098.patch > HDP 3.0 TP - create Service Advisor for YARN/MR > --- > > Key: AMBARI-19098 > URL: https://issues.apache.org/jira/browse/AMBARI-19098 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19098.patch > > > Create a Service Advisor script for YARN/MR in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19098) HDP 3.0 TP - create Service Advisor for YARN/MR
[ https://issues.apache.org/jira/browse/AMBARI-19098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19098: - Status: Open (was: Patch Available) > HDP 3.0 TP - create Service Advisor for YARN/MR > --- > > Key: AMBARI-19098 > URL: https://issues.apache.org/jira/browse/AMBARI-19098 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19098.patch > > > Create a Service Advisor script for YARN/MR in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19098) HDP 3.0 TP - create Service Advisor for YARN/MR
[ https://issues.apache.org/jira/browse/AMBARI-19098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19098: - Attachment: (was: AMBARI-19098.patch) > HDP 3.0 TP - create Service Advisor for YARN/MR > --- > > Key: AMBARI-19098 > URL: https://issues.apache.org/jira/browse/AMBARI-19098 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > > Create a Service Advisor script for YARN/MR in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19685) Stack advisor needs to enforce component dependency for slaves and masters
[
https://issues.apache.org/jira/browse/AMBARI-19685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837046#comment-15837046
]
Hadoop QA commented on AMBARI-19685:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849177/AMBARI-19685.3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10235//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10235//console
This message is automatically generated.
> Stack advisor needs to enforce component dependency for slaves and masters
> --
>
> Key: AMBARI-19685
> URL: https://issues.apache.org/jira/browse/AMBARI-19685
> Project: Ambari
> Issue Type: Task
> Components: ambari-sever
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 3.0.0
>
> Attachments: AMBARI-19685.2.patch, AMBARI-19685.3.patch,
> AMBARI-19685.patch
>
>
> * Install Ambari cluster with latest trunk bits
> * Modify
> /var/lib/ambari-server/resources/common-services/ZEPPELIN/0.6.0.2.5/metainfo.xml
> to add the following:
> {noformat}
> Add to node of ZEPPELIN_MASTER:
>
> SPARK/LIVY_SERVER
> host
>
> Add to node:
>
> SPARK
>
> {noformat}
> * Install HDP 2.5.3 cluster with Spark
> * Once the cluster is installed, use Add Service Wizard to add Zeppelin
> * Assign Slaves and Clients step should appear (without the metainfo.xml
> change, it will be skipped)
> * The user should not be able to proceed beyond this page unless at least one
> Livy Server is selected <- this validation should be handled by the stack
> advisor
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19699) Axis units and aggregators are wrong in some graphs of ambari grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-19699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837028#comment-15837028 ] Hudson commented on AMBARI-19699: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6535 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6535/]) AMBARI-19699. Axis units and aggregators are wrong in some graphs of (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bb8b44cff641c49397d1eb72481398036e90f459]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/default/grafana-ambari-server-database.json * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/default/grafana-ambari-server.json > Axis units and aggregators are wrong in some graphs of ambari grafana > dashboards > > > Key: AMBARI-19699 > URL: https://issues.apache.org/jira/browse/AMBARI-19699 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19699.v0.branch-2.5.patch > > > Need to fix the following: > ReadAllQuery.HostRoleCommandEntity is missing a Y axis. > Total Cache Misses Y axis is wrong should not be time. > Remove Max aggregator from all metrics (JVM dashboard) > Cache Hits and Misses rate graphs aren't in the same units -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19699) Axis units and aggregators are wrong in some graphs of ambari grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-19699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837013#comment-15837013 ] Hudson commented on AMBARI-19699: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #792 (See [https://builds.apache.org/job/Ambari-branch-2.5/792/]) AMBARI-19699. Axis units and aggregators are wrong in some graphs of (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4db2d97280813d5c6f1c1025cb085d3ad00425ed]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/default/grafana-ambari-server.json * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/default/grafana-ambari-server-database.json > Axis units and aggregators are wrong in some graphs of ambari grafana > dashboards > > > Key: AMBARI-19699 > URL: https://issues.apache.org/jira/browse/AMBARI-19699 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19699.v0.branch-2.5.patch > > > Need to fix the following: > ReadAllQuery.HostRoleCommandEntity is missing a Y axis. > Total Cache Misses Y axis is wrong should not be time. > Remove Max aggregator from all metrics (JVM dashboard) > Cache Hits and Misses rate graphs aren't in the same units -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19700) When hiveserver2 LDAP authentication is enabled hive.server2.authentication.ldap.url property gets exported with hardcoded hostname
[
https://issues.apache.org/jira/browse/AMBARI-19700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836996#comment-15836996
]
Hadoop QA commented on AMBARI-19700:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849182/AMBARI-19700.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/10234//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10234//console
This message is automatically generated.
> When hiveserver2 LDAP authentication is enabled
> hive.server2.authentication.ldap.url property gets exported with hardcoded
> hostname
> ---
>
> Key: AMBARI-19700
> URL: https://issues.apache.org/jira/browse/AMBARI-19700
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19700.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19699) Axis units and aggregators are wrong in some graphs of ambari grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-19699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-19699: - Resolution: Fixed Status: Resolved (was: Patch Available) > Axis units and aggregators are wrong in some graphs of ambari grafana > dashboards > > > Key: AMBARI-19699 > URL: https://issues.apache.org/jira/browse/AMBARI-19699 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19699.v0.branch-2.5.patch > > > Need to fix the following: > ReadAllQuery.HostRoleCommandEntity is missing a Y axis. > Total Cache Misses Y axis is wrong should not be time. > Remove Max aggregator from all metrics (JVM dashboard) > Cache Hits and Misses rate graphs aren't in the same units -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19699) Axis units and aggregators are wrong in some graphs of ambari grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-19699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836972#comment-15836972 ] Yusaku Sako commented on AMBARI-19699: -- This has been +1'd on ReviewBoard. Committed to trunk and branch-2.5. > Axis units and aggregators are wrong in some graphs of ambari grafana > dashboards > > > Key: AMBARI-19699 > URL: https://issues.apache.org/jira/browse/AMBARI-19699 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19699.v0.branch-2.5.patch > > > Need to fix the following: > ReadAllQuery.HostRoleCommandEntity is missing a Y axis. > Total Cache Misses Y axis is wrong should not be time. > Remove Max aggregator from all metrics (JVM dashboard) > Cache Hits and Misses rate graphs aren't in the same units -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19658) LogSearch Integration Cache Timeout should be configurable
[
https://issues.apache.org/jira/browse/AMBARI-19658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836955#comment-15836955
]
Hudson commented on AMBARI-19658:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #791 (See
[https://builds.apache.org/job/Ambari-branch-2.5/791/])
AMBARI-19658. LogSearch Integration Cache Timeout should be (rnettleton:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=adc63c05aa69610a36fcc4aa67ac37aa3cfe522e])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LogSearchDataRetrievalService.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/logging/LogSearchDataRetrievalServiceTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
> LogSearch Integration Cache Timeout should be configurable
> --
>
> Key: AMBARI-19658
> URL: https://issues.apache.org/jira/browse/AMBARI-19658
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Nettleton
>Assignee: Robert Nettleton
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19658.patch
>
>
> In Ambari 2.4.0, during the initial integration with LogSearch, a cache was
> implemented to reduce the number of calls to the LogSearch service when the
> PropertyProvider implementation for LogSearch integration is called in other
> contexts (such as Rolling/Express Upgrades, REST API calls on the
> HostComponent resource, etc).
> That cache was implemented in the following class:
> {code}
> org.apache.ambari.server.controller.logging.LogSearchDataRetrievalService
> {code}
> In the initial implementation, the cache was hard-coded to expire within in
> hour.
> In
> org.apache.ambari.server.controller.logging.LogSearchDataRetrievalService#doStart:
> {code}
> protected void doStart() {
> LOG.debug("Initializing caches");
> // initialize the log file name cache
> logFileNameCache = CacheBuilder.newBuilder().expireAfterWrite(1,
> TimeUnit.HOURS).build();
> // initialize the log file tail URI cache
> logFileTailURICache = CacheBuilder.newBuilder().expireAfterWrite(1,
> TimeUnit.HOURS).build();
> // initialize the Executor
> executor = Executors.newSingleThreadExecutor();
> }
> {code}
> An hour is probably too short of an interval, since the cache data is
> unlikely to change often. This timeout should be a configurable option in
> the Ambari LogSearch Integration code.
> 1. The default timeout should be much larger, as this information obtained
> from the LogSearch service is generally static. We should increase the
> timeout to be at least 24 hours, or perhaps move to an unbounded timeout,
> provided that the timeout would be configurable.
> 2. The max timeout for the cache should be configurable in ambari.properties,
> with a reasonable default if not set (as mentioned above).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19688) Ubuntu14 base url fields on "Select version" page are duplicates
[ https://issues.apache.org/jira/browse/AMBARI-19688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836954#comment-15836954 ] Hudson commented on AMBARI-19688: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #791 (See [https://builds.apache.org/job/Ambari-branch-2.5/791/]) AMBARI-19688 - Ubuntu14 base url fields on "Select version" page are (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=337a651fa0a1cfdab79d71b06d3c7976e16e6992]) * (edit) ambari-web/app/controllers/installer.js > Ubuntu14 base url fields on "Select version" page are duplicates > > > Key: AMBARI-19688 > URL: https://issues.apache.org/jira/browse/AMBARI-19688 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19688_diagnosis.patch > > > Ubuntu14 base url fields on "Select version" page are duplicates -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19688) Ubuntu14 base url fields on "Select version" page are duplicates
[ https://issues.apache.org/jira/browse/AMBARI-19688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836949#comment-15836949 ] Hudson commented on AMBARI-19688: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6534 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6534/]) AMBARI-19688 - Ubuntu14 base url fields on "Select version" page are (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b3a070c0011a542504c9fd586b26bccfaf1568f1]) * (edit) ambari-web/app/controllers/installer.js > Ubuntu14 base url fields on "Select version" page are duplicates > > > Key: AMBARI-19688 > URL: https://issues.apache.org/jira/browse/AMBARI-19688 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19688_diagnosis.patch > > > Ubuntu14 base url fields on "Select version" page are duplicates -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19700) When hiveserver2 LDAP authentication is enabled hive.server2.authentication.ldap.url property gets exported with hardcoded hostname
[ https://issues.apache.org/jira/browse/AMBARI-19700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-19700: --- Status: Patch Available (was: In Progress) > When hiveserver2 LDAP authentication is enabled > hive.server2.authentication.ldap.url property gets exported with hardcoded > hostname > --- > > Key: AMBARI-19700 > URL: https://issues.apache.org/jira/browse/AMBARI-19700 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Reporter: Amruta Borkar >Assignee: Amruta Borkar >Priority: Minor > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19700.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19688) Ubuntu14 base url fields on "Select version" page are duplicates
[ https://issues.apache.org/jira/browse/AMBARI-19688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19688: -- Status: Patch Available (was: Open) > Ubuntu14 base url fields on "Select version" page are duplicates > > > Key: AMBARI-19688 > URL: https://issues.apache.org/jira/browse/AMBARI-19688 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19688_diagnosis.patch > > > Ubuntu14 base url fields on "Select version" page are duplicates -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19660) Add log rotation settings - handle upgrade scenario - Storm, Hive
[ https://issues.apache.org/jira/browse/AMBARI-19660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836845#comment-15836845 ] Hudson commented on AMBARI-19660: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6533 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6533/]) AMBARI-19660. Add log rotation settings - handle upgrade scenario - (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=78fefdd4c327390062d16a15594b32bb816f65cf]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml > Add log rotation settings - handle upgrade scenario - Storm, Hive > - > > Key: AMBARI-19660 > URL: https://issues.apache.org/jira/browse/AMBARI-19660 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > > Changes made to all upgrade packs 2.3->2.4,2.5,2.6 ; 2.4->2.5,2.6 ; 2.5->2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19658) LogSearch Integration Cache Timeout should be configurable
[
https://issues.apache.org/jira/browse/AMBARI-19658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836844#comment-15836844
]
Hudson commented on AMBARI-19658:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6533 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6533/])
AMBARI-19658. LogSearch Integration Cache Timeout should be (rnettleton:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=604620021908995d7b4581176ceecf6c44ffea26])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LogSearchDataRetrievalService.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/logging/LogSearchDataRetrievalServiceTest.java
> LogSearch Integration Cache Timeout should be configurable
> --
>
> Key: AMBARI-19658
> URL: https://issues.apache.org/jira/browse/AMBARI-19658
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Nettleton
>Assignee: Robert Nettleton
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19658.patch
>
>
> In Ambari 2.4.0, during the initial integration with LogSearch, a cache was
> implemented to reduce the number of calls to the LogSearch service when the
> PropertyProvider implementation for LogSearch integration is called in other
> contexts (such as Rolling/Express Upgrades, REST API calls on the
> HostComponent resource, etc).
> That cache was implemented in the following class:
> {code}
> org.apache.ambari.server.controller.logging.LogSearchDataRetrievalService
> {code}
> In the initial implementation, the cache was hard-coded to expire within in
> hour.
> In
> org.apache.ambari.server.controller.logging.LogSearchDataRetrievalService#doStart:
> {code}
> protected void doStart() {
> LOG.debug("Initializing caches");
> // initialize the log file name cache
> logFileNameCache = CacheBuilder.newBuilder().expireAfterWrite(1,
> TimeUnit.HOURS).build();
> // initialize the log file tail URI cache
> logFileTailURICache = CacheBuilder.newBuilder().expireAfterWrite(1,
> TimeUnit.HOURS).build();
> // initialize the Executor
> executor = Executors.newSingleThreadExecutor();
> }
> {code}
> An hour is probably too short of an interval, since the cache data is
> unlikely to change often. This timeout should be a configurable option in
> the Ambari LogSearch Integration code.
> 1. The default timeout should be much larger, as this information obtained
> from the LogSearch service is generally static. We should increase the
> timeout to be at least 24 hours, or perhaps move to an unbounded timeout,
> provided that the timeout would be configurable.
> 2. The max timeout for the cache should be configurable in ambari.properties,
> with a reasonable default if not set (as mentioned above).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19688) Ubuntu14 base url fields on "Select version" page are duplicates
[ https://issues.apache.org/jira/browse/AMBARI-19688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19688: -- Resolution: Fixed Status: Resolved (was: Patch Available) Diagnosis patch committed to trunk and 2.5. b3a070c0011a542504c9fd586b26bccfaf1568f1 > Ubuntu14 base url fields on "Select version" page are duplicates > > > Key: AMBARI-19688 > URL: https://issues.apache.org/jira/browse/AMBARI-19688 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19688_diagnosis.patch > > > Ubuntu14 base url fields on "Select version" page are duplicates -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19700) When hiveserver2 LDAP authentication is enabled hive.server2.authentication.ldap.url property gets exported with hardcoded hostname
Amruta Borkar created AMBARI-19700: -- Summary: When hiveserver2 LDAP authentication is enabled hive.server2.authentication.ldap.url property gets exported with hardcoded hostname Key: AMBARI-19700 URL: https://issues.apache.org/jira/browse/AMBARI-19700 Project: Ambari Issue Type: Bug Components: ambari-server, blueprints Reporter: Amruta Borkar Assignee: Amruta Borkar Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19700) When hiveserver2 LDAP authentication is enabled hive.server2.authentication.ldap.url property gets exported with hardcoded hostname
[ https://issues.apache.org/jira/browse/AMBARI-19700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-19700: --- Fix Version/s: 2.5.0 trunk > When hiveserver2 LDAP authentication is enabled > hive.server2.authentication.ldap.url property gets exported with hardcoded > hostname > --- > > Key: AMBARI-19700 > URL: https://issues.apache.org/jira/browse/AMBARI-19700 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Reporter: Amruta Borkar >Assignee: Amruta Borkar >Priority: Minor > Fix For: trunk, 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19660) Add log rotation settings - handle upgrade scenario - Storm, Hive
[ https://issues.apache.org/jira/browse/AMBARI-19660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836831#comment-15836831 ] Hudson commented on AMBARI-19660: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #790 (See [https://builds.apache.org/job/Ambari-branch-2.5/790/]) AMBARI-19660. Add log rotation settings - handle upgrade scenario - (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9f8401a4af4bdb123c030d7f783a5176136ec5db]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml > Add log rotation settings - handle upgrade scenario - Storm, Hive > - > > Key: AMBARI-19660 > URL: https://issues.apache.org/jira/browse/AMBARI-19660 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > > Changes made to all upgrade packs 2.3->2.4,2.5,2.6 ; 2.4->2.5,2.6 ; 2.5->2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19700) When hiveserver2 LDAP authentication is enabled hive.server2.authentication.ldap.url property gets exported with hardcoded hostname
[ https://issues.apache.org/jira/browse/AMBARI-19700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-19700: --- Attachment: AMBARI-19700.patch > When hiveserver2 LDAP authentication is enabled > hive.server2.authentication.ldap.url property gets exported with hardcoded > hostname > --- > > Key: AMBARI-19700 > URL: https://issues.apache.org/jira/browse/AMBARI-19700 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Reporter: Amruta Borkar >Assignee: Amruta Borkar >Priority: Minor > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19700.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19658) LogSearch Integration Cache Timeout should be configurable
[
https://issues.apache.org/jira/browse/AMBARI-19658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Nettleton updated AMBARI-19658:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Patch merged to trunk and branch-2.5
> LogSearch Integration Cache Timeout should be configurable
> --
>
> Key: AMBARI-19658
> URL: https://issues.apache.org/jira/browse/AMBARI-19658
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Nettleton
>Assignee: Robert Nettleton
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19658.patch
>
>
> In Ambari 2.4.0, during the initial integration with LogSearch, a cache was
> implemented to reduce the number of calls to the LogSearch service when the
> PropertyProvider implementation for LogSearch integration is called in other
> contexts (such as Rolling/Express Upgrades, REST API calls on the
> HostComponent resource, etc).
> That cache was implemented in the following class:
> {code}
> org.apache.ambari.server.controller.logging.LogSearchDataRetrievalService
> {code}
> In the initial implementation, the cache was hard-coded to expire within in
> hour.
> In
> org.apache.ambari.server.controller.logging.LogSearchDataRetrievalService#doStart:
> {code}
> protected void doStart() {
> LOG.debug("Initializing caches");
> // initialize the log file name cache
> logFileNameCache = CacheBuilder.newBuilder().expireAfterWrite(1,
> TimeUnit.HOURS).build();
> // initialize the log file tail URI cache
> logFileTailURICache = CacheBuilder.newBuilder().expireAfterWrite(1,
> TimeUnit.HOURS).build();
> // initialize the Executor
> executor = Executors.newSingleThreadExecutor();
> }
> {code}
> An hour is probably too short of an interval, since the cache data is
> unlikely to change often. This timeout should be a configurable option in
> the Ambari LogSearch Integration code.
> 1. The default timeout should be much larger, as this information obtained
> from the LogSearch service is generally static. We should increase the
> timeout to be at least 24 hours, or perhaps move to an unbounded timeout,
> provided that the timeout would be configurable.
> 2. The max timeout for the cache should be configurable in ambari.properties,
> with a reasonable default if not set (as mentioned above).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19693) Permission issues with conf.server/hive-site.xml across several hive components
[
https://issues.apache.org/jira/browse/AMBARI-19693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836788#comment-15836788
]
Hudson commented on AMBARI-19693:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6532 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6532/])
AMBARI-19693. Permission issues with conf.server/hive-site.xml across
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2a2b4e94feacfff56097293810867ce627b1778a])
* (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hcat_client.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hcat.py
> Permission issues with conf.server/hive-site.xml across several hive
> components
> ---
>
> Key: AMBARI-19693
> URL: https://issues.apache.org/jira/browse/AMBARI-19693
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19693-branch-2.5.patch, AMBARI-19693.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 193, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 95, in service_check
> hcat_service_check()
> 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/HIVE/0.12.0.2.0/package/scripts/hcat_service_check.py",
> line 65, in hcat_service_check
> logoutput=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
> ambari...@example.com; env JAVA_HOME=/usr/jdk64/jdk1.7.0_67
> /var/lib/ambari-agent/tmp/hcatSmoke.sh hcatsmokeid16ac7075_date383016 prepare
> true' returned 88. Hortonworks #
> This is MOTD message, added for testing in qe infra
> WARNING: Use "yarn jar" to launch YARN applications.
> FAILED: SemanticException [Error 10072]: Database does not exist: default
> WARNING: Use "yarn jar" to launch YARN applications.
> OK
> Time taken: 3.012 seconds
> WARNING: Use "yarn jar" to launch YARN applications.
> FAILED: SemanticException [Error 10072]: Database does not exist: default
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19682) Small fixes to log4j rotation properties - Yarn, ZooKeeper, AMS-Hbase, Logsearch/Logfeeder
[ https://issues.apache.org/jira/browse/AMBARI-19682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836789#comment-15836789 ] Hudson commented on AMBARI-19682: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6532 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6532/]) AMBARI-19682. Small fixes for common log rotation (Madhuvanthi (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1b630ebc6406ac2d81b375d4b503e028f6609c0e]) * (edit) ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-log4j.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-log4j.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-log4j.xml * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-log4j.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-log4j.xml * (edit) ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5/configuration/zookeeper-log4j.xml > Small fixes to log4j rotation properties - Yarn, ZooKeeper, AMS-Hbase, > Logsearch/Logfeeder > -- > > Key: AMBARI-19682 > URL: https://issues.apache.org/jira/browse/AMBARI-19682 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > > Naming convention changes for services listed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19685) Stack advisor needs to enforce component dependency for slaves and masters
[
https://issues.apache.org/jira/browse/AMBARI-19685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-19685:
--
Attachment: AMBARI-19685.3.patch
> Stack advisor needs to enforce component dependency for slaves and masters
> --
>
> Key: AMBARI-19685
> URL: https://issues.apache.org/jira/browse/AMBARI-19685
> Project: Ambari
> Issue Type: Task
> Components: ambari-sever
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 3.0.0
>
> Attachments: AMBARI-19685.2.patch, AMBARI-19685.3.patch,
> AMBARI-19685.patch
>
>
> * Install Ambari cluster with latest trunk bits
> * Modify
> /var/lib/ambari-server/resources/common-services/ZEPPELIN/0.6.0.2.5/metainfo.xml
> to add the following:
> {noformat}
> Add to node of ZEPPELIN_MASTER:
>
> SPARK/LIVY_SERVER
> host
>
> Add to node:
>
> SPARK
>
> {noformat}
> * Install HDP 2.5.3 cluster with Spark
> * Once the cluster is installed, use Add Service Wizard to add Zeppelin
> * Assign Slaves and Clients step should appear (without the metainfo.xml
> change, it will be skipped)
> * The user should not be able to proceed beyond this page unless at least one
> Livy Server is selected <- this validation should be handled by the stack
> advisor
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19682) Small fixes to log4j rotation properties - Yarn, ZooKeeper, AMS-Hbase, Logsearch/Logfeeder
[ https://issues.apache.org/jira/browse/AMBARI-19682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836782#comment-15836782 ] Hudson commented on AMBARI-19682: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #789 (See [https://builds.apache.org/job/Ambari-branch-2.5/789/]) AMBARI-19682. Small fixes for common log rotation (Madhuvanthi (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c34a836b77662163a3b6f3b6fe533b6cf01d45e5]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-log4j.xml * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-log4j.xml * (edit) ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5/configuration/zookeeper-log4j.xml * (edit) ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-log4j.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-log4j.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-log4j.xml > Small fixes to log4j rotation properties - Yarn, ZooKeeper, AMS-Hbase, > Logsearch/Logfeeder > -- > > Key: AMBARI-19682 > URL: https://issues.apache.org/jira/browse/AMBARI-19682 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > > Naming convention changes for services listed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19693) Permission issues with conf.server/hive-site.xml across several hive components
[
https://issues.apache.org/jira/browse/AMBARI-19693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836781#comment-15836781
]
Hudson commented on AMBARI-19693:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #789 (See
[https://builds.apache.org/job/Ambari-branch-2.5/789/])
AMBARI-19693. Permission issues with conf.server/hive-site.xml across
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=59441de0ba9cc7bc649bc2127e1e78d86a84fd5a])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hcat.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hcat_client.py
> Permission issues with conf.server/hive-site.xml across several hive
> components
> ---
>
> Key: AMBARI-19693
> URL: https://issues.apache.org/jira/browse/AMBARI-19693
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19693-branch-2.5.patch, AMBARI-19693.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 193, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 95, in service_check
> hcat_service_check()
> 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/HIVE/0.12.0.2.0/package/scripts/hcat_service_check.py",
> line 65, in hcat_service_check
> logoutput=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
> ambari...@example.com; env JAVA_HOME=/usr/jdk64/jdk1.7.0_67
> /var/lib/ambari-agent/tmp/hcatSmoke.sh hcatsmokeid16ac7075_date383016 prepare
> true' returned 88. Hortonworks #
> This is MOTD message, added for testing in qe infra
> WARNING: Use "yarn jar" to launch YARN applications.
> FAILED: SemanticException [Error 10072]: Database does not exist: default
> WARNING: Use "yarn jar" to launch YARN applications.
> OK
> Time taken: 3.012 seconds
> WARNING: Use "yarn jar" to launch YARN applications.
> FAILED: SemanticException [Error 10072]: Database does not exist: default
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19688) Ubuntu14 base url fields on "Select version" page are duplicates
[ https://issues.apache.org/jira/browse/AMBARI-19688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836757#comment-15836757 ] Xi Wang commented on AMBARI-19688: -- +1 for patch. > Ubuntu14 base url fields on "Select version" page are duplicates > > > Key: AMBARI-19688 > URL: https://issues.apache.org/jira/browse/AMBARI-19688 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19688_diagnosis.patch > > > Ubuntu14 base url fields on "Select version" page are duplicates -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19699) Axis units and aggregators are wrong in some graphs of ambari grafana dashboards
[
https://issues.apache.org/jira/browse/AMBARI-19699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836735#comment-15836735
]
Hadoop QA commented on AMBARI-19699:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849165/AMBARI-19699.v0.branch-2.5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10233//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10233//console
This message is automatically generated.
> Axis units and aggregators are wrong in some graphs of ambari grafana
> dashboards
>
>
> Key: AMBARI-19699
> URL: https://issues.apache.org/jira/browse/AMBARI-19699
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19699.v0.branch-2.5.patch
>
>
> Need to fix the following:
> ReadAllQuery.HostRoleCommandEntity is missing a Y axis.
> Total Cache Misses Y axis is wrong should not be time.
> Remove Max aggregator from all metrics (JVM dashboard)
> Cache Hits and Misses rate graphs aren't in the same units
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-19660) Add log rotation settings - handle upgrade scenario - Storm, Hive
[ https://issues.apache.org/jira/browse/AMBARI-19660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-19660. Resolution: Fixed Committed to trunk and branch-2.5 > Add log rotation settings - handle upgrade scenario - Storm, Hive > - > > Key: AMBARI-19660 > URL: https://issues.apache.org/jira/browse/AMBARI-19660 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > > Changes made to all upgrade packs 2.3->2.4,2.5,2.6 ; 2.4->2.5,2.6 ; 2.5->2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19682) Small fixes to log4j rotation properties - Yarn, ZooKeeper, AMS-Hbase, Logsearch/Logfeeder
[ https://issues.apache.org/jira/browse/AMBARI-19682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-19682. Resolution: Fixed Committed to trunk and branch-2.5 > Small fixes to log4j rotation properties - Yarn, ZooKeeper, AMS-Hbase, > Logsearch/Logfeeder > -- > > Key: AMBARI-19682 > URL: https://issues.apache.org/jira/browse/AMBARI-19682 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > > Naming convention changes for services listed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19693) Permission issues with conf.server/hive-site.xml across several hive components
[
https://issues.apache.org/jira/browse/AMBARI-19693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-19693:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> Permission issues with conf.server/hive-site.xml across several hive
> components
> ---
>
> Key: AMBARI-19693
> URL: https://issues.apache.org/jira/browse/AMBARI-19693
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19693-branch-2.5.patch, AMBARI-19693.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 193, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 95, in service_check
> hcat_service_check()
> 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/HIVE/0.12.0.2.0/package/scripts/hcat_service_check.py",
> line 65, in hcat_service_check
> logoutput=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
> ambari...@example.com; env JAVA_HOME=/usr/jdk64/jdk1.7.0_67
> /var/lib/ambari-agent/tmp/hcatSmoke.sh hcatsmokeid16ac7075_date383016 prepare
> true' returned 88. Hortonworks #
> This is MOTD message, added for testing in qe infra
> WARNING: Use "yarn jar" to launch YARN applications.
> FAILED: SemanticException [Error 10072]: Database does not exist: default
> WARNING: Use "yarn jar" to launch YARN applications.
> OK
> Time taken: 3.012 seconds
> WARNING: Use "yarn jar" to launch YARN applications.
> FAILED: SemanticException [Error 10072]: Database does not exist: default
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19681) Credential Store should add hadoop credential provider path property to all affected configuration types
[
https://issues.apache.org/jira/browse/AMBARI-19681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836674#comment-15836674
]
Hudson commented on AMBARI-19681:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6531 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6531/])
AMBARI-19681: Credential store should add hadoop credential provider
(nsomasundaram:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f4f7571d8f9a7709f030cd2587052492e40e8527])
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/security_commons.py
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
> Credential Store should add hadoop credential provider path property to all
> affected configuration types
>
>
> Key: AMBARI-19681
> URL: https://issues.apache.org/jira/browse/AMBARI-19681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55853.patch
>
>
> CustomServiceOrchestrator.py function generateJceks adds the property
> 'hadoop.security.credential.provider.path' only to the last configuration
> type that requires it. The function iterates over the configtype_credentials
> dictionary, and at each iteration it updates the variable named config (line
> 272):
> {code}
> config = commandJson['configurations'][config_type]
> {code}
> After the iteration is over, and the provider_paths variable is set the
> function adds the provider paths to the dictionary with the key
> 'hadoop.security.credential.provider.path' (line 292)
> {code}
> config[self.CREDENTIAL_PROVIDER_PROPERTY_NAME] = ','.join(provider_paths)
> {code}
> The problem is that at this point the variable config contains the latest
> config type that needs this property to be set up, while all of them should
> have it! So if both config_type_1, and config_type_2 have passwords
> properties present in configtype_credentials, only config_type_2 will have
> the dictionary entry set for the key
> 'hadoop.security.credential.provider.path', and it will contain a reference
> to both of their jceks files!
> Another issue is that there is no reason to collect the provider paths to an
> array, each config_type should have a reference only to it's own provider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19693) Permission issues with conf.server/hive-site.xml across several hive components
[
https://issues.apache.org/jira/browse/AMBARI-19693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-19693:
-
Attachment: AMBARI-19693-branch-2.5.patch
> Permission issues with conf.server/hive-site.xml across several hive
> components
> ---
>
> Key: AMBARI-19693
> URL: https://issues.apache.org/jira/browse/AMBARI-19693
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19693-branch-2.5.patch, AMBARI-19693.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 193, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 95, in service_check
> hcat_service_check()
> 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/HIVE/0.12.0.2.0/package/scripts/hcat_service_check.py",
> line 65, in hcat_service_check
> logoutput=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
> ambari...@example.com; env JAVA_HOME=/usr/jdk64/jdk1.7.0_67
> /var/lib/ambari-agent/tmp/hcatSmoke.sh hcatsmokeid16ac7075_date383016 prepare
> true' returned 88. Hortonworks #
> This is MOTD message, added for testing in qe infra
> WARNING: Use "yarn jar" to launch YARN applications.
> FAILED: SemanticException [Error 10072]: Database does not exist: default
> WARNING: Use "yarn jar" to launch YARN applications.
> OK
> Time taken: 3.012 seconds
> WARNING: Use "yarn jar" to launch YARN applications.
> FAILED: SemanticException [Error 10072]: Database does not exist: default
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19685) Stack advisor needs to enforce component dependency for slaves and masters
[
https://issues.apache.org/jira/browse/AMBARI-19685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836669#comment-15836669
]
Hadoop QA commented on AMBARI-19685:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849157/AMBARI-19685.2.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 7 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-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10232//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10232//console
This message is automatically generated.
> Stack advisor needs to enforce component dependency for slaves and masters
> --
>
> Key: AMBARI-19685
> URL: https://issues.apache.org/jira/browse/AMBARI-19685
> Project: Ambari
> Issue Type: Task
> Components: ambari-sever
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 3.0.0
>
> Attachments: AMBARI-19685.2.patch, AMBARI-19685.patch
>
>
> * Install Ambari cluster with latest trunk bits
> * Modify
> /var/lib/ambari-server/resources/common-services/ZEPPELIN/0.6.0.2.5/metainfo.xml
> to add the following:
> {noformat}
> Add to node of ZEPPELIN_MASTER:
>
> SPARK/LIVY_SERVER
> host
>
> Add to node:
>
> SPARK
>
> {noformat}
> * Install HDP 2.5.3 cluster with Spark
> * Once the cluster is installed, use Add Service Wizard to add Zeppelin
> * Assign Slaves and Clients step should appear (without the metainfo.xml
> change, it will be skipped)
> * The user should not be able to proceed beyond this page unless at least one
> Livy Server is selected <- this validation should be handled by the stack
> advisor
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19681) Credential Store should add hadoop credential provider path property to all affected configuration types
[
https://issues.apache.org/jira/browse/AMBARI-19681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836656#comment-15836656
]
Hudson commented on AMBARI-19681:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #788 (See
[https://builds.apache.org/job/Ambari-branch-2.5/788/])
AMBARI-19681: Credential store should add hadoop credential provider
(nsomasundaram:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=77bd5ebebaf5808a4e9627cca0b0a77a12ad6aec])
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/security_commons.py
> Credential Store should add hadoop credential provider path property to all
> affected configuration types
>
>
> Key: AMBARI-19681
> URL: https://issues.apache.org/jira/browse/AMBARI-19681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55853.patch
>
>
> CustomServiceOrchestrator.py function generateJceks adds the property
> 'hadoop.security.credential.provider.path' only to the last configuration
> type that requires it. The function iterates over the configtype_credentials
> dictionary, and at each iteration it updates the variable named config (line
> 272):
> {code}
> config = commandJson['configurations'][config_type]
> {code}
> After the iteration is over, and the provider_paths variable is set the
> function adds the provider paths to the dictionary with the key
> 'hadoop.security.credential.provider.path' (line 292)
> {code}
> config[self.CREDENTIAL_PROVIDER_PROPERTY_NAME] = ','.join(provider_paths)
> {code}
> The problem is that at this point the variable config contains the latest
> config type that needs this property to be set up, while all of them should
> have it! So if both config_type_1, and config_type_2 have passwords
> properties present in configtype_credentials, only config_type_2 will have
> the dictionary entry set for the key
> 'hadoop.security.credential.provider.path', and it will contain a reference
> to both of their jceks files!
> Another issue is that there is no reason to collect the provider paths to an
> array, each config_type should have a reference only to it's own provider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19699) Axis units and aggregators are wrong in some graphs of ambari grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-19699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19699: Status: Patch Available (was: Open) > Axis units and aggregators are wrong in some graphs of ambari grafana > dashboards > > > Key: AMBARI-19699 > URL: https://issues.apache.org/jira/browse/AMBARI-19699 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19699.v0.branch-2.5.patch > > > Need to fix the following: > ReadAllQuery.HostRoleCommandEntity is missing a Y axis. > Total Cache Misses Y axis is wrong should not be time. > Remove Max aggregator from all metrics (JVM dashboard) > Cache Hits and Misses rate graphs aren't in the same units -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19699) Axis units and aggregators are wrong in some graphs of ambari grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-19699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19699: Attachment: AMBARI-19699.v0.branch-2.5.patch > Axis units and aggregators are wrong in some graphs of ambari grafana > dashboards > > > Key: AMBARI-19699 > URL: https://issues.apache.org/jira/browse/AMBARI-19699 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19699.v0.branch-2.5.patch > > > Need to fix the following: > ReadAllQuery.HostRoleCommandEntity is missing a Y axis. > Total Cache Misses Y axis is wrong should not be time. > Remove Max aggregator from all metrics (JVM dashboard) > Cache Hits and Misses rate graphs aren't in the same units -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-13324) Ambari doesn't create Flume Kerberos principal + keytab
[ https://issues.apache.org/jira/browse/AMBARI-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836640#comment-15836640 ] Hudson commented on AMBARI-13324: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6530 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6530/]) AMBARI-13324 automate creating Flume Keytab and principal (Shi Wang via (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d77f3a54fcbb79e9a2518a56bb78b0468a8a8b4f]) * (edit) ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/params.py * (add) ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/flume_check.py * (edit) ambari-server/src/test/python/stacks/2.0.6/FLUME/test_service_check.py > Ambari doesn't create Flume Kerberos principal + keytab > --- > > Key: AMBARI-13324 > URL: https://issues.apache.org/jira/browse/AMBARI-13324 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 > Environment: HDP 2.3 + Kerberos MIT KDC >Reporter: Hari Sekhon >Assignee: Shi Wang > Fix For: trunk > > Attachments: > 0001-AMBARI-13324-Ambari-doesn-t-create-Flume-Kerberos-pr.patch, > flume_kerberos.txt > > > When deploying Kerberos via Ambari with MIT KDC, Ambari doesn't generate a > Kerberos principal and keytab for Flume. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19697) Uninstalled services including Ganglia is coming up in Config History-Service dropdown
[ https://issues.apache.org/jira/browse/AMBARI-19697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhanya Balasundaran updated AMBARI-19697: - Description: - Navigate to dashboard page - Choose 'Config History' tab - Service dropdown has all services supported by the stack. It even shows Ganglia which is not supported now. Checked on an older version and its not there. was: - Navigate to dashboard page - Choose 'Config History' tab - In Service dropdown we have Ganglia which is not supported now. Checked on an older version and its not there. > Uninstalled services including Ganglia is coming up in Config History-Service > dropdown > -- > > Key: AMBARI-19697 > URL: https://issues.apache.org/jira/browse/AMBARI-19697 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran > Fix For: 2.5.0 > > > - Navigate to dashboard page > - Choose 'Config History' tab > - Service dropdown has all services supported by the stack. It even shows > Ganglia which is not supported now. > Checked on an older version and its not there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19697) Uninstalled services including Ganglia is coming up in Config History-Service dropdown
[ https://issues.apache.org/jira/browse/AMBARI-19697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhanya Balasundaran updated AMBARI-19697: - Summary: Uninstalled services including Ganglia is coming up in Config History-Service dropdown (was: Ganglia is coming up in Config History-Service dropdown) > Uninstalled services including Ganglia is coming up in Config History-Service > dropdown > -- > > Key: AMBARI-19697 > URL: https://issues.apache.org/jira/browse/AMBARI-19697 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran > Fix For: 2.5.0 > > > - Navigate to dashboard page > - Choose 'Config History' tab > - In Service dropdown we have Ganglia which is not supported now. > Checked on an older version and its not there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19699) Axis units and aggregators are wrong in some graphs of ambari grafana dashboards
Vivek Ratnavel Subramanian created AMBARI-19699: --- Summary: Axis units and aggregators are wrong in some graphs of ambari grafana dashboards Key: AMBARI-19699 URL: https://issues.apache.org/jira/browse/AMBARI-19699 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Priority: Minor Fix For: 2.5.0 Need to fix the following: ReadAllQuery.HostRoleCommandEntity is missing a Y axis. Total Cache Misses Y axis is wrong should not be time. Remove Max aggregator from all metrics (JVM dashboard) Cache Hits and Misses rate graphs aren't in the same units -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19698) Author name in config history is not shown completely
Dhanya Balasundaran created AMBARI-19698: Summary: Author name in config history is not shown completely Key: AMBARI-19698 URL: https://issues.apache.org/jira/browse/AMBARI-19698 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Dhanya Balasundaran Fix For: 2.5.0 Author name 'testuserconfighistory' is ellipsised and shown as 'testuserconfigh...'in direct view as well as pop up view at the configs history. Looks like there is no option for user to see the complete name of the author -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-18574:
Description:
The default value for hbase.hregion.memstore.chunkpool.maxsize is:
{code}
final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
{code}
This would result in chunk pool being disabled, leading to excessive
MemStoreLAB chunk allocations.
Ambari should set the value to 1.0
was:
The default value for hbase.hregion.memstore.chunkpool.maxsize is:
{code}
final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
{code}
This would result in chunk pool being disabled, leading to excessive
MemStoreLAB chunk allocations.
Ambari should set the value to 1.0
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19697) Ganglia is coming up in Config History-Service dropdown
Dhanya Balasundaran created AMBARI-19697: Summary: Ganglia is coming up in Config History-Service dropdown Key: AMBARI-19697 URL: https://issues.apache.org/jira/browse/AMBARI-19697 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Dhanya Balasundaran Fix For: 2.5.0 - Navigate to dashboard page - Choose 'Config History' tab - In Service dropdown we have Ganglia which is not supported now. Checked on an older version and its not there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19695) Remove thrown exceptions while validating Kerberos Authentication configuration
[
https://issues.apache.org/jira/browse/AMBARI-19695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836623#comment-15836623
]
Hadoop QA commented on AMBARI-19695:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849132/AMBARI-19695.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 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/10231//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10231//console
This message is automatically generated.
> Remove thrown exceptions while validating Kerberos Authentication
> configuration
> ---
>
> Key: AMBARI-19695
> URL: https://issues.apache.org/jira/browse/AMBARI-19695
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 2.5.0
>
> Attachments: AMBARI-19695.2.5.patch, AMBARI-19695.trunk.patch
>
>
> When starting Ambari where Kerberos authentication is enabled
> (authentication.kerberos.enabled=true), Ambari validates the relevant
> configuration properties. If a sever issue is found, an exception is thrown.
> This causes issues in installations where Ambari is expected to be able to
> perform Kerberos authentication but all of the data is available for since
> this is it expected to be provided later. For example, the SPNEGO keytab file
> will be created when Kerberos is enabled sometime after Ambari starts up.
> To prevent Ambari from shutting down when all the required data is not
> available, thrown exceptions should be removed from
> org.apache.ambari.server.configuration.Configuration#createKerberosAuthenticationProperties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19681) Credential Store should add hadoop credential provider path property to all affected configuration types
[
https://issues.apache.org/jira/browse/AMBARI-19681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19681:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.5 and trunk
> Credential Store should add hadoop credential provider path property to all
> affected configuration types
>
>
> Key: AMBARI-19681
> URL: https://issues.apache.org/jira/browse/AMBARI-19681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55853.patch
>
>
> CustomServiceOrchestrator.py function generateJceks adds the property
> 'hadoop.security.credential.provider.path' only to the last configuration
> type that requires it. The function iterates over the configtype_credentials
> dictionary, and at each iteration it updates the variable named config (line
> 272):
> {code}
> config = commandJson['configurations'][config_type]
> {code}
> After the iteration is over, and the provider_paths variable is set the
> function adds the provider paths to the dictionary with the key
> 'hadoop.security.credential.provider.path' (line 292)
> {code}
> config[self.CREDENTIAL_PROVIDER_PROPERTY_NAME] = ','.join(provider_paths)
> {code}
> The problem is that at this point the variable config contains the latest
> config type that needs this property to be set up, while all of them should
> have it! So if both config_type_1, and config_type_2 have passwords
> properties present in configtype_credentials, only config_type_2 will have
> the dictionary entry set for the key
> 'hadoop.security.credential.provider.path', and it will contain a reference
> to both of their jceks files!
> Another issue is that there is no reason to collect the provider paths to an
> array, each config_type should have a reference only to it's own provider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-13324) Ambari doesn't create Flume Kerberos principal + keytab
[ https://issues.apache.org/jira/browse/AMBARI-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-13324: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari doesn't create Flume Kerberos principal + keytab > --- > > Key: AMBARI-13324 > URL: https://issues.apache.org/jira/browse/AMBARI-13324 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 > Environment: HDP 2.3 + Kerberos MIT KDC >Reporter: Hari Sekhon >Assignee: Shi Wang > Fix For: trunk > > Attachments: > 0001-AMBARI-13324-Ambari-doesn-t-create-Flume-Kerberos-pr.patch, > flume_kerberos.txt > > > When deploying Kerberos via Ambari with MIT KDC, Ambari doesn't generate a > Kerberos principal and keytab for Flume. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-13324) Ambari doesn't create Flume Kerberos principal + keytab
[ https://issues.apache.org/jira/browse/AMBARI-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836579#comment-15836579 ] Di Li commented on AMBARI-13324: pushed to trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=d77f3a54fcbb79e9a2518a56bb78b0468a8a8b4f > Ambari doesn't create Flume Kerberos principal + keytab > --- > > Key: AMBARI-13324 > URL: https://issues.apache.org/jira/browse/AMBARI-13324 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 > Environment: HDP 2.3 + Kerberos MIT KDC >Reporter: Hari Sekhon >Assignee: Shi Wang > Fix For: trunk > > Attachments: > 0001-AMBARI-13324-Ambari-doesn-t-create-Flume-Kerberos-pr.patch, > flume_kerberos.txt > > > When deploying Kerberos via Ambari with MIT KDC, Ambari doesn't generate a > Kerberos principal and keytab for Flume. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19681) Credential Store should add hadoop credential provider path property to all affected configuration types
[
https://issues.apache.org/jira/browse/AMBARI-19681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836542#comment-15836542
]
Hadoop QA commented on AMBARI-19681:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849145/rb55853.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-agent.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10230//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10230//console
This message is automatically generated.
> Credential Store should add hadoop credential provider path property to all
> affected configuration types
>
>
> Key: AMBARI-19681
> URL: https://issues.apache.org/jira/browse/AMBARI-19681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55853.patch
>
>
> CustomServiceOrchestrator.py function generateJceks adds the property
> 'hadoop.security.credential.provider.path' only to the last configuration
> type that requires it. The function iterates over the configtype_credentials
> dictionary, and at each iteration it updates the variable named config (line
> 272):
> {code}
> config = commandJson['configurations'][config_type]
> {code}
> After the iteration is over, and the provider_paths variable is set the
> function adds the provider paths to the dictionary with the key
> 'hadoop.security.credential.provider.path' (line 292)
> {code}
> config[self.CREDENTIAL_PROVIDER_PROPERTY_NAME] = ','.join(provider_paths)
> {code}
> The problem is that at this point the variable config contains the latest
> config type that needs this property to be set up, while all of them should
> have it! So if both config_type_1, and config_type_2 have passwords
> properties present in configtype_credentials, only config_type_2 will have
> the dictionary entry set for the key
> 'hadoop.security.credential.provider.path', and it will contain a reference
> to both of their jceks files!
> Another issue is that there is no reason to collect the provider paths to an
> array, each config_type should have a reference only to it's own provider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19685) Stack advisor needs to enforce component dependency for slaves and masters
[
https://issues.apache.org/jira/browse/AMBARI-19685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-19685:
--
Attachment: AMBARI-19685.2.patch
> Stack advisor needs to enforce component dependency for slaves and masters
> --
>
> Key: AMBARI-19685
> URL: https://issues.apache.org/jira/browse/AMBARI-19685
> Project: Ambari
> Issue Type: Task
> Components: ambari-sever
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 3.0.0
>
> Attachments: AMBARI-19685.2.patch, AMBARI-19685.patch
>
>
> * Install Ambari cluster with latest trunk bits
> * Modify
> /var/lib/ambari-server/resources/common-services/ZEPPELIN/0.6.0.2.5/metainfo.xml
> to add the following:
> {noformat}
> Add to node of ZEPPELIN_MASTER:
>
> SPARK/LIVY_SERVER
> host
>
> Add to node:
>
> SPARK
>
> {noformat}
> * Install HDP 2.5.3 cluster with Spark
> * Once the cluster is installed, use Add Service Wizard to add Zeppelin
> * Assign Slaves and Clients step should appear (without the metainfo.xml
> change, it will be skipped)
> * The user should not be able to proceed beyond this page unless at least one
> Livy Server is selected <- this validation should be handled by the stack
> advisor
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19592) Create grafana dashboards for Druid Metrics
[ https://issues.apache.org/jira/browse/AMBARI-19592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836521#comment-15836521 ] Hudson commented on AMBARI-19592: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #787 (See [https://builds.apache.org/job/Ambari-branch-2.5/787/]) AMBARI-19592 : Create grafana dashboards for Druid Metrics and configure (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9bc595ef5719c6e63d432f012ab095beec0a70e1]) * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-common.xml * (add) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-druid-home.json * (add) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-druid-ingestion.json * (edit) ambari-metrics/ambari-metrics-grafana/ambari-metrics/datasource.js * (add) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-druid-query.json * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py > Create grafana dashboards for Druid Metrics > --- > > Key: AMBARI-19592 > URL: https://issues.apache.org/jira/browse/AMBARI-19592 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-19592.patch > > > Druid can now ingest metrics to ambari-metrics-server. > Add grafana dashboards for druid metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13324) Ambari doesn't create Flume Kerberos principal + keytab
[ https://issues.apache.org/jira/browse/AMBARI-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Wang updated AMBARI-13324: -- Attachment: (was: 0001-AMBARI-13324-createFlumeKeytab.patch) > Ambari doesn't create Flume Kerberos principal + keytab > --- > > Key: AMBARI-13324 > URL: https://issues.apache.org/jira/browse/AMBARI-13324 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 > Environment: HDP 2.3 + Kerberos MIT KDC >Reporter: Hari Sekhon >Assignee: Shi Wang > Fix For: trunk > > Attachments: > 0001-AMBARI-13324-Ambari-doesn-t-create-Flume-Kerberos-pr.patch, > flume_kerberos.txt > > > When deploying Kerberos via Ambari with MIT KDC, Ambari doesn't generate a > Kerberos principal and keytab for Flume. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13324) Ambari doesn't create Flume Kerberos principal + keytab
[ https://issues.apache.org/jira/browse/AMBARI-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Wang updated AMBARI-13324: -- Attachment: 0001-AMBARI-13324-Ambari-doesn-t-create-Flume-Kerberos-pr.patch > Ambari doesn't create Flume Kerberos principal + keytab > --- > > Key: AMBARI-13324 > URL: https://issues.apache.org/jira/browse/AMBARI-13324 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 > Environment: HDP 2.3 + Kerberos MIT KDC >Reporter: Hari Sekhon >Assignee: Shi Wang > Fix For: trunk > > Attachments: > 0001-AMBARI-13324-Ambari-doesn-t-create-Flume-Kerberos-pr.patch, > flume_kerberos.txt > > > When deploying Kerberos via Ambari with MIT KDC, Ambari doesn't generate a > Kerberos principal and keytab for Flume. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19592) Create grafana dashboards for Druid Metrics
[ https://issues.apache.org/jira/browse/AMBARI-19592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836519#comment-15836519 ] Hudson commented on AMBARI-19592: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6529 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6529/]) AMBARI-19592 : Create grafana dashboards for Druid Metrics and configure (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ad0f4ecc67e39d109449e945b5108440059b4240]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py * (add) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-druid-home.json * (add) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-druid-ingestion.json * (add) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-druid-query.json * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/params.py * (edit) ambari-metrics/ambari-metrics-grafana/ambari-metrics/datasource.js * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-common.xml > Create grafana dashboards for Druid Metrics > --- > > Key: AMBARI-19592 > URL: https://issues.apache.org/jira/browse/AMBARI-19592 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-19592.patch > > > Druid can now ingest metrics to ambari-metrics-server. > Add grafana dashboards for druid metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19668) Supporting zookeeper security only from HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-19668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836518#comment-15836518 ] Hudson commented on AMBARI-19668: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6529 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6529/]) AMBARI-19668. Supporting zookeeper security only from HDP 2.6. (Attila (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d0dc19e0c95000a87884029ddb6c7ab4f3f32fb7]) * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/services/HDFS/configuration/hadoop-env.xml * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/OOZIE/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/configuration/hadoop-env.xml * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/properties/stack_features.json * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.3/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/kerberos.json * (edit) ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/hadoop-env.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HDFS/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/YARN/kerberos.json * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/configuration/hadoop-env.xml * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/hadoop-env.xml * (edit) ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/kerberos.json * (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/YARN/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/properties/stack_features.json * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/properties/stack_features.json * (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/zkfc_slave.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/YARN/kerberos.json * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/zkfc_slave.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_zkfc.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/constants.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/kerberos.json > Supporting zookeeper security only from HDP 2.6 > --- > > Key: AMBARI-19668 > URL: https://issues.apache.org/jira/browse/AMBARI-19668 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.5.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 2.5.0 > > Attachments: AMBARI-19668_branch-2.5.patch, AMBARI-19668_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19696) Move HS2 does not install dependent components on the target host
Andrii Tkach created AMBARI-19696: - Summary: Move HS2 does not install dependent components on the target host Key: AMBARI-19696 URL: https://issues.apache.org/jira/browse/AMBARI-19696 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.5.0 Fix the Move Wizard to install the dependencies automatically as we do in Install/Add Service Wizards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19689) Error on Files view-SIMPLE authentication is not enabled
[ https://issues.apache.org/jira/browse/AMBARI-19689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836464#comment-15836464 ] Hudson commented on AMBARI-19689: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6528 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6528/]) AMBARI-19689. Error on Files view-SIMPLE authentication is not enabled. (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=75b30a4e974bce0df3cd9d2d0efc428f101d8601]) * (edit) contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/ConfigurationBuilder.java > Error on Files view-SIMPLE authentication is not enabled > > > Key: AMBARI-19689 > URL: https://issues.apache.org/jira/browse/AMBARI-19689 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-19689_trunk.patch > > > 20 Jan 2017 09:07:12,659 INFO [ambari-client-thread-17242] HdfsUtil:151 - > HdfsApi connected OK > 20 Jan 2017 09:07:12,661 INFO [ambari-client-thread-17242] > TrashPolicyDefault:87 - Namenode trash configuration: Deletion interval = 360 > minutes, Emptier interval = 0 minutes. > 20 Jan 2017 09:07:12,664 WARN [ambari-client-thread-17242] > RetryInvocationHandler:217 - Exception while invoking > ClientNamenodeProtocolTranslatorPB.getFileInfo over null. Not retrying > because try once and fail. > org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException): > SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS] > at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1552) > at org.apache.hadoop.ipc.Client.call(Client.java:1496) > at org.apache.hadoop.ipc.Client.call(Client.java:1396) > at > org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233) > at com.sun.proxy.$Proxy171.getFileInfo(Unknown Source) > at > org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getFileInfo(ClientNamenodeProtocolTranslatorPB.java:816) > at sun.reflect.GeneratedMethodAccessor844.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:278) > at > org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:194) > at > org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:176) > at com.sun.proxy.$Proxy172.getFileInfo(Unknown Source) > at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:2158) > at > org.apache.hadoop.hdfs.DistributedFileSystem$25.doCall(DistributedFileSystem.java:1423) > at > org.apache.hadoop.hdfs.DistributedFileSystem$25.doCall(DistributedFileSystem.java:1419) > at > org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) > at > org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1419) > at org.apache.ambari.view.utils.hdfs.HdfsApi$3.run(HdfsApi.java:130) > at org.apache.ambari.view.utils.hdfs.HdfsApi$3.run(HdfsApi.java:128) > 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:1724) > at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:400) > at > org.apache.ambari.view.utils.hdfs.HdfsApi.getFileStatus(HdfsApi.java:128) > at > org.apache.ambari.view.commons.hdfs.UserService.trashdir(UserService.java:105) > 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 > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at >
[jira] [Updated] (AMBARI-19686) Add condition for detecting Blueprint call so that 'llap' named queue can be created on 1st BP invocation, if deemed required.
[ https://issues.apache.org/jira/browse/AMBARI-19686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19686: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add condition for detecting Blueprint call so that 'llap' named queue can be > created on 1st BP invocation, if deemed required. > -- > > Key: AMBARI-19686 > URL: https://issues.apache.org/jira/browse/AMBARI-19686 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19686.patch > > > - The 1st BP call is not getting the 'llap' named queue created, and is > expected to create the queue. In the same scenario, where we enable Hive > Server Interactive (HSI) from UI, the queue gets created. > *Issue:* > - The current code is checking if there is *enable_hive_interactive* in > changed-configurations, then only allow queue creation, implying 1st > invocation. This is not true for BP 1st time invocation where HSI would be > started. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19681) Credential Store should add hadoop credential provider path property to all affected configuration types
[
https://issues.apache.org/jira/browse/AMBARI-19681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19681:
---
Attachment: (was: BUG-72951.patch)
> Credential Store should add hadoop credential provider path property to all
> affected configuration types
>
>
> Key: AMBARI-19681
> URL: https://issues.apache.org/jira/browse/AMBARI-19681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55853.patch
>
>
> CustomServiceOrchestrator.py function generateJceks adds the property
> 'hadoop.security.credential.provider.path' only to the last configuration
> type that requires it. The function iterates over the configtype_credentials
> dictionary, and at each iteration it updates the variable named config (line
> 272):
> {code}
> config = commandJson['configurations'][config_type]
> {code}
> After the iteration is over, and the provider_paths variable is set the
> function adds the provider paths to the dictionary with the key
> 'hadoop.security.credential.provider.path' (line 292)
> {code}
> config[self.CREDENTIAL_PROVIDER_PROPERTY_NAME] = ','.join(provider_paths)
> {code}
> The problem is that at this point the variable config contains the latest
> config type that needs this property to be set up, while all of them should
> have it! So if both config_type_1, and config_type_2 have passwords
> properties present in configtype_credentials, only config_type_2 will have
> the dictionary entry set for the key
> 'hadoop.security.credential.provider.path', and it will contain a reference
> to both of their jceks files!
> Another issue is that there is no reason to collect the provider paths to an
> array, each config_type should have a reference only to it's own provider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19592) Create grafana dashboards for Druid Metrics
[
https://issues.apache.org/jira/browse/AMBARI-19592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19592:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to
branch-2.5
{code}
commit 9bc595ef5719c6e63d432f012ab095beec0a70e1
Author: Aravindan Vijayan
Date: Tue Jan 24 10:51:18 2017 -0800
AMBARI-19592 : Create grafana dashboards for Druid Metrics and configure
druid to send metrics to AMS. (Nishant Bangarwa via avijayan)
{code}
and trunk.
{code}
commit ad0f4ecc67e39d109449e945b5108440059b4240
Author: Aravindan Vijayan
Date: Tue Jan 24 10:52:56 2017 -0800
AMBARI-19592 : Create grafana dashboards for Druid Metrics and configure
druid to send metrics to AMS. (Nishant Bangarwa via avijayan)
{code}
> Create grafana dashboards for Druid Metrics
> ---
>
> Key: AMBARI-19592
> URL: https://issues.apache.org/jira/browse/AMBARI-19592
> Project: Ambari
> Issue Type: Task
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19592.patch
>
>
> Druid can now ingest metrics to ambari-metrics-server.
> Add grafana dashboards for druid metrics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19681) Credential Store should add hadoop credential provider path property to all affected configuration types
[
https://issues.apache.org/jira/browse/AMBARI-19681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19681:
---
Attachment: rb55853.patch
> Credential Store should add hadoop credential provider path property to all
> affected configuration types
>
>
> Key: AMBARI-19681
> URL: https://issues.apache.org/jira/browse/AMBARI-19681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: BUG-72951.patch, rb55853.patch
>
>
> CustomServiceOrchestrator.py function generateJceks adds the property
> 'hadoop.security.credential.provider.path' only to the last configuration
> type that requires it. The function iterates over the configtype_credentials
> dictionary, and at each iteration it updates the variable named config (line
> 272):
> {code}
> config = commandJson['configurations'][config_type]
> {code}
> After the iteration is over, and the provider_paths variable is set the
> function adds the provider paths to the dictionary with the key
> 'hadoop.security.credential.provider.path' (line 292)
> {code}
> config[self.CREDENTIAL_PROVIDER_PROPERTY_NAME] = ','.join(provider_paths)
> {code}
> The problem is that at this point the variable config contains the latest
> config type that needs this property to be set up, while all of them should
> have it! So if both config_type_1, and config_type_2 have passwords
> properties present in configtype_credentials, only config_type_2 will have
> the dictionary entry set for the key
> 'hadoop.security.credential.provider.path', and it will contain a reference
> to both of their jceks files!
> Another issue is that there is no reason to collect the provider paths to an
> array, each config_type should have a reference only to it's own provider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19681) Credential Store should add hadoop credential provider path property to all affected configuration types
[
https://issues.apache.org/jira/browse/AMBARI-19681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19681:
---
Status: Patch Available (was: Open)
> Credential Store should add hadoop credential provider path property to all
> affected configuration types
>
>
> Key: AMBARI-19681
> URL: https://issues.apache.org/jira/browse/AMBARI-19681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55853.patch
>
>
> CustomServiceOrchestrator.py function generateJceks adds the property
> 'hadoop.security.credential.provider.path' only to the last configuration
> type that requires it. The function iterates over the configtype_credentials
> dictionary, and at each iteration it updates the variable named config (line
> 272):
> {code}
> config = commandJson['configurations'][config_type]
> {code}
> After the iteration is over, and the provider_paths variable is set the
> function adds the provider paths to the dictionary with the key
> 'hadoop.security.credential.provider.path' (line 292)
> {code}
> config[self.CREDENTIAL_PROVIDER_PROPERTY_NAME] = ','.join(provider_paths)
> {code}
> The problem is that at this point the variable config contains the latest
> config type that needs this property to be set up, while all of them should
> have it! So if both config_type_1, and config_type_2 have passwords
> properties present in configtype_credentials, only config_type_2 will have
> the dictionary entry set for the key
> 'hadoop.security.credential.provider.path', and it will contain a reference
> to both of their jceks files!
> Another issue is that there is no reason to collect the provider paths to an
> array, each config_type should have a reference only to it's own provider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19681) Credential Store should add hadoop credential provider path property to all affected configuration types
[
https://issues.apache.org/jira/browse/AMBARI-19681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19681:
---
Status: Open (was: Patch Available)
> Credential Store should add hadoop credential provider path property to all
> affected configuration types
>
>
> Key: AMBARI-19681
> URL: https://issues.apache.org/jira/browse/AMBARI-19681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55853.patch
>
>
> CustomServiceOrchestrator.py function generateJceks adds the property
> 'hadoop.security.credential.provider.path' only to the last configuration
> type that requires it. The function iterates over the configtype_credentials
> dictionary, and at each iteration it updates the variable named config (line
> 272):
> {code}
> config = commandJson['configurations'][config_type]
> {code}
> After the iteration is over, and the provider_paths variable is set the
> function adds the provider paths to the dictionary with the key
> 'hadoop.security.credential.provider.path' (line 292)
> {code}
> config[self.CREDENTIAL_PROVIDER_PROPERTY_NAME] = ','.join(provider_paths)
> {code}
> The problem is that at this point the variable config contains the latest
> config type that needs this property to be set up, while all of them should
> have it! So if both config_type_1, and config_type_2 have passwords
> properties present in configtype_credentials, only config_type_2 will have
> the dictionary entry set for the key
> 'hadoop.security.credential.provider.path', and it will contain a reference
> to both of their jceks files!
> Another issue is that there is no reason to collect the provider paths to an
> array, each config_type should have a reference only to it's own provider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
