[jira] [Updated] (AMBARI-16961) Deployment via blueprint failing due to Logsearch client install failure
[ https://issues.apache.org/jira/browse/AMBARI-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-16961: -- Attachment: AMBARI-16961.patch > Deployment via blueprint failing due to Logsearch client install failure > > > Key: AMBARI-16961 > URL: https://issues.apache.org/jira/browse/AMBARI-16961 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16961.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16961) Deployment via blueprint failing due to Logsearch client install failure
[ https://issues.apache.org/jira/browse/AMBARI-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-16961: -- Attachment: (was: AMBARI-16961.patch) > Deployment via blueprint failing due to Logsearch client install failure > > > Key: AMBARI-16961 > URL: https://issues.apache.org/jira/browse/AMBARI-16961 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16961.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16983) Installer/ASW: Next and Back button should be disabled once its clicked
[
https://issues.apache.org/jira/browse/AMBARI-16983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310624#comment-15310624
]
Hadoop QA commented on AMBARI-16983:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807411/AMBARI-16983.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7101//console
This message is automatically generated.
> Installer/ASW: Next and Back button should be disabled once its clicked
> ---
>
> Key: AMBARI-16983
> URL: https://issues.apache.org/jira/browse/AMBARI-16983
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-16983.patch
>
>
> On installer/ASW wizard "Assign Masters", "Select Salves and Clients",
> "Configure Services" pages, clicking on next or back button should show
> spinner next to those buttons respectively.
> When either of these buttons are clicked on a page, both button should be
> disabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16979) YARN default configs are invalid
[ https://issues.apache.org/jira/browse/AMBARI-16979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-16979: Attachment: AMBARI-16979_4-trunk.patch > YARN default configs are invalid > > > Key: AMBARI-16979 > URL: https://issues.apache.org/jira/browse/AMBARI-16979 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16979_2-trunk.patch, AMBARI-16979_3-trunk.patch, > AMBARI-16979_4-trunk.patch > > > The default value of yarn.resourcemanager.zk-acl is set to > "world:anyone:rwcda ". The extra space is causing the yarn config to be > considered invalid > The default value of scheduler shows empty. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16979) YARN default configs are invalid
[ https://issues.apache.org/jira/browse/AMBARI-16979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-16979: Status: Patch Available (was: Open) > YARN default configs are invalid > > > Key: AMBARI-16979 > URL: https://issues.apache.org/jira/browse/AMBARI-16979 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16979_2-trunk.patch, AMBARI-16979_3-trunk.patch, > AMBARI-16979_4-trunk.patch > > > The default value of yarn.resourcemanager.zk-acl is set to > "world:anyone:rwcda ". The extra space is causing the yarn config to be > considered invalid > The default value of scheduler shows empty. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16969) Provide ability in AMS to filter tracked metrics through a whitelist metic file.
[ https://issues.apache.org/jira/browse/AMBARI-16969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-16969: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk and branch-2.4 > Provide ability in AMS to filter tracked metrics through a whitelist metic > file. > > > Key: AMBARI-16969 > URL: https://issues.apache.org/jira/browse/AMBARI-16969 > Project: Ambari > Issue Type: Task >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Attachments: AMBARI-16969-trunk.patch, AMBARI-16969.patch > > > The file should contain a list of metrics that will be the only metrics > stored and aggregated in AMS. > Config to use for specifying metric file. > ams-site : timeline.metrics.whitelist.file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16859) Kafka dashboards for Grafana
[ https://issues.apache.org/jira/browse/AMBARI-16859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-16859: - Attachment: (was: AMBARI-16859.patch) > Kafka dashboards for Grafana > > > Key: AMBARI-16859 > URL: https://issues.apache.org/jira/browse/AMBARI-16859 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao > Fix For: 2.4.0 > > Attachments: AMBARI-16859.patch > > > Add 3 dashboards to Grafana > - Kafka Home > - Kafka Hosts (Templatized) > - Kafka Topics (Templatized per Topic) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16985) "Wizard in progress" bar should not look clickable
[
https://issues.apache.org/jira/browse/AMBARI-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310617#comment-15310617
]
Hadoop QA commented on AMBARI-16985:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807428/AMBARI-16985.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7099//console
This message is automatically generated.
> "Wizard in progress" bar should not look clickable
> --
>
> Key: AMBARI-16985
> URL: https://issues.apache.org/jira/browse/AMBARI-16985
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-16985.patch
>
>
> Change cursor type to default on " is in progress" bar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16979) YARN default configs are invalid
[
https://issues.apache.org/jira/browse/AMBARI-16979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310637#comment-15310637
]
Hadoop QA commented on AMBARI-16979:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807421/AMBARI-16979_3-trunk.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7103//console
This message is automatically generated.
> YARN default configs are invalid
>
>
> Key: AMBARI-16979
> URL: https://issues.apache.org/jira/browse/AMBARI-16979
> Project: Ambari
> Issue Type: Bug
> Components: blueprints
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16979_2-trunk.patch, AMBARI-16979_3-trunk.patch
>
>
> The default value of yarn.resourcemanager.zk-acl is set to
> "world:anyone:rwcda ". The extra space is causing the yarn config to be
> considered invalid
> The default value of scheduler shows empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16965) Exception while detecting JMX protocol for HISTORYSERVER
[
https://issues.apache.org/jira/browse/AMBARI-16965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310693#comment-15310693
]
Hadoop QA commented on AMBARI-16965:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807462/AMBARI-16965.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7109//console
This message is automatically generated.
> Exception while detecting JMX protocol for HISTORYSERVER
>
>
> Key: AMBARI-16965
> URL: https://issues.apache.org/jira/browse/AMBARI-16965
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16965.patch
>
>
> Secured cluster with HDP 2.5. (also installed Ranger but I'm not sure that it
> influences on this)
> I see a lot of exception in ambari server logs:
>
>
>
> 25 May 2016 16:50:16,982 INFO [pool-7-thread-26]
> AbstractProviderModule:1184 - Defaulting JMX to HTTP protocol for for
> clusterName = c1, componentName = HISTORYSERVERHISTORYSERVER
> 25 May 2016 16:50:23,617 INFO [pool-7-thread-28]
> AbstractProviderModule:1182 - Exception while detecting JMX protocol for
> clusterName = c1, componentName = HISTORYSERVER
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getJMXProtocolString(AbstractProviderModule.java:1205)
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getJMXProtocol(AbstractProviderModule.java:1175)
> at
> org.apache.ambari.server.controller.jmx.JMXPropertyProvider.getJMXProtocol(JMXPropertyProvider.java:378)
> at
> org.apache.ambari.server.controller.jmx.JMXPropertyProvider.populateResource(JMXPropertyProvider.java:194)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:185)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:183)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
> It appears every few seconds
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16987) After relogin get the same page was before logout instead of Dashboard
[
https://issues.apache.org/jira/browse/AMBARI-16987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310658#comment-15310658
]
Antonenko Alexander commented on AMBARI-16987:
--
28524 tests complete (24 seconds)
154 tests pending
rat check passed
> After relogin get the same page was before logout instead of Dashboard
> --
>
> Key: AMBARI-16987
> URL: https://issues.apache.org/jira/browse/AMBARI-16987
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16987.patch
>
>
> STR:
> # Deploy cluster
> # Go to any tab, but not Dashboard
> # Log out
> # Log in again
> Result: got the same page as before log out.
> Tested also on Ambari built from ambari-vdf brach
> Env:
> {code}
> ambari-server --hash
> 2ab5c04efcdc42190279f3259250663ea1f7d8bb
> rpm -qa |grep ambari
> ambari-server-2.4.99.0-87.x86_64
> ambari-agent-2.4.99.0-87.x86_64
> {code}
> Tested on the Chrome (latest), Firefox 24.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16988) Invalid recommended value for storm.local.dir (/usr/hdp/hadoop/storm)
[
https://issues.apache.org/jira/browse/AMBARI-16988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-16988:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk and branch-2.4
> Invalid recommended value for storm.local.dir (/usr/hdp/hadoop/storm)
> -
>
> Key: AMBARI-16988
> URL: https://issues.apache.org/jira/browse/AMBARI-16988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16988.patch
>
>
> Ambari was installed on the host with the following mounts (Ubuntu 16,
> HDP-2.5):
> {noformat}
> root@u16-ambari-ubuntu-xenial-01:~# df -h
> Filesystem Size Used Avail Use% Mounted on
> udev4.8G 0 4.8G 0% /dev
> tmpfs 981M 15M 967M 2% /run
> /dev/sda1 9.7G 3.4G 6.3G 35% /
> tmpfs 4.8G 4.0K 4.8G 1% /dev/shm
> tmpfs 5.0M 0 5.0M 0% /run/lock
> tmpfs 4.8G 0 4.8G 0% /sys/fs/cgroup
> tmpfs 100K 0 100K 0% /run/lxcfs/controllers
> /dev/sdc135G 1.9G 31G 6% /usr/hdp
> tmpfs 981M 0 981M 0% /run/user/1000
> {noformat}
> The recommended value was:
> {noformat}
> "storm.local.dir" : "/usr/hdp/hadoop/storm"
> {noformat}
> hdp-select expects that folder name inside of /usr/hdp correspond to version
> numbers.
> {noformat}
> root@u16-ambari-ubuntu-xenial-01:~# hdp-select versions
> Traceback (most recent call last):
> File "/usr/bin/hdp-select", line 391, in
> printVersions()
> File "/usr/bin/hdp-select", line 248, in printVersions
> result[tuple(map(int, versionRegex.split(f)))] = f
> ValueError: invalid literal for int() with base 10: 'hadoop'
> root@u16-ambari-ubuntu-xenial-01:~# ll /usr/hdp
> total 36
> drwxr-xr-x 6 root root 4096 May 27 10:53 ./
> drwxr-xr-x 12 root root 4096 May 26 17:19 ../
> drwxr-xr-x 17 root root 4096 May 27 10:53 2.5.0.0-568/
> drwxr-xr-x 2 root root 4096 May 27 10:44 current/
> drwxr-xr-x 3 root root 4096 May 27 10:53 hadoop/
> drwx-- 2 root root 16384 May 26 17:02 lost+found/
> {noformat}
> It's a brittle part of hdp-select and probably should be fixed.
> Anyway Ambari shouldn't recommend /usr/hdp/hadoop/storm folder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16988) Invalid recommended value for storm.local.dir (/usr/hdp/hadoop/storm)
[
https://issues.apache.org/jira/browse/AMBARI-16988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310533#comment-15310533
]
Andrii Tkach commented on AMBARI-16988:
---
+1 for the patch
> Invalid recommended value for storm.local.dir (/usr/hdp/hadoop/storm)
> -
>
> Key: AMBARI-16988
> URL: https://issues.apache.org/jira/browse/AMBARI-16988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16988.patch
>
>
> Ambari was installed on the host with the following mounts (Ubuntu 16,
> HDP-2.5):
> {noformat}
> root@u16-ambari-ubuntu-xenial-01:~# df -h
> Filesystem Size Used Avail Use% Mounted on
> udev4.8G 0 4.8G 0% /dev
> tmpfs 981M 15M 967M 2% /run
> /dev/sda1 9.7G 3.4G 6.3G 35% /
> tmpfs 4.8G 4.0K 4.8G 1% /dev/shm
> tmpfs 5.0M 0 5.0M 0% /run/lock
> tmpfs 4.8G 0 4.8G 0% /sys/fs/cgroup
> tmpfs 100K 0 100K 0% /run/lxcfs/controllers
> /dev/sdc135G 1.9G 31G 6% /usr/hdp
> tmpfs 981M 0 981M 0% /run/user/1000
> {noformat}
> The recommended value was:
> {noformat}
> "storm.local.dir" : "/usr/hdp/hadoop/storm"
> {noformat}
> hdp-select expects that folder name inside of /usr/hdp correspond to version
> numbers.
> {noformat}
> root@u16-ambari-ubuntu-xenial-01:~# hdp-select versions
> Traceback (most recent call last):
> File "/usr/bin/hdp-select", line 391, in
> printVersions()
> File "/usr/bin/hdp-select", line 248, in printVersions
> result[tuple(map(int, versionRegex.split(f)))] = f
> ValueError: invalid literal for int() with base 10: 'hadoop'
> root@u16-ambari-ubuntu-xenial-01:~# ll /usr/hdp
> total 36
> drwxr-xr-x 6 root root 4096 May 27 10:53 ./
> drwxr-xr-x 12 root root 4096 May 26 17:19 ../
> drwxr-xr-x 17 root root 4096 May 27 10:53 2.5.0.0-568/
> drwxr-xr-x 2 root root 4096 May 27 10:44 current/
> drwxr-xr-x 3 root root 4096 May 27 10:53 hadoop/
> drwx-- 2 root root 16384 May 26 17:02 lost+found/
> {noformat}
> It's a brittle part of hdp-select and probably should be fixed.
> Anyway Ambari shouldn't recommend /usr/hdp/hadoop/storm folder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16979) YARN default configs are invalid
[ https://issues.apache.org/jira/browse/AMBARI-16979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-16979: Status: Open (was: Patch Available) > YARN default configs are invalid > > > Key: AMBARI-16979 > URL: https://issues.apache.org/jira/browse/AMBARI-16979 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16979_2-trunk.patch, AMBARI-16979_3-trunk.patch > > > The default value of yarn.resourcemanager.zk-acl is set to > "world:anyone:rwcda ". The extra space is causing the yarn config to be > considered invalid > The default value of scheduler shows empty. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16986) Required empty config is present after Upgrade from 2.1.2.1 to 2.4.0.0 for HIVE and HBASE
[
https://issues.apache.org/jira/browse/AMBARI-16986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310717#comment-15310717
]
Hadoop QA commented on AMBARI-16986:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807450/AMBARI-16986.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7114//console
This message is automatically generated.
> Required empty config is present after Upgrade from 2.1.2.1 to 2.4.0.0 for
> HIVE and HBASE
> -
>
> Key: AMBARI-16986
> URL: https://issues.apache.org/jira/browse/AMBARI-16986
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16986.patch
>
>
> STR:
> 1) Install old version - 2.1.1
> 2) Enable Mit security
> 3)Make upgrade
> 4)Add smartSense
> Actual results: Required empty config is present after Upgrade from 2.1.2.1
> to 2.4.0.0 for HIVE and HBASE
> Screenshots were attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16859) Kafka dashboards for Grafana
[ https://issues.apache.org/jira/browse/AMBARI-16859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-16859: - Attachment: AMBARI-16859.patch > Kafka dashboards for Grafana > > > Key: AMBARI-16859 > URL: https://issues.apache.org/jira/browse/AMBARI-16859 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao > Fix For: 2.4.0 > > Attachments: AMBARI-16859.patch > > > Add 3 dashboards to Grafana > - Kafka Home > - Kafka Hosts (Templatized) > - Kafka Topics (Templatized per Topic) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16965) Exception while detecting JMX protocol for HISTORYSERVER
[
https://issues.apache.org/jira/browse/AMBARI-16965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310727#comment-15310727
]
Hadoop QA commented on AMBARI-16965:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807462/AMBARI-16965.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7116//console
This message is automatically generated.
> Exception while detecting JMX protocol for HISTORYSERVER
>
>
> Key: AMBARI-16965
> URL: https://issues.apache.org/jira/browse/AMBARI-16965
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16965.patch
>
>
> Secured cluster with HDP 2.5. (also installed Ranger but I'm not sure that it
> influences on this)
> I see a lot of exception in ambari server logs:
>
>
>
> 25 May 2016 16:50:16,982 INFO [pool-7-thread-26]
> AbstractProviderModule:1184 - Defaulting JMX to HTTP protocol for for
> clusterName = c1, componentName = HISTORYSERVERHISTORYSERVER
> 25 May 2016 16:50:23,617 INFO [pool-7-thread-28]
> AbstractProviderModule:1182 - Exception while detecting JMX protocol for
> clusterName = c1, componentName = HISTORYSERVER
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getJMXProtocolString(AbstractProviderModule.java:1205)
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getJMXProtocol(AbstractProviderModule.java:1175)
> at
> org.apache.ambari.server.controller.jmx.JMXPropertyProvider.getJMXProtocol(JMXPropertyProvider.java:378)
> at
> org.apache.ambari.server.controller.jmx.JMXPropertyProvider.populateResource(JMXPropertyProvider.java:194)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:185)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:183)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
> It appears every few seconds
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16971) Stack VDF should ignore unsupported OS
[ https://issues.apache.org/jira/browse/AMBARI-16971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-16971: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Stack VDF should ignore unsupported OS > -- > > Key: AMBARI-16971 > URL: https://issues.apache.org/jira/browse/AMBARI-16971 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole > Fix For: 2.4.0 > > Attachments: AMBARI-16971.patch > > > Stack VDF loaded via hdp_urlinfo.json may contain OS families that are not > supported by the stack. They should not be included in the merged Version > Definition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16979) YARN default configs are invalid
[
https://issues.apache.org/jira/browse/AMBARI-16979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310609#comment-15310609
]
Hadoop QA commented on AMBARI-16979:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807421/AMBARI-16979_3-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.internal.HostResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7098//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7098//console
This message is automatically generated.
> YARN default configs are invalid
>
>
> Key: AMBARI-16979
> URL: https://issues.apache.org/jira/browse/AMBARI-16979
> Project: Ambari
> Issue Type: Bug
> Components: blueprints
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16979_2-trunk.patch, AMBARI-16979_3-trunk.patch
>
>
> The default value of yarn.resourcemanager.zk-acl is set to
> "world:anyone:rwcda ". The extra space is causing the yarn config to be
> considered invalid
> The default value of scheduler shows empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16988) Invalid recommended value for storm.local.dir (/usr/hdp/hadoop/storm)
[
https://issues.apache.org/jira/browse/AMBARI-16988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310679#comment-15310679
]
Hadoop QA commented on AMBARI-16988:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807453/AMBARI-16988.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7108//console
This message is automatically generated.
> Invalid recommended value for storm.local.dir (/usr/hdp/hadoop/storm)
> -
>
> Key: AMBARI-16988
> URL: https://issues.apache.org/jira/browse/AMBARI-16988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16988.patch
>
>
> Ambari was installed on the host with the following mounts (Ubuntu 16,
> HDP-2.5):
> {noformat}
> root@u16-ambari-ubuntu-xenial-01:~# df -h
> Filesystem Size Used Avail Use% Mounted on
> udev4.8G 0 4.8G 0% /dev
> tmpfs 981M 15M 967M 2% /run
> /dev/sda1 9.7G 3.4G 6.3G 35% /
> tmpfs 4.8G 4.0K 4.8G 1% /dev/shm
> tmpfs 5.0M 0 5.0M 0% /run/lock
> tmpfs 4.8G 0 4.8G 0% /sys/fs/cgroup
> tmpfs 100K 0 100K 0% /run/lxcfs/controllers
> /dev/sdc135G 1.9G 31G 6% /usr/hdp
> tmpfs 981M 0 981M 0% /run/user/1000
> {noformat}
> The recommended value was:
> {noformat}
> "storm.local.dir" : "/usr/hdp/hadoop/storm"
> {noformat}
> hdp-select expects that folder name inside of /usr/hdp correspond to version
> numbers.
> {noformat}
> root@u16-ambari-ubuntu-xenial-01:~# hdp-select versions
> Traceback (most recent call last):
> File "/usr/bin/hdp-select", line 391, in
> printVersions()
> File "/usr/bin/hdp-select", line 248, in printVersions
> result[tuple(map(int, versionRegex.split(f)))] = f
> ValueError: invalid literal for int() with base 10: 'hadoop'
> root@u16-ambari-ubuntu-xenial-01:~# ll /usr/hdp
> total 36
> drwxr-xr-x 6 root root 4096 May 27 10:53 ./
> drwxr-xr-x 12 root root 4096 May 26 17:19 ../
> drwxr-xr-x 17 root root 4096 May 27 10:53 2.5.0.0-568/
> drwxr-xr-x 2 root root 4096 May 27 10:44 current/
> drwxr-xr-x 3 root root 4096 May 27 10:53 hadoop/
> drwx-- 2 root root 16384 May 26 17:02 lost+found/
> {noformat}
> It's a brittle part of hdp-select and probably should be fixed.
> Anyway Ambari shouldn't recommend /usr/hdp/hadoop/storm folder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16980) History tab takes long to populate when there is more entry in history table.
[
https://issues.apache.org/jira/browse/AMBARI-16980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310635#comment-15310635
]
Hadoop QA commented on AMBARI-16980:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807429/AMBARI-16980_branch-2.4-1.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7102//console
This message is automatically generated.
> History tab takes long to populate when there is more entry in history table.
> -
>
> Key: AMBARI-16980
> URL: https://issues.apache.org/jira/browse/AMBARI-16980
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: ambari-2.2.2
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-16980_branch-2.4-1.patch
>
>
> for 638 entries in history table it takes more than 14 seconds to get the
> data from server and populate the table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16989) Ambari-server fails to start after reboot on Ubuntu
[
https://issues.apache.org/jira/browse/AMBARI-16989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310702#comment-15310702
]
Hadoop QA commented on AMBARI-16989:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807469/AMBARI-16989.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7110//console
This message is automatically generated.
> Ambari-server fails to start after reboot on Ubuntu
> ---
>
> Key: AMBARI-16989
> URL: https://issues.apache.org/jira/browse/AMBARI-16989
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16989.patch
>
>
> [root@gc7201 ~]# ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 33, in
> from ambari_server.dbConfiguration import DATABASE_NAMES,
> LINUX_DBMS_KEYS_LIST
> File
> "/usr/lib/python2.6/site-packages/ambari_server/dbConfiguration.py", line 28,
> in
> from ambari_server.serverConfiguration import
> decrypt_password_for_alias, get_ambari_properties, get_is_secure, \
> File
> "/usr/lib/python2.6/site-packages/ambari_server/serverConfiguration.py", line
> 537, in
> configDefaults = ServerConfigDefaults()
> File
> "/usr/lib/python2.6/site-packages/ambari_server/serverConfiguration.py", line
> 456, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
> File
> "/usr/lib/python2.6/site-packages/ambari_server/serverConfiguration.py", line
> 352, in __init__
> self.check_if_directories_writable([self.OUT_DIR, self.PID_DIR])
> File
> "/usr/lib/python2.6/site-packages/ambari_server/serverConfiguration.py", line
> 394, in check_if_directories_writable
> raise FatalException(-1, "Unable to access {0} directory. Confirm the
> directory is created and is writable by the Ambari Server user account
> '{1}'".format(directory, getpass.getuser()))
> ambari_commons.exceptions.FatalException: "Fatal exception: Unable to
> access /var/run/ambari-server directory. Confirm the directory is created and
> is writable by the Ambari Server user account 'root', exit code -1"
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16979) YARN default configs are invalid
[
https://issues.apache.org/jira/browse/AMBARI-16979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310705#comment-15310705
]
Hadoop QA commented on AMBARI-16979:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807474/AMBARI-16979_4-trunk.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7111//console
This message is automatically generated.
> YARN default configs are invalid
>
>
> Key: AMBARI-16979
> URL: https://issues.apache.org/jira/browse/AMBARI-16979
> Project: Ambari
> Issue Type: Bug
> Components: blueprints
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16979_2-trunk.patch, AMBARI-16979_3-trunk.patch,
> AMBARI-16979_4-trunk.patch
>
>
> The default value of yarn.resourcemanager.zk-acl is set to
> "world:anyone:rwcda ". The extra space is causing the yarn config to be
> considered invalid
> The default value of scheduler shows empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16987) After relogin get the same page was before logout instead of Dashboard
[
https://issues.apache.org/jira/browse/AMBARI-16987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-16987:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk and branch-2.4
> After relogin get the same page was before logout instead of Dashboard
> --
>
> Key: AMBARI-16987
> URL: https://issues.apache.org/jira/browse/AMBARI-16987
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16987.patch
>
>
> STR:
> # Deploy cluster
> # Go to any tab, but not Dashboard
> # Log out
> # Log in again
> Result: got the same page as before log out.
> Tested also on Ambari built from ambari-vdf brach
> Env:
> {code}
> ambari-server --hash
> 2ab5c04efcdc42190279f3259250663ea1f7d8bb
> rpm -qa |grep ambari
> ambari-server-2.4.99.0-87.x86_64
> ambari-agent-2.4.99.0-87.x86_64
> {code}
> Tested on the Chrome (latest), Firefox 24.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-16911) Enable HS2 Interactive > Select Hosts does not have Cancel and close
[ https://issues.apache.org/jira/browse/AMBARI-16911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-16911. -- Resolution: Fixed Additional patch committed to trunk and branch-2.4 > Enable HS2 Interactive > Select Hosts does not have Cancel and close > > > Key: AMBARI-16911 > URL: https://issues.apache.org/jira/browse/AMBARI-16911 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: ambari-2.4.0 >Reporter: Shraddha Sumit >Assignee: Antonenko Alexander >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-16911.patch, before.png, now-1.png, now-2.png > > > Deploy cluster using ambari with Hive and slider > Enable HS2 Interactive > Expected: Select Hosts (Assign masters) page should have Cancel button and > 'X' icon to close or cancel this action. > Actual: On Select Hosts (Assign masters) page there is no 'Cancel' button or > 'X' icon for user to cancel this action. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16995) While installing cluster from UI, 3 atlas fields are not auto populated in customize services page
Vivek Rathod created AMBARI-16995: - Summary: While installing cluster from UI, 3 atlas fields are not auto populated in customize services page Key: AMBARI-16995 URL: https://issues.apache.org/jira/browse/AMBARI-16995 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: ambari-2.4.0 Environment: ambari-server version: ambari-server-2.4.0.0-622.x86_64 ambari-server --hash: dc340e8c6cb4fa6c062f805cc1917f62299a5f50 HDP Stack: 2.5 HDP Version: 2.5.0.0-614 Ambari DB: :Oracle Reporter: Vivek Rathod Priority: Critical Fix For: ambari-2.4.0 Here are those properties: atlas.audit.hbase.zookeeper.quorum atlas.graph.index.search.solr.zookeeper-url atlas.graph.storage.hostname -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16961) Deployment via blueprint failing due to Logsearch client install failure
[ https://issues.apache.org/jira/browse/AMBARI-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-16961: -- Attachment: AMBARI-16961.patch > Deployment via blueprint failing due to Logsearch client install failure > > > Key: AMBARI-16961 > URL: https://issues.apache.org/jira/browse/AMBARI-16961 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16961.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16996) Enabling interactive query in kerberized cluster after re-login results in HS2 interactive installation failure
[ https://issues.apache.org/jira/browse/AMBARI-16996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-16996: Status: Patch Available (was: Open) Verified that the patch fixes the issue. ambari-web unit tests passes with the fix: 28632 tests complete (29 seconds) 154 tests pending > Enabling interactive query in kerberized cluster after re-login results in > HS2 interactive installation failure > > > Key: AMBARI-16996 > URL: https://issues.apache.org/jira/browse/AMBARI-16996 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16996.patch > > > *Steps to Reproduce:* > # Install a cluster with hive > # Kerberize the cluster > # Log out of the cluster > # Log in back to the cluster > # Enable interactive query for hive service. > # Save configurations for Hive service > *Expected Result*: On saving configurations, HS2 interactive and other > dependencies are installed and started successfully > *Actual Result*: On saving configurations, HS2 interactive install task fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16961) Deployment via blueprint failing due to Logsearch client install failure
[ https://issues.apache.org/jira/browse/AMBARI-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-16961: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Deployment via blueprint failing due to Logsearch client install failure > > > Key: AMBARI-16961 > URL: https://issues.apache.org/jira/browse/AMBARI-16961 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16961.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16961) Deployment via blueprint failing due to Logsearch client install failure
[
https://issues.apache.org/jira/browse/AMBARI-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311469#comment-15311469
]
Olivér Szabó commented on AMBARI-16961:
---
committed to trunk:
{code:java}
commit f3e2768e7a8fbebfc9a234735bc3f7c863c7a7d8
Author: oleewere
Date: Thu Jun 2 01:35:41 2016 +0200
AMBARI-16961. Remove LogSearch dependency from ATLAS (oleewere)
{code}
committed to branch-2.4:
{code:java}
commit c0f4d1b6f317a65a7b8812984789d959eb0d44d0
Author: oleewere
Date: Thu Jun 2 01:35:41 2016 +0200
AMBARI-16961. Remove LogSearch dependency from ATLAS (oleewere)
{code}
> Deployment via blueprint failing due to Logsearch client install failure
>
>
> Key: AMBARI-16961
> URL: https://issues.apache.org/jira/browse/AMBARI-16961
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16961.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16719) Enable authentication using Ambari for LogSearch
[ https://issues.apache.org/jira/browse/AMBARI-16719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311492#comment-15311492 ] Hudson commented on AMBARI-16719: - FAILURE: Integrated in Ambari-trunk-Commit #4982 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4982/]) AMBARI-16719. Enable authentication using Ambari for LogSearch (Miklos (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2ff12b7e0ff3ff111f5f8b01e2a232b3109f4ab7]) * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java * ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelperTest.java * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * ambari-server/src/test/python/stacks/2.4/configs/default.json * ambari-server/src/main/java/org/apache/ambari/server/utils/StageUtils.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java * ambari-server/src/test/java/org/apache/ambari/server/utils/StageUtilsTest.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProviderTest.java * ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py * ambari-logsearch/ambari-logsearch-portal/src/main/resources/logsearch.properties * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderHDP22Test.java * ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-properties.xml * ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/web/security/LogsearchExternalServerAuthenticationProvider.java * ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/params.py * ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * ambari-web/app/data/HDP2/site_properties.js * ambari-server/src/test/java/org/apache/ambari/server/controller/BackgroundCustomCommandExecutionTest.java * ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java * ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/templates/logsearch.properties.j2 > Enable authentication using Ambari for LogSearch > > > Key: AMBARI-16719 > URL: https://issues.apache.org/jira/browse/AMBARI-16719 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Don Bosco Durai >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-16719.patch > > > We need to add the following properties to logsearch.properties for enabling > authentication using Ambari. > logsearch.auth.external_auth.enable=true > logsearch.auth.external_auth.host_url=http://AMBARI_HOST:8080 > logsearch.auth.external_auth.login_url=/api/v1/users/$USERNAME/privileges?fields=* > logsearch.roles.allowed=AMBARI.ADMINISTRATOR > Do not replace $USERNAME. This will be replaced by LogSearch code based on > the username > The corresponding changes to LogSearch are already committed. This can be > manually tested by adding the above properties in logsearch custom properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16993) Misc fixes related to slider while enabling interactive query
[ https://issues.apache.org/jira/browse/AMBARI-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311494#comment-15311494 ] Hudson commented on AMBARI-16993: - FAILURE: Integrated in Ambari-trunk-Commit #4982 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4982/]) AMBARI-16993. Misc fixes related to slider while enabling interactive (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f6cd388f221132828302269b50159c9d8475f1ed]) * ambari-web/app/mixins/main/service/configs/component_actions_by_configs.js * ambari-web/app/controllers/wizard/step7/assign_master_controller.js * ambari-web/test/controllers/wizard/step7/assign_master_controller_test.js > Misc fixes related to slider while enabling interactive query > -- > > Key: AMBARI-16993 > URL: https://issues.apache.org/jira/browse/AMBARI-16993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16993.patch > > > *Scenario 1:* > # Install a Ambari-2.2.2 cluster with hive service > # Upgrade to Ambari-2.4.0 > # Enable interactive query. A popup asking to install slider service first > will be shown. Also recommendations for enable interactive query are shown in > the bg > # Dismiss the popup. This again disables interactive query > *Actual behavior:* Recommendations for enabled interactive query remains > *Expected behavior:* Since interactive query is again disabled, > recommendations for enabled interactive query should go away. > *Scenario 2:* > # Install a 3 host Ambari-2.4.0 cluster with hive service. Install slider > client on 2 out of 3 hosts. > # Enable interactive query. Select a host on which slider client is absent > for HS2 interactive. > # Save configurations > *Actual behavior:* Install components request has tasks to installs Slider > client on all 3 hosts > *Expected behavior:* Install components request should install Slider client > only on 1 host (HS2 interactive host) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[ https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311493#comment-15311493 ] Hudson commented on AMBARI-16992: - FAILURE: Integrated in Ambari-trunk-Commit #4982 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4982/]) AMBARI-16992: Recommend hawq_rm_nvcore_limit_perseg in HAWQ service (bhuvnesh2703: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b4df6da51164b71543c764eb8e94cf7fa74da8ce]) * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/service_advisor.py * ambari-server/src/test/python/stacks/2.3/HAWQ/test_service_advisor.py * ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py > Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor > - > > Key: AMBARI-16992 > URL: https://issues.apache.org/jira/browse/AMBARI-16992 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16992-trunk-orig.patch > > > Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16996) Enabling interactive query in kerberized cluster after re-login results in HS2 interactive installation failure
[
https://issues.apache.org/jira/browse/AMBARI-16996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311495#comment-15311495
]
Hadoop QA commented on AMBARI-16996:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807570/AMBARI-16996.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/7127//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7127//console
This message is automatically generated.
> Enabling interactive query in kerberized cluster after re-login results in
> HS2 interactive installation failure
>
>
> Key: AMBARI-16996
> URL: https://issues.apache.org/jira/browse/AMBARI-16996
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16996.patch
>
>
> *Steps to Reproduce:*
> # Install a cluster with hive
> # Kerberize the cluster
> # Log out of the cluster
> # Log in back to the cluster
> # Enable interactive query for hive service.
> # Save configurations for Hive service
> *Expected Result*: On saving configurations, HS2 interactive and other
> dependencies are installed and started successfully
> *Actual Result*: On saving configurations, HS2 interactive install task fails
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[
https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311500#comment-15311500
]
Hadoop QA commented on AMBARI-16992:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807519/AMBARI-16992-trunk-orig.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7129//console
This message is automatically generated.
> Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
> -
>
> Key: AMBARI-16992
> URL: https://issues.apache.org/jira/browse/AMBARI-16992
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16992-trunk-orig.patch
>
>
> Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16859) Kafka dashboards for Grafana
[ https://issues.apache.org/jira/browse/AMBARI-16859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-16859: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4. > Kafka dashboards for Grafana > > > Key: AMBARI-16859 > URL: https://issues.apache.org/jira/browse/AMBARI-16859 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao > Fix For: 2.4.0 > > Attachments: AMBARI-16859.patch > > > Add 3 dashboards to Grafana > - Kafka Home > - Kafka Hosts (Templatized) > - Kafka Topics (Templatized per Topic) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16933) VDF should use package-version for the os, not the release
[
https://issues.apache.org/jira/browse/AMBARI-16933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310922#comment-15310922
]
Hudson commented on AMBARI-16933:
-
FAILURE: Integrated in Ambari-trunk-Commit #4979 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4979/])
AMBARI-16933. VDF should use package-version for the os, not the release
(ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7033b1c5490a61756727a517fd4a02ecce0c11d9])
*
ambari-server/src/main/java/org/apache/ambari/server/state/repository/VersionDefinitionXml.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/stack/RepositoryXml.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/repository/VersionDefinitionTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/repository/Release.java
* ambari-server/src/test/resources/hbase_version_test.xml
> VDF should use package-version for the os, not the release
> --
>
> Key: AMBARI-16933
> URL: https://issues.apache.org/jira/browse/AMBARI-16933
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
> Fix For: 2.4.0
>
> Attachments: AMBARI-16933.patch
>
>
> The aggregated VDF skips package-version as it is defined in the {{release}}
> element. This is incorrect as it implies that information is consistent for
> all repositories in the VDF. The element has been moved, so code needs to
> account for that when formulating commands to the agent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16969) Provide ability in AMS to filter tracked metrics through a whitelist metic file.
[ https://issues.apache.org/jira/browse/AMBARI-16969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310920#comment-15310920 ] Hudson commented on AMBARI-16969: - FAILURE: Integrated in Ambari-trunk-Commit #4979 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4979/]) AMBARI-16969 : Provide ability in AMS to filter tracked metrics through (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5027ab38fffe53eccfc1032ae9e577df7af2cca8]) * ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java * ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/AggregatorUtils.java * ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java * ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java > Provide ability in AMS to filter tracked metrics through a whitelist metic > file. > > > Key: AMBARI-16969 > URL: https://issues.apache.org/jira/browse/AMBARI-16969 > Project: Ambari > Issue Type: Task >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Attachments: AMBARI-16969-trunk.patch, AMBARI-16969.patch > > > The file should contain a list of metrics that will be the only metrics > stored and aggregated in AMS. > Config to use for specifying metric file. > ams-site : timeline.metrics.whitelist.file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16971) Stack VDF should ignore unsupported OS
[ https://issues.apache.org/jira/browse/AMBARI-16971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310921#comment-15310921 ] Hudson commented on AMBARI-16971: - FAILURE: Integrated in Ambari-trunk-Commit #4979 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4979/]) AMBARI-16971. Stack VDF should ignore unsupported OS (ncole) (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=99a615566dc36c1b54e6c13a268149e49a952b50]) * ambari-server/src/main/java/org/apache/ambari/server/state/stack/LatestRepoCallable.java * ambari-server/src/test/resources/stacks/HDP/2.2.0/repos/version-2.2.0.4-124-suse11.xml * ambari-server/src/test/resources/stacks/HDP/2.2.0/repos/hdp.json * ambari-server/src/main/java/org/apache/ambari/server/state/stack/OsFamily.java * ambari-common/src/main/python/ambari_commons/resources/os_family.json * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProviderTest.java > Stack VDF should ignore unsupported OS > -- > > Key: AMBARI-16971 > URL: https://issues.apache.org/jira/browse/AMBARI-16971 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole > Fix For: 2.4.0 > > Attachments: AMBARI-16971.patch > > > Stack VDF loaded via hdp_urlinfo.json may contain OS families that are not > supported by the stack. They should not be included in the merged Version > Definition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16970) Update derivation of hawq_rm_memory_limit_perseg
[ https://issues.apache.org/jira/browse/AMBARI-16970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16970: Resolution: Fixed Assignee: bhuvnesh chaudhary Fix Version/s: 2.4.0 Status: Resolved (was: Patch Available) > Update derivation of hawq_rm_memory_limit_perseg > > > Key: AMBARI-16970 > URL: https://issues.apache.org/jira/browse/AMBARI-16970 > Project: Ambari > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16970-1.patch, AMBARI-16970.patch > > > Update derivation of hawq_rm_memory_limit_perseg. It should be calculated > based on vm.overcommit_ratio, vm.overcommit_memory and the available system > memory. It should also have a default value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16991) Fix metric sink
[ https://issues.apache.org/jira/browse/AMBARI-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-16991: Status: Patch Available (was: In Progress) > Fix metric sink > --- > > Key: AMBARI-16991 > URL: https://issues.apache.org/jira/browse/AMBARI-16991 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-16991.patch > > > After a recent change the AbstractTimelineMetricsSink class has an abstract > function called getZookeeperQuorum(). If the extending class is returning > null, then the sink is not working (neither does it if it returns a valid > zookeeper connection string). Fixed the first issue, now it is working > without a zookeeper connect string. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16990) [Grafana] Add HDFS - Users dashboard
[ https://issues.apache.org/jira/browse/AMBARI-16990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-16990: - Attachment: AMBARI-16990.patch > [Grafana] Add HDFS - Users dashboard > > > Key: AMBARI-16990 > URL: https://issues.apache.org/jira/browse/AMBARI-16990 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao > Fix For: 2.4.0 > > Attachments: AMBARI-16990.patch > > > Create HDFS - Users templatized dashboard to visualize call queue metrics on > a per user level for Grafana. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16986) Required empty config is present after Upgrade from 2.1.2.1 to 2.4.0.0 for HIVE and HBASE
[
https://issues.apache.org/jira/browse/AMBARI-16986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310995#comment-15310995
]
Hadoop QA commented on AMBARI-16986:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807450/AMBARI-16986.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
org.apache.ambari.server.stack.StackManagerTest
org.apache.ambari.server.stack.StackManagerMiscTest
org.apache.ambari.server.controller.internal.HostResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7117//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7117//console
This message is automatically generated.
> Required empty config is present after Upgrade from 2.1.2.1 to 2.4.0.0 for
> HIVE and HBASE
> -
>
> Key: AMBARI-16986
> URL: https://issues.apache.org/jira/browse/AMBARI-16986
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16986.patch
>
>
> STR:
> 1) Install old version - 2.1.1
> 2) Enable Mit security
> 3)Make upgrade
> 4)Add smartSense
> Actual results: Required empty config is present after Upgrade from 2.1.2.1
> to 2.4.0.0 for HIVE and HBASE
> Screenshots were attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16977) VDF: couple UI bugs in Install Wiz
[ https://issues.apache.org/jira/browse/AMBARI-16977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-16977: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 e2dd1261e99bc71306ad91aa7b1e75ce144af0bc > VDF: couple UI bugs in Install Wiz > -- > > Key: AMBARI-16977 > URL: https://issues.apache.org/jira/browse/AMBARI-16977 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, amvari-me >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-16977.v0.patch > > > Fix bugs in the case that public repo is unavailable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16990) [Grafana] Add HDFS - Users dashboard
[ https://issues.apache.org/jira/browse/AMBARI-16990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-16990: - Issue Type: Task (was: Bug) > [Grafana] Add HDFS - Users dashboard > > > Key: AMBARI-16990 > URL: https://issues.apache.org/jira/browse/AMBARI-16990 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao > Fix For: 2.4.0 > > Attachments: AMBARI-16990.patch > > > Create HDFS - Users templatized dashboard to visualize call queue metrics on > a per user level for Grafana. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-14049) Installing cluster with accumulo using blueprints causes accumulo tserver startup failure
[ https://issues.apache.org/jira/browse/AMBARI-14049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311031#comment-15311031 ] Jack Lauritsen commented on AMBARI-14049: - Any progress on this? > Installing cluster with accumulo using blueprints causes accumulo tserver > startup failure > - > > Key: AMBARI-14049 > URL: https://issues.apache.org/jira/browse/AMBARI-14049 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.1.2 > Environment: CentOS 6 >Reporter: Jasbir Dhillon >Priority: Critical > > Installing accumulo on a cluster using blueprints causes accumulo tserver > startup failure. > We have three host_groups. > Host_group_1 consists of the components: PIG, KAFKA_BROKER, HISTORYSERVER, > OOZIE_CLIENT, NAMENODE, HCAT, METRICS_MONITOR, AMBARI_SERVER, > ACCUMULO_MASTER, APP_TIMELINE_SERVER, ACCUMULO_MONITOR, HIVE_CLIENT, > HDFS_CLIENT, METRICS_COLLECTOR, FLUME_HANDLER, DATANODE, WEBHCAT_SERVER, > ZOOKEEPER_SERVER, ZOOKEEPER_CLIENT, HIVE_SERVER, OOZIE_SERVER, TEZ_CLIENT, > HIVE_METASTORE, ACCUMULO_TRACER, YARN_CLIENT, ACCUMULO_GC, MAPREDUCE2_CLIENT, > MYSQL_SERVER, ACCUMULO_CLIENT > Host_group_2 consists of the components: ZOOKEEPER_SERVER, NODEMANAGER, > METRICS_MONITOR, SECONDARY_NAMENODE, DATANODE, ACCUMULO_TSERVER. > Host_group_3 consists of the components: ZOOKEEPER_SERVER, NODEMANAGER, > METRICS_MONITOR, DATANODE, ACCUMULO_TSERVER > The accumulo tservers fail due to the following error. The accumulo tserver > start up task should wait for the namenode to start up which is running on > host group 1. I tested the above configuration without blueprints and it > works fine as host group 2 and host group 3 wait for tasks on host group 1 to > complete prior to starting up the components. > 2015-11-24 18:59:05,807 [zookeeper.ZooUtil] ERROR: Problem reading instance > id out of hdfs at hdfs:// name>:8020/apps/accumulo/data/instance_id > java.net.ConnectException: Call From / > to :8020 failed on connection exception: > java.net.ConnectException: Connection refused; For more details see: > http://wiki.apache.org/hadoop/ConnectionRefused > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at org.apache.hadoop.net.NetUtils.wrapWithMessage(NetUtils.java:792) > at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:732) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-16821) Improve TimelineMetricsCache eviction/flush logic using a cache library
[
https://issues.apache.org/jira/browse/AMBARI-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley reopened AMBARI-16821:
--
Re-opening due to
{code}
2016-06-01 18:23:52,664 INFO - *** Check database
started ***
2016-06-01 18:23:56,229 ERROR - Unexpected error, database check failed
java.lang.NoSuchMethodError:
com.google.common.collect.Sets.newConcurrentHashSet()Ljava/util/Set;
at
org.apache.ambari.server.state.services.MetricsRetrievalService.(MetricsRetrievalService.java:138)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:374)
at
org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:544)
at
org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:374)
at
org.apache.ambari.server.checks.DatabaseConsistencyChecker$CheckHelperControllerModule.configure(DatabaseConsistencyChecker.java:66)
at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
at com.google.inject.spi.Elements.getElements(Elements.java:101)
at
com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
at
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
at com.google.inject.Guice.createInjector(Guice.java:95)
at com.google.inject.Guice.createInjector(Guice.java:72)
at com.google.inject.Guice.createInjector(Guice.java:62)
at
org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:102)
{code}
{code}
commit 8d30f1a4d1da10225f66ecc02f757b4db904c5c0 (HEAD -> trunk, origin/trunk,
origin/HEAD)
Author: Jonathan Hurley
Date: Wed Jun 1 16:31:26 2016 -0400
Revert "AMBARI-16821 Improve TimelineMetricsCache eviction/flush logic
using a cache library (dsen)"
This reverts commit bef695d3fc44528d94a0fa60a3f1b6c5db51f02d.
{code}
{code}
commit 12b1a0c803335ec60ca5fce51cd31ea8478be795 (HEAD -> branch-2.4,
origin/branch-2.4)
Author: Jonathan Hurley
Date: Wed Jun 1 16:34:05 2016 -0400
Revert "AMBARI-16821 Improve TimelineMetricsCache eviction/flush logic
using a cache library (dsen)"
This reverts commit ecaef41426ff67811ac4b2f5c618fb651286d160.
{code}
> Improve TimelineMetricsCache eviction/flush logic using a cache library
> ---
>
> Key: AMBARI-16821
> URL: https://issues.apache.org/jira/browse/AMBARI-16821
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.4.0
>
> Attachments: AMBARI-16821_1.patch, AMBARI-16821_2.patch,
> AMBARI-16821_3-trunk.patch, AMBARI-16821_4-trunk.patch, BUG-55307.patch
>
>
> The TimelineMetricsCache implementation in the metrics sink side is currently
> a ConcurrentSkipListMap. It is better to use pre built cache libraries like
> Guava that offer more support.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16990) [Grafana] Add HDFS - Users dashboard
[ https://issues.apache.org/jira/browse/AMBARI-16990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-16990: - Status: Patch Available (was: Open) > [Grafana] Add HDFS - Users dashboard > > > Key: AMBARI-16990 > URL: https://issues.apache.org/jira/browse/AMBARI-16990 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao > Fix For: 2.4.0 > > Attachments: AMBARI-16990.patch > > > Create HDFS - Users templatized dashboard to visualize call queue metrics on > a per user level for Grafana. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16972) Strange behavior of Add Version functionality
[ https://issues.apache.org/jira/browse/AMBARI-16972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-16972: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 7d1223232221294b692e2ee1ac795c2a5b4e26f6 > Strange behavior of Add Version functionality > - > > Key: AMBARI-16972 > URL: https://issues.apache.org/jira/browse/AMBARI-16972 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-16972.v0.patch > > > STR: > 1. Install cluster. > 2. Go to Manage Ambari > Versions > Register Version. > 3. Click Add Version for HDP-2.5, type URL for some version (for example > http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/2.x/BUILDS/2.5.0.0-427/HDP-2.5.0.0-427.xml) > and click Add Version Info. > As a result version from VDF file will be loaded as selected, but if you open > select box you will see current installed version and HDP-2.5 (Default > Version Definition) instead of version, that you typed. If you will add > version with the same VDF file, it will be added. But what is HDP-2.5 > (Default Version Definition) and why it appears in combo box after first > version adding. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16985) "Wizard in progress" bar should not look clickable
[
https://issues.apache.org/jira/browse/AMBARI-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311021#comment-15311021
]
Hadoop QA commented on AMBARI-16985:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807428/AMBARI-16985.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/7118//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7118//console
This message is automatically generated.
> "Wizard in progress" bar should not look clickable
> --
>
> Key: AMBARI-16985
> URL: https://issues.apache.org/jira/browse/AMBARI-16985
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-16985.patch
>
>
> Change cursor type to default on " is in progress" bar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16986) Required empty config is present after Upgrade from 2.1.2.1 to 2.4.0.0 for HIVE and HBASE
[ https://issues.apache.org/jira/browse/AMBARI-16986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-16986: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > Required empty config is present after Upgrade from 2.1.2.1 to 2.4.0.0 for > HIVE and HBASE > - > > Key: AMBARI-16986 > URL: https://issues.apache.org/jira/browse/AMBARI-16986 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16986.patch > > > STR: > 1) Install old version - 2.1.1 > 2) Enable Mit security > 3)Make upgrade > 4)Add smartSense > Actual results: Required empty config is present after Upgrade from 2.1.2.1 > to 2.4.0.0 for HIVE and HBASE > Screenshots were attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16990) [Grafana] Add HDFS - Users dashboard
[ https://issues.apache.org/jira/browse/AMBARI-16990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-16990: - Attachment: (was: AMBARI-16990.patch) > [Grafana] Add HDFS - Users dashboard > > > Key: AMBARI-16990 > URL: https://issues.apache.org/jira/browse/AMBARI-16990 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao > Fix For: 2.4.0 > > > Create HDFS - Users templatized dashboard to visualize call queue metrics on > a per user level for Grafana. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16672) clean up import * for OOZIE service
[ https://issues.apache.org/jira/browse/AMBARI-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16672: --- Status: Patch Available (was: Open) > clean up import * for OOZIE service > --- > > Key: AMBARI-16672 > URL: https://issues.apache.org/jira/browse/AMBARI-16672 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16672.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16672) clean up import * for OOZIE service
[ https://issues.apache.org/jira/browse/AMBARI-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16672: --- Status: Open (was: Patch Available) > clean up import * for OOZIE service > --- > > Key: AMBARI-16672 > URL: https://issues.apache.org/jira/browse/AMBARI-16672 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16672.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16672) clean up import * for OOZIE service
[ https://issues.apache.org/jira/browse/AMBARI-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16672: --- Attachment: (was: AMBARI-16672.patch) > clean up import * for OOZIE service > --- > > Key: AMBARI-16672 > URL: https://issues.apache.org/jira/browse/AMBARI-16672 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16672.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16672) clean up import * for OOZIE service
[ https://issues.apache.org/jira/browse/AMBARI-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16672: --- Attachment: AMBARI-16672.patch > clean up import * for OOZIE service > --- > > Key: AMBARI-16672 > URL: https://issues.apache.org/jira/browse/AMBARI-16672 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16672.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16272) Ambari Upgrade shouldn't automatically add stack configs
[
https://issues.apache.org/jira/browse/AMBARI-16272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311069#comment-15311069
]
Tim Thorpe commented on AMBARI-16272:
-
This seems to have broken the StackManager tests
Running org.apache.ambari.server.stack.StackManagerTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.884 sec <<<
FAILURE! - in org.apache.ambari.server.stack.StackManag
org.apache.ambari.server.stack.StackManagerTest Time elapsed: 0.883 sec <<<
ERROR!
org.apache.ambari.server.AmbariException: File
/home/tim/dev/workspaces/stackext/ambari/ambari-server/target/test-classes/stacks/HDP/ration/hdfs-site.xml
didn't pass the validation. Error message is : cvc-complex-type.2.4.a: Invalid
content was found starting with e'{display-name, filename, deleted,
on-ambari-upgrade, on-stack-upgrade, property-type, value-attributes,
depends-on, property_depende
at
org.apache.ambari.server.stack.StackManagerTest.createTestStackManager(StackManagerTest.java:123)
at
org.apache.ambari.server.stack.StackManagerTest.createTestStackManager(StackManagerTest.java:94)
at
org.apache.ambari.server.stack.StackManagerTest.initStack(StackManagerTest.java:89)
> Ambari Upgrade shouldn't automatically add stack configs
>
>
> Key: AMBARI-16272
> URL: https://issues.apache.org/jira/browse/AMBARI-16272
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-16272.patch
>
>
> Today, Ambari Upgrade will automatically add stack configs.
> However, it also causes problems when default properties or properties with
> default value such as "localhost" end up being added.
> This led to many bugs. E.g., cluster with NameNode HA shouldn't automatically
> add dfs.namenode.secondary.http-address
> Properties should be explicitly added during RU/EU config packs instead of
> relying on annotating them with.
> {code}
> DONT_ADD_ON_UPGRADE
> {code}
> This logic today will even add new config types. E.g., add ranger-env even
> though Ranger is not installed. If the customer then upgrades the stack from
> HDP 2.2 to 2.3, and then adds Ranger, they can get the wrong configs.
> If we change this behavior, it's good to do so in a major release such as 2.4
> We add required xml tags to properties:
> # If it's a new property from stack X to X+1, we don't want it to be added
> automatically added. If we do want to add it, we should annotate it with
> "ADD_ON_UPGRADE"
> # Similar to above, but handle "DELETE_ON_UPGRADE"
> # Similar to above, but handle "CHANGE_ON_UPGRADE" to forcefully set to a new
> value if it exists
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16965) Exception while detecting JMX protocol for HISTORYSERVER
[ https://issues.apache.org/jira/browse/AMBARI-16965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-16965: - Attachment: AMBARI-16965.patch > Exception while detecting JMX protocol for HISTORYSERVER > > > Key: AMBARI-16965 > URL: https://issues.apache.org/jira/browse/AMBARI-16965 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-16965.patch > > > Secured cluster with HDP 2.5. (also installed Ranger but I'm not sure that it > influences on this) > I see a lot of exception in ambari server logs: > > > > 25 May 2016 16:50:16,982 INFO [pool-7-thread-26] > AbstractProviderModule:1184 - Defaulting JMX to HTTP protocol for for > clusterName = c1, componentName = HISTORYSERVERHISTORYSERVER > 25 May 2016 16:50:23,617 INFO [pool-7-thread-28] > AbstractProviderModule:1182 - Exception while detecting JMX protocol for > clusterName = c1, componentName = HISTORYSERVER > java.lang.NullPointerException > at > org.apache.ambari.server.controller.internal.AbstractProviderModule.getJMXProtocolString(AbstractProviderModule.java:1205) > at > org.apache.ambari.server.controller.internal.AbstractProviderModule.getJMXProtocol(AbstractProviderModule.java:1175) > at > org.apache.ambari.server.controller.jmx.JMXPropertyProvider.getJMXProtocol(JMXPropertyProvider.java:378) > at > org.apache.ambari.server.controller.jmx.JMXPropertyProvider.populateResource(JMXPropertyProvider.java:194) > at > org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:185) > at > org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:183) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > > It appears every few seconds -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16965) Exception while detecting JMX protocol for HISTORYSERVER
[ https://issues.apache.org/jira/browse/AMBARI-16965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-16965: - Attachment: (was: AMBARI-16965.patch) > Exception while detecting JMX protocol for HISTORYSERVER > > > Key: AMBARI-16965 > URL: https://issues.apache.org/jira/browse/AMBARI-16965 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-16965.patch > > > Secured cluster with HDP 2.5. (also installed Ranger but I'm not sure that it > influences on this) > I see a lot of exception in ambari server logs: > > > > 25 May 2016 16:50:16,982 INFO [pool-7-thread-26] > AbstractProviderModule:1184 - Defaulting JMX to HTTP protocol for for > clusterName = c1, componentName = HISTORYSERVERHISTORYSERVER > 25 May 2016 16:50:23,617 INFO [pool-7-thread-28] > AbstractProviderModule:1182 - Exception while detecting JMX protocol for > clusterName = c1, componentName = HISTORYSERVER > java.lang.NullPointerException > at > org.apache.ambari.server.controller.internal.AbstractProviderModule.getJMXProtocolString(AbstractProviderModule.java:1205) > at > org.apache.ambari.server.controller.internal.AbstractProviderModule.getJMXProtocol(AbstractProviderModule.java:1175) > at > org.apache.ambari.server.controller.jmx.JMXPropertyProvider.getJMXProtocol(JMXPropertyProvider.java:378) > at > org.apache.ambari.server.controller.jmx.JMXPropertyProvider.populateResource(JMXPropertyProvider.java:194) > at > org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:185) > at > org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:183) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > > It appears every few seconds -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16988) Invalid recommended value for storm.local.dir (/usr/hdp/hadoop/storm)
[
https://issues.apache.org/jira/browse/AMBARI-16988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310690#comment-15310690
]
Antonenko Alexander commented on AMBARI-16988:
--
28524 tests complete (24 seconds)
154 tests pending
rat check passed
> Invalid recommended value for storm.local.dir (/usr/hdp/hadoop/storm)
> -
>
> Key: AMBARI-16988
> URL: https://issues.apache.org/jira/browse/AMBARI-16988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16988.patch
>
>
> Ambari was installed on the host with the following mounts (Ubuntu 16,
> HDP-2.5):
> {noformat}
> root@u16-ambari-ubuntu-xenial-01:~# df -h
> Filesystem Size Used Avail Use% Mounted on
> udev4.8G 0 4.8G 0% /dev
> tmpfs 981M 15M 967M 2% /run
> /dev/sda1 9.7G 3.4G 6.3G 35% /
> tmpfs 4.8G 4.0K 4.8G 1% /dev/shm
> tmpfs 5.0M 0 5.0M 0% /run/lock
> tmpfs 4.8G 0 4.8G 0% /sys/fs/cgroup
> tmpfs 100K 0 100K 0% /run/lxcfs/controllers
> /dev/sdc135G 1.9G 31G 6% /usr/hdp
> tmpfs 981M 0 981M 0% /run/user/1000
> {noformat}
> The recommended value was:
> {noformat}
> "storm.local.dir" : "/usr/hdp/hadoop/storm"
> {noformat}
> hdp-select expects that folder name inside of /usr/hdp correspond to version
> numbers.
> {noformat}
> root@u16-ambari-ubuntu-xenial-01:~# hdp-select versions
> Traceback (most recent call last):
> File "/usr/bin/hdp-select", line 391, in
> printVersions()
> File "/usr/bin/hdp-select", line 248, in printVersions
> result[tuple(map(int, versionRegex.split(f)))] = f
> ValueError: invalid literal for int() with base 10: 'hadoop'
> root@u16-ambari-ubuntu-xenial-01:~# ll /usr/hdp
> total 36
> drwxr-xr-x 6 root root 4096 May 27 10:53 ./
> drwxr-xr-x 12 root root 4096 May 26 17:19 ../
> drwxr-xr-x 17 root root 4096 May 27 10:53 2.5.0.0-568/
> drwxr-xr-x 2 root root 4096 May 27 10:44 current/
> drwxr-xr-x 3 root root 4096 May 27 10:53 hadoop/
> drwx-- 2 root root 16384 May 26 17:02 lost+found/
> {noformat}
> It's a brittle part of hdp-select and probably should be fixed.
> Anyway Ambari shouldn't recommend /usr/hdp/hadoop/storm folder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (AMBARI-16911) Enable HS2 Interactive > Select Hosts does not have Cancel and close
[ https://issues.apache.org/jira/browse/AMBARI-16911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reopened AMBARI-16911: -- Assignee: Antonenko Alexander (was: Jaimin D Jetly) > Enable HS2 Interactive > Select Hosts does not have Cancel and close > > > Key: AMBARI-16911 > URL: https://issues.apache.org/jira/browse/AMBARI-16911 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: ambari-2.4.0 >Reporter: Shraddha Sumit >Assignee: Antonenko Alexander >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-16911.patch, before.png, now-1.png, now-2.png > > > Deploy cluster using ambari with Hive and slider > Enable HS2 Interactive > Expected: Select Hosts (Assign masters) page should have Cancel button and > 'X' icon to close or cancel this action. > Actual: On Select Hosts (Assign masters) page there is no 'Cancel' button or > 'X' icon for user to cancel this action. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16719) Enable authentication using Ambari for LogSearch
[
https://issues.apache.org/jira/browse/AMBARI-16719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311282#comment-15311282
]
Olivér Szabó commented on AMBARI-16719:
---
committed to branch-2.4:
{code:java}
commit e64a347131f3e088437902e9cfca324540566b18
Author: Miklos Gergely
Date: Thu Jun 2 00:21:56 2016 +0200
AMBARI-16719. Enable authentication using Ambari for LogSearch (Miklos
Gergely via oleewere)
{code}
committed to trunk:
{code:java}
commit 2ff12b7e0ff3ff111f5f8b01e2a232b3109f4ab7
Author: Miklos Gergely
Date: Thu Jun 2 00:21:56 2016 +0200
AMBARI-16719. Enable authentication using Ambari for LogSearch (Miklos
Gergely via oleewere)
{code}
> Enable authentication using Ambari for LogSearch
>
>
> Key: AMBARI-16719
> URL: https://issues.apache.org/jira/browse/AMBARI-16719
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Don Bosco Durai
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-16719.patch
>
>
> We need to add the following properties to logsearch.properties for enabling
> authentication using Ambari.
> logsearch.auth.external_auth.enable=true
> logsearch.auth.external_auth.host_url=http://AMBARI_HOST:8080
> logsearch.auth.external_auth.login_url=/api/v1/users/$USERNAME/privileges?fields=*
> logsearch.roles.allowed=AMBARI.ADMINISTRATOR
> Do not replace $USERNAME. This will be replaced by LogSearch code based on
> the username
> The corresponding changes to LogSearch are already committed. This can be
> manually tested by adding the above properties in logsearch custom properties
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16719) Enable authentication using Ambari for LogSearch
[ https://issues.apache.org/jira/browse/AMBARI-16719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-16719: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Enable authentication using Ambari for LogSearch > > > Key: AMBARI-16719 > URL: https://issues.apache.org/jira/browse/AMBARI-16719 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Don Bosco Durai >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-16719.patch > > > We need to add the following properties to logsearch.properties for enabling > authentication using Ambari. > logsearch.auth.external_auth.enable=true > logsearch.auth.external_auth.host_url=http://AMBARI_HOST:8080 > logsearch.auth.external_auth.login_url=/api/v1/users/$USERNAME/privileges?fields=* > logsearch.roles.allowed=AMBARI.ADMINISTRATOR > Do not replace $USERNAME. This will be replaced by LogSearch code based on > the username > The corresponding changes to LogSearch are already committed. This can be > manually tested by adding the above properties in logsearch custom properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16994) Ambari Server Upgrade should always update stack_features and stack_tools config properties
Jayush Luniya created AMBARI-16994: -- Summary: Ambari Server Upgrade should always update stack_features and stack_tools config properties Key: AMBARI-16994 URL: https://issues.apache.org/jira/browse/AMBARI-16994 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: 2.4.0 In Ambari 2.4.0.0, we will be added stack_features and stack_tools config properties. On upgrade to Ambari 2.4.0.0 these config properties will be automatically added because these are new properties. For all future Ambari upgrades above Ambari 2.4+, we should always update these config properties to the latest config property value as defined in the stack. The change here is essentially for future proofing beyond Ambari 2.4.0.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16991) Fix metric sink
[
https://issues.apache.org/jira/browse/AMBARI-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311305#comment-15311305
]
Hadoop QA commented on AMBARI-16991:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807503/AMBARI-16991.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 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
ambari-logsearch/ambari-logsearch-portal
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7122//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7122//console
This message is automatically generated.
> Fix metric sink
> ---
>
> Key: AMBARI-16991
> URL: https://issues.apache.org/jira/browse/AMBARI-16991
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-16991.patch
>
>
> After a recent change the AbstractTimelineMetricsSink class has an abstract
> function called getZookeeperQuorum(). If the extending class is returning
> null, then the sink is not working (neither does it if it returns a valid
> zookeeper connection string). Fixed the first issue, now it is working
> without a zookeeper connect string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16993) Misc fixes related to slider while enabling interactive query
[ https://issues.apache.org/jira/browse/AMBARI-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-16993: Resolution: Fixed Status: Resolved (was: Patch Available) Received +1 on reviewboard. Patch committed to trunk and branch-2.4 > Misc fixes related to slider while enabling interactive query > -- > > Key: AMBARI-16993 > URL: https://issues.apache.org/jira/browse/AMBARI-16993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16993.patch > > > *Scenario 1:* > # Install a Ambari-2.2.2 cluster with hive service > # Upgrade to Ambari-2.4.0 > # Enable interactive query. A popup asking to install slider service first > will be shown. Also recommendations for enable interactive query are shown in > the bg > # Dismiss the popup. This again disables interactive query > *Actual behavior:* Recommendations for enabled interactive query remains > *Expected behavior:* Since interactive query is again disabled, > recommendations for enabled interactive query should go away. > *Scenario 2:* > # Install a 3 host Ambari-2.4.0 cluster with hive service. Install slider > client on 2 out of 3 hosts. > # Enable interactive query. Select a host on which slider client is absent > for HS2 interactive. > # Save configurations > *Actual behavior:* Install components request has tasks to installs Slider > client on all 3 hosts > *Expected behavior:* Install components request should install Slider client > only on 1 host (HS2 interactive host) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16990) [Grafana] Add HDFS - Users dashboard
[
https://issues.apache.org/jira/browse/AMBARI-16990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311253#comment-15311253
]
Hadoop QA commented on AMBARI-16990:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807516/AMBARI-16990.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7121//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7121//console
This message is automatically generated.
> [Grafana] Add HDFS - Users dashboard
>
>
> Key: AMBARI-16990
> URL: https://issues.apache.org/jira/browse/AMBARI-16990
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Prajwal Rao
>Assignee: Prajwal Rao
> Fix For: 2.4.0
>
> Attachments: AMBARI-16990.patch
>
>
> Create HDFS - Users templatized dashboard to visualize call queue metrics on
> a per user level for Grafana.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[ https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary resolved AMBARI-16992. - Resolution: Fixed > Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor > - > > Key: AMBARI-16992 > URL: https://issues.apache.org/jira/browse/AMBARI-16992 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16992-trunk-orig.patch > > > Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[ https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reopened AMBARI-16992: - > Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor > - > > Key: AMBARI-16992 > URL: https://issues.apache.org/jira/browse/AMBARI-16992 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16992-trunk-orig.patch > > > Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16977) VDF: couple UI bugs in Install Wiz
[ https://issues.apache.org/jira/browse/AMBARI-16977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311288#comment-15311288 ] Hudson commented on AMBARI-16977: - FAILURE: Integrated in Ambari-trunk-Commit #4981 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4981/]) AMBARI-16977 VDF: couple UI bugs in Install Wiz (zhewang) (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e2dd1261e99bc71306ad91aa7b1e75ce144af0bc]) * ambari-web/app/templates/wizard/step1.hbs * ambari-web/test/controllers/wizard/step1_test.js * ambari-web/app/controllers/wizard/step1_controller.js * ambari-web/app/styles/application.less * ambari-web/app/messages.js * ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html * ambari-admin/src/main/resources/ui/admin-web/app/styles/main.css > VDF: couple UI bugs in Install Wiz > -- > > Key: AMBARI-16977 > URL: https://issues.apache.org/jira/browse/AMBARI-16977 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, amvari-me >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-16977.v0.patch > > > Fix bugs in the case that public repo is unavailable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16985) "Wizard in progress" bar should not look clickable
[ https://issues.apache.org/jira/browse/AMBARI-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311289#comment-15311289 ] Hudson commented on AMBARI-16985: - FAILURE: Integrated in Ambari-trunk-Commit #4981 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4981/]) AMBARI-16985. "Wizard in progress" bar should not look clickable (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2c51b64c63dc424f35a1849c9b4588a157d13218]) * ambari-web/app/templates/application.hbs * ambari-web/app/controllers/global/wizard_watcher_controller.js > "Wizard in progress" bar should not look clickable > -- > > Key: AMBARI-16985 > URL: https://issues.apache.org/jira/browse/AMBARI-16985 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-16985.patch > > > Change cursor type to default on " is in progress" bar. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16849) clean up import * for YARN service
[ https://issues.apache.org/jira/browse/AMBARI-16849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311290#comment-15311290 ] Hudson commented on AMBARI-16849: - FAILURE: Integrated in Ambari-trunk-Commit #4981 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4981/]) AMBARI-16849: clean up import * for YARN service - add missing import ( (jluniya: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=29f9fa341ff795503ee5b782181179b50180850e]) * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/nodemanager.py > clean up import * for YARN service > -- > > Key: AMBARI-16849 > URL: https://issues.apache.org/jira/browse/AMBARI-16849 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.4.0, 2.2.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16849-2.patch, AMBARI-16849.patch > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for YARN service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16821) Improve TimelineMetricsCache eviction/flush logic using a cache library
[ https://issues.apache.org/jira/browse/AMBARI-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311287#comment-15311287 ] Hudson commented on AMBARI-16821: - FAILURE: Integrated in Ambari-trunk-Commit #4981 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4981/]) Revert "AMBARI-16821 Improve TimelineMetricsCache eviction/flush logic (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8d30f1a4d1da10225f66ecc02f757b4db904c5c0]) * ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/TimelineMetricsCacheTest.java * ambari-server/pom.xml * ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/cache/TimelineMetricsCache.java * ambari-metrics/ambari-metrics-hadoop-sink/src/test/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSinkTest.java * ambari-project/pom.xml * ambari-metrics/ambari-metrics-common/pom.xml > Improve TimelineMetricsCache eviction/flush logic using a cache library > --- > > Key: AMBARI-16821 > URL: https://issues.apache.org/jira/browse/AMBARI-16821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-16821_1.patch, AMBARI-16821_2.patch, > AMBARI-16821_3-trunk.patch, AMBARI-16821_4-trunk.patch, BUG-55307.patch > > > The TimelineMetricsCache implementation in the metrics sink side is currently > a ConcurrentSkipListMap. It is better to use pre built cache libraries like > Guava that offer more support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16972) Strange behavior of Add Version functionality
[ https://issues.apache.org/jira/browse/AMBARI-16972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311292#comment-15311292 ] Hudson commented on AMBARI-16972: - FAILURE: Integrated in Ambari-trunk-Commit #4981 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4981/]) AMBARI-16972 Strange behavior of Add Version functionality (zhewang) (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7d1223232221294b692e2ee1ac795c2a5b4e26f6]) * ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/AddVersionModal.js > Strange behavior of Add Version functionality > - > > Key: AMBARI-16972 > URL: https://issues.apache.org/jira/browse/AMBARI-16972 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-16972.v0.patch > > > STR: > 1. Install cluster. > 2. Go to Manage Ambari > Versions > Register Version. > 3. Click Add Version for HDP-2.5, type URL for some version (for example > http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/2.x/BUILDS/2.5.0.0-427/HDP-2.5.0.0-427.xml) > and click Add Version Info. > As a result version from VDF file will be loaded as selected, but if you open > select box you will see current installed version and HDP-2.5 (Default > Version Definition) instead of version, that you typed. If you will add > version with the same VDF file, it will be added. But what is HDP-2.5 > (Default Version Definition) and why it appears in combo box after first > version adding. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[ https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-16992: -- Status: Patch Available (was: Reopened) > Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor > - > > Key: AMBARI-16992 > URL: https://issues.apache.org/jira/browse/AMBARI-16992 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16992-trunk-orig.patch > > > Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[ https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-16992: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor > - > > Key: AMBARI-16992 > URL: https://issues.apache.org/jira/browse/AMBARI-16992 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16992-trunk-orig.patch, > AMBARI-16992-trunk-v1.patch > > > Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[
https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311683#comment-15311683
]
Matt commented on AMBARI-16992:
---
Committed to trunk:
{code}
commit bd85c28158b8c1bd7dbea13ac25519a2551d917d
Author: Matt
Date: Wed Jun 1 20:34:08 2016 -0700
{code}
Committed to branch-2.4:
{code}
commit 4544d26fc049dcb2f6d712665eab865416f216ba
Author: Matt
Date: Wed Jun 1 20:34:58 2016 -0700
{code}
Marking as resolved.
> Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
> -
>
> Key: AMBARI-16992
> URL: https://issues.apache.org/jira/browse/AMBARI-16992
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16992-trunk-orig.patch,
> AMBARI-16992-trunk-v1.patch
>
>
> Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16961) Deployment via blueprint failing due to Logsearch client install failure
[ https://issues.apache.org/jira/browse/AMBARI-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311619#comment-15311619 ] Hudson commented on AMBARI-16961: - FAILURE: Integrated in Ambari-trunk-Commit #4983 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4983/]) AMBARI-16961. Remove LogSearch dependency from ATLAS (oleewere) (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f3e2768e7a8fbebfc9a234735bc3f7c863c7a7d8]) * ambari-server/src/test/python/stacks/2.5/configs/default.json * ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/metainfo.xml * ambari-server/src/test/python/stacks/2.3/configs/default.json * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/metainfo.xml * ambari-server/src/main/resources/stacks/HDP/2.3/role_command_order.json * ambari-server/src/test/python/stacks/2.3/ATLAS/test_metadata_server.py * ambari-server/src/test/python/stacks/2.4/configs/default.json * ambari-server/src/test/python/stacks/2.3/configs/secure.json * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py * ambari-common/src/main/python/resource_management/libraries/functions/solr_cloud_util.py * ambari-server/src/test/python/stacks/2.5/ATLAS/test_atlas_server.py * ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/setup_logsearch_solr.py * ambari-common/src/main/python/resource_management/libraries/functions/package_conditions.py * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py > Deployment via blueprint failing due to Logsearch client install failure > > > Key: AMBARI-16961 > URL: https://issues.apache.org/jira/browse/AMBARI-16961 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16961.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16890) Updating Ambari configs changes for latest Ranger configs
[
https://issues.apache.org/jira/browse/AMBARI-16890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311620#comment-15311620
]
Hudson commented on AMBARI-16890:
-
FAILURE: Integrated in Ambari-trunk-Commit #4983 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4983/])
AMBARI-16890 Updating Ambari configs changes for latest Ranger configs
(sgunturi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e803e960527c94dcf74b4e81aa836e3e70ac1e06])
* ambari-web/app/data/HDP2.3/site_properties.js
* ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
*
ambari-server/src/main/resources/common-services/RANGER/0.5.0/configuration/ranger-admin-site.xml
*
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/configuration/ranger-kms-audit.xml
*
ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/ranger-admin-site.xml
*
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml
* ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
* ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
*
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml
* ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml
*
ambari-server/src/main/resources/common-services/RANGER/0.4.0/configuration/ranger-site.xml
> Updating Ambari configs changes for latest Ranger configs
> -
>
> Key: AMBARI-16890
> URL: https://issues.apache.org/jira/browse/AMBARI-16890
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16890.1.patch, AMBARI-16890.2.patch,
> AMBARI-16890.patch
>
>
> Changes include:
> # Enable Ranger SSO property as a checkbox
> # Populate query param originalUrl
> # Adding below new properties to ranger-admin-site.xml:
> - ranger.kms.service.user.hdfs – default value "hdfs"
> - ranger.kms.service.user.hive – default value "hive"
> # Updating default value for below properties in latest stack:
> - ranger.ldap.ad.user.searchfilter {code}(sAMAccountName={0}){code}
> - ranger.ldap.user.searchfilter {code}(uid={0}){code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[ https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-16992: -- Attachment: AMBARI-16992-trunk-v1.patch > Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor > - > > Key: AMBARI-16992 > URL: https://issues.apache.org/jira/browse/AMBARI-16992 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16992-trunk-orig.patch, > AMBARI-16992-trunk-v1.patch > > > Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[ https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-16992: -- Issue Type: Improvement (was: Bug) > Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor > - > > Key: AMBARI-16992 > URL: https://issues.apache.org/jira/browse/AMBARI-16992 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.4.0 > > > Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
Matt created AMBARI-16992: - Summary: Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor Key: AMBARI-16992 URL: https://issues.apache.org/jira/browse/AMBARI-16992 Project: Ambari Issue Type: Bug Components: stacks Reporter: Matt Assignee: Matt Priority: Minor Fix For: trunk, 2.4.0 Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16993) Misc fixes related to slider while enabling interactive query
[ https://issues.apache.org/jira/browse/AMBARI-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-16993: Description: *Scenario 1:* # Install a Ambari-2.2.2 cluster with hive service # Upgrade to Ambari-2.4.0 # Enable interactive query. A popup asking to install slider service first will be shown. Also recommendations for enable interactive query are shown in the bg # Dismiss the popup. This again disables interactive query *Actual behavior:* Recommendations for enabled interactive query remains *Expected behavior:* Since interactive query is again disabled, recommendations for enabled interactive query should go away. *Scenario 2:* # Install a 3 host Ambari-2.4.0 cluster with hive service. Install slider client on 2 out of 3 hosts. # Enable interactive query. Select a host on which slider client is absent for HS2 interactive. # Save configurations *Actual behavior:* Install components request has tasks to installs Slider client on all 3 hosts *Expected behavior:* Install components request should install Slider client only on 1 host (HS2 interactive host) > Misc fixes related to slider while enabling interactive query > -- > > Key: AMBARI-16993 > URL: https://issues.apache.org/jira/browse/AMBARI-16993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > > *Scenario 1:* > # Install a Ambari-2.2.2 cluster with hive service > # Upgrade to Ambari-2.4.0 > # Enable interactive query. A popup asking to install slider service first > will be shown. Also recommendations for enable interactive query are shown in > the bg > # Dismiss the popup. This again disables interactive query > *Actual behavior:* Recommendations for enabled interactive query remains > *Expected behavior:* Since interactive query is again disabled, > recommendations for enabled interactive query should go away. > *Scenario 2:* > # Install a 3 host Ambari-2.4.0 cluster with hive service. Install slider > client on 2 out of 3 hosts. > # Enable interactive query. Select a host on which slider client is absent > for HS2 interactive. > # Save configurations > *Actual behavior:* Install components request has tasks to installs Slider > client on all 3 hosts > *Expected behavior:* Install components request should install Slider client > only on 1 host (HS2 interactive host) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16797) clean up import * for SPARK service
[ https://issues.apache.org/jira/browse/AMBARI-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16797: --- Status: Open (was: Patch Available) > clean up import * for SPARK service > --- > > Key: AMBARI-16797 > URL: https://issues.apache.org/jira/browse/AMBARI-16797 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16797.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16993) Misc fixes related to slider while enabling interactive query
[ https://issues.apache.org/jira/browse/AMBARI-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-16993: Attachment: AMBARI-16993.patch > Misc fixes related to slider while enabling interactive query > -- > > Key: AMBARI-16993 > URL: https://issues.apache.org/jira/browse/AMBARI-16993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16993.patch > > > *Scenario 1:* > # Install a Ambari-2.2.2 cluster with hive service > # Upgrade to Ambari-2.4.0 > # Enable interactive query. A popup asking to install slider service first > will be shown. Also recommendations for enable interactive query are shown in > the bg > # Dismiss the popup. This again disables interactive query > *Actual behavior:* Recommendations for enabled interactive query remains > *Expected behavior:* Since interactive query is again disabled, > recommendations for enabled interactive query should go away. > *Scenario 2:* > # Install a 3 host Ambari-2.4.0 cluster with hive service. Install slider > client on 2 out of 3 hosts. > # Enable interactive query. Select a host on which slider client is absent > for HS2 interactive. > # Save configurations > *Actual behavior:* Install components request has tasks to installs Slider > client on all 3 hosts > *Expected behavior:* Install components request should install Slider client > only on 1 host (HS2 interactive host) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16719) Enable authentication using Ambari for LogSearch
[ https://issues.apache.org/jira/browse/AMBARI-16719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-16719: Attachment: AMBARI-16719.patch > Enable authentication using Ambari for LogSearch > > > Key: AMBARI-16719 > URL: https://issues.apache.org/jira/browse/AMBARI-16719 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Don Bosco Durai >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-16719.patch > > > We need to add the following properties to logsearch.properties for enabling > authentication using Ambari. > logsearch.auth.external_auth.enable=true > logsearch.auth.external_auth.host_url=http://AMBARI_HOST:8080 > logsearch.auth.external_auth.login_url=/api/v1/users/$USERNAME/privileges?fields=* > logsearch.roles.allowed=AMBARI.ADMINISTRATOR > Do not replace $USERNAME. This will be replaced by LogSearch code based on > the username > The corresponding changes to LogSearch are already committed. This can be > manually tested by adding the above properties in logsearch custom properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16719) Enable authentication using Ambari for LogSearch
[ https://issues.apache.org/jira/browse/AMBARI-16719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-16719: Attachment: (was: AMBARI-16719.patch) > Enable authentication using Ambari for LogSearch > > > Key: AMBARI-16719 > URL: https://issues.apache.org/jira/browse/AMBARI-16719 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Don Bosco Durai >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-16719.patch > > > We need to add the following properties to logsearch.properties for enabling > authentication using Ambari. > logsearch.auth.external_auth.enable=true > logsearch.auth.external_auth.host_url=http://AMBARI_HOST:8080 > logsearch.auth.external_auth.login_url=/api/v1/users/$USERNAME/privileges?fields=* > logsearch.roles.allowed=AMBARI.ADMINISTRATOR > Do not replace $USERNAME. This will be replaced by LogSearch code based on > the username > The corresponding changes to LogSearch are already committed. This can be > manually tested by adding the above properties in logsearch custom properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16821) Improve TimelineMetricsCache eviction/flush logic using a cache library
[
https://issues.apache.org/jira/browse/AMBARI-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311100#comment-15311100
]
Jonathan Hurley commented on AMBARI-16821:
--
Looks like the problem is that the classes are being shipped with
{{ambari-metrics-common-2.4.0.0.5228.jar}} and are not being shaded.
{code}
[root@c6401 ambari-server]# pwd
/usr/lib/ambari-server
[root@c6401 ambari-server]# ls -l guava*
-rwxrwxrwx 1 root root 2225441 Jun 1 20:22 guava-16.0.jar
{code}
{code}
[root@c6401 ambari-server]# unzip -l ambari-metrics-common-2.4.0.0.5228.jar |
grep Sets.class
2859 06-01-2016 20:21
com/google/common/collect/ImmutableMap$1MapViewOfValuesAsSingletonSets.class
18255 06-01-2016 20:21 com/google/common/collect/Sets.class
{code}
> Improve TimelineMetricsCache eviction/flush logic using a cache library
> ---
>
> Key: AMBARI-16821
> URL: https://issues.apache.org/jira/browse/AMBARI-16821
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.4.0
>
> Attachments: AMBARI-16821_1.patch, AMBARI-16821_2.patch,
> AMBARI-16821_3-trunk.patch, AMBARI-16821_4-trunk.patch, BUG-55307.patch
>
>
> The TimelineMetricsCache implementation in the metrics sink side is currently
> a ConcurrentSkipListMap. It is better to use pre built cache libraries like
> Guava that offer more support.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16911) Enable HS2 Interactive > Select Hosts does not have Cancel and close
[ https://issues.apache.org/jira/browse/AMBARI-16911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311108#comment-15311108 ] Hudson commented on AMBARI-16911: - FAILURE: Integrated in Ambari-trunk-Commit #4980 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4980/]) AMBARI-16911. Enable HS2 Interactive > Select Hosts does not have Cancel (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b1499e2fcb0ec7a2c26348bceadec4c1abc9b625]) * ambari-web/app/views/wizard/step7/assign_master_view.js * ambari-web/app/templates/common/assign_master_components.hbs > Enable HS2 Interactive > Select Hosts does not have Cancel and close > > > Key: AMBARI-16911 > URL: https://issues.apache.org/jira/browse/AMBARI-16911 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: ambari-2.4.0 >Reporter: Shraddha Sumit >Assignee: Antonenko Alexander >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-16911.patch, before.png, now-1.png, now-2.png > > > Deploy cluster using ambari with Hive and slider > Enable HS2 Interactive > Expected: Select Hosts (Assign masters) page should have Cancel button and > 'X' icon to close or cancel this action. > Actual: On Select Hosts (Assign masters) page there is no 'Cancel' button or > 'X' icon for user to cancel this action. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16859) Kafka dashboards for Grafana
[ https://issues.apache.org/jira/browse/AMBARI-16859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311107#comment-15311107 ] Hudson commented on AMBARI-16859: - FAILURE: Integrated in Ambari-trunk-Commit #4980 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4980/]) AMBARI-16859. Kafka dashboards for Grafana. (Prajwal Rao via yusaku) (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=70e90fa3a0769bb884c301f986fb3d8b6586768f]) * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-kafka-home.json * ambari-metrics/ambari-metrics-grafana/ambari-metrics/datasource.js * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-kafka-topics.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-kafka-hosts.json > Kafka dashboards for Grafana > > > Key: AMBARI-16859 > URL: https://issues.apache.org/jira/browse/AMBARI-16859 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao > Fix For: 2.4.0 > > Attachments: AMBARI-16859.patch > > > Add 3 dashboards to Grafana > - Kafka Home > - Kafka Hosts (Templatized) > - Kafka Topics (Templatized per Topic) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16988) Invalid recommended value for storm.local.dir (/usr/hdp/hadoop/storm)
[
https://issues.apache.org/jira/browse/AMBARI-16988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311106#comment-15311106
]
Hudson commented on AMBARI-16988:
-
FAILURE: Integrated in Ambari-trunk-Commit #4980 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4980/])
AMBARI-16988. Invalid recommended value for storm.local.dir (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2327365b2e99179a0fb82b9284395cae0690001a])
* ambari-web/app/utils/configs/mount_points_based_initializer_mixin.js
* ambari-web/app/controllers/wizard/step7_controller.js
* ambari-web/test/utils/configs/config_initializer_test.js
> Invalid recommended value for storm.local.dir (/usr/hdp/hadoop/storm)
> -
>
> Key: AMBARI-16988
> URL: https://issues.apache.org/jira/browse/AMBARI-16988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16988.patch
>
>
> Ambari was installed on the host with the following mounts (Ubuntu 16,
> HDP-2.5):
> {noformat}
> root@u16-ambari-ubuntu-xenial-01:~# df -h
> Filesystem Size Used Avail Use% Mounted on
> udev4.8G 0 4.8G 0% /dev
> tmpfs 981M 15M 967M 2% /run
> /dev/sda1 9.7G 3.4G 6.3G 35% /
> tmpfs 4.8G 4.0K 4.8G 1% /dev/shm
> tmpfs 5.0M 0 5.0M 0% /run/lock
> tmpfs 4.8G 0 4.8G 0% /sys/fs/cgroup
> tmpfs 100K 0 100K 0% /run/lxcfs/controllers
> /dev/sdc135G 1.9G 31G 6% /usr/hdp
> tmpfs 981M 0 981M 0% /run/user/1000
> {noformat}
> The recommended value was:
> {noformat}
> "storm.local.dir" : "/usr/hdp/hadoop/storm"
> {noformat}
> hdp-select expects that folder name inside of /usr/hdp correspond to version
> numbers.
> {noformat}
> root@u16-ambari-ubuntu-xenial-01:~# hdp-select versions
> Traceback (most recent call last):
> File "/usr/bin/hdp-select", line 391, in
> printVersions()
> File "/usr/bin/hdp-select", line 248, in printVersions
> result[tuple(map(int, versionRegex.split(f)))] = f
> ValueError: invalid literal for int() with base 10: 'hadoop'
> root@u16-ambari-ubuntu-xenial-01:~# ll /usr/hdp
> total 36
> drwxr-xr-x 6 root root 4096 May 27 10:53 ./
> drwxr-xr-x 12 root root 4096 May 26 17:19 ../
> drwxr-xr-x 17 root root 4096 May 27 10:53 2.5.0.0-568/
> drwxr-xr-x 2 root root 4096 May 27 10:44 current/
> drwxr-xr-x 3 root root 4096 May 27 10:53 hadoop/
> drwx-- 2 root root 16384 May 26 17:02 lost+found/
> {noformat}
> It's a brittle part of hdp-select and probably should be fixed.
> Anyway Ambari shouldn't recommend /usr/hdp/hadoop/storm folder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16970) Update derivation of hawq_rm_memory_limit_perseg
[ https://issues.apache.org/jira/browse/AMBARI-16970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311109#comment-15311109 ] Hudson commented on AMBARI-16970: - FAILURE: Integrated in Ambari-trunk-Commit #4980 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4980/]) AMBARI-16970: Update derivation of hawq_rm_memory_limit_perseg (bhuvnesh2703: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=761000633ef42899b7f983ddca9a78ea52816759]) * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/service_advisor.py * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-sysctl-env.xml * ambari-server/src/test/python/stacks/2.3/HAWQ/test_service_advisor.py * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-site.xml > Update derivation of hawq_rm_memory_limit_perseg > > > Key: AMBARI-16970 > URL: https://issues.apache.org/jira/browse/AMBARI-16970 > Project: Ambari > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16970-1.patch, AMBARI-16970.patch > > > Update derivation of hawq_rm_memory_limit_perseg. It should be calculated > based on vm.overcommit_ratio, vm.overcommit_memory and the available system > memory. It should also have a default value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16272) Ambari Upgrade shouldn't automatically add stack configs
[ https://issues.apache.org/jira/browse/AMBARI-16272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311104#comment-15311104 ] Hudson commented on AMBARI-16272: - FAILURE: Integrated in Ambari-trunk-Commit #4980 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4980/]) AMBARI-16272. Ambari Upgrade shouldn't automatically add stack configs. (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=70aacc6dbcf762ce387ecca544977a2ace006c6d]) * ambari-server/src/main/resources/stacks/HDP/2.3/services/HBASE/configuration/hbase-site.xml * ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/configuration/hadoop-policy.xml * ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/ECS/configuration/core-site.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/HBASE/configuration/ranger-hbase-plugin-properties.xml * ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/ranger-tagsync-site.xml * ambari-server/src/test/resources/stacks/HDP/1.3.1/services/HDFS/configuration/core-site.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.3/services/YARN/configuration/capacity-scheduler.xml * ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/configuration/hbase-env.xml * ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/configuration/oozie-env.xml * ambari-server/src/test/resources/stacks/HDP/1.3.0/services/MAPREDUCE/configuration/mapred-queue-acls.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/STORM/configuration/storm-site.xml * ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/configuration/yarn-log4j.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/AMBARI_METRICS/configuration/ams-site.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/configuration/hadoop-env.xml * ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/hadoop-env.xml * ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/YARN/configuration-mapred/mapred-site.xml * ambari-server/src/test/resources/stacks/HDP/0.2/services/MAPREDUCE/configuration/hbase-site.xml * ambari-server/src/test/resources/stacks/HDP/2.0.8/services/HBASE/configuration/hbase-site.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/YARN/configuration/yarn-env.xml * ambari-server/src/main/resources/stacks/HDP/2.2/services/FALCON/configuration/falcon-startup.properties.xml * ambari-server/src/test/resources/stacks_with_common_services/HDP/0.2/services/HDFS/configuration/hdfs-site.xml * ambari-server/src/test/resources/common-services/HDFS/1.0/configuration/hbase-site.xml * ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-queue-acls.xml * ambari-server/src/test/resources/stacks/HDP/2.0.6.1/services/FLUME/configuration/flume-conf.xml * ambari-server/src/main/resources/common-services/KAFKA/0.9.0/configuration/ranger-kafka-security.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-log4j.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/ZOOKEEPER/configuration/zookeeper-env.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/AMBARI_METRICS/configuration/ams-log4j.xml * ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/tagsync-log4j.xml * ambari-server/src/main/resources/stacks/HDP/2.1/services/YARN/configuration/yarn-site.xml * ambari-server/src/main/resources/common-services/KAFKA/0.9.0/configuration/kafka-broker.xml * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hcat-env.xml * ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/ECS/configuration/hdfs-site.xml * ambari-server/src/test/resources/stacks/HDP/2.0.1/services/HDFS/configuration/hadoop-policy.xml * ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/STORM/configuration/storm-env.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/HBASE/configuration/hbase-env.xml * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hdfs-log4j.xml * ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-service_logs-solrconfig.xml * ambari-server/src/test/resources/stacks/HDP/2.0.5/services/YARN/configuration/yarn-site.xml * ambari-server/src/main/resources/common-services/KAFKA/0.8.1/configuration/kafka-broker.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hivemetastore-site.xml * ambari-server/src/test/resources/stacks/HDP/2.0.6/services/YARN/configuration/yarn-site.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/HDFS/configuration/hdfs-site.xml * ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/mapred-queue-acls.xml *
[jira] [Commented] (AMBARI-16987) After relogin get the same page was before logout instead of Dashboard
[
https://issues.apache.org/jira/browse/AMBARI-16987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311105#comment-15311105
]
Hudson commented on AMBARI-16987:
-
FAILURE: Integrated in Ambari-trunk-Commit #4980 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4980/])
AMBARI-16987. After relogin get the same page was before logout instead
(hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=92dec5bd689b78cdb9a5a257ddecc02b2c664e66])
* ambari-web/app/router.js
> After relogin get the same page was before logout instead of Dashboard
> --
>
> Key: AMBARI-16987
> URL: https://issues.apache.org/jira/browse/AMBARI-16987
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16987.patch
>
>
> STR:
> # Deploy cluster
> # Go to any tab, but not Dashboard
> # Log out
> # Log in again
> Result: got the same page as before log out.
> Tested also on Ambari built from ambari-vdf brach
> Env:
> {code}
> ambari-server --hash
> 2ab5c04efcdc42190279f3259250663ea1f7d8bb
> rpm -qa |grep ambari
> ambari-server-2.4.99.0-87.x86_64
> ambari-agent-2.4.99.0-87.x86_64
> {code}
> Tested on the Chrome (latest), Firefox 24.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16993) Misc fixes related to slider while enabling interactive query
[ https://issues.apache.org/jira/browse/AMBARI-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-16993: Attachment: (was: AMBARI-16993.patch) > Misc fixes related to slider while enabling interactive query > -- > > Key: AMBARI-16993 > URL: https://issues.apache.org/jira/browse/AMBARI-16993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > > *Scenario 1:* > # Install a Ambari-2.2.2 cluster with hive service > # Upgrade to Ambari-2.4.0 > # Enable interactive query. A popup asking to install slider service first > will be shown. Also recommendations for enable interactive query are shown in > the bg > # Dismiss the popup. This again disables interactive query > *Actual behavior:* Recommendations for enabled interactive query remains > *Expected behavior:* Since interactive query is again disabled, > recommendations for enabled interactive query should go away. > *Scenario 2:* > # Install a 3 host Ambari-2.4.0 cluster with hive service. Install slider > client on 2 out of 3 hosts. > # Enable interactive query. Select a host on which slider client is absent > for HS2 interactive. > # Save configurations > *Actual behavior:* Install components request has tasks to installs Slider > client on all 3 hosts > *Expected behavior:* Install components request should install Slider client > only on 1 host (HS2 interactive host) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16993) Misc fixes related to slider while enabling interactive query
[ https://issues.apache.org/jira/browse/AMBARI-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-16993: Status: Patch Available (was: Open) Verifies that the patch resolves both the stated issues ambari-web unit tests with the patch: 28524 tests complete (28 seconds) 154 tests pending > Misc fixes related to slider while enabling interactive query > -- > > Key: AMBARI-16993 > URL: https://issues.apache.org/jira/browse/AMBARI-16993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16993.patch > > > *Scenario 1:* > # Install a Ambari-2.2.2 cluster with hive service > # Upgrade to Ambari-2.4.0 > # Enable interactive query. A popup asking to install slider service first > will be shown. Also recommendations for enable interactive query are shown in > the bg > # Dismiss the popup. This again disables interactive query > *Actual behavior:* Recommendations for enabled interactive query remains > *Expected behavior:* Since interactive query is again disabled, > recommendations for enabled interactive query should go away. > *Scenario 2:* > # Install a 3 host Ambari-2.4.0 cluster with hive service. Install slider > client on 2 out of 3 hosts. > # Enable interactive query. Select a host on which slider client is absent > for HS2 interactive. > # Save configurations > *Actual behavior:* Install components request has tasks to installs Slider > client on all 3 hosts > *Expected behavior:* Install components request should install Slider client > only on 1 host (HS2 interactive host) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[ https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-16992: -- Attachment: AMBARI-16992-trunk-orig.patch > Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor > - > > Key: AMBARI-16992 > URL: https://issues.apache.org/jira/browse/AMBARI-16992 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16992-trunk-orig.patch > > > Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16985) "Wizard in progress" bar should not look clickable
[ https://issues.apache.org/jira/browse/AMBARI-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1532#comment-1532 ] Aleksandr Kovalenko commented on AMBARI-16985: -- committed to trunk and branch-2.4 > "Wizard in progress" bar should not look clickable > -- > > Key: AMBARI-16985 > URL: https://issues.apache.org/jira/browse/AMBARI-16985 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-16985.patch > > > Change cursor type to default on " is in progress" bar. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16993) Misc fixes related to slider while enabling interactive query
Jaimin D Jetly created AMBARI-16993: --- Summary: Misc fixes related to slider while enabling interactive query Key: AMBARI-16993 URL: https://issues.apache.org/jira/browse/AMBARI-16993 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Jaimin D Jetly Assignee: Jaimin D Jetly Priority: Critical Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16985) "Wizard in progress" bar should not look clickable
[ https://issues.apache.org/jira/browse/AMBARI-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1531#comment-1531 ] Aleksandr Kovalenko commented on AMBARI-16985: -- Did not add unit test as it was just template change. > "Wizard in progress" bar should not look clickable > -- > > Key: AMBARI-16985 > URL: https://issues.apache.org/jira/browse/AMBARI-16985 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-16985.patch > > > Change cursor type to default on " is in progress" bar. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
