[jira] [Created] (AMBARI-20475) Issue with cut/copy functionality in workflow manager
Supreeth Sharma created AMBARI-20475: Summary: Issue with cut/copy functionality in workflow manager Key: AMBARI-20475 URL: https://issues.apache.org/jira/browse/AMBARI-20475 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Supreeth Sharma Priority: Blocker Fix For: 2.5.0 Action node configurations are getting copied across copied nodes even after pasting the original node. Steps to reproduce : 1) Create an action node. 2) Copy the node 3) Create a new node of the same type in the workflow by pasting the node. 4) Now modify the configurations for one node. Then configuration is also getting changed for the second node. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20473) Ambari build fails for views project that uses ember-cli
[ https://issues.apache.org/jira/browse/AMBARI-20473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20473: -- Attachment: AMBARI-20473_branch-2.5.patch > Ambari build fails for views project that uses ember-cli > > > Key: AMBARI-20473 > URL: https://issues.apache.org/jira/browse/AMBARI-20473 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20473_branch-2.5.patch, AMBARI-20473.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20474) Log4j Pattern for Storm cluster.xml and worker.xml Does Not Include Thread Information
[ https://issues.apache.org/jira/browse/AMBARI-20474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated AMBARI-20474: Status: Patch Available (was: In Progress) > Log4j Pattern for Storm cluster.xml and worker.xml Does Not Include Thread > Information > -- > > Key: AMBARI-20474 > URL: https://issues.apache.org/jira/browse/AMBARI-20474 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Critical > Attachments: storm_log4j_updated_config.patch > > > Add thread information to make log patterns match Storm codebase -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20474) Log4j Pattern for Storm cluster.xml and worker.xml Does Not Include Thread Information
[ https://issues.apache.org/jira/browse/AMBARI-20474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated AMBARI-20474: Attachment: storm_log4j_updated_config.patch > Log4j Pattern for Storm cluster.xml and worker.xml Does Not Include Thread > Information > -- > > Key: AMBARI-20474 > URL: https://issues.apache.org/jira/browse/AMBARI-20474 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Critical > Attachments: storm_log4j_updated_config.patch > > > Add thread information to make log patterns match Storm codebase -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20474) Log4j Pattern for Storm cluster.xml and worker.xml Does Not Include Thread Information
Hugo Louro created AMBARI-20474: --- Summary: Log4j Pattern for Storm cluster.xml and worker.xml Does Not Include Thread Information Key: AMBARI-20474 URL: https://issues.apache.org/jira/browse/AMBARI-20474 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Hugo Louro Assignee: Hugo Louro Priority: Critical Add thread information to make log patterns match Storm codebase -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20473) Ambari build fails for views project that uses ember-cli
[ https://issues.apache.org/jira/browse/AMBARI-20473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927477#comment-15927477 ] Sumit Mohanty commented on AMBARI-20473: LGTM, +1 > Ambari build fails for views project that uses ember-cli > > > Key: AMBARI-20473 > URL: https://issues.apache.org/jira/browse/AMBARI-20473 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20473.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20473) Ambari build fails for views project that uses ember-cli
[ https://issues.apache.org/jira/browse/AMBARI-20473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20473: -- Priority: Blocker (was: Major) > Ambari build fails for views project that uses ember-cli > > > Key: AMBARI-20473 > URL: https://issues.apache.org/jira/browse/AMBARI-20473 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20473.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20473) Ambari build fails for views project that uses ember-cli
[ https://issues.apache.org/jira/browse/AMBARI-20473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20473: -- Attachment: AMBARI-20473.patch > Ambari build fails for views project that uses ember-cli > > > Key: AMBARI-20473 > URL: https://issues.apache.org/jira/browse/AMBARI-20473 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-20473.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20473) Ambari build fails for views project that uses ember-cli
Jaimin Jetly created AMBARI-20473: - Summary: Ambari build fails for views project that uses ember-cli Key: AMBARI-20473 URL: https://issues.apache.org/jira/browse/AMBARI-20473 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20469) Add a new property to yarn-site.xml yarn.log.server.web-service.url
[ https://issues.apache.org/jira/browse/AMBARI-20469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927401#comment-15927401 ] Hudson commented on AMBARI-20469: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7053 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7053/]) AMBARI-20469. Add a new property to yarn-site.xml (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8ca09f9fc80a62d332c100e721b4cc2d2a16ceb3]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration/yarn-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py > Add a new property to yarn-site.xml yarn.log.server.web-service.url > --- > > Key: AMBARI-20469 > URL: https://issues.apache.org/jira/browse/AMBARI-20469 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-20469_trunk.patch > > > This property depends on yarn.timeline-service.webapp.address and > yarn.http.policy. > It is used by Yarn, Tez services. > The translation of the url from the default localhost to the actual hostname > has to happen depending on the http policy. > this is required in order to use the Tez Log Links. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20469) Add a new property to yarn-site.xml yarn.log.server.web-service.url
[ https://issues.apache.org/jira/browse/AMBARI-20469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927397#comment-15927397 ] Hudson commented on AMBARI-20469: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1267 (See [https://builds.apache.org/job/Ambari-branch-2.5/1267/]) AMBARI-20469. Add a new property to yarn-site.xml (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9e30137c6840c13fac0798313a7f8536243d5abd]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration/yarn-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java > Add a new property to yarn-site.xml yarn.log.server.web-service.url > --- > > Key: AMBARI-20469 > URL: https://issues.apache.org/jira/browse/AMBARI-20469 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-20469_trunk.patch > > > This property depends on yarn.timeline-service.webapp.address and > yarn.http.policy. > It is used by Yarn, Tez services. > The translation of the url from the default localhost to the actual hostname > has to happen depending on the http policy. > this is required in order to use the Tez Log Links. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20472) MapRed History server start does not create directories in HDFS when WEBHDFS is disabled.
[
https://issues.apache.org/jira/browse/AMBARI-20472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927389#comment-15927389
]
Hadoop QA commented on AMBARI-20472:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12858995/AMBARI-20472.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
contrib/fast-hdfs-resource.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11046//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11046//console
This message is automatically generated.
> MapRed History server start does not create directories in HDFS when WEBHDFS
> is disabled.
> -
>
> Key: AMBARI-20472
> URL: https://issues.apache.org/jira/browse/AMBARI-20472
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20472.patch
>
>
> MapRed HistoryServer start logic (implemented in yarn.py) creates various
> dirs in HDFS. The dir creation only runs thru when WEBHDFS is enabled. When
> WEBHDFS is disabled, HdfsResource calls bailed with NPE as the following one.
> Creating: Resource [source=null, target=/app-logs, type=directory,
> action=create, owner=yarn, group=hadoop, mode=777, recursiveChown=false,
> recursiveChmod=true, changePermissionforParents=false, manageIfExists=false]
> Exception occurred, Reason: null
> java.lang.NullPointerException
> at org.apache.hadoop.fs.FileSystem.fixRelativePart(FileSystem.java:2211)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1300)
> at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1426)
> at org.apache.ambari.fast_hdfs_resource.Runner.main(Runner.java:80)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20472) MapRed History server start does not create directories in HDFS when WEBHDFS is disabled.
[ https://issues.apache.org/jira/browse/AMBARI-20472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20472: --- Status: Patch Available (was: Open) > MapRed History server start does not create directories in HDFS when WEBHDFS > is disabled. > - > > Key: AMBARI-20472 > URL: https://issues.apache.org/jira/browse/AMBARI-20472 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20472.patch > > > MapRed HistoryServer start logic (implemented in yarn.py) creates various > dirs in HDFS. The dir creation only runs thru when WEBHDFS is enabled. When > WEBHDFS is disabled, HdfsResource calls bailed with NPE as the following one. > Creating: Resource [source=null, target=/app-logs, type=directory, > action=create, owner=yarn, group=hadoop, mode=777, recursiveChown=false, > recursiveChmod=true, changePermissionforParents=false, manageIfExists=false] > Exception occurred, Reason: null > java.lang.NullPointerException > at org.apache.hadoop.fs.FileSystem.fixRelativePart(FileSystem.java:2211) > at > org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1300) > at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1426) > at org.apache.ambari.fast_hdfs_resource.Runner.main(Runner.java:80) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20472) MapRed History server start does not create directories in HDFS when WEBHDFS is disabled.
[ https://issues.apache.org/jira/browse/AMBARI-20472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20472: --- Attachment: AMBARI-20472.patch > MapRed History server start does not create directories in HDFS when WEBHDFS > is disabled. > - > > Key: AMBARI-20472 > URL: https://issues.apache.org/jira/browse/AMBARI-20472 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20472.patch > > > MapRed HistoryServer start logic (implemented in yarn.py) creates various > dirs in HDFS. The dir creation only runs thru when WEBHDFS is enabled. When > WEBHDFS is disabled, HdfsResource calls bailed with NPE as the following one. > Creating: Resource [source=null, target=/app-logs, type=directory, > action=create, owner=yarn, group=hadoop, mode=777, recursiveChown=false, > recursiveChmod=true, changePermissionforParents=false, manageIfExists=false] > Exception occurred, Reason: null > java.lang.NullPointerException > at org.apache.hadoop.fs.FileSystem.fixRelativePart(FileSystem.java:2211) > at > org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1300) > at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1426) > at org.apache.ambari.fast_hdfs_resource.Runner.main(Runner.java:80) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20472) MapRed History server start does not create directories in HDFS when WEBHDFS is disabled.
Di Li created AMBARI-20472: -- Summary: MapRed History server start does not create directories in HDFS when WEBHDFS is disabled. Key: AMBARI-20472 URL: https://issues.apache.org/jira/browse/AMBARI-20472 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Di Li Assignee: Di Li Fix For: trunk MapRed HistoryServer start logic (implemented in yarn.py) creates various dirs in HDFS. The dir creation only runs thru when WEBHDFS is enabled. When WEBHDFS is disabled, HdfsResource calls bailed with NPE as the following one. Creating: Resource [source=null, target=/app-logs, type=directory, action=create, owner=yarn, group=hadoop, mode=777, recursiveChown=false, recursiveChmod=true, changePermissionforParents=false, manageIfExists=false] Exception occurred, Reason: null java.lang.NullPointerException at org.apache.hadoop.fs.FileSystem.fixRelativePart(FileSystem.java:2211) at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1300) at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1426) at org.apache.ambari.fast_hdfs_resource.Runner.main(Runner.java:80) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20469) Add a new property to yarn-site.xml yarn.log.server.web-service.url
[ https://issues.apache.org/jira/browse/AMBARI-20469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-20469: --- Attachment: AMBARI-20469_trunk.patch > Add a new property to yarn-site.xml yarn.log.server.web-service.url > --- > > Key: AMBARI-20469 > URL: https://issues.apache.org/jira/browse/AMBARI-20469 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-20469_trunk.patch > > > This property depends on yarn.timeline-service.webapp.address and > yarn.http.policy. > It is used by Yarn, Tez services. > The translation of the url from the default localhost to the actual hostname > has to happen depending on the http policy. > this is required in order to use the Tez Log Links. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927264#comment-15927264 ] Hudson commented on AMBARI-20402: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7052 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7052/]) AMBARI-20402: Assign Slaves and Clients page displays incorrect (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=55dc8ac9224366c0fd08d03da42176652a146ce0]) * (edit) ambari-web/app/mixins/wizard/assign_master_components.js > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20402.patch, AMBARI-20402_trunk.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-19557) ranger_usersync should install with ranger_admin in the same host
[ https://issues.apache.org/jira/browse/AMBARI-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu reassigned AMBARI-19557: Assignee: zhangxiaolu (was: alice) > ranger_usersync should install with ranger_admin in the same host > - > > Key: AMBARI-19557 > URL: https://issues.apache.org/jira/browse/AMBARI-19557 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.4.0 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19557.patch > > > http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.0/bk_Ranger_Install_Guide/content/ch03s01.html中描述如下： > The Ranger Admin and Ranger Usersync services must be installed on the same > cluster node. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) Hbase-client installed failed when hdfs hasnot installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Fix Version/s: 2.5.0 trunk > Hbase-client installed failed when hdfs hasnot installed > > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20368.patch, screenshot-1.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20470) Ambari build fails at Files view
[
https://issues.apache.org/jira/browse/AMBARI-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927246#comment-15927246
]
Hudson commented on AMBARI-20470:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1266 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1266/])
AMBARI-20470. Ambari build fails at Files view.(jaimin) (jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8268b842ecf000264bd59699da5f59b449a2646c])
* (edit) contrib/views/files/src/main/resources/ui/package.json
> Ambari build fails at Files view
>
>
> Key: AMBARI-20470
> URL: https://issues.apache.org/jira/browse/AMBARI-20470
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 2.5.0
>
> Attachments: AMBARI-20470.patch
>
>
> Files view fails with below error:
> {code}
> /Users/Jaimin/vagrant/ambari-vagrant/centos6.4/gerrit/gerrit-ambari/contrib/views/files/src/main/resources/ui/node_modules/async-disk-cache/node_modules/username/index.js:2
> const os = require('os');
> ^
> Use of const in strict mode.
> SyntaxError: Use of const in strict mode.
> at Module._compile (module.js:439:25)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.require (module.js:364:17)
> at require (module.js:380:17)
> at Object.
> (/Users/Jaimin/vagrant/ambari-vagrant/centos6.4/gerrit/gerrit-ambari/contrib/views/files/src/main/resources/ui/node_modules/async-disk-cache/index.js:24:16)
> at Module._compile (module.js:456:26)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20470) Ambari build fails at Files view
[
https://issues.apache.org/jira/browse/AMBARI-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927245#comment-15927245
]
Hudson commented on AMBARI-20470:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7051 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7051/])
AMBARI-20470. Ambari build fails at Files view.(jaimin) (jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=63ab0ab91058ffe8fb4dafa9f7eb96f5b1c8ec05])
* (edit) contrib/views/files/src/main/resources/ui/package.json
> Ambari build fails at Files view
>
>
> Key: AMBARI-20470
> URL: https://issues.apache.org/jira/browse/AMBARI-20470
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 2.5.0
>
> Attachments: AMBARI-20470.patch
>
>
> Files view fails with below error:
> {code}
> /Users/Jaimin/vagrant/ambari-vagrant/centos6.4/gerrit/gerrit-ambari/contrib/views/files/src/main/resources/ui/node_modules/async-disk-cache/node_modules/username/index.js:2
> const os = require('os');
> ^
> Use of const in strict mode.
> SyntaxError: Use of const in strict mode.
> at Module._compile (module.js:439:25)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.require (module.js:364:17)
> at require (module.js:380:17)
> at Object.
> (/Users/Jaimin/vagrant/ambari-vagrant/centos6.4/gerrit/gerrit-ambari/contrib/views/files/src/main/resources/ui/node_modules/async-disk-cache/index.js:24:16)
> at Module._compile (module.js:456:26)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20471) Add hadoop.caller.context setting to hdfs-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-20471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez reassigned AMBARI-20471: Assignee: Chen Liang > Add hadoop.caller.context setting to hdfs-site.xml > -- > > Key: AMBARI-20471 > URL: https://issues.apache.org/jira/browse/AMBARI-20471 > Project: Ambari > Issue Type: Bug >Reporter: Chen Liang >Assignee: Chen Liang > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927212#comment-15927212 ] Sangeeta Ravindran commented on AMBARI-20402: - Pushed to trunk as commit 55dc8ac9224366c0fd08d03da42176652a146ce0 Author: Sangeeta Ravindran Date: Wed Mar 15 16:50:11 2017 -0700 > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20402.patch, AMBARI-20402_trunk.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20402: Attachment: AMBARI-20402_trunk.patch > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20402.patch, AMBARI-20402_trunk.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20402: Fix Version/s: trunk > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20402.patch, AMBARI-20402_trunk.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20471) Add hadoop.caller.context setting to hdfs-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-20471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Liang updated AMBARI-20471: Issue Type: Bug (was: Improvement) > Add hadoop.caller.context setting to hdfs-site.xml > -- > > Key: AMBARI-20471 > URL: https://issues.apache.org/jira/browse/AMBARI-20471 > Project: Ambari > Issue Type: Bug >Reporter: Chen Liang > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20471) Add hadoop.caller.context setting to hdfs-site.xml
Chen Liang created AMBARI-20471: --- Summary: Add hadoop.caller.context setting to hdfs-site.xml Key: AMBARI-20471 URL: https://issues.apache.org/jira/browse/AMBARI-20471 Project: Ambari Issue Type: Improvement Reporter: Chen Liang -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20470) Ambari build fails at Files view
[
https://issues.apache.org/jira/browse/AMBARI-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-20470:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Received +1 on ReviewBoard.
Patch committed to branch-2.5 and trunk
> Ambari build fails at Files view
>
>
> Key: AMBARI-20470
> URL: https://issues.apache.org/jira/browse/AMBARI-20470
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 2.5.0
>
> Attachments: AMBARI-20470.patch
>
>
> Files view fails with below error:
> {code}
> /Users/Jaimin/vagrant/ambari-vagrant/centos6.4/gerrit/gerrit-ambari/contrib/views/files/src/main/resources/ui/node_modules/async-disk-cache/node_modules/username/index.js:2
> const os = require('os');
> ^
> Use of const in strict mode.
> SyntaxError: Use of const in strict mode.
> at Module._compile (module.js:439:25)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.require (module.js:364:17)
> at require (module.js:380:17)
> at Object.
> (/Users/Jaimin/vagrant/ambari-vagrant/centos6.4/gerrit/gerrit-ambari/contrib/views/files/src/main/resources/ui/node_modules/async-disk-cache/index.js:24:16)
> at Module._compile (module.js:456:26)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20333) Value for "User Limit Factor" should be float instead of integer in YARN Queue Manager.
[ https://issues.apache.org/jira/browse/AMBARI-20333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927171#comment-15927171 ] Hudson commented on AMBARI-20333: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7050 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7050/]) AMBARI-20333 - Value for User Limit Factor should be float instead of (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=df4c44a04dece13565927f34e14766876826accf]) * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/capacityInput.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/queue.hbs > Value for "User Limit Factor" should be float instead of integer in YARN > Queue Manager. > --- > > Key: AMBARI-20333 > URL: https://issues.apache.org/jira/browse/AMBARI-20333 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20333.patch, screenshot-1.png > > > According to yarn documentation, > "yarn.scheduler.capacity..user-limit-factor" should be a float: > https://hadoop.apache.org/docs/r2.4.1/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html > Hence the user should be allowed to enter decimal values for 'User limit > factor' -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20470) Ambari build fails at Files view
[
https://issues.apache.org/jira/browse/AMBARI-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-20470:
--
Description:
Files view fails with below error:
{code}
/Users/Jaimin/vagrant/ambari-vagrant/centos6.4/gerrit/gerrit-ambari/contrib/views/files/src/main/resources/ui/node_modules/async-disk-cache/node_modules/username/index.js:2
const os = require('os');
^
Use of const in strict mode.
SyntaxError: Use of const in strict mode.
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.
(/Users/Jaimin/vagrant/ambari-vagrant/centos6.4/gerrit/gerrit-ambari/contrib/views/files/src/main/resources/ui/node_modules/async-disk-cache/index.js:24:16)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
{code}
> Ambari build fails at Files view
>
>
> Key: AMBARI-20470
> URL: https://issues.apache.org/jira/browse/AMBARI-20470
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 2.5.0
>
> Attachments: AMBARI-20470.patch
>
>
> Files view fails with below error:
> {code}
> /Users/Jaimin/vagrant/ambari-vagrant/centos6.4/gerrit/gerrit-ambari/contrib/views/files/src/main/resources/ui/node_modules/async-disk-cache/node_modules/username/index.js:2
> const os = require('os');
> ^
> Use of const in strict mode.
> SyntaxError: Use of const in strict mode.
> at Module._compile (module.js:439:25)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.require (module.js:364:17)
> at require (module.js:380:17)
> at Object.
> (/Users/Jaimin/vagrant/ambari-vagrant/centos6.4/gerrit/gerrit-ambari/contrib/views/files/src/main/resources/ui/node_modules/async-disk-cache/index.js:24:16)
> at Module._compile (module.js:456:26)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20470) Ambari build fails at Files view
[ https://issues.apache.org/jira/browse/AMBARI-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20470: -- Status: Patch Available (was: Open) Verified that the patch fixes the issue and builds Files view project successfully > Ambari build fails at Files view > > > Key: AMBARI-20470 > URL: https://issues.apache.org/jira/browse/AMBARI-20470 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-20470.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20470) Ambari build fails at Files view
[ https://issues.apache.org/jira/browse/AMBARI-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20470: -- Attachment: AMBARI-20470.patch > Ambari build fails at Files view > > > Key: AMBARI-20470 > URL: https://issues.apache.org/jira/browse/AMBARI-20470 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-20470.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20470) Ambari build fails at Files view
Jaimin Jetly created AMBARI-20470: - Summary: Ambari build fails at Files view Key: AMBARI-20470 URL: https://issues.apache.org/jira/browse/AMBARI-20470 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20469) Add a new property to yarn-site.xml yarn.log.server.web-service.url
Madhuvanthi Radhakrishnan created AMBARI-20469: -- Summary: Add a new property to yarn-site.xml yarn.log.server.web-service.url Key: AMBARI-20469 URL: https://issues.apache.org/jira/browse/AMBARI-20469 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 2.5.0 This property depends on yarn.timeline-service.webapp.address and yarn.http.policy. It is used by Yarn, Tez services. The translation of the url from the default localhost to the actual hostname has to happen depending on the http policy. this is required in order to use the Tez Log Links. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20333) Value for "User Limit Factor" should be float instead of integer in YARN Queue Manager.
[ https://issues.apache.org/jira/browse/AMBARI-20333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20333: Resolution: Fixed Status: Resolved (was: Patch Available) Commited to trunk as: commit df4c44a04dece13565927f34e14766876826accf > Value for "User Limit Factor" should be float instead of integer in YARN > Queue Manager. > --- > > Key: AMBARI-20333 > URL: https://issues.apache.org/jira/browse/AMBARI-20333 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20333.patch, screenshot-1.png > > > According to yarn documentation, > "yarn.scheduler.capacity..user-limit-factor" should be a float: > https://hadoop.apache.org/docs/r2.4.1/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html > Hence the user should be allowed to enter decimal values for 'User limit > factor' -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20423) Add alerts for STS in Spark and Spark 2
[ https://issues.apache.org/jira/browse/AMBARI-20423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927099#comment-15927099 ] Sviatoslav Tereshchenko commented on AMBARI-20423: -- [~merlin] Thanks. > Add alerts for STS in Spark and Spark 2 > --- > > Key: AMBARI-20423 > URL: https://issues.apache.org/jira/browse/AMBARI-20423 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Sviatoslav Tereshchenko >Assignee: Mingjie Tang > Fix For: 2.5.0 > > > STR: > 1)Deploy cluster > 2)Stop "Thrift Server" of Spark 2 > Actual result: Spark 2 is not showed on services menu alerts page, when some > Spark 2 component is stopped. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20468) Ubuntu: When Disable Security Infra Solr Instance and RM start are failed
Sviatoslav Tereshchenko created AMBARI-20468: Summary: Ubuntu: When Disable Security Infra Solr Instance and RM start are failed Key: AMBARI-20468 URL: https://issues.apache.org/jira/browse/AMBARI-20468 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Environment: Ubuntu Reporter: Sviatoslav Tereshchenko Priority: Critical Fix For: 2.5.0 STR: 1) Check that Kerberos is in the list of services 3) Disable security Actual result: When Disable Security Infra Solr Instance and RM start are failed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20468) Ubuntu: When Disable Security Infra Solr Instance and RM start are failed
[ https://issues.apache.org/jira/browse/AMBARI-20468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927088#comment-15927088 ] Sviatoslav Tereshchenko commented on AMBARI-20468: -- FYI [~vbrodetskyi] > Ubuntu: When Disable Security Infra Solr Instance and RM start are failed > - > > Key: AMBARI-20468 > URL: https://issues.apache.org/jira/browse/AMBARI-20468 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 > Environment: Ubuntu >Reporter: Sviatoslav Tereshchenko >Priority: Critical > Fix For: 2.5.0 > > > STR: > 1) Check that Kerberos is in the list of services > 3) Disable security > Actual result: > When Disable Security Infra Solr Instance and RM start are failed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20363) After clearing the content of Users in Yarn Queue Manager, it still shows the user in effective administrators
[ https://issues.apache.org/jira/browse/AMBARI-20363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927042#comment-15927042 ] Hudson commented on AMBARI-20363: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7049 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7049/]) AMBARI-20363 - After clearing the content of Users in Yarn Queue (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f6e88e0871d429b5e5b8530d545578ee96025a99]) * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/userGroupInput.js > After clearing the content of Users in Yarn Queue Manager, it still shows the > user in effective administrators > -- > > Key: AMBARI-20363 > URL: https://issues.apache.org/jira/browse/AMBARI-20363 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20363.patch, screenshot-1.png > > > In the "Access Control and Status, clear the content of Users under the > "Administer Queue". > It' still shows the user icon in Effective Administraters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19928) Solr grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-19928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927007#comment-15927007 ] Hudson commented on AMBARI-19928: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1265 (See [https://builds.apache.org/job/Ambari-branch-2.5/1265/]) AMBARI-19928. Solr grafana dashboards. (Willy Solaligue via yusaku) (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8dbd718c4d4f1281203dd1e060bfbc19cbb23796]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-solr-hosts-dashboard.json * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-solr-cores-dashboard.json > Solr grafana dashboards > --- > > Key: AMBARI-19928 > URL: https://issues.apache.org/jira/browse/AMBARI-19928 > Project: Ambari > Issue Type: New Feature >Affects Versions: 2.5.0 >Reporter: Willy Solaligue >Assignee: Willy Solaligue > Fix For: 2.5.0 > > Attachments: AMBARI-19928-2.5.patch, AMBARI-19928-2.5.patch, > AMBARI-19928-trunk.patch, AMBARI-19928-trunk.patch, Screen Shot 2017-02-09 at > 11.40.00 AM.png > > > - Add solr grafana dashboards for the solr stack available here: > https://github.com/lucidworks/solr-stack -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-17353) First class support for YARN hosted services
[ https://issues.apache.org/jira/browse/AMBARI-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-17353: --- Fix Version/s: 3.0.0 > First class support for YARN hosted services > > > Key: AMBARI-17353 > URL: https://issues.apache.org/jira/browse/AMBARI-17353 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-web >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > YARN-896 and SLIDER-183 enabled running long running applications (services) > on YARN. Apache Ambari Slider View provides us a way to deploy and manage > long running services on YARN. > However, the Slider View provides a limited functionality and does not > provide a first class support for YARN hosted services similar to traditional > services deployed directly on the hosts by Ambari. > Besides while YARN-896 got the ball rolling for supporting services on YARN, > the YARN team is working on major improvements and a first class support for > YARN hosted services (YARN-4692). > This initiative is for providing a first class support for YARN-hosted > services and leverage all the YARN improvements planned and documented in > YARN-4692. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20465) Multi Host Component Instance Support
[ https://issues.apache.org/jira/browse/AMBARI-20465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-20465: --- Affects Version/s: (was: 3.0.0) 2.5.0 > Multi Host Component Instance Support > - > > Key: AMBARI-20465 > URL: https://issues.apache.org/jira/browse/AMBARI-20465 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19621) Mpack Based Operations Model - Mpack v2
[ https://issues.apache.org/jira/browse/AMBARI-19621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-19621: --- Affects Version/s: (was: 3.0.0) 2.5.0 > Mpack Based Operations Model - Mpack v2 > --- > > Key: AMBARI-19621 > URL: https://issues.apache.org/jira/browse/AMBARI-19621 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20466) Multi Cluster Support
[ https://issues.apache.org/jira/browse/AMBARI-20466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-20466: --- Affects Version/s: (was: 3.0.0) 2.5.0 > Multi Cluster Support > - > > Key: AMBARI-20466 > URL: https://issues.apache.org/jira/browse/AMBARI-20466 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20463) Multi Service Instance Support
[ https://issues.apache.org/jira/browse/AMBARI-20463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-20463: --- Affects Version/s: (was: 3.0.0) 2.5.0 > Multi Service Instance Support > -- > > Key: AMBARI-20463 > URL: https://issues.apache.org/jira/browse/AMBARI-20463 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19620) Apache Ambari v2 Rest API
[ https://issues.apache.org/jira/browse/AMBARI-19620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-19620: --- Affects Version/s: (was: 3.0.0) 2.5.0 > Apache Ambari v2 Rest API > - > > Key: AMBARI-19620 > URL: https://issues.apache.org/jira/browse/AMBARI-19620 > Project: Ambari > Issue Type: Epic > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20466) Multi Cluster Support
[ https://issues.apache.org/jira/browse/AMBARI-20466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-20466: --- Fix Version/s: (was: 3.0.0) trunk > Multi Cluster Support > - > > Key: AMBARI-20466 > URL: https://issues.apache.org/jira/browse/AMBARI-20466 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 3.0.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20363) After clearing the content of Users in Yarn Queue Manager, it still shows the user in effective administrators
[ https://issues.apache.org/jira/browse/AMBARI-20363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20363: Resolution: Fixed Status: Resolved (was: Patch Available) Commited to trunk as commit f6e88e0871d429b5e5b8530d545578ee96025a99 Author: Sangeeta Ravindran Date: Wed Mar 15 13:58:24 2017 -0700 AMBARI-20363 - After clearing the content of Users in Yarn Queue Manager, it still shows the user in effective administrators (Anita Jebaraj via sangeetar) > After clearing the content of Users in Yarn Queue Manager, it still shows the > user in effective administrators > -- > > Key: AMBARI-20363 > URL: https://issues.apache.org/jira/browse/AMBARI-20363 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20363.patch, screenshot-1.png > > > In the "Access Control and Status, clear the content of Users under the > "Administer Queue". > It' still shows the user icon in Effective Administraters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19928) Solr grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-19928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926984#comment-15926984 ] Hudson commented on AMBARI-19928: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7048 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7048/]) AMBARI-19928. Solr grafana dashboards. (Willy Solaligue via yusaku) (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dca46a9a5fcbfd7f57b0de3a231e6c976c6d5779]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-solr-hosts-dashboard.json * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-solr-cores-dashboard.json > Solr grafana dashboards > --- > > Key: AMBARI-19928 > URL: https://issues.apache.org/jira/browse/AMBARI-19928 > Project: Ambari > Issue Type: New Feature >Affects Versions: 2.5.0 >Reporter: Willy Solaligue >Assignee: Willy Solaligue > Fix For: 2.5.0 > > Attachments: AMBARI-19928-2.5.patch, AMBARI-19928-2.5.patch, > AMBARI-19928-trunk.patch, AMBARI-19928-trunk.patch, Screen Shot 2017-02-09 at > 11.40.00 AM.png > > > - Add solr grafana dashboards for the solr stack available here: > https://github.com/lucidworks/solr-stack -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20423) Add alerts for STS in Spark and Spark 2
[ https://issues.apache.org/jira/browse/AMBARI-20423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingjie Tang reassigned AMBARI-20423: - Assignee: Mingjie Tang > Add alerts for STS in Spark and Spark 2 > --- > > Key: AMBARI-20423 > URL: https://issues.apache.org/jira/browse/AMBARI-20423 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Sviatoslav Tereshchenko >Assignee: Mingjie Tang > Fix For: 2.5.0 > > > STR: > 1)Deploy cluster > 2)Stop "Thrift Server" of Spark 2 > Actual result: Spark 2 is not showed on services menu alerts page, when some > Spark 2 component is stopped. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20467) Add alerts for Livy in Spark and Spark 2
[ https://issues.apache.org/jira/browse/AMBARI-20467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20467: -- Assignee: Mingjie Tang > Add alerts for Livy in Spark and Spark 2 > > > Key: AMBARI-20467 > URL: https://issues.apache.org/jira/browse/AMBARI-20467 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Mingjie Tang >Assignee: Mingjie Tang > > Stop the livy server of spark and spark2, > Spark and spark2 need to show alert. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20461) override_uid should set to false when upgrading Ambari 2.1 to 2.2 or newer with custom stacks
[
https://issues.apache.org/jira/browse/AMBARI-20461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926903#comment-15926903
]
Hadoop QA commented on AMBARI-20461:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12858896/AMBARI-20461.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/11045//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11045//console
This message is automatically generated.
> override_uid should set to false when upgrading Ambari 2.1 to 2.2 or newer
> with custom stacks
> -
>
> Key: AMBARI-20461
> URL: https://issues.apache.org/jira/browse/AMBARI-20461
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20461.patch
>
>
> Custom stacks may not have override_hbase_uid property in hbase-env.xml, in
> this case, override_uid is currently set to true by Ambari's auto merge
> logic. it should be set to false when upgrading Ambari 2.1 to 2.2 or newer
> with custom stacks in order to respect the existing UID customers already set
> on their clusters.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20467) Add alerts for Livy in Spark and Spark 2
Mingjie Tang created AMBARI-20467: - Summary: Add alerts for Livy in Spark and Spark 2 Key: AMBARI-20467 URL: https://issues.apache.org/jira/browse/AMBARI-20467 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Mingjie Tang Stop the livy server of spark and spark2, Spark and spark2 need to show alert. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20423) Add alerts for STS in Spark and Spark 2
[ https://issues.apache.org/jira/browse/AMBARI-20423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926896#comment-15926896 ] Mingjie Tang commented on AMBARI-20423: --- I create a other JIRA for livy issue. https://issues.apache.org/jira/browse/AMBARI-20467 > Add alerts for STS in Spark and Spark 2 > --- > > Key: AMBARI-20423 > URL: https://issues.apache.org/jira/browse/AMBARI-20423 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Sviatoslav Tereshchenko > Fix For: 2.5.0 > > > STR: > 1)Deploy cluster > 2)Stop "Thrift Server" of Spark 2 > Actual result: Spark 2 is not showed on services menu alerts page, when some > Spark 2 component is stopped. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-18460) DRPC_SERVER server install failed during install wizard with unsupported operand type error
[ https://issues.apache.org/jira/browse/AMBARI-18460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Ramakrishnan resolved AMBARI-18460. -- Resolution: Cannot Reproduce > DRPC_SERVER server install failed during install wizard with unsupported > operand type error > --- > > Key: AMBARI-18460 > URL: https://issues.apache.org/jira/browse/AMBARI-18460 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Priority: Critical > Fix For: 2.5.0 > > > DRPC_SERVER server install failed during install wizard with unsupported > operand type error. > Error message : > "stderr" : "Traceback (most recent call last):\n File > \"/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/drpc_server.py\", > line 139, in \nDrpcServer().execute()\n File > \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\", > line 280, in execute\nmethod(env)\n File > \"/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/drpc_server.py\", > line 44, in install\nself.configure(env)\n File > \"/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/drpc_server.py\", > line 47, in configure\nimport params\n File > \"/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/params.py\", > line 26, in \nfrom params_linux import *\n File > \"/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/params_linux.py\", > line 210, in \nmetric_collector_hosts += host + ':' + > metric_collector_port + ','\nTypeError: unsupported operand type(s) for +=: > 'NoneType' and 'str'", -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20423) Add alerts for STS in Spark and Spark 2
[ https://issues.apache.org/jira/browse/AMBARI-20423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926890#comment-15926890 ] Mingjie Tang commented on AMBARI-20423: --- let us fix the alert for the STS at first, then go to the livy. [~stereshchenko] > Add alerts for STS in Spark and Spark 2 > --- > > Key: AMBARI-20423 > URL: https://issues.apache.org/jira/browse/AMBARI-20423 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Sviatoslav Tereshchenko > Fix For: 2.5.0 > > > STR: > 1)Deploy cluster > 2)Stop "Thrift Server" of Spark 2 > Actual result: Spark 2 is not showed on services menu alerts page, when some > Spark 2 component is stopped. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20423) Add alerts for STS in Spark and Spark 2
[ https://issues.apache.org/jira/browse/AMBARI-20423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingjie Tang updated AMBARI-20423: -- Summary: Add alerts for STS in Spark and Spark 2 (was: Add alerts for STS and Livy in Spark and Spark 2) > Add alerts for STS in Spark and Spark 2 > --- > > Key: AMBARI-20423 > URL: https://issues.apache.org/jira/browse/AMBARI-20423 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Sviatoslav Tereshchenko > Fix For: 2.5.0 > > > STR: > 1)Deploy cluster > 2)Stop "Thrift Server" of Spark 2 > Actual result: Spark 2 is not showed on services menu alerts page, when some > Spark 2 component is stopped. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20464) Side Nav: several issues and adjustments
[
https://issues.apache.org/jira/browse/AMBARI-20464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926816#comment-15926816
]
Hadoop QA commented on AMBARI-20464:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12858915/AMBARI-20464.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11044//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11044//console
This message is automatically generated.
> Side Nav: several issues and adjustments
>
>
> Key: AMBARI-20464
> URL: https://issues.apache.org/jira/browse/AMBARI-20464
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-20464.patch
>
>
> 1. Scrolling on Side Nav menu can trigger scrolling on the main content. The
> same issue for modals, wizards .etc.
> 2. Service Actions icon "..." should occupy more space to click on.
> Current behavior: need to click exactly on the icon to show actions dropdown.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Description: *Multi Stack Services* (AMBARI-19621) _Scenario: Deploy HDP & HDF services in same cluster_ - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. _Scenario: Deploy HDP services from different stack versions in same cluster_ - Deploy ZK, HDFS, YARN from HDP-2.5, but deploy latest SPARK from HDP-2.6. *Multiple Service Instances* (AMBARI-20463) _Scenario: Multi service instances on same version_ - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA _Scenario: Multi service instances on different versions_ - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* (AMBARI-20465) _Scenario: Multi component instances from a service instance on the same host_ - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* (AMBARI-20466) _Scenario: Manage multiple Hadoop clusters under single Ambari Server_ - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* (AMBARI-17353) _Scenario: HBase on YARN_ - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. _Scenario: Credit Fraud Detection YARN Assembly_ - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. *Multi Everything Aware APIs* (AMBARI-19621) - V2 Ambari Rest API to support Multi Everything Architecture was: *Multi Stack Services* (AMBARI-19621) _Scenario: Deploy HDP & HDF services in same cluster_ - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* (AMBARI-20463) _Scenario: Multi service instances on same version_ - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA _Scenario: Multi service instances on different versions_ - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* (AMBARI-20465) _Scenario: Multi component instances from a service instance on the same host_ - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* (AMBARI-20466) _Scenario: Manage multiple Hadoop clusters under single Ambari Server_ - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* (AMBARI-17353) _Scenario: HBase on YARN_ - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. _Scenario: Credit Fraud Detection YARN Assembly_ - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. *Multi Everything Aware APIs* (AMBARI-19621) - V2 Ambari Rest API to support Multi Everything Architecture > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-upgrade, ambari-web, > stacks >Affects Versions: 2.5.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* (AMBARI-19621) > _Scenario: Deploy HDP & HDF services in same cluster_ > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > _Scenario: Deploy HDP services from different stack versions in same cluster_ > - Deploy ZK, HDFS, YARN from HDP-2.5, but deploy latest SPARK from HDP-2.6. > *Multiple Service Instances* (AMBARI-20463) > _Scenario: Multi service instances on same version_ > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > _Scenario: Multi service instances on different versions_ > - Cluster includes instance of SP
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Description: *Multi Stack Services* (AMBARI-19621) _Scenario: Deploy HDP & HDF services in same cluster_ - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* (AMBARI-20463) _Scenario: Multi service instances on same version_ - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA _Scenario: Multi service instances on different versions_ - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* (AMBARI-20465) _Scenario: Multi component instances from a service instance on the same host_ - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* (AMBARI-20466) _Scenario: Manage multiple Hadoop clusters under single Ambari Server_ - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* (AMBARI-17353) _Scenario: HBase on YARN_ - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. _Scenario: Credit Fraud Detection YARN Assembly_ - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. *Multi Everything Aware APIs* (AMBARI-19621) - V2 Ambari Rest API to support Multi Everything Architecture was: *Multi Stack Services* _Scenario: Deploy HDP & HDF services in same cluster_ - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* _Scenario: Multi service instances on same version_ - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA _Scenario: Multi service instances on different versions_ - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* _Scenario: Multi component instances from a service instance on the same host_ - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* _Scenario: Manage multiple Hadoop clusters under single Ambari Server_ - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* _Scenario: HBase on YARN_ - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. _Scenario: Credit Fraud Detection YARN Assembly_ - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. *Multi Everything Aware APIs* - V2 Ambari Rest API to support Multi Everything Architecture > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-upgrade, ambari-web, > stacks >Affects Versions: 2.5.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* (AMBARI-19621) > _Scenario: Deploy HDP & HDF services in same cluster_ > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > *Multiple Service Instances* (AMBARI-20463) > _Scenario: Multi service instances on same version_ > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > _Scenario: Multi service instances on different versions_ > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > *Multi Host Component Instances* (AMBARI-20465) > _Scenario: Multi component instances from a service instance on the same host_ > - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. > - Single instance of KAFKA broker is unable to utilize all the resources on > the host. > - User wants to scale up performance by deploying m
[jira] [Created] (AMBARI-20466) Multi Cluster Support
Jayush Luniya created AMBARI-20466: -- Summary: Multi Cluster Support Key: AMBARI-20466 URL: https://issues.apache.org/jira/browse/AMBARI-20466 Project: Ambari Issue Type: Epic Components: ambari-agent, ambari-server, ambari-web Affects Versions: 3.0.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Description: *Multi Stack Services* _Scenario: Deploy HDP & HDF services in same cluster_ - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* _Scenario: Multi service instances on same version_ - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA _Scenario: Multi service instances on different versions_ - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* _Scenario: Multi component instances from a service instance on the same host_ - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* _Scenario: Manage multiple Hadoop clusters under single Ambari Server_ - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* _Scenario: HBase on YARN_ - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. _Scenario: Credit Fraud Detection YARN Assembly_ - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. *Multi Everything Aware APIs* - V2 Ambari Rest API to support Multi Everything Architecture was: *Multi Stack Services* _Scenario: Deploy HDP & HDF services in same cluster_ - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* _Scenario: Multi service instances on same version_ - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA _Scenario: Multi service instances on different versions_ - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. * Multi Everything Aware APIs* - V2 Ambari Rest API to support Multi Everything Architecture *Multi Host Component Instances* _Scenario: Multi component instances from a service instance on the same host_ - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* _Scenario: Manage multiple Hadoop clusters under single Ambari Server_ - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* _Scenario: HBase on YARN_ - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. _Scenario: Credit Fraud Detection YARN Assembly_ - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-upgrade, ambari-web, > stacks >Affects Versions: 2.5.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* > _Scenario: Deploy HDP & HDF services in same cluster_ > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > *Multiple Service Instances* > _Scenario: Multi service instances on same version_ > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > _Scenario: Multi service instances on different versions_ > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > *Multi Host Component Instances* > _Scenario: Multi component instances from a service instance on the same host_ > - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. > - Single instance of KAFKA broker is unable to utilize all the resources on > the host. > - User wants to scale up performance by deploying multiple instances of the > KAFKA brokers/host. > *Multi Cluster* > _Scenario: Manage multiple Hadoop clusters under single Ambari
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Description: *Multi Stack Services* _Scenario: Deploy HDP & HDF services in same cluster_ - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* _Scenario: Multi service instances on same version_ - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA _Scenario: Multi service instances on different versions_ - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. * Multi Everything Aware APIs* - V2 Ambari Rest API to support Multi Everything Architecture *Multi Host Component Instances* _Scenario: Multi component instances from a service instance on the same host_ - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* _Scenario: Manage multiple Hadoop clusters under single Ambari Server_ - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* _Scenario: HBase on YARN_ - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. _Scenario: Credit Fraud Detection YARN Assembly_ - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. was: *Multi Stack Services* _Scenario: Deploy HDP & HDF services in same cluster_ - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* _Scenario: Multi service instances on same version_ - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA _Scenario: Multi service instances on different versions_ - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* _Scenario: Multi component instances from a service instance on the same host_ - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* _Scenario: Manage multiple Hadoop clusters under single Ambari Server_ - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* _Scenario: HBase on YARN_ - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. _Scenario: Credit Fraud Detection YARN Assembly_ - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-upgrade, ambari-web, > stacks >Affects Versions: 2.5.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* > _Scenario: Deploy HDP & HDF services in same cluster_ > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > *Multiple Service Instances* > _Scenario: Multi service instances on same version_ > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > _Scenario: Multi service instances on different versions_ > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > * Multi Everything Aware APIs* > - V2 Ambari Rest API to support Multi Everything Architecture > *Multi Host Component Instances* > _Scenario: Multi component instances from a service instance on the same host_ > - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. > - Single instance of KAFKA broker is unable to utilize all the resources on > the host. > - User wants to scale up performance by deploying multiple instances of the > KAFKA brokers/host. > *Multi Cluster* > _Scenario: Manage multiple Hadoop clusters under single
[jira] [Updated] (AMBARI-17353) First class support for YARN hosted services
[ https://issues.apache.org/jira/browse/AMBARI-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-17353: --- Epic Name: Yarn Hosted Services (was: AmbariYarnServices) > First class support for YARN hosted services > > > Key: AMBARI-17353 > URL: https://issues.apache.org/jira/browse/AMBARI-17353 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-web >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > > YARN-896 and SLIDER-183 enabled running long running applications (services) > on YARN. Apache Ambari Slider View provides us a way to deploy and manage > long running services on YARN. > However, the Slider View provides a limited functionality and does not > provide a first class support for YARN hosted services similar to traditional > services deployed directly on the hosts by Ambari. > Besides while YARN-896 got the ball rolling for supporting services on YARN, > the YARN team is working on major improvements and a first class support for > YARN hosted services (YARN-4692). > This initiative is for providing a first class support for YARN-hosted > services and leverage all the YARN improvements planned and documented in > YARN-4692. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19621) Mpack Based Operations Model - Mpack v2
[ https://issues.apache.org/jira/browse/AMBARI-19621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-19621: --- Summary: Mpack Based Operations Model - Mpack v2 (was: Mpack Based Operations Model) > Mpack Based Operations Model - Mpack v2 > --- > > Key: AMBARI-19621 > URL: https://issues.apache.org/jira/browse/AMBARI-19621 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 3.0.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20465) Multi Host Component Instance Support
Jayush Luniya created AMBARI-20465: -- Summary: Multi Host Component Instance Support Key: AMBARI-20465 URL: https://issues.apache.org/jira/browse/AMBARI-20465 Project: Ambari Issue Type: Epic Components: ambari-agent, ambari-server, ambari-web Affects Versions: 3.0.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20464) Side Nav: several issues and adjustments
[ https://issues.apache.org/jira/browse/AMBARI-20464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20464: - Status: Patch Available (was: Open) > Side Nav: several issues and adjustments > > > Key: AMBARI-20464 > URL: https://issues.apache.org/jira/browse/AMBARI-20464 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-20464.patch > > > 1. Scrolling on Side Nav menu can trigger scrolling on the main content. The > same issue for modals, wizards .etc. > 2. Service Actions icon "..." should occupy more space to click on. > Current behavior: need to click exactly on the icon to show actions dropdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20464) Side Nav: several issues and adjustments
[ https://issues.apache.org/jira/browse/AMBARI-20464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20464: - Attachment: AMBARI-20464.patch > Side Nav: several issues and adjustments > > > Key: AMBARI-20464 > URL: https://issues.apache.org/jira/browse/AMBARI-20464 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-20464.patch > > > 1. Scrolling on Side Nav menu can trigger scrolling on the main content. The > same issue for modals, wizards .etc. > 2. Service Actions icon "..." should occupy more space to click on. > Current behavior: need to click exactly on the icon to show actions dropdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20449) Upgrade pre-checks screen does not show CONFIG_MERGE warning
[
https://issues.apache.org/jira/browse/AMBARI-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926716#comment-15926716
]
Hudson commented on AMBARI-20449:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7047 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7047/])
AMBARI-20449 Upgrade pre-checks screen does not show CONFIG_MERGE (atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8b2565ae872ed16da3f36d7f620ae7c2c128695f])
* (edit) ambari-web/test/views/common/modal_popups/cluster_check_popup_test.js
* (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js
* (edit) ambari-web/app/messages.js
* (add)
ambari-web/app/templates/main/admin/stack_upgrade/upgrade_configs_recommend_table.hbs
* (edit) ambari-web/app/templates/common/modal_popups/cluster_check_dialog.hbs
* (edit)
ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* (edit) ambari-web/app/views/common/modal_popups/cluster_check_popup.js
> Upgrade pre-checks screen does not show CONFIG_MERGE warning
>
>
> Key: AMBARI-20449
> URL: https://issues.apache.org/jira/browse/AMBARI-20449
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20449_branch-2.5.patch, AMBARI-20449.patch,
> Screen Shot 2017-03-13 at 6.49.59 PM.png, Screen Shot 2017-03-13 at 6.50.03
> PM.png
>
>
> *STR*
> # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1
> # Register HDP-2.6 version and install the bits
> # Click on Upgrade and click on Warning hyperlink for EU
> *Result*:
> Shows 2 warnings for EU. Click on the Warning and it shows "only one warning"
> and the warning for CONFIG_MERGE pre-check does not show up
> (see attachments)
> From the output of pre-checks API call, I do see two warning for Config Merge
> as below:
> {code}
> "href" :
> "http://172.22.81.58:8080/api/v1/clusters/cl1/rolling_upgrades_check/CONFIG_MERGE";,
> "UpgradeChecks" : {
> "check" : "Configuration Merge Check",
> "check_type" : "CLUSTER",
> "cluster_name" : "cl1",
> "failed_detail" : [
> {
> "type" : "topology",
> "property" : "content",
> "current" : "\n\n\n\n
> \nauthentication\n
> ShiroProvider\n
> true\n\n
> sessionTimeout\n30\n
> \n\n
> main.ldapRealm\n
> org.apache.hadoop.gateway.shirorealm.KnoxLdapRealm\n
> \n\n
> main.ldapRealm.userDnTemplate\n
> uid=
> "id" : "CONFIG_MERGE",
> "reason" : "The following config types will have values overwritten:
> hive-interactive-env, topology, hadoop-env",
> "repository_version" : "2.6.0.2-24",
> "status" : "WARNING",
> "upgrade_type" : "NON_ROLLING"
> }
> }
> "id" : "HEALTH",
> "reason" : "The following issues have been detected on this cluster
> and should be addressed before upgrading: CRITICAL: NameNode Last Checkpoint:
> nats11-46-tups-erm16tofnsecha-s11-5.openstacklocal\nCRITICAL: NameNode Last
> Checkpoint: nats11-46-tups-erm16tofnsecha-s11-1",
> "repository_version" : "2.6.0.2-24",
> "status" : "WARNING",
> "upgrade_type" : "NON_ROLLING"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20427) Ambari should allow empty string for hive.metastore.uris when running in embedded mode
[ https://issues.apache.org/jira/browse/AMBARI-20427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926717#comment-15926717 ] Hudson commented on AMBARI-20427: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7047 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7047/]) AMBARI-20427. Ambari should allow empty string for hive.metastore.uris (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=19e7c65ba2dcf09010aeeb3e3c39c78b410c7a84]) * (edit) ambari-common/src/main/python/resource_management/libraries/functions/get_port_from_url.py * (edit) ambari-agent/src/test/python/resource_management/TestLibraryFunctions.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/configuration/hive-site.xml * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-site.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py > Ambari should allow empty string for hive.metastore.uris when running in > embedded mode > -- > > Key: AMBARI-20427 > URL: https://issues.apache.org/jira/browse/AMBARI-20427 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: trunk > > Attachments: AMBARI-20427.patch > > > Ambari UI prevents setting a value of null or empty string for > hive.metastore.uris > This is a valid use-case for embedded mode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20464) Side Nav: several issues and adjustments
[ https://issues.apache.org/jira/browse/AMBARI-20464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926715#comment-15926715 ] Xi Wang commented on AMBARI-20464: -- 20577 passing (28s) 153 pending > Side Nav: several issues and adjustments > > > Key: AMBARI-20464 > URL: https://issues.apache.org/jira/browse/AMBARI-20464 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-20464.patch > > > 1. Scrolling on Side Nav menu can trigger scrolling on the main content. The > same issue for modals, wizards .etc. > 2. Service Actions icon "..." should occupy more space to click on. > Current behavior: need to click exactly on the icon to show actions dropdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20449) Upgrade pre-checks screen does not show CONFIG_MERGE warning
[
https://issues.apache.org/jira/browse/AMBARI-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926708#comment-15926708
]
Hudson commented on AMBARI-20449:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1264 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1264/])
AMBARI-20449 Upgrade pre-checks screen does not show CONFIG_MERGE (atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=24952fa6af07573b60dccf5c10b8e6eaaca418b0])
* (edit)
ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* (edit) ambari-web/app/templates/common/modal_popups/cluster_check_dialog.hbs
* (edit) ambari-web/app/views/common/modal_popups/cluster_check_popup.js
* (add)
ambari-web/app/templates/main/admin/stack_upgrade/upgrade_configs_recommend_table.hbs
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js
* (edit) ambari-web/test/views/common/modal_popups/cluster_check_popup_test.js
> Upgrade pre-checks screen does not show CONFIG_MERGE warning
>
>
> Key: AMBARI-20449
> URL: https://issues.apache.org/jira/browse/AMBARI-20449
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20449_branch-2.5.patch, AMBARI-20449.patch,
> Screen Shot 2017-03-13 at 6.49.59 PM.png, Screen Shot 2017-03-13 at 6.50.03
> PM.png
>
>
> *STR*
> # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1
> # Register HDP-2.6 version and install the bits
> # Click on Upgrade and click on Warning hyperlink for EU
> *Result*:
> Shows 2 warnings for EU. Click on the Warning and it shows "only one warning"
> and the warning for CONFIG_MERGE pre-check does not show up
> (see attachments)
> From the output of pre-checks API call, I do see two warning for Config Merge
> as below:
> {code}
> "href" :
> "http://172.22.81.58:8080/api/v1/clusters/cl1/rolling_upgrades_check/CONFIG_MERGE";,
> "UpgradeChecks" : {
> "check" : "Configuration Merge Check",
> "check_type" : "CLUSTER",
> "cluster_name" : "cl1",
> "failed_detail" : [
> {
> "type" : "topology",
> "property" : "content",
> "current" : "\n\n\n\n
> \nauthentication\n
> ShiroProvider\n
> true\n\n
> sessionTimeout\n30\n
> \n\n
> main.ldapRealm\n
> org.apache.hadoop.gateway.shirorealm.KnoxLdapRealm\n
> \n\n
> main.ldapRealm.userDnTemplate\n
> uid=
> "id" : "CONFIG_MERGE",
> "reason" : "The following config types will have values overwritten:
> hive-interactive-env, topology, hadoop-env",
> "repository_version" : "2.6.0.2-24",
> "status" : "WARNING",
> "upgrade_type" : "NON_ROLLING"
> }
> }
> "id" : "HEALTH",
> "reason" : "The following issues have been detected on this cluster
> and should be addressed before upgrading: CRITICAL: NameNode Last Checkpoint:
> nats11-46-tups-erm16tofnsecha-s11-5.openstacklocal\nCRITICAL: NameNode Last
> Checkpoint: nats11-46-tups-erm16tofnsecha-s11-1",
> "repository_version" : "2.6.0.2-24",
> "status" : "WARNING",
> "upgrade_type" : "NON_ROLLING"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Description: *Multi Stack Services* _Scenario: Deploy HDP & HDF services in same cluster_ - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* _Scenario: Multi service instances on same version_ - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA _Scenario: Multi service instances on different versions_ - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* _Scenario: Multi component instances from a service instance on the same host_ - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* _Scenario: Manage multiple Hadoop clusters under single Ambari Server_ - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* _Scenario: HBase on YARN_ - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. _Scenario: Credit Fraud Detection YARN Assembly_ - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. was: *Multi Stack Services* Scenario: Deploy HDP & HDF services in same cluster - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* Scenario: Multi service instances on same version - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA Scenario: Multi service instances on different versions - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* Scenario: Multi component instances from a service instance on the same host - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* Scenario: Manage multiple Hadoop clusters under single Ambari Server - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* Scenario: HBase on YARN - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. Scenario: Credit Fraud Detection YARN Assembly - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-upgrade, ambari-web, > stacks >Affects Versions: 2.5.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* > _Scenario: Deploy HDP & HDF services in same cluster_ > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > *Multiple Service Instances* > _Scenario: Multi service instances on same version_ > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > _Scenario: Multi service instances on different versions_ > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > *Multi Host Component Instances* > _Scenario: Multi component instances from a service instance on the same host_ > - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. > - Single instance of KAFKA broker is unable to utilize all the resources on > the host. > - User wants to scale up performance by deploying multiple instances of the > KAFKA brokers/host. > *Multi Cluster* > _Scenario: Manage multiple Hadoop clusters under single Ambari Server_ > - Customer has multiple small Hadoop clusters and would like to manage and > monitor them with a single Ambari Server instance. > *Multi Yarn Hosted Services* > _Scenario: HBase on YARN_
[jira] [Created] (AMBARI-20464) Side Nav: several issues and adjustments
Xi Wang created AMBARI-20464: Summary: Side Nav: several issues and adjustments Key: AMBARI-20464 URL: https://issues.apache.org/jira/browse/AMBARI-20464 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Xi Wang Assignee: Xi Wang 1. Scrolling on Side Nav menu can trigger scrolling on the main content. The same issue for modals, wizards .etc. 2. Service Actions icon "..." should occupy more space to click on. Current behavior: need to click exactly on the icon to show actions dropdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20464) Side Nav: several issues and adjustments
[ https://issues.apache.org/jira/browse/AMBARI-20464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20464: - Fix Version/s: 3.0.0 > Side Nav: several issues and adjustments > > > Key: AMBARI-20464 > URL: https://issues.apache.org/jira/browse/AMBARI-20464 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > > 1. Scrolling on Side Nav menu can trigger scrolling on the main content. The > same issue for modals, wizards .etc. > 2. Service Actions icon "..." should occupy more space to click on. > Current behavior: need to click exactly on the icon to show actions dropdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19621) Mpack Based Operations Model
[ https://issues.apache.org/jira/browse/AMBARI-19621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-19621: --- Epic Name: Mpack V2 (was: V2Mpack) > Mpack Based Operations Model > > > Key: AMBARI-19621 > URL: https://issues.apache.org/jira/browse/AMBARI-19621 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 3.0.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19621) Mpack Based Operations Model
[ https://issues.apache.org/jira/browse/AMBARI-19621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-19621: --- Summary: Mpack Based Operations Model (was: Management Pack v2) > Mpack Based Operations Model > > > Key: AMBARI-19621 > URL: https://issues.apache.org/jira/browse/AMBARI-19621 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 3.0.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Epic Name: Multi Everything Architecture (was: MultiEverythingArchitecture) > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-upgrade, ambari-web, > stacks >Affects Versions: 2.5.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* > Scenario: Deploy HDP & HDF services in same cluster > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > *Multiple Service Instances* > Scenario: Multi service instances on same version > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > Scenario: Multi service instances on different versions > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > *Multi Host Component Instances* > Scenario: Multi component instances from a service instance on the same host > - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. > - Single instance of KAFKA broker is unable to utilize all the resources on > the host. > - User wants to scale up performance by deploying multiple instances of the > KAFKA brokers/host. > *Multi Cluster* > Scenario: Manage multiple Hadoop clusters under single Ambari Server > - Customer has multiple small Hadoop clusters and would like to manage and > monitor them with a single Ambari Server instance. > *Multi Yarn Hosted Services* > Scenario: HBase on YARN > - Deploy second instance of HBase as a long running YARN service. > - Manage YARN hosted service similar to traditional hosted services. > - First class support for Yarn hosted services. > Scenario: Credit Fraud Detection YARN Assembly > - YARN Assembly can have its own ZK, KAFKA etc. > - Manage YARN Assemblies as first-class citizen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20463) Multi Service Instance Support
[ https://issues.apache.org/jira/browse/AMBARI-20463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-20463: --- Epic Name: Multi Service Instance (was: Multi Service Instance Support) > Multi Service Instance Support > -- > > Key: AMBARI-20463 > URL: https://issues.apache.org/jira/browse/AMBARI-20463 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 3.0.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Epic Name: MultiEverythingArchitecture > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-upgrade, ambari-web, > stacks >Affects Versions: 2.5.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* > Scenario: Deploy HDP & HDF services in same cluster > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > *Multiple Service Instances* > Scenario: Multi service instances on same version > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > Scenario: Multi service instances on different versions > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > *Multi Host Component Instances* > Scenario: Multi component instances from a service instance on the same host > - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. > - Single instance of KAFKA broker is unable to utilize all the resources on > the host. > - User wants to scale up performance by deploying multiple instances of the > KAFKA brokers/host. > *Multi Cluster* > Scenario: Manage multiple Hadoop clusters under single Ambari Server > - Customer has multiple small Hadoop clusters and would like to manage and > monitor them with a single Ambari Server instance. > *Multi Yarn Hosted Services* > Scenario: HBase on YARN > - Deploy second instance of HBase as a long running YARN service. > - Manage YARN hosted service similar to traditional hosted services. > - First class support for Yarn hosted services. > Scenario: Credit Fraud Detection YARN Assembly > - YARN Assembly can have its own ZK, KAFKA etc. > - Manage YARN Assemblies as first-class citizen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Component/s: ambari-web ambari-upgrade ambari-server ambari-agent > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-upgrade, ambari-web, > stacks >Affects Versions: 2.5.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* > Scenario: Deploy HDP & HDF services in same cluster > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > *Multiple Service Instances* > Scenario: Multi service instances on same version > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > Scenario: Multi service instances on different versions > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > *Multi Host Component Instances* > Scenario: Multi component instances from a service instance on the same host > - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. > - Single instance of KAFKA broker is unable to utilize all the resources on > the host. > - User wants to scale up performance by deploying multiple instances of the > KAFKA brokers/host. > *Multi Cluster* > Scenario: Manage multiple Hadoop clusters under single Ambari Server > - Customer has multiple small Hadoop clusters and would like to manage and > monitor them with a single Ambari Server instance. > *Multi Yarn Hosted Services* > Scenario: HBase on YARN > - Deploy second instance of HBase as a long running YARN service. > - Manage YARN hosted service similar to traditional hosted services. > - First class support for Yarn hosted services. > Scenario: Credit Fraud Detection YARN Assembly > - YARN Assembly can have its own ZK, KAFKA etc. > - Manage YARN Assemblies as first-class citizen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Affects Version/s: (was: 2.4.0) 2.5.0 > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server, ambari-upgrade, ambari-web, > stacks >Affects Versions: 2.5.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* > Scenario: Deploy HDP & HDF services in same cluster > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > *Multiple Service Instances* > Scenario: Multi service instances on same version > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > Scenario: Multi service instances on different versions > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > *Multi Host Component Instances* > Scenario: Multi component instances from a service instance on the same host > - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. > - Single instance of KAFKA broker is unable to utilize all the resources on > the host. > - User wants to scale up performance by deploying multiple instances of the > KAFKA brokers/host. > *Multi Cluster* > Scenario: Manage multiple Hadoop clusters under single Ambari Server > - Customer has multiple small Hadoop clusters and would like to manage and > monitor them with a single Ambari Server instance. > *Multi Yarn Hosted Services* > Scenario: HBase on YARN > - Deploy second instance of HBase as a long running YARN service. > - Manage YARN hosted service similar to traditional hosted services. > - First class support for Yarn hosted services. > Scenario: Credit Fraud Detection YARN Assembly > - YARN Assembly can have its own ZK, KAFKA etc. > - Manage YARN Assemblies as first-class citizen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Description: *Multi Stack Services* Scenario: Deploy HDP & HDF services in same cluster - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* Scenario: Multi service instances on same version - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA Scenario: Multi service instances on different versions - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* Scenario: Multi component instances from a service instance on the same host - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* Scenario: Manage multiple Hadoop clusters under single Ambari Server - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* Scenario: HBase on YARN - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. Scenario: Credit Fraud Detection YARN Assembly - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. was: *Multi Stack Services* Scenario: Deploy HDP & HDF services in same cluster - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* Scenario: Multi service instances on same version - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA Scenario: Multi service instances on different versions - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* Scenario: Multi component instances from a service instance on the same host - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* Scenario: Manage multiple Hadoop clusters under single Ambari Server - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* Scenario: HBase on YARN - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. Scenario: Credit Fraud Detection YARN Assembly - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* > Scenario: Deploy HDP & HDF services in same cluster > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > *Multiple Service Instances* > Scenario: Multi service instances on same version > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > Scenario: Multi service instances on different versions > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > *Multi Host Component Instances* > Scenario: Multi component instances from a service instance on the same host > - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. > - Single instance of KAFKA broker is unable to utilize all the resources on > the host. > - User wants to scale up performance by deploying multiple instances of the > KAFKA brokers/host. > *Multi Cluster* > Scenario: Manage multiple Hadoop clusters under single Ambari Server > - Customer has multiple small Hadoop clusters and would like to manage and > monitor them with a single Ambari Server instance. > *Multi Yarn Hosted Services* > Scenario: HBase on YARN > - Deploy second instance of HBase as a long running YARN service. > - Manage YARN hos
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Description: *Multi Stack Services* Scenario: Deploy HDP & HDF services in same cluster - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* Scenario: Multi service instances on same version - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA Scenario: Multi service instances on different versions - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* Scenario: Multi component instances from a service instance on the same host - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* Scenario: Manage multiple Hadoop clusters under single Ambari Server - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* Scenario: HBase on YARN - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. Scenario: Credit Fraud Detection YARN Assembly - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. was: *Multi Stack Services* # Scenario: Deploy HDP & HDF services in same cluster - Deploy HDF services in an HDP cluster (Nifi from HDF, HDFS from HDP stack). *Multiple Service Instances* # Scenario: Multi service instances on same version - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA # Scenario: Multi service instances on different versions - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. # Deploy cluster with multiple instances of a service # Provide an ability to handle multiple instances of a Service in a given cluster. In addition, provide ability for a Stack definition to handle multiple versions of a given Service (which than can have 0 or more instances in a given cluster). > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* > Scenario: Deploy HDP & HDF services in same cluster > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > *Multiple Service Instances* > Scenario: Multi service instances on same version > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > Scenario: Multi service instances on different versions > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > *Multi Host Component Instances* > Scenario: Multi component instances from a service instance on the same host > - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. > - Single instance of KAFKA broker is unable to utilize all the resources on > the host. > - User wants to scale up performance by deploying multiple instances of the > KAFKA brokers/host. > *Multi Cluster* > Scenario: Manage multiple Hadoop clusters under single Ambari Server > - Customer has multiple small Hadoop clusters and would like to manage and > monitor them with a single Ambari Server instance. > *Multi Yarn Hosted Services* > Scenario: HBase on YARN > - Deploy second instance of HBase as a long running YARN service. > - Manage YARN hosted service similar to traditional hosted services. > - First class support for Yarn hosted services. > Scenario: Credit Fraud Detection YARN Assembly > - YARN Assembly can have its own ZK, KAFKA etc. > - Manage YARN Assemblies as first-class citizen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Description: *Multi Stack Services* Scenario: Deploy HDP & HDF services in same cluster - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* Scenario: Multi service instances on same version - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA Scenario: Multi service instances on different versions - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* Scenario: Multi component instances from a service instance on the same host - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* Scenario: Manage multiple Hadoop clusters under single Ambari Server - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* Scenario: HBase on YARN - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. Scenario: Credit Fraud Detection YARN Assembly - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. was: *Multi Stack Services* Scenario: Deploy HDP & HDF services in same cluster - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. *Multiple Service Instances* Scenario: Multi service instances on same version - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA Scenario: Multi service instances on different versions - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. *Multi Host Component Instances* Scenario: Multi component instances from a service instance on the same host - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. - Single instance of KAFKA broker is unable to utilize all the resources on the host. - User wants to scale up performance by deploying multiple instances of the KAFKA brokers/host. *Multi Cluster* Scenario: Manage multiple Hadoop clusters under single Ambari Server - Customer has multiple small Hadoop clusters and would like to manage and monitor them with a single Ambari Server instance. *Multi Yarn Hosted Services* Scenario: HBase on YARN - Deploy second instance of HBase as a long running YARN service. - Manage YARN hosted service similar to traditional hosted services. - First class support for Yarn hosted services. Scenario: Credit Fraud Detection YARN Assembly - YARN Assembly can have its own ZK, KAFKA etc. - Manage YARN Assemblies as first-class citizen. > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* > Scenario: Deploy HDP & HDF services in same cluster > - Deploy HDFS from HDP and Kafka, Storm, NiFI from HDF in the same cluster. > *Multiple Service Instances* > Scenario: Multi service instances on same version > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > Scenario: Multi service instances on different versions > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > *Multi Host Component Instances* > Scenario: Multi component instances from a service instance on the same host > - Single host with 128GB RAM, 16 (actual) Cores, 12*4TB disks. > - Single instance of KAFKA broker is unable to utilize all the resources on > the host. > - User wants to scale up performance by deploying multiple instances of the > KAFKA brokers/host. > *Multi Cluster* > Scenario: Manage multiple Hadoop clusters under single Ambari Server > - Customer has multiple small Hadoop clusters and would like to manage and > monitor them with a single Ambari Server instance. > *Multi Yarn Hosted Services* > Scenario: HBase on YARN > - Deploy second instance of HBase as a long running YARN service. > - Manage YARN hoste
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Description: *Multi Stack Services* # Scenario: Deploy HDP & HDF services in same cluster - Deploy HDF services in an HDP cluster (Nifi from HDF, HDFS from HDP stack). *Multiple Service Instances* # Scenario: Multi service instances on same version - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. - User wants to add instance of ZooKeeper vX which is being used by STORM and KAFKA # Scenario: Multi service instances on different versions - Cluster includes instance of SPARK vX. - User wants to add additional instance of SPARK vY. # Deploy cluster with multiple instances of a service # Provide an ability to handle multiple instances of a Service in a given cluster. In addition, provide ability for a Stack definition to handle multiple versions of a given Service (which than can have 0 or more instances in a given cluster). was:Provide an ability to handle multiple instances of a Service in a given cluster. In addition, provide ability for a Stack definition to handle multiple versions of a given Service (which than can have 0 or more instances in a given cluster). > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > *Multi Stack Services* > # Scenario: Deploy HDP & HDF services in same cluster > - Deploy HDF services in an HDP cluster (Nifi from HDF, HDFS from HDP stack). > *Multiple Service Instances* > # Scenario: Multi service instances on same version > - Cluster includes instance of ZooKeeper vX which is being used by HDFS, YARN. > - User wants to add instance of ZooKeeper vX which is being used by STORM and > KAFKA > # Scenario: Multi service instances on different versions > - Cluster includes instance of SPARK vX. > - User wants to add additional instance of SPARK vY. > # Deploy cluster with multiple instances of a service > # > Provide an ability to handle multiple instances of a Service in a given > cluster. In addition, provide ability for a Stack definition to handle > multiple versions of a given Service (which than can have 0 or more instances > in a given cluster). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20463) Multi Service Instance Support
Jayush Luniya created AMBARI-20463: -- Summary: Multi Service Instance Support Key: AMBARI-20463 URL: https://issues.apache.org/jira/browse/AMBARI-20463 Project: Ambari Issue Type: Epic Components: ambari-agent, ambari-server, ambari-web Affects Versions: 3.0.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-14714) [Umbrella] Multi Everything Architecture
[ https://issues.apache.org/jira/browse/AMBARI-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14714: --- Summary: [Umbrella] Multi Everything Architecture (was: [Umbrella] Multi Instance Architecture) > [Umbrella] Multi Everything Architecture > > > Key: AMBARI-14714 > URL: https://issues.apache.org/jira/browse/AMBARI-14714 > Project: Ambari > Issue Type: Epic > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jeff Sposetti >Assignee: Jayush Luniya >Priority: Critical > Fix For: 3.0.0 > > > Provide an ability to handle multiple instances of a Service in a given > cluster. In addition, provide ability for a Stack definition to handle > multiple versions of a given Service (which than can have 0 or more instances > in a given cluster). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20427) Ambari should allow empty string for hive.metastore.uris when running in embedded mode
[ https://issues.apache.org/jira/browse/AMBARI-20427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-20427: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 19e7c65ba2dcf09010aeeb3e3c39c78b410c7a84 > Ambari should allow empty string for hive.metastore.uris when running in > embedded mode > -- > > Key: AMBARI-20427 > URL: https://issues.apache.org/jira/browse/AMBARI-20427 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: trunk > > Attachments: AMBARI-20427.patch > > > Ambari UI prevents setting a value of null or empty string for > hive.metastore.uris > This is a valid use-case for embedded mode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20462) Duplicate entries in DB for auto__instance privileges upon Ambari server restart
[
https://issues.apache.org/jira/browse/AMBARI-20462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas reassigned AMBARI-20462:
-
Assignee: Robert Levas
> Duplicate entries in DB for auto__instance privileges upon Ambari
> server restart
> --
>
> Key: AMBARI-20462
> URL: https://issues.apache.org/jira/browse/AMBARI-20462
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Robert Levas
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
>
> When I create a new user from Ambari UI and let’s say give him ‘Cluster User’
> role; later go to Users page it shows the permissions as seen in the
> screenshot
> The UI display is fine, however when I make an API call like below
> /api/v1/users/tom/privileges?fields=*
>
> It shows three entries for each auto__instance privilege. As an
> example: for ‘AUTO_FILES_INSTANCE’ I see three entries like:
> api/v1/users/tom/privileges/6
> api/v1/users/tom/privileges/56
> api/v1/users/tom/privileges/106
>
> and so on, so we have 16 entries (One for Cluster.User + 3 * privileges for
> each of five View instances)
>
> The same behavior is seen for groups too like:
> /api/v1/groups/gp1/privileges?fields=*
> *Example*
> It is expected that only one of the following rows exists:
> {noformat}
> ambaricustom=> select * from adminprivilege where privilege_id in (6, 56,
> 106);
> privilege_id | permission_id | resource_id | principal_id
> --+---+-+--
> 6 | 4 | 54 |8
>56 | 4 | 54 |8
> 106 | 4 | 54 |8
> (3 rows)
> {noformat}
>
> * permission_id (4): VIEW.USER
> * resource_id (54): AUTO_FILES_INSTANCE
> * principal_id (8): CLUSTER.USER
> *Cause*
> When Ambari server restarts, it installs the automatically created view
> instances without first checking to see if they have been previously created.
> Each restart of Ambari server will create a new set of duplicated records.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20449) Upgrade pre-checks screen does not show CONFIG_MERGE warning
[
https://issues.apache.org/jira/browse/AMBARI-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-20449:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Upgrade pre-checks screen does not show CONFIG_MERGE warning
>
>
> Key: AMBARI-20449
> URL: https://issues.apache.org/jira/browse/AMBARI-20449
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20449_branch-2.5.patch, AMBARI-20449.patch,
> Screen Shot 2017-03-13 at 6.49.59 PM.png, Screen Shot 2017-03-13 at 6.50.03
> PM.png
>
>
> *STR*
> # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1
> # Register HDP-2.6 version and install the bits
> # Click on Upgrade and click on Warning hyperlink for EU
> *Result*:
> Shows 2 warnings for EU. Click on the Warning and it shows "only one warning"
> and the warning for CONFIG_MERGE pre-check does not show up
> (see attachments)
> From the output of pre-checks API call, I do see two warning for Config Merge
> as below:
> {code}
> "href" :
> "http://172.22.81.58:8080/api/v1/clusters/cl1/rolling_upgrades_check/CONFIG_MERGE";,
> "UpgradeChecks" : {
> "check" : "Configuration Merge Check",
> "check_type" : "CLUSTER",
> "cluster_name" : "cl1",
> "failed_detail" : [
> {
> "type" : "topology",
> "property" : "content",
> "current" : "\n\n\n\n
> \nauthentication\n
> ShiroProvider\n
> true\n\n
> sessionTimeout\n30\n
> \n\n
> main.ldapRealm\n
> org.apache.hadoop.gateway.shirorealm.KnoxLdapRealm\n
> \n\n
> main.ldapRealm.userDnTemplate\n
> uid=
> "id" : "CONFIG_MERGE",
> "reason" : "The following config types will have values overwritten:
> hive-interactive-env, topology, hadoop-env",
> "repository_version" : "2.6.0.2-24",
> "status" : "WARNING",
> "upgrade_type" : "NON_ROLLING"
> }
> }
> "id" : "HEALTH",
> "reason" : "The following issues have been detected on this cluster
> and should be addressed before upgrading: CRITICAL: NameNode Last Checkpoint:
> nats11-46-tups-erm16tofnsecha-s11-5.openstacklocal\nCRITICAL: NameNode Last
> Checkpoint: nats11-46-tups-erm16tofnsecha-s11-1",
> "repository_version" : "2.6.0.2-24",
> "status" : "WARNING",
> "upgrade_type" : "NON_ROLLING"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20449) Upgrade pre-checks screen does not show CONFIG_MERGE warning
[
https://issues.apache.org/jira/browse/AMBARI-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926619#comment-15926619
]
Andrii Tkach commented on AMBARI-20449:
---
committed to trunk and branch-2.5
> Upgrade pre-checks screen does not show CONFIG_MERGE warning
>
>
> Key: AMBARI-20449
> URL: https://issues.apache.org/jira/browse/AMBARI-20449
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20449_branch-2.5.patch, AMBARI-20449.patch,
> Screen Shot 2017-03-13 at 6.49.59 PM.png, Screen Shot 2017-03-13 at 6.50.03
> PM.png
>
>
> *STR*
> # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1
> # Register HDP-2.6 version and install the bits
> # Click on Upgrade and click on Warning hyperlink for EU
> *Result*:
> Shows 2 warnings for EU. Click on the Warning and it shows "only one warning"
> and the warning for CONFIG_MERGE pre-check does not show up
> (see attachments)
> From the output of pre-checks API call, I do see two warning for Config Merge
> as below:
> {code}
> "href" :
> "http://172.22.81.58:8080/api/v1/clusters/cl1/rolling_upgrades_check/CONFIG_MERGE";,
> "UpgradeChecks" : {
> "check" : "Configuration Merge Check",
> "check_type" : "CLUSTER",
> "cluster_name" : "cl1",
> "failed_detail" : [
> {
> "type" : "topology",
> "property" : "content",
> "current" : "\n\n\n\n
> \nauthentication\n
> ShiroProvider\n
> true\n\n
> sessionTimeout\n30\n
> \n\n
> main.ldapRealm\n
> org.apache.hadoop.gateway.shirorealm.KnoxLdapRealm\n
> \n\n
> main.ldapRealm.userDnTemplate\n
> uid=
> "id" : "CONFIG_MERGE",
> "reason" : "The following config types will have values overwritten:
> hive-interactive-env, topology, hadoop-env",
> "repository_version" : "2.6.0.2-24",
> "status" : "WARNING",
> "upgrade_type" : "NON_ROLLING"
> }
> }
> "id" : "HEALTH",
> "reason" : "The following issues have been detected on this cluster
> and should be addressed before upgrading: CRITICAL: NameNode Last Checkpoint:
> nats11-46-tups-erm16tofnsecha-s11-5.openstacklocal\nCRITICAL: NameNode Last
> Checkpoint: nats11-46-tups-erm16tofnsecha-s11-1",
> "repository_version" : "2.6.0.2-24",
> "status" : "WARNING",
> "upgrade_type" : "NON_ROLLING"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20462) Duplicate entries in DB for auto__instance privileges upon Ambari server restart
Vivek Sharma created AMBARI-20462:
-
Summary: Duplicate entries in DB for auto__instance
privileges upon Ambari server restart
Key: AMBARI-20462
URL: https://issues.apache.org/jira/browse/AMBARI-20462
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Vivek Sharma
Priority: Critical
Fix For: 2.5.0
When I create a new user from Ambari UI and let’s say give him ‘Cluster User’
role; later go to Users page it shows the permissions as seen in the screenshot
The UI display is fine, however when I make an API call like below
/api/v1/users/tom/privileges?fields=*
It shows three entries for each auto__instance privilege. As an example:
for ‘AUTO_FILES_INSTANCE’ I see three entries like:
api/v1/users/tom/privileges/6
api/v1/users/tom/privileges/56
api/v1/users/tom/privileges/106
and so on, so we have 16 entries (One for Cluster.User + 3 * privileges for
each of five View instances)
The same behavior is seen for groups too like:
/api/v1/groups/gp1/privileges?fields=*
*Example*
It is expected that only one of the following rows exists:
{noformat}
ambaricustom=> select * from adminprivilege where privilege_id in (6, 56, 106);
privilege_id | permission_id | resource_id | principal_id
--+---+-+--
6 | 4 | 54 |8
56 | 4 | 54 |8
106 | 4 | 54 |8
(3 rows)
{noformat}
* permission_id (4): VIEW.USER
* resource_id (54): AUTO_FILES_INSTANCE
* principal_id (8): CLUSTER.USER
*Cause*
When Ambari server restarts, it installs the automatically created view
instances without first checking to see if they have been previously created.
Each restart of Ambari server will create a new set of duplicated records.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20433) Need the ability to have dynamic dependency between component/services
[ https://issues.apache.org/jira/browse/AMBARI-20433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926589#comment-15926589 ] Louis Mau commented on AMBARI-20433: Another example is HDFS having a static dependency on Zookeeper even though the latter is not needed until HA is enabled. The check for Zookeeper is better done during HA enablement rather than enforced at installation time when HA might not be needed. > Need the ability to have dynamic dependency between component/services > -- > > Key: AMBARI-20433 > URL: https://issues.apache.org/jira/browse/AMBARI-20433 > Project: Ambari > Issue Type: Improvement > Components: ambari-server > Environment: all >Reporter: Tuong Truong > > Currently, service interdependency are statically defined in the stack > regardless its needed or not. For instance, Spark has a static dependency on > Hive and will force Hive to be installed whenevern Spark is install, but Hive > is only needed if Spark Thrift Server component is installed. > It would be nice if the stack has to ability to declare the dependency > conditionally and at component level and the dependency will only be in > effect when the component is chosen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20457) Dependent Configurations popup: cells with current and recommended value can have different width
[ https://issues.apache.org/jira/browse/AMBARI-20457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926580#comment-15926580 ] Hudson commented on AMBARI-20457: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7046 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7046/]) AMBARI-20457 Dependent Configurations popup: cells with current and (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d16d18d456e562feb6099df0c6528ed61e88fdd0]) * (edit) ambari-web/app/styles/application.less > Dependent Configurations popup: cells with current and recommended value can > have different width > - > > Key: AMBARI-20457 > URL: https://issues.apache.org/jira/browse/AMBARI-20457 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20457.patch > > > In dependent configs popup, cells with current and recommended value for > properties to be added or removed sometimes have inequal width. Also, word > wrapping of 'Property undefined/removed' messages is incorrect. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20427) Ambari should allow empty string for hive.metastore.uris when running in embedded mode
[ https://issues.apache.org/jira/browse/AMBARI-20427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-20427: - Status: Patch Available (was: Open) > Ambari should allow empty string for hive.metastore.uris when running in > embedded mode > -- > > Key: AMBARI-20427 > URL: https://issues.apache.org/jira/browse/AMBARI-20427 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: trunk > > Attachments: AMBARI-20427.patch > > > Ambari UI prevents setting a value of null or empty string for > hive.metastore.uris > This is a valid use-case for embedded mode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20368) Hbase-client installed failed when hdfs hasnot installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926554#comment-15926554 ] Alejandro Fernandez commented on AMBARI-20368: -- [~alicezhangxiaolu], what branch is this for? Please also include it in the code review > Hbase-client installed failed when hdfs hasnot installed > > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Attachments: AMBARI-20368.patch, screenshot-1.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20368) Hbase-client installed failed when hdfs hasnot installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez reassigned AMBARI-20368: Assignee: zhangxiaolu > Hbase-client installed failed when hdfs hasnot installed > > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Attachments: AMBARI-20368.patch, screenshot-1.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20461) override_uid should set to false when upgrading Ambari 2.1 to 2.2 or newer with custom stacks
[ https://issues.apache.org/jira/browse/AMBARI-20461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20461: --- Status: Patch Available (was: Open) > override_uid should set to false when upgrading Ambari 2.1 to 2.2 or newer > with custom stacks > - > > Key: AMBARI-20461 > URL: https://issues.apache.org/jira/browse/AMBARI-20461 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20461.patch > > > Custom stacks may not have override_hbase_uid property in hbase-env.xml, in > this case, override_uid is currently set to true by Ambari's auto merge > logic. it should be set to false when upgrading Ambari 2.1 to 2.2 or newer > with custom stacks in order to respect the existing UID customers already set > on their clusters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20461) override_uid should set to false when upgrading Ambari 2.1 to 2.2 or newer with custom stacks
[ https://issues.apache.org/jira/browse/AMBARI-20461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20461: --- Fix Version/s: trunk > override_uid should set to false when upgrading Ambari 2.1 to 2.2 or newer > with custom stacks > - > > Key: AMBARI-20461 > URL: https://issues.apache.org/jira/browse/AMBARI-20461 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20461.patch > > > Custom stacks may not have override_hbase_uid property in hbase-env.xml, in > this case, override_uid is currently set to true by Ambari's auto merge > logic. it should be set to false when upgrading Ambari 2.1 to 2.2 or newer > with custom stacks in order to respect the existing UID customers already set > on their clusters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
