[jira] [Commented] (AMBARI-17828) Nimbus, Storm UI server stopped after disabling ranger plugins
[ https://issues.apache.org/jira/browse/AMBARI-17828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387203#comment-15387203 ] Vivek Rathod commented on AMBARI-17828: --- cc [~vperiasamy] > Nimbus, Storm UI server stopped after disabling ranger plugins > -- > > Key: AMBARI-17828 > URL: https://issues.apache.org/jira/browse/AMBARI-17828 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 > Environment: ambari-server version: ambari-server-2.4.0.0-892 > ambari-server --hash: 61d963c0167932a7e08799c81449e1ba7b91c652 >Reporter: Vivek Rathod >Priority: Critical > Fix For: 2.4.0 > > > STR: > Enable all ranger plugins and restart services with stale configs > Disable all ranger plugins and restart services > Nimbus and Storm UI server are down after that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17828) Nimbus, Storm UI server stopped after disabling ranger plugins
Vivek Rathod created AMBARI-17828: - Summary: Nimbus, Storm UI server stopped after disabling ranger plugins Key: AMBARI-17828 URL: https://issues.apache.org/jira/browse/AMBARI-17828 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Environment: ambari-server version: ambari-server-2.4.0.0-892 ambari-server --hash: 61d963c0167932a7e08799c81449e1ba7b91c652 Reporter: Vivek Rathod Priority: Critical Fix For: 2.4.0 STR: Enable all ranger plugins and restart services with stale configs Disable all ranger plugins and restart services Nimbus and Storm UI server are down after that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17818) Tez & Hive: Memory management should use scaled down Xmx for sizing buffers
[ https://issues.apache.org/jira/browse/AMBARI-17818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated AMBARI-17818: - Status: Patch Available (was: Open) > Tez & Hive: Memory management should use scaled down Xmx for sizing buffers > --- > > Key: AMBARI-17818 > URL: https://issues.apache.org/jira/browse/AMBARI-17818 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Gopal V >Assignee: Gopal V > Attachments: AMBARI-17818.1.patch, AMBARI-17818.2.patch > > > The defaults in Ambari assume 80% of the YARN container size is allocate to > the user heap (Xmx). > On top of this particular restriction, the allocation blocks are divided into > Eden/Survivor/Tenured - a single allocation spanning 40% of the heap might > fail for tez runtime.io.sort.mb. > Scale down the Tez sort size and map join by 0.8x to match Xmx. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17818) Tez & Hive: Memory management should use scaled down Xmx for sizing buffers
[ https://issues.apache.org/jira/browse/AMBARI-17818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated AMBARI-17818: - Attachment: AMBARI-17818.2.patch Recreate patch with a/ & b/ prefixes. > Tez & Hive: Memory management should use scaled down Xmx for sizing buffers > --- > > Key: AMBARI-17818 > URL: https://issues.apache.org/jira/browse/AMBARI-17818 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Gopal V >Assignee: Gopal V > Attachments: AMBARI-17818.1.patch, AMBARI-17818.2.patch > > > The defaults in Ambari assume 80% of the YARN container size is allocate to > the user heap (Xmx). > On top of this particular restriction, the allocation blocks are divided into > Eden/Survivor/Tenured - a single allocation spanning 40% of the heap might > fail for tez runtime.io.sort.mb. > Scale down the Tez sort size and map join by 0.8x to match Xmx. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17818) Tez & Hive: Memory management should use scaled down Xmx for sizing buffers
[ https://issues.apache.org/jira/browse/AMBARI-17818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated AMBARI-17818: - Status: Open (was: Patch Available) > Tez & Hive: Memory management should use scaled down Xmx for sizing buffers > --- > > Key: AMBARI-17818 > URL: https://issues.apache.org/jira/browse/AMBARI-17818 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Gopal V >Assignee: Gopal V > Attachments: AMBARI-17818.1.patch > > > The defaults in Ambari assume 80% of the YARN container size is allocate to > the user heap (Xmx). > On top of this particular restriction, the allocation blocks are divided into > Eden/Survivor/Tenured - a single allocation spanning 40% of the heap might > fail for tez runtime.io.sort.mb. > Scale down the Tez sort size and map join by 0.8x to match Xmx. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17818) Tez & Hive: Memory management should use scaled down Xmx for sizing buffers
[
https://issues.apache.org/jira/browse/AMBARI-17818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387191#comment-15387191
]
Gopal V commented on AMBARI-17818:
--
{code}
error: src/main/resources/stacks/HDP/2.2/services/stack_advisor.py: No such
file or directory
error: src/main/resources/stacks/HDP/2.3/services/stack_advisor.py: No such
file or directory
error: src/test/python/stacks/2.2/common/test_stack_advisor.py: No such file or
directory
error: src/test/python/stacks/2.3/common/test_stack_advisor.py: No such file or
directory
PATCH APPLICATION FAILED
{code}
Does Ambari not -p0 patch apply?
{code}
--- ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
+++ ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
{code}
> Tez & Hive: Memory management should use scaled down Xmx for sizing buffers
> ---
>
> Key: AMBARI-17818
> URL: https://issues.apache.org/jira/browse/AMBARI-17818
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Reporter: Gopal V
>Assignee: Gopal V
> Attachments: AMBARI-17818.1.patch
>
>
> The defaults in Ambari assume 80% of the YARN container size is allocate to
> the user heap (Xmx).
> On top of this particular restriction, the allocation blocks are divided into
> Eden/Survivor/Tenured - a single allocation spanning 40% of the heap might
> fail for tez runtime.io.sort.mb.
> Scale down the Tez sort size and map join by 0.8x to match Xmx.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17818) Tez & Hive: Memory management should use scaled down Xmx for sizing buffers
[
https://issues.apache.org/jira/browse/AMBARI-17818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387184#comment-15387184
]
Hadoop QA commented on AMBARI-17818:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12819160/AMBARI-17818.1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7948//console
This message is automatically generated.
> Tez & Hive: Memory management should use scaled down Xmx for sizing buffers
> ---
>
> Key: AMBARI-17818
> URL: https://issues.apache.org/jira/browse/AMBARI-17818
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Reporter: Gopal V
>Assignee: Gopal V
> Attachments: AMBARI-17818.1.patch
>
>
> The defaults in Ambari assume 80% of the YARN container size is allocate to
> the user heap (Xmx).
> On top of this particular restriction, the allocation blocks are divided into
> Eden/Survivor/Tenured - a single allocation spanning 40% of the heap might
> fail for tez runtime.io.sort.mb.
> Scale down the Tez sort size and map join by 0.8x to match Xmx.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17821) Atlas: Add Service Customize Services Page Issues
[ https://issues.apache.org/jira/browse/AMBARI-17821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387074#comment-15387074 ] Hudson commented on AMBARI-17821: - FAILURE: Integrated in Ambari-trunk-Commit #5350 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5350/]) AMBARI-17821 Atlas: Add Service Customize Services Page Issues (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5f079eb32cd752a260290310c74efe7a0d9592d7]) * ambari-web/app/views/common/configs/service_config_container_view.js * ambari-web/test/views/common/configs/service_config_container_view_test.js > Atlas: Add Service Customize Services Page Issues > - > > Key: AMBARI-17821 > URL: https://issues.apache.org/jira/browse/AMBARI-17821 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.4.0 > > > - Deploy secure cluster via blueprints without Atlas > - Navigate to Add Service Wizard to Add Atlas > - At the customize services page we see 2 issues : > - First is that it takes a long time to load > - Second, as the page was loaded it shows 5 required properties at the > Advanced tab, but it quickly goes away -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17747) EU/RU Kafka should come right after ZK instead of before Atlas, fix role command order
[ https://issues.apache.org/jira/browse/AMBARI-17747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387073#comment-15387073 ] Hudson commented on AMBARI-17747: - FAILURE: Integrated in Ambari-trunk-Commit #5350 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5350/]) Revert "AMBARI-17747. EU/RU Kafka should come right after ZK instead of (jluniya: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e95259bb341e23a81474832798eff328076f6f7b]) * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.5/role_command_order.json * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.4.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml > EU/RU Kafka should come right after ZK instead of before Atlas, fix role > command order > -- > > Key: AMBARI-17747 > URL: https://issues.apache.org/jira/browse/AMBARI-17747 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Jayush Luniya > Fix For: 2.4.0 > > Attachments: AMBARI-17747.branch-2.4.patch, AMBARI-17747.trunk.patch > > > Atlas has a dependency on Kafka, yet EU/EU upgrades Atlas and then Kafka. > We should move Kafka right after ZK. > Also check role command order so that Atlas starts after HBASE and Kafka have > been started. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17783) Add falcon to oozie admin user for HDP 2.5
[
https://issues.apache.org/jira/browse/AMBARI-17783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387051#comment-15387051
]
Alejandro Fernandez commented on AMBARI-17783:
--
Oozie was installed in cluster and it failed with
{code}
Traceback (most recent call last):
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 158,
in
main(sys.argv)
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 115,
in main
result = stackAdvisor.validateConfigurations(services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 536, in validateConfigurations
validationItems = self.getConfigurationsValidationItems(services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 612, in getConfigurationsValidationItems
recommendations = self.recommendConfigurations(services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 760, in recommendConfigurations
calculation(configurations, clusterSummary, services, hosts)
File
"/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.5/services/stack_advisor.py",
line 45, in recommendOozieConfigurations
oozieUser =
services["configurations"]["oozie-env"]["properties"]["oozie_user"]
KeyError: 'oozie-env'
{code}
> Add falcon to oozie admin user for HDP 2.5
> --
>
> Key: AMBARI-17783
> URL: https://issues.apache.org/jira/browse/AMBARI-17783
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Murali Ramasami
>Assignee: Venkat Ranganathan
> Fix For: 2.4.0
>
> Attachments: AMBARI-17783.patch
>
>
> we need to add falcon and falcon-admin in the oozie_admin_users of oozie
> advanced env section.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (AMBARI-17783) Add falcon to oozie admin user for HDP 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez reopened AMBARI-17783: -- > Add falcon to oozie admin user for HDP 2.5 > -- > > Key: AMBARI-17783 > URL: https://issues.apache.org/jira/browse/AMBARI-17783 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Murali Ramasami >Assignee: Venkat Ranganathan > Fix For: 2.4.0 > > Attachments: AMBARI-17783.patch > > > we need to add falcon and falcon-admin in the oozie_admin_users of oozie > advanced env section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17827) Spark thrift server should be stopped before RM stop
[ https://issues.apache.org/jira/browse/AMBARI-17827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-17827: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.4 > Spark thrift server should be stopped before RM stop > > > Key: AMBARI-17827 > URL: https://issues.apache.org/jira/browse/AMBARI-17827 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Yesha Vora >Assignee: Jeff Zhang > Fix For: 2.4.0 > > Attachments: AMBARI-17827-1.patch > > > Ambari restarts the services while kerberizing the cluster. In this restart, > Amabri should stop spark thrift server before Resourcemanager. > Since spark thrift server starts yarn application, its is necessary that > spark-thrift server should be stopped before Resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17827) Spark thrift server should be stopped before RM stop
[ https://issues.apache.org/jira/browse/AMBARI-17827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386981#comment-15386981 ] Sumit Mohanty commented on AMBARI-17827: LGTM, +1 > Spark thrift server should be stopped before RM stop > > > Key: AMBARI-17827 > URL: https://issues.apache.org/jira/browse/AMBARI-17827 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Yesha Vora >Assignee: Jeff Zhang > Fix For: 2.4.0 > > Attachments: AMBARI-17827-1.patch > > > Ambari restarts the services while kerberizing the cluster. In this restart, > Amabri should stop spark thrift server before Resourcemanager. > Since spark thrift server starts yarn application, its is necessary that > spark-thrift server should be stopped before Resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17827) Spark thrift server should be stopped before RM stop
[ https://issues.apache.org/jira/browse/AMBARI-17827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-17827: --- Fix Version/s: 2.4.0 > Spark thrift server should be stopped before RM stop > > > Key: AMBARI-17827 > URL: https://issues.apache.org/jira/browse/AMBARI-17827 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Yesha Vora >Assignee: Jeff Zhang > Fix For: 2.4.0 > > Attachments: AMBARI-17827-1.patch > > > Ambari restarts the services while kerberizing the cluster. In this restart, > Amabri should stop spark thrift server before Resourcemanager. > Since spark thrift server starts yarn application, its is necessary that > spark-thrift server should be stopped before Resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17827) Spark thrift server should be stopped before RM stop
[ https://issues.apache.org/jira/browse/AMBARI-17827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated AMBARI-17827: Status: Patch Available (was: Open) > Spark thrift server should be stopped before RM stop > > > Key: AMBARI-17827 > URL: https://issues.apache.org/jira/browse/AMBARI-17827 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Yesha Vora >Assignee: Jeff Zhang > Attachments: AMBARI-17827-1.patch > > > Ambari restarts the services while kerberizing the cluster. In this restart, > Amabri should stop spark thrift server before Resourcemanager. > Since spark thrift server starts yarn application, its is necessary that > spark-thrift server should be stopped before Resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17827) Spark thrift server should be stopped before RM stop
[ https://issues.apache.org/jira/browse/AMBARI-17827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated AMBARI-17827: Attachment: AMBARI-17827-1.patch > Spark thrift server should be stopped before RM stop > > > Key: AMBARI-17827 > URL: https://issues.apache.org/jira/browse/AMBARI-17827 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Yesha Vora >Assignee: Jeff Zhang > Attachments: AMBARI-17827-1.patch > > > Ambari restarts the services while kerberizing the cluster. In this restart, > Amabri should stop spark thrift server before Resourcemanager. > Since spark thrift server starts yarn application, its is necessary that > spark-thrift server should be stopped before Resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-17827) Spark thrift server should be stopped before RM stop
[ https://issues.apache.org/jira/browse/AMBARI-17827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang reassigned AMBARI-17827: --- Assignee: Jeff Zhang > Spark thrift server should be stopped before RM stop > > > Key: AMBARI-17827 > URL: https://issues.apache.org/jira/browse/AMBARI-17827 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Yesha Vora >Assignee: Jeff Zhang > > Ambari restarts the services while kerberizing the cluster. In this restart, > Amabri should stop spark thrift server before Resourcemanager. > Since spark thrift server starts yarn application, its is necessary that > spark-thrift server should be stopped before Resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17827) Spark thrift server should be stopped before RM stop
Yesha Vora created AMBARI-17827: --- Summary: Spark thrift server should be stopped before RM stop Key: AMBARI-17827 URL: https://issues.apache.org/jira/browse/AMBARI-17827 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Yesha Vora Ambari restarts the services while kerberizing the cluster. In this restart, Amabri should stop spark thrift server before Resourcemanager. Since spark thrift server starts yarn application, its is necessary that spark-thrift server should be stopped before Resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17825) Fix the empty value which may get passed back from 'get_llap_cap_percent_slider' fn.
[ https://issues.apache.org/jira/browse/AMBARI-17825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17825: - Attachment: AMBARI-17825.patch > Fix the empty value which may get passed back from > 'get_llap_cap_percent_slider' fn. > > > Key: AMBARI-17825 > URL: https://issues.apache.org/jira/browse/AMBARI-17825 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17825.patch > > > - The fn . get_llap_cap_percent_slider() may return None if the bounded > conditions are not met while fetching 'lllap_queue_capacity'. > - Also, had issue with typecasting from string to int. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17826) Change in Ambari for Atlas config properties for Kerberos auth
[
https://issues.apache.org/jira/browse/AMBARI-17826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386959#comment-15386959
]
Swapan Shridhar commented on AMBARI-17826:
--
+1.
> Change in Ambari for Atlas config properties for Kerberos auth
> --
>
> Key: AMBARI-17826
> URL: https://issues.apache.org/jira/browse/AMBARI-17826
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17826.patch
>
>
> Remove unsupported property {{atlas.authentication.method.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17826) Change in Ambari for Atlas config properties for Kerberos auth
[
https://issues.apache.org/jira/browse/AMBARI-17826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-17826:
---
Attachment: AMBARI-17826.patch
> Change in Ambari for Atlas config properties for Kerberos auth
> --
>
> Key: AMBARI-17826
> URL: https://issues.apache.org/jira/browse/AMBARI-17826
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17826.patch
>
>
> Remove unsupported property {{atlas.authentication.method.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17826) Change in Ambari for Atlas config properties for Kerberos auth
Sumit Mohanty created AMBARI-17826:
--
Summary: Change in Ambari for Atlas config properties for Kerberos
auth
Key: AMBARI-17826
URL: https://issues.apache.org/jira/browse/AMBARI-17826
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.4.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
Fix For: 2.4.0
Remove unsupported property {{atlas.authentication.method.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17825) Fix the empty value which may get passed back from 'get_llap_cap_percent_slider' fn.
Swapan Shridhar created AMBARI-17825: Summary: Fix the empty value which may get passed back from 'get_llap_cap_percent_slider' fn. Key: AMBARI-17825 URL: https://issues.apache.org/jira/browse/AMBARI-17825 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 2.4.0 - The fn . get_llap_cap_percent_slider() may return None if the bounded conditions are not met while fetching 'lllap_queue_capacity'. - Also, had issue with typecasting from string to int. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17747) EU/RU Kafka should come right after ZK instead of before Atlas, fix role command order
[ https://issues.apache.org/jira/browse/AMBARI-17747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386933#comment-15386933 ] Jayush Luniya commented on AMBARI-17747: Reopening JIRA as upgrade runs into issues when Kafka Ranger Plugin is enabled. Reverted patches from trunk and branch-2.4 > EU/RU Kafka should come right after ZK instead of before Atlas, fix role > command order > -- > > Key: AMBARI-17747 > URL: https://issues.apache.org/jira/browse/AMBARI-17747 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Jayush Luniya > Fix For: 2.4.0 > > Attachments: AMBARI-17747.branch-2.4.patch, AMBARI-17747.trunk.patch > > > Atlas has a dependency on Kafka, yet EU/EU upgrades Atlas and then Kafka. > We should move Kafka right after ZK. > Also check role command order so that Atlas starts after HBASE and Kafka have > been started. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-17747) EU/RU Kafka should come right after ZK instead of before Atlas, fix role command order
[ https://issues.apache.org/jira/browse/AMBARI-17747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reopened AMBARI-17747: > EU/RU Kafka should come right after ZK instead of before Atlas, fix role > command order > -- > > Key: AMBARI-17747 > URL: https://issues.apache.org/jira/browse/AMBARI-17747 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > Attachments: AMBARI-17747.branch-2.4.patch, AMBARI-17747.trunk.patch > > > Atlas has a dependency on Kafka, yet EU/EU upgrades Atlas and then Kafka. > We should move Kafka right after ZK. > Also check role command order so that Atlas starts after HBASE and Kafka have > been started. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-17747) EU/RU Kafka should come right after ZK instead of before Atlas, fix role command order
[ https://issues.apache.org/jira/browse/AMBARI-17747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reassigned AMBARI-17747: -- Assignee: Jayush Luniya (was: Alejandro Fernandez) > EU/RU Kafka should come right after ZK instead of before Atlas, fix role > command order > -- > > Key: AMBARI-17747 > URL: https://issues.apache.org/jira/browse/AMBARI-17747 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Jayush Luniya > Fix For: 2.4.0 > > Attachments: AMBARI-17747.branch-2.4.patch, AMBARI-17747.trunk.patch > > > Atlas has a dependency on Kafka, yet EU/EU upgrades Atlas and then Kafka. > We should move Kafka right after ZK. > Also check role command order so that Atlas starts after HBASE and Kafka have > been started. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17750) Design user interface for views under service tab and other related general improvements
[ https://issues.apache.org/jira/browse/AMBARI-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17750: Fix Version/s: (was: trunk) branch-embedded-views > Design user interface for views under service tab and other related general > improvements > > > Key: AMBARI-17750 > URL: https://issues.apache.org/jira/browse/AMBARI-17750 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin D Jetly >Assignee: Subhrajit Das >Priority: Critical > Fix For: branch-embedded-views > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17566) Embed related Views from the Service dashboard page
[ https://issues.apache.org/jira/browse/AMBARI-17566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17566: Fix Version/s: (was: trunk) branch-embedded-views > Embed related Views from the Service dashboard page > --- > > Key: AMBARI-17566 > URL: https://issues.apache.org/jira/browse/AMBARI-17566 > Project: Ambari > Issue Type: Epic > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Manasi Maheshwari > Fix For: branch-embedded-views > > > Today, all of the Views appear under a dropdown menu on the right-hand top of > the page. > Ideally, the Files View would show up under HDFS, Capacity Scheduler under > YARN, etc. > 1. > We need a way to annotate a View with the service(s) it's associated with, so > that any view developer can create this association. The API can then expose > endpoints > api/v1/views/FILES/ (show service_name: "HDFS") > api/v1/clusters/$name/services/HDFS/views (reference to the FILES view) > 2. Views that are associated with the service should be available from the > service's dashboard page (e.g., next to the Heatmaps and Configs as tabs). > These Views should be embedded within the service dashboard page so that they > appear as if they are part of the page. This way, the user is not taken out > of the current context and provides seamless UX. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17824) Show existing views under relevant service page as tabs
Jaimin D Jetly created AMBARI-17824: --- Summary: Show existing views under relevant service page as tabs Key: AMBARI-17824 URL: https://issues.apache.org/jira/browse/AMBARI-17824 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.5.0 Reporter: Jaimin D Jetly Assignee: Manasi Maheshwari Fix For: branch-embedded-views Following needs to be done as part of this work # view instances needs to be shown under relevant service as tabs # content of the view resources needs to be shown in iframe # Quick links location needs to be adjusted so it does not collapse with view tabs # Left service menu on the service page needs to be removed to give more space to view content # Increase the span for the pages under service page for larger width -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17807) Should only upload spark assembly jar once
[ https://issues.apache.org/jira/browse/AMBARI-17807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386860#comment-15386860 ] Hudson commented on AMBARI-17807: - FAILURE: Integrated in Ambari-trunk-Commit #5349 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5349/]) AMBARI-17807. Should only upload spark assembly jar once (Jeff Zhang via (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7ac9c5483123e76c767c18dc741f35bd60b3bb8c]) * ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/spark_service.py * ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/spark_service.py > Should only upload spark assembly jar once > -- > > Key: AMBARI-17807 > URL: https://issues.apache.org/jira/browse/AMBARI-17807 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17807-1.patch, AMBARI-17807-2.patch > > > For now, spark assembly jar will be uploaded multiple times if job history > server and thrift server are both installed. It should only been uploaded > when job history server is installed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386861#comment-15386861 ] Hudson commented on AMBARI-16027: - FAILURE: Integrated in Ambari-trunk-Commit #5349 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5349/]) AMBARI-16027. Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=66a2b9761693399069488338f70f498641ee00cf]) * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/kafka.py * ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml * ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml * ambari-server/src/main/resources/common-services/KAFKA/0.9.0/configuration/kafka-broker.xml * ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.4.xml > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17820) UI sometimes stucks while deleting service due to JS error
[
https://issues.apache.org/jira/browse/AMBARI-17820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386859#comment-15386859
]
Hudson commented on AMBARI-17820:
-
FAILURE: Integrated in Ambari-trunk-Commit #5349 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5349/])
AMBARI-17820. UI sometimes stucks while deleting service due to JS (jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1e252acf8d7e33bcb3cab83feedc2e6f3d1f1163])
* ambari-web/app/views/main/service/info/summary.js
> UI sometimes stucks while deleting service due to JS error
> --
>
> Key: AMBARI-17820
> URL: https://issues.apache.org/jira/browse/AMBARI-17820
> 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-17820.1.patch
>
>
> Patch includes following change:
> {code}
> sourceIds.forEach(function(item, index) {
> if (!dataIds.contains(item)) {
> - source.removeAt(index);
> + var sourceItem = source.findProperty('id',item);
> + source.removeObject(sourceItem);
> }
>});
> {code}
> The issue was because sourceIds array being iterated was assumed to have same
> length as source array whose elements are being conditionally removed.
> The bug was that when condition was satisfied and an element was removed,
> source array became smaller and its elements were shifted left due to element
> removal. This made possibility that on last iteration of the loop if the
> condition to remove element is again satisfied then source array will not
> have element on the index. So source.removeAt(index); will throw no element
> at index exception
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17633) yarn.nodemanager.remote-app-log-dir should be added stickybit.
[
https://issues.apache.org/jira/browse/AMBARI-17633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386808#comment-15386808
]
Masahiro Tanaka commented on AMBARI-17633:
--
Hi [~aonishuk], [~mpapirkovskyy], could you review this?
> yarn.nodemanager.remote-app-log-dir should be added stickybit.
> --
>
> Key: AMBARI-17633
> URL: https://issues.apache.org/jira/browse/AMBARI-17633
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS7.2 Ambari2.4, HDP2.4
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17633.1.patch, AMBARI-17633.2.patch,
> AMBARI-17633.patch
>
>
> When installing YARN+MapReduce2, I got a WARN message in nodemanager log(in
> Log Search View) like below
> {code}
> 2016-07-09 06:30:21,865 WARN logaggregation.LogAggregationService
> LogAggregationService.java:230 - Remote Root Log Dir [/app-logs] already
> exist, but with incorrect permissions. Expected: [rwxrwxrwt], Found:
> [rwxrwxrwx]. The cluster may have problems with multiple users.
> {code}
> I think the cause of this WARN is
> [this](https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py#L115).
> We should add stickybit to {{yarn.nodemanager.remote-app-log-dir}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17750) Design user interface for views under service tab and other related general improvements
[ https://issues.apache.org/jira/browse/AMBARI-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17750: Assignee: Subhrajit Das (was: Jaimin D Jetly) > Design user interface for views under service tab and other related general > improvements > > > Key: AMBARI-17750 > URL: https://issues.apache.org/jira/browse/AMBARI-17750 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin D Jetly >Assignee: Subhrajit Das >Priority: Critical > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17750) Design user interface for views under service tab and other related general improvements
[ https://issues.apache.org/jira/browse/AMBARI-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386793#comment-15386793 ] Jaimin D Jetly commented on AMBARI-17750: - Thanks [~Subhrajit Das] > Design user interface for views under service tab and other related general > improvements > > > Key: AMBARI-17750 > URL: https://issues.apache.org/jira/browse/AMBARI-17750 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin D Jetly >Assignee: Subhrajit Das >Priority: Critical > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17750) Design user interface for views under service tab and other related general improvements
[ https://issues.apache.org/jira/browse/AMBARI-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386788#comment-15386788 ] Subhrajit Das commented on AMBARI-17750: You can assign this to me. > Design user interface for views under service tab and other related general > improvements > > > Key: AMBARI-17750 > URL: https://issues.apache.org/jira/browse/AMBARI-17750 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-17750) Design user interface for views under service tab and other related general improvements
[ https://issues.apache.org/jira/browse/AMBARI-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly reassigned AMBARI-17750: --- Assignee: Jaimin D Jetly > Design user interface for views under service tab and other related general > improvements > > > Key: AMBARI-17750 > URL: https://issues.apache.org/jira/browse/AMBARI-17750 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17704) Livy upgrade not working
[ https://issues.apache.org/jira/browse/AMBARI-17704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386706#comment-15386706 ] Bikas Saha commented on AMBARI-17704: - [~sumitmohanty] Please review hopefully for the last time! > Livy upgrade not working > > > Key: AMBARI-17704 > URL: https://issues.apache.org/jira/browse/AMBARI-17704 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17704.1.patch, AMBARI-17704.addendum.2.patch, > AMBARI-17704.addendum.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17704) Livy upgrade not working
[ https://issues.apache.org/jira/browse/AMBARI-17704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated AMBARI-17704: Attachment: AMBARI-17704.addendum.2.patch Still missing imports. In addendum.2 I have made imports identical to history_server.py which works. So hopefully this is the last iteration unless it complains about unused imports :P > Livy upgrade not working > > > Key: AMBARI-17704 > URL: https://issues.apache.org/jira/browse/AMBARI-17704 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17704.1.patch, AMBARI-17704.addendum.2.patch, > AMBARI-17704.addendum.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-17823) Increase retries and timeout for actions
[ https://issues.apache.org/jira/browse/AMBARI-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan reassigned AMBARI-17823: --- Assignee: Venkat Ranganathan > Increase retries and timeout for actions > - > > Key: AMBARI-17823 > URL: https://issues.apache.org/jira/browse/AMBARI-17823 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Trupti Dhavle >Assignee: Venkat Ranganathan > Fix For: trunk > > > It is noticed that during rolling upgrades where services go down, sometimes > oozie workflows get suspended as it gives up trying. This requires increasing > retries and timeout for actions in oozie configs so that workflows work > seamless even when services go down in RU -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Attachment: AMBARI-17694-1.patch > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694-1.patch, AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Status: Patch Available (was: Open) > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694-1.patch, AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17822) Create AMBARI_INFRA service definition
[ https://issues.apache.org/jira/browse/AMBARI-17822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-17822: -- Component/s: stacks > Create AMBARI_INFRA service definition > -- > > Key: AMBARI-17822 > URL: https://issues.apache.org/jira/browse/AMBARI-17822 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server, stacks >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Critical > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17822) Create AMBARI_INFRA service definition
[ https://issues.apache.org/jira/browse/AMBARI-17822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-17822: -- Component/s: ambari-server ambari-logsearch > Create AMBARI_INFRA service definition > -- > > Key: AMBARI-17822 > URL: https://issues.apache.org/jira/browse/AMBARI-17822 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Critical > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17308) Ambari Logfeeder outputs a lot of errors due to parse date
[
https://issues.apache.org/jira/browse/AMBARI-17308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17308:
-
Status: Patch Available (was: Open)
> Ambari Logfeeder outputs a lot of errors due to parse date
> --
>
> Key: AMBARI-17308
> URL: https://issues.apache.org/jira/browse/AMBARI-17308
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk, 2.4.0
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17308.patch
>
>
> In logsearch_feeder service log, we got errors like below
> {code}
> 2016-06-20 15:28:09,368 ERROR file=ambari-audit.log
> org.apache.ambari.logfeeder.mapper.MapperDate LogFeederUtil.java:356 - Error
> applying date transformation. isEpoch=false,
> dateFormat=-MM-dd'T'HH:mm:ss.SSSZ, value=2016-06-20T15:28:08.000.
> mapClass=map_date, input=input:source=file,
> path=/var/log/ambari-server/ambari-audit.log, fieldName=logtime. Messages
> suppressed before: 2
> java.text.ParseException: Unparseable date: "2016-06-20T15:28:08.000"
> at java.text.DateFormat.parse(DateFormat.java:366)
> at
> org.apache.ambari.logfeeder.mapper.MapperDate.apply(MapperDate.java:83)
> at org.apache.ambari.logfeeder.filter.Filter.apply(Filter.java:154)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.applyMessage(FilterGrok.java:291)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.flush(FilterGrok.java:320)
> at org.apache.ambari.logfeeder.input.Input.flush(Input.java:125)
> at
> org.apache.ambari.logfeeder.input.InputFile.processFile(InputFile.java:430)
> at org.apache.ambari.logfeeder.input.InputFile.start(InputFile.java:260)
> at org.apache.ambari.logfeeder.input.Input.run(Input.java:100)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> ambari-audit.log is like below
> {code}
> 2016-07-21T01:52:49.875+09, User(admin), RemoteIp(192.168.72.1),
> Operation(Repository update), RequestType(PUT),
> url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu14/repositories/HDP-2.5),
> ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu14), Repo
> id(HDP-2.5), Base
> URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu14/2.x/BUILDS/2.5.0.0-1025)
> 2016-07-21T01:52:49.905+09, User(admin), RemoteIp(192.168.72.1),
> Operation(Repository update), RequestType(PUT),
> url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu16/repositories/HDP-2.5),
> ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu16), Repo
> id(HDP-2.5), Base
> URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu16/2.x/BUILDS/2.5.0.0-1025)
> 2016-07-21T01:52:50.015+09, User(admin), RemoteIp(192.168.72.1),
> Operation(Repository update), RequestType(PUT),
> url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu14/repositories/HDP-UTILS-1.1.0.21),
> ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu14), Repo
> id(HDP-UTILS-1.1.0.21), Base
> URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ubuntu14)
> {code}
> I think date format of the ambari-audit.log ({{2016-07-21T01:52:49.875+09}})
> should be like {{2016-07-21T01:52:49.875+0900}}, since grok-pattern can't
> handle {{2016-07-21T01:52:49.875+09}} format.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17308) Ambari Logfeeder outputs a lot of errors due to parse date
[
https://issues.apache.org/jira/browse/AMBARI-17308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17308:
-
Attachment: AMBARI-17308.patch
> Ambari Logfeeder outputs a lot of errors due to parse date
> --
>
> Key: AMBARI-17308
> URL: https://issues.apache.org/jira/browse/AMBARI-17308
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk, 2.4.0
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17308.patch
>
>
> In logsearch_feeder service log, we got errors like below
> {code}
> 2016-06-20 15:28:09,368 ERROR file=ambari-audit.log
> org.apache.ambari.logfeeder.mapper.MapperDate LogFeederUtil.java:356 - Error
> applying date transformation. isEpoch=false,
> dateFormat=-MM-dd'T'HH:mm:ss.SSSZ, value=2016-06-20T15:28:08.000.
> mapClass=map_date, input=input:source=file,
> path=/var/log/ambari-server/ambari-audit.log, fieldName=logtime. Messages
> suppressed before: 2
> java.text.ParseException: Unparseable date: "2016-06-20T15:28:08.000"
> at java.text.DateFormat.parse(DateFormat.java:366)
> at
> org.apache.ambari.logfeeder.mapper.MapperDate.apply(MapperDate.java:83)
> at org.apache.ambari.logfeeder.filter.Filter.apply(Filter.java:154)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.applyMessage(FilterGrok.java:291)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.flush(FilterGrok.java:320)
> at org.apache.ambari.logfeeder.input.Input.flush(Input.java:125)
> at
> org.apache.ambari.logfeeder.input.InputFile.processFile(InputFile.java:430)
> at org.apache.ambari.logfeeder.input.InputFile.start(InputFile.java:260)
> at org.apache.ambari.logfeeder.input.Input.run(Input.java:100)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> ambari-audit.log is like below
> {code}
> 2016-07-21T01:52:49.875+09, User(admin), RemoteIp(192.168.72.1),
> Operation(Repository update), RequestType(PUT),
> url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu14/repositories/HDP-2.5),
> ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu14), Repo
> id(HDP-2.5), Base
> URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu14/2.x/BUILDS/2.5.0.0-1025)
> 2016-07-21T01:52:49.905+09, User(admin), RemoteIp(192.168.72.1),
> Operation(Repository update), RequestType(PUT),
> url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu16/repositories/HDP-2.5),
> ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu16), Repo
> id(HDP-2.5), Base
> URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu16/2.x/BUILDS/2.5.0.0-1025)
> 2016-07-21T01:52:50.015+09, User(admin), RemoteIp(192.168.72.1),
> Operation(Repository update), RequestType(PUT),
> url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu14/repositories/HDP-UTILS-1.1.0.21),
> ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu14), Repo
> id(HDP-UTILS-1.1.0.21), Base
> URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ubuntu14)
> {code}
> I think date format of the ambari-audit.log ({{2016-07-21T01:52:49.875+09}})
> should be like {{2016-07-21T01:52:49.875+0900}}, since grok-pattern can't
> handle {{2016-07-21T01:52:49.875+09}} format.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-17821) Atlas: Add Service Customize Services Page Issues
[ https://issues.apache.org/jira/browse/AMBARI-17821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang reassigned AMBARI-17821: - Assignee: Richard Zang > Atlas: Add Service Customize Services Page Issues > - > > Key: AMBARI-17821 > URL: https://issues.apache.org/jira/browse/AMBARI-17821 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.4.0 > > > - Deploy secure cluster via blueprints without Atlas > - Navigate to Add Service Wizard to Add Atlas > - At the customize services page we see 2 issues : > - First is that it takes a long time to load > - Second, as the page was loaded it shows 5 required properties at the > Advanced tab, but it quickly goes away -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17821) Atlas: Add Service Customize Services Page Issues
[ https://issues.apache.org/jira/browse/AMBARI-17821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-17821: -- Assignee: (was: Richard Zang) > Atlas: Add Service Customize Services Page Issues > - > > Key: AMBARI-17821 > URL: https://issues.apache.org/jira/browse/AMBARI-17821 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Priority: Critical > Fix For: 2.4.0 > > > - Deploy secure cluster via blueprints without Atlas > - Navigate to Add Service Wizard to Add Atlas > - At the customize services page we see 2 issues : > - First is that it takes a long time to load > - Second, as the page was loaded it shows 5 required properties at the > Advanced tab, but it quickly goes away -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Attachment: (was: AMBARI-17694-1.patch) > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Status: Open (was: Patch Available) > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Comment: was deleted (was: Updated the patch based on comments from Robert) > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17823) Increase retries and timeout for actions
Trupti Dhavle created AMBARI-17823: -- Summary: Increase retries and timeout for actions Key: AMBARI-17823 URL: https://issues.apache.org/jira/browse/AMBARI-17823 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Trupti Dhavle Fix For: trunk It is noticed that during rolling upgrades where services go down, sometimes oozie workflows get suspended as it gives up trying. This requires increasing retries and timeout for actions in oozie configs so that workflows work seamless even when services go down in RU -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17822) Create AMBARI_INFRA service definition
Olivér Szabó created AMBARI-17822: - Summary: Create AMBARI_INFRA service definition Key: AMBARI-17822 URL: https://issues.apache.org/jira/browse/AMBARI-17822 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Priority: Critical Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17821) Atlas: Add Service Customize Services Page Issues
[ https://issues.apache.org/jira/browse/AMBARI-17821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-17821: -- Summary: Atlas: Add Service Customize Services Page Issues (was: Atlas: Add Service Customize Services Page Issue) > Atlas: Add Service Customize Services Page Issues > - > > Key: AMBARI-17821 > URL: https://issues.apache.org/jira/browse/AMBARI-17821 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.4.0 > > > - Deploy secure cluster via blueprints without Atlas > - Navigate to Add Service Wizard to Add Atlas > - At the customize services page we see 2 issues : > - First is that it takes a long time to load > - Second, as the page was loaded it shows 5 required properties at the > Advanced tab, but it quickly goes away -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17821) Atlas: Add Service Customize Services Page Issue
Richard Zang created AMBARI-17821: - Summary: Atlas: Add Service Customize Services Page Issue Key: AMBARI-17821 URL: https://issues.apache.org/jira/browse/AMBARI-17821 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Richard Zang Assignee: Richard Zang Priority: Critical Fix For: 2.4.0 - Deploy secure cluster via blueprints without Atlas - Navigate to Add Service Wizard to Add Atlas - At the customize services page we see 2 issues : - First is that it takes a long time to load - Second, as the page was loaded it shows 5 required properties at the Advanced tab, but it quickly goes away -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Attachment: AMBARI-17694-1.patch > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694-1.patch, AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Updated the patch based on comments from Robert > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694-1.patch, AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17694: -- Status: Open (was: Patch Available) > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17041) Support password type for custom properties
[
https://issues.apache.org/jira/browse/AMBARI-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keta Patel updated AMBARI-17041:
Status: Patch Available (was: Open)
> Support password type for custom properties
> ---
>
> Key: AMBARI-17041
> URL: https://issues.apache.org/jira/browse/AMBARI-17041
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Tuong Truong
>Assignee: Keta Patel
> Attachments: AMBARI-17041-July14.patch, AMBARI-17041-July15.patch,
> AMBARI-17041-July20.patch, AMBARI-17041-trunk-July08.patch,
> AMBARI-17041-trunk-Jun29.patch, AMBARI-17041-trunk.patch,
> add_property_pop_up.tiff,
> cluster_config_with_password_type_in_config_attributes_column.tiff,
> custom_properties_after_save.tiff, custom_property_password_type.tiff,
> custom_property_regular_type.tiff, property_type_schema.tiff,
> schema_of_clusterconfig_table.tiff
>
>
> Currently, services can define properties in the XML configuration files that
> is flagged as type password:
>
> my.special.password
>
> PASSWORD
> Password to be masked
>
> and it will be masked properly in the UI as well as blueprint.
> Custom property should also support this option so that password can be added
> as custom property and treat accordingly.
> ==
> Proposed Design for the fix:
> ==
> At present only the key-value information of the service properties is stored
> in the DB ("clusterconfig" table in the "config_data" column).
> The "config_attributes" column stores only certain attributes like "final"
> indicating the list of properties set with the Final flag = true.
> The information about the property-type (i.e PASSWORD, USER, GROUP,
> ADDITIONAL_USER_PROPERTY, VALUE_FROM_PROPERTY_FILE, NOT_MANAGED_HDFS_PATH,
> etc) is extracted from the corresponding service's property file (e.g.
> hive-site.xml, core-site.xml, webhcat-env.xml, etc). These files contain
> information of the existing properties only. Custom Properties added by
> ambari user have no provision to store their additional attributes.
> Since, for this Jira we are concerned with only attribute for
> Custom Properties, we could add an additional field called "Property Type" in
> the "Add Property" pop-up which shows up on clicking "Add Property ..." in
> the Custom property section for a service. For now, only 2 options are shown
> in the drop-down list: NONE and PASSWORD .
> A few sample test properties are created using the new "Add Property" pop-up
> as can be seen in the following attachments.
> Attachments:
> "add_property_pop_up.tiff"
> "custom_property_password_type.tiff"
> "custom_property_regular_type.tiff"
> "custom_properties_after_save.tiff"
> The information for these Custom properties is stored in the
> DB in "clusterconfig" table, "config_attributes" column.
> The schema for "clusterconfig" table can be seen in the attachment:
> "schema_of_clusterconfig_table.tiff"
> The content of the "config_attributes" column with the
> information from the new Custom properties can be seen in the attachment:
> "cluster_config_with_password_type_in_config_attributes_column.tiff"
> Note: The fix so far is performed only for new Custom properties. The
> information for existing properties is extracted from the
> corresponding property xml files for the service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17041) Support password type for custom properties
[
https://issues.apache.org/jira/browse/AMBARI-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386627#comment-15386627
]
Keta Patel commented on AMBARI-17041:
-
Attached updated patch "AMBARI-17041-July20.patch" with optimization in
config.js as suggested on Review Board.
The ambari-web tests after applying the patch:
29292 tests complete (42 seconds)
154 tests pending
> Support password type for custom properties
> ---
>
> Key: AMBARI-17041
> URL: https://issues.apache.org/jira/browse/AMBARI-17041
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Tuong Truong
>Assignee: Keta Patel
> Attachments: AMBARI-17041-July14.patch, AMBARI-17041-July15.patch,
> AMBARI-17041-July20.patch, AMBARI-17041-trunk-July08.patch,
> AMBARI-17041-trunk-Jun29.patch, AMBARI-17041-trunk.patch,
> add_property_pop_up.tiff,
> cluster_config_with_password_type_in_config_attributes_column.tiff,
> custom_properties_after_save.tiff, custom_property_password_type.tiff,
> custom_property_regular_type.tiff, property_type_schema.tiff,
> schema_of_clusterconfig_table.tiff
>
>
> Currently, services can define properties in the XML configuration files that
> is flagged as type password:
>
> my.special.password
>
> PASSWORD
> Password to be masked
>
> and it will be masked properly in the UI as well as blueprint.
> Custom property should also support this option so that password can be added
> as custom property and treat accordingly.
> ==
> Proposed Design for the fix:
> ==
> At present only the key-value information of the service properties is stored
> in the DB ("clusterconfig" table in the "config_data" column).
> The "config_attributes" column stores only certain attributes like "final"
> indicating the list of properties set with the Final flag = true.
> The information about the property-type (i.e PASSWORD, USER, GROUP,
> ADDITIONAL_USER_PROPERTY, VALUE_FROM_PROPERTY_FILE, NOT_MANAGED_HDFS_PATH,
> etc) is extracted from the corresponding service's property file (e.g.
> hive-site.xml, core-site.xml, webhcat-env.xml, etc). These files contain
> information of the existing properties only. Custom Properties added by
> ambari user have no provision to store their additional attributes.
> Since, for this Jira we are concerned with only attribute for
> Custom Properties, we could add an additional field called "Property Type" in
> the "Add Property" pop-up which shows up on clicking "Add Property ..." in
> the Custom property section for a service. For now, only 2 options are shown
> in the drop-down list: NONE and PASSWORD .
> A few sample test properties are created using the new "Add Property" pop-up
> as can be seen in the following attachments.
> Attachments:
> "add_property_pop_up.tiff"
> "custom_property_password_type.tiff"
> "custom_property_regular_type.tiff"
> "custom_properties_after_save.tiff"
> The information for these Custom properties is stored in the
> DB in "clusterconfig" table, "config_attributes" column.
> The schema for "clusterconfig" table can be seen in the attachment:
> "schema_of_clusterconfig_table.tiff"
> The content of the "config_attributes" column with the
> information from the new Custom properties can be seen in the attachment:
> "cluster_config_with_password_type_in_config_attributes_column.tiff"
> Note: The fix so far is performed only for new Custom properties. The
> information for existing properties is extracted from the
> corresponding property xml files for the service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17041) Support password type for custom properties
[
https://issues.apache.org/jira/browse/AMBARI-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keta Patel updated AMBARI-17041:
Status: Open (was: Patch Available)
> Support password type for custom properties
> ---
>
> Key: AMBARI-17041
> URL: https://issues.apache.org/jira/browse/AMBARI-17041
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Tuong Truong
>Assignee: Keta Patel
> Attachments: AMBARI-17041-July14.patch, AMBARI-17041-July15.patch,
> AMBARI-17041-July20.patch, AMBARI-17041-trunk-July08.patch,
> AMBARI-17041-trunk-Jun29.patch, AMBARI-17041-trunk.patch,
> add_property_pop_up.tiff,
> cluster_config_with_password_type_in_config_attributes_column.tiff,
> custom_properties_after_save.tiff, custom_property_password_type.tiff,
> custom_property_regular_type.tiff, property_type_schema.tiff,
> schema_of_clusterconfig_table.tiff
>
>
> Currently, services can define properties in the XML configuration files that
> is flagged as type password:
>
> my.special.password
>
> PASSWORD
> Password to be masked
>
> and it will be masked properly in the UI as well as blueprint.
> Custom property should also support this option so that password can be added
> as custom property and treat accordingly.
> ==
> Proposed Design for the fix:
> ==
> At present only the key-value information of the service properties is stored
> in the DB ("clusterconfig" table in the "config_data" column).
> The "config_attributes" column stores only certain attributes like "final"
> indicating the list of properties set with the Final flag = true.
> The information about the property-type (i.e PASSWORD, USER, GROUP,
> ADDITIONAL_USER_PROPERTY, VALUE_FROM_PROPERTY_FILE, NOT_MANAGED_HDFS_PATH,
> etc) is extracted from the corresponding service's property file (e.g.
> hive-site.xml, core-site.xml, webhcat-env.xml, etc). These files contain
> information of the existing properties only. Custom Properties added by
> ambari user have no provision to store their additional attributes.
> Since, for this Jira we are concerned with only attribute for
> Custom Properties, we could add an additional field called "Property Type" in
> the "Add Property" pop-up which shows up on clicking "Add Property ..." in
> the Custom property section for a service. For now, only 2 options are shown
> in the drop-down list: NONE and PASSWORD .
> A few sample test properties are created using the new "Add Property" pop-up
> as can be seen in the following attachments.
> Attachments:
> "add_property_pop_up.tiff"
> "custom_property_password_type.tiff"
> "custom_property_regular_type.tiff"
> "custom_properties_after_save.tiff"
> The information for these Custom properties is stored in the
> DB in "clusterconfig" table, "config_attributes" column.
> The schema for "clusterconfig" table can be seen in the attachment:
> "schema_of_clusterconfig_table.tiff"
> The content of the "config_attributes" column with the
> information from the new Custom properties can be seen in the attachment:
> "cluster_config_with_password_type_in_config_attributes_column.tiff"
> Note: The fix so far is performed only for new Custom properties. The
> information for existing properties is extracted from the
> corresponding property xml files for the service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17041) Support password type for custom properties
[
https://issues.apache.org/jira/browse/AMBARI-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keta Patel updated AMBARI-17041:
Attachment: AMBARI-17041-July20.patch
> Support password type for custom properties
> ---
>
> Key: AMBARI-17041
> URL: https://issues.apache.org/jira/browse/AMBARI-17041
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Tuong Truong
>Assignee: Keta Patel
> Attachments: AMBARI-17041-July14.patch, AMBARI-17041-July15.patch,
> AMBARI-17041-July20.patch, AMBARI-17041-trunk-July08.patch,
> AMBARI-17041-trunk-Jun29.patch, AMBARI-17041-trunk.patch,
> add_property_pop_up.tiff,
> cluster_config_with_password_type_in_config_attributes_column.tiff,
> custom_properties_after_save.tiff, custom_property_password_type.tiff,
> custom_property_regular_type.tiff, property_type_schema.tiff,
> schema_of_clusterconfig_table.tiff
>
>
> Currently, services can define properties in the XML configuration files that
> is flagged as type password:
>
> my.special.password
>
> PASSWORD
> Password to be masked
>
> and it will be masked properly in the UI as well as blueprint.
> Custom property should also support this option so that password can be added
> as custom property and treat accordingly.
> ==
> Proposed Design for the fix:
> ==
> At present only the key-value information of the service properties is stored
> in the DB ("clusterconfig" table in the "config_data" column).
> The "config_attributes" column stores only certain attributes like "final"
> indicating the list of properties set with the Final flag = true.
> The information about the property-type (i.e PASSWORD, USER, GROUP,
> ADDITIONAL_USER_PROPERTY, VALUE_FROM_PROPERTY_FILE, NOT_MANAGED_HDFS_PATH,
> etc) is extracted from the corresponding service's property file (e.g.
> hive-site.xml, core-site.xml, webhcat-env.xml, etc). These files contain
> information of the existing properties only. Custom Properties added by
> ambari user have no provision to store their additional attributes.
> Since, for this Jira we are concerned with only attribute for
> Custom Properties, we could add an additional field called "Property Type" in
> the "Add Property" pop-up which shows up on clicking "Add Property ..." in
> the Custom property section for a service. For now, only 2 options are shown
> in the drop-down list: NONE and PASSWORD .
> A few sample test properties are created using the new "Add Property" pop-up
> as can be seen in the following attachments.
> Attachments:
> "add_property_pop_up.tiff"
> "custom_property_password_type.tiff"
> "custom_property_regular_type.tiff"
> "custom_properties_after_save.tiff"
> The information for these Custom properties is stored in the
> DB in "clusterconfig" table, "config_attributes" column.
> The schema for "clusterconfig" table can be seen in the attachment:
> "schema_of_clusterconfig_table.tiff"
> The content of the "config_attributes" column with the
> information from the new Custom properties can be seen in the attachment:
> "cluster_config_with_password_type_in_config_attributes_column.tiff"
> Note: The fix so far is performed only for new Custom properties. The
> information for existing properties is extracted from the
> corresponding property xml files for the service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17815) Add tech preview text for Log Search service definition
[ https://issues.apache.org/jira/browse/AMBARI-17815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386619#comment-15386619 ] Hudson commented on AMBARI-17815: - FAILURE: Integrated in Ambari-trunk-Commit #5348 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5348/]) AMBARI-17815. Add tech preview text for Log Search service definition (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8cd37908164875029c315cf7d549da83619c0f58]) * ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/metainfo.xml > Add tech preview text for Log Search service definition > --- > > Key: AMBARI-17815 > URL: https://issues.apache.org/jira/browse/AMBARI-17815 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17819) "Manage ambari" button shown to Cluster Administrator
[ https://issues.apache.org/jira/browse/AMBARI-17819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386615#comment-15386615 ] Hudson commented on AMBARI-17819: - FAILURE: Integrated in Ambari-trunk-Commit #5348 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5348/]) AMBARI-17819. "Manage ambari" button shown to Cluster Administrator (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e79d388a864d680d0072bf591d8f4ff83a02f726]) * ambari-web/app/templates/application.hbs > "Manage ambari" button shown to Cluster Administrator > - > > Key: AMBARI-17819 > URL: https://issues.apache.org/jira/browse/AMBARI-17819 > 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-17819.patch > > > STR : > 1) Create a cluster admin user > 2) Login as cluster admin user > 3) Check options on the right corner. It shows "Manage Ambari". This button > should only be visible to the ambari admin > Clicking on the button redirects me to the metrics page (Possibly because the > permission is not available) > PS :This test was blocked for a while now and that's why could not verify > this. I am unsure of when this broke. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17808) Kerberos Client fails to install
[
https://issues.apache.org/jira/browse/AMBARI-17808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386616#comment-15386616
]
Hudson commented on AMBARI-17808:
-
FAILURE: Integrated in Ambari-trunk-Commit #5348 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5348/])
AMBARI-17808. Kerberos Client fails to install (rlevas) (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=96a29c816e1a9b3a6096f5f24c94f5a3552b4a67])
*
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/package/templates/kadm5_acl.j2
*
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/metainfo.xml
*
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_server.py
*
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/package/templates/kdc_conf.j2
*
ambari-common/src/main/python/resource_management/libraries/functions/package_conditions.py
> Kerberos Client fails to install
>
>
> Key: AMBARI-17808
> URL: https://issues.apache.org/jira/browse/AMBARI-17808
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Labels: kerberos
> Fix For: 2.4.0
>
> Attachments: AMBARI-17808_branch-2.4_01.patch,
> AMBARI-17808_trunk_01.patch
>
>
> Log
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_client.py",
> line 80, in
> KerberosClient().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_client.py",
> line 28, in install
> self.install_packages(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 545, in install_packages
> if Script.check_package_condition(package):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 583, in check_package_condition
> return chooser_method()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/package_conditions.py",
> line 93, in should_install_kerberos_server
> return 'role' in config and not
> _has_applicable_local_component("KERBEROS_CLIENT")
> TypeError: _has_applicable_local_component() takes exactly 2 arguments (1
> given)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17291) zookeeper.quorum in storm-metrics2.properties is broken
[
https://issues.apache.org/jira/browse/AMBARI-17291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386617#comment-15386617
]
Hudson commented on AMBARI-17291:
-
FAILURE: Integrated in Ambari-trunk-Commit #5348 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5348/])
AMBARI-17291 zookeeper.quorum in storm-metrics2.properties is broken (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0079796ad541824db1cf9c72461da3e651cdd788])
*
ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py
> zookeeper.quorum in storm-metrics2.properties is broken
> ---
>
> Key: AMBARI-17291
> URL: https://issues.apache.org/jira/browse/AMBARI-17291
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, ambari-server
>Affects Versions: trunk
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-17291.1.patch, AMBARI-17291.patch
>
>
> When installed Storm and Ambari Metrics (and ZooKeeper, for dependency),
> {{zookeeper.quorum}} in /etc/storm/conf/storm-metrics2.properties is looks
> like this.
> {code}
> zookeeper.quorum=[:2181,':2181,c:2181,7:2181,2:2181,0:2181,1:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,2:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,3:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,]:2181
> {code}
> storm.zookeeper.servers is
> {{['c7201.ambari.apache.org','c7202.ambari.apache.org','c7203.ambari.apache.org']}}
> Steps to reproduce.
> Install Ambari Server (I used
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos7/2.x/latest/trunk/ambaribn.repo)
> Setup and start Ambari Server (ambari-server setup -s and ambari-server start)
> Install Storm and ZooKeeper via Ambari Server (HDP2.4)
> Install Ambari Metrics
> Restart all required
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17720) HAWQ fails to execute queries in low-memory environment
[ https://issues.apache.org/jira/browse/AMBARI-17720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386613#comment-15386613 ] Hudson commented on AMBARI-17720: - FAILURE: Integrated in Ambari-trunk-Commit #5348 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5348/]) AMBARI-17720: HAWQ fails to execute queries in low-memory environment (matt: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0d54f17c296ba0fe265b90e3b91d4d2bc983e95d]) * 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-site.xml * ambari-server/src/test/python/common-services/PXF/test_service_advisor.py * ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py * ambari-server/src/main/resources/common-services/PXF/3.0.0/service_advisor.py > HAWQ fails to execute queries in low-memory environment > --- > > Key: AMBARI-17720 > URL: https://issues.apache.org/jira/browse/AMBARI-17720 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Matt >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17720-trunk-orig.patch, > AMBARI-17720-trunk-v1.patch, AMBARI-17720-trunk-v2.patch > > > When a user is running on vagrant or single node with low system memory, > configurations are not sufficient to allocate containers for "default" 6 > vsegs per node especially during HASH dist table query or external table > query. > Stack advisor should adjust the config values to ensure service checks and > queries (including Random tables, HASH dist tables, PXF ext tables) do not > fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17809) DataNode failed to start because of "small initial heap"
[
https://issues.apache.org/jira/browse/AMBARI-17809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386607#comment-15386607
]
Hudson commented on AMBARI-17809:
-
FAILURE: Integrated in Ambari-trunk-Commit #5348 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5348/])
AMBARI-17809 DataNode failed to start because of "small initial heap" (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=63b18db043f479db8e24c7568108d7e1dcc1aceb])
* ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
> DataNode failed to start because of "small initial heap"
>
>
> Key: AMBARI-17809
> URL: https://issues.apache.org/jira/browse/AMBARI-17809
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17809-branch-2.4.patch
>
>
> dtnode_heapsize should end with "m" like
> {code}
> "dtnode_heapsize" : "1024m",
> {code}
> but in the cluster it's
> {code}
> "dtnode_heapsize" : "1024",
> {code}
> stack_advisor failed with
> {code}
> 20 Jul 2016 04:52:17,900 INFO [pool-17-thread-1] StackAdvisorRunner:71 -
> advisor script stderr: Traceback (most recent call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 158,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 109,
> in main
> result = stackAdvisor.recommendConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 760, in recommendConfigurations
> calculation(configurations, clusterSummary, services, hosts)
> File
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.5/services/stack_advisor.py",
> line 46, in recommendOozieConfigurations
> newAdminUsers = "{0},oozie-admin,{1}".format(oozieUser, falconUser)
> UnboundLocalError: local variable 'falconUser' referenced before assignment
> 20 Jul 2016 04:52:17,902 ERROR [pool-17-thread-1]
> ClusterConfigurationRequest:156 - An exception occurred while doing
> configuration topology update:
> org.apache.ambari.server.controller.internal.ConfigurationTopologyException:
> Configuration recommendation failed.
> {code}
> and 1024m hasn't been recommended for dtnode_heapsize
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17804) ATS goes down after deleting Smartsense and restarting services with stale configs
[ https://issues.apache.org/jira/browse/AMBARI-17804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386612#comment-15386612 ] Hudson commented on AMBARI-17804: - FAILURE: Integrated in Ambari-trunk-Commit #5348 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5348/]) AMBARI-17804. ATS goes down after deleting Smartsense and restarting (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5324771272e15a7178ffef52e2dc70c4c2fbb4d3]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-site.xml > ATS goes down after deleting Smartsense and restarting services with stale > configs > -- > > Key: AMBARI-17804 > URL: https://issues.apache.org/jira/browse/AMBARI-17804 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17804.patch > > > During service deletes, occasionally the YARN config changes and ATS stops. > ATS started up fine after changing the value of to > *yarn.timeline-service.entity-group-fs-store.group-id-plugin-classpath* > to > */usr/hdp/2.5.0.0-1009/spark/hdpLib/** -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17784) AMS Storm Sink: remove redundant information from kafka offset metrics on storm-kafka
[ https://issues.apache.org/jira/browse/AMBARI-17784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386605#comment-15386605 ] Hudson commented on AMBARI-17784: - FAILURE: Integrated in Ambari-trunk-Commit #5348 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5348/]) AMBARI-17784 : AMS Storm Sink: remove redundant information from kafka (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2e873b6c4a4a7dae9c33f8df3e5f97ac61f73499]) * ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java * ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java * ambari-metrics/ambari-metrics-storm-sink-legacy/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java * ambari-metrics/ambari-metrics-storm-sink/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java > AMS Storm Sink: remove redundant information from kafka offset metrics on > storm-kafka > - > > Key: AMBARI-17784 > URL: https://issues.apache.org/jira/browse/AMBARI-17784 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Assignee: Jungtaek Lim > Attachments: AMBARI-17784-v1-on-top-of-AMBARI-17725.patch, > AMBARI-17784-v1.patch > > > This is follow-up issue for AMBARI-17725. > After AMBARI-17725, we can distinguish cluster metrics and topology metrics, > which makes us possible to topology name and component name as variables for > templatized dashboard. > But kafkaOffset metrics still have kafka topic and partition information to > middle of metric name which make us hard to pick. Since worker host and > worker port, and task id is not needed for kafkaOffset metrics, we can get > rid of those things from only kafkaOffset metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17725) AMS Storm Sink: Storm topology level metrics should have prefix to distinguish cluster level metrics
[ https://issues.apache.org/jira/browse/AMBARI-17725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386608#comment-15386608 ] Hudson commented on AMBARI-17725: - FAILURE: Integrated in Ambari-trunk-Commit #5348 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5348/]) AMBARI-17725 : AMS Storm Sink: Storm topology level metrics should have (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=da2e67710f8d39958a412a33f08a675b2d75863f]) * ambari-metrics/ambari-metrics-storm-sink/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java * ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java * ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java * ambari-metrics/ambari-metrics-storm-sink-legacy/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java > AMS Storm Sink: Storm topology level metrics should have prefix to > distinguish cluster level metrics > > > Key: AMBARI-17725 > URL: https://issues.apache.org/jira/browse/AMBARI-17725 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Assignee: Jungtaek Lim > Attachments: AMBARI-17725-v1.patch > > > Since Ambari 2.4.0 we have two kinds of Storm metrics into AMS which one is > cluster level and another one is topology level. > Currently we don't add prefix on them which makes them hard to distinguish, > which should be needed to create topology level dashboard in Grafana. > To resolve this we should add the prefix to Storm topology level metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17724) AMS Storm sink: Set metrics filter to reduce large amount of built-in Storm metrics
[ https://issues.apache.org/jira/browse/AMBARI-17724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386609#comment-15386609 ] Hudson commented on AMBARI-17724: - FAILURE: Integrated in Ambari-trunk-Commit #5348 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5348/]) AMBARI-17724 : AMS Storm sink: Set metrics filter to reduce large amount (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=70c3ef14b609ad609cff026a635c47b03f90d556]) * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/storm-site.xml > AMS Storm sink: Set metrics filter to reduce large amount of built-in Storm > metrics > --- > > Key: AMBARI-17724 > URL: https://issues.apache.org/jira/browse/AMBARI-17724 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Assignee: Jungtaek Lim > Attachments: AMBARI-17724-v1.patch > > > Since Storm built-in metrics are provided to each task, topology with high > parallelism incurs lots of metrics pushed to AMS. > Since we intend to provide Storm dashboards with AMS (working in progress), > we can filter out metrics not used for dashboards to reduce overall metrics > count. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17802) Blueprint deployment configures "org.apache.atlas.hive.hook.HiveHook" twice for "hive.exec.post.hooks" config
[ https://issues.apache.org/jira/browse/AMBARI-17802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386614#comment-15386614 ] Hudson commented on AMBARI-17802: - FAILURE: Integrated in Ambari-trunk-Commit #5348 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5348/]) AMBARI-17802. Blueprint deployment configures (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0d926322f9905b36c0b267e451958150c1954eed]) * ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java > Blueprint deployment configures "org.apache.atlas.hive.hook.HiveHook" twice > for "hive.exec.post.hooks" config > - > > Key: AMBARI-17802 > URL: https://issues.apache.org/jira/browse/AMBARI-17802 > Project: Ambari > Issue Type: Bug > Components: blueprints, stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > Attachments: AMBARI-17802.branch-2.4.patch, AMBARI-17802.trunk.patch > > > STR: > Install Ambari 2.4 > Blueprint for HDP 2.5 with Atlas and Hive > Because both Blueprints and Stack Advisor have code to append > "org.apache.atlas.hive.hook.HiveHook" to hive-site's "hive.exec.post.hooks" > config, the value appears twice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17811) LogSearch search engine resource throws NullPointer when LogSearch not available
[
https://issues.apache.org/jira/browse/AMBARI-17811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386606#comment-15386606
]
Hudson commented on AMBARI-17811:
-
FAILURE: Integrated in Ambari-trunk-Commit #5348 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5348/])
AMBARI-17811. LogSearch search engine resource throws NullPointer when
(rnettleton:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e2636c725b12f32ea929746a82e0ebaea8bf9bbe])
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/LoggingService.java
*
ambari-server/src/test/java/org/apache/ambari/server/api/services/LoggingServiceTest.java
> LogSearch search engine resource throws NullPointer when LogSearch not
> available
>
>
> Key: AMBARI-17811
> URL: https://issues.apache.org/jira/browse/AMBARI-17811
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Nettleton
>Assignee: Robert Nettleton
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17811.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The LogSearch integration in the Ambari REST layer uses a "searchEngine"
> interface to abstract out the calls to the LogSearch Server, in order to
> handle search query requests.
> If LogSearch is not running, and a REST GET call is made on the following
> Ambari resource:
> {code}clusters/$CLUSTER_NAME/logging/searchEngine{code}
> The following NullPointerException will be thrown in ambari-server.log:
> {code}
> java.lang.NullPointerException
> at
> org.apache.ambari.server.api.services.LoggingService.handleDirectRequest(LoggingService.java:113)
> at
> org.apache.ambari.server.api.services.LoggingService.getSearchEngine(LoggingService.java:76)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {code}
> The Ambari LogSearch integration should handle this type of failure more
> gracefully. In the event that this REST resource is accessed when LogSearch
> is not running, or is not deployed, then a check for a null
> LoggingRequestHelper should be implemented, and a reasonable error message
> returned to the caller, to indicate that the "searchEngine" resource is not
> currently available.
> I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17816) Rebalance HDFS failed with "float division by zero"
[
https://issues.apache.org/jira/browse/AMBARI-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386610#comment-15386610
]
Hudson commented on AMBARI-17816:
-
FAILURE: Integrated in Ambari-trunk-Commit #5348 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5348/])
AMBARI-17816 Rebalance HDFS failed with "float division by zero" (dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bb1b16910f77d65087f6b108355d159f857d255e])
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
> Rebalance HDFS failed with "float division by zero"
> ---
>
> Key: AMBARI-17816
> URL: https://issues.apache.org/jira/browse/AMBARI-17816
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17816.patch
>
>
> Rebalancing HDFS is failing with stderr :
> {code}
> Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py\",
> line 414, in \nNameNode().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py\",
> line 342, in rebalancehdfs\nlogoutput = False,\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 273, in action_run\ntries=self.resource.tries,
> try_sleep=self.resource.try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 71, in inner\nresult = function(command, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 265, in _call\nraise
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Caused by
> on_new_line function failed with exception for input argument ' 0
> 0 B 0 B0 B':\nTraceback (most
> recent call last):\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 262, in _call\non_new_line(line, out_fd == proc.stderr)\n File
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py\",
> line 332, in handle_new_line\nres['completePercent'] =
> calculateCompletePercent(parser.initialLine, pl)\n File
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py\",
> line 306, in calculateCompletePercent\nreturn 1.0 -
> current.bytesLeftToMove/first.bytesLeftToMove\nZeroDivisionError: float
> division by zero
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17807) Should only upload spark assembly jar once
[ https://issues.apache.org/jira/browse/AMBARI-17807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-17807: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.4 > Should only upload spark assembly jar once > -- > > Key: AMBARI-17807 > URL: https://issues.apache.org/jira/browse/AMBARI-17807 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17807-1.patch, AMBARI-17807-2.patch > > > For now, spark assembly jar will be uploaded multiple times if job history > server and thrift server are both installed. It should only been uploaded > when job history server is installed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17807) Should only upload spark assembly jar once
[ https://issues.apache.org/jira/browse/AMBARI-17807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-17807: --- Status: Open (was: Patch Available) > Should only upload spark assembly jar once > -- > > Key: AMBARI-17807 > URL: https://issues.apache.org/jira/browse/AMBARI-17807 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17807-1.patch, AMBARI-17807-2.patch > > > For now, spark assembly jar will be uploaded multiple times if job history > server and thrift server are both installed. It should only been uploaded > when job history server is installed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17807) Should only upload spark assembly jar once
[ https://issues.apache.org/jira/browse/AMBARI-17807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386593#comment-15386593 ] Sumit Mohanty commented on AMBARI-17807: Tested that the patch applies correctly. And ran local unit tests. > Should only upload spark assembly jar once > -- > > Key: AMBARI-17807 > URL: https://issues.apache.org/jira/browse/AMBARI-17807 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17807-1.patch, AMBARI-17807-2.patch > > > For now, spark assembly jar will be uploaded multiple times if job history > server and thrift server are both installed. It should only been uploaded > when job history server is installed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17818) Tez & Hive: Memory management should use scaled down Xmx for sizing buffers
[ https://issues.apache.org/jira/browse/AMBARI-17818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated AMBARI-17818: - Component/s: stacks > Tez & Hive: Memory management should use scaled down Xmx for sizing buffers > --- > > Key: AMBARI-17818 > URL: https://issues.apache.org/jira/browse/AMBARI-17818 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Gopal V >Assignee: Gopal V > Attachments: AMBARI-17818.1.patch > > > The defaults in Ambari assume 80% of the YARN container size is allocate to > the user heap (Xmx). > On top of this particular restriction, the allocation blocks are divided into > Eden/Survivor/Tenured - a single allocation spanning 40% of the heap might > fail for tez runtime.io.sort.mb. > Scale down the Tez sort size and map join by 0.8x to match Xmx. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17291) zookeeper.quorum in storm-metrics2.properties is broken
[
https://issues.apache.org/jira/browse/AMBARI-17291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386551#comment-15386551
]
Masahiro Tanaka commented on AMBARI-17291:
--
Thank you [~avijayan]!
> zookeeper.quorum in storm-metrics2.properties is broken
> ---
>
> Key: AMBARI-17291
> URL: https://issues.apache.org/jira/browse/AMBARI-17291
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, ambari-server
>Affects Versions: trunk
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-17291.1.patch, AMBARI-17291.patch
>
>
> When installed Storm and Ambari Metrics (and ZooKeeper, for dependency),
> {{zookeeper.quorum}} in /etc/storm/conf/storm-metrics2.properties is looks
> like this.
> {code}
> zookeeper.quorum=[:2181,':2181,c:2181,7:2181,2:2181,0:2181,1:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,2:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,3:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,]:2181
> {code}
> storm.zookeeper.servers is
> {{['c7201.ambari.apache.org','c7202.ambari.apache.org','c7203.ambari.apache.org']}}
> Steps to reproduce.
> Install Ambari Server (I used
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos7/2.x/latest/trunk/ambaribn.repo)
> Setup and start Ambari Server (ambari-server setup -s and ambari-server start)
> Install Storm and ZooKeeper via Ambari Server (HDP2.4)
> Install Ambari Metrics
> Restart all required
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17820) UI sometimes stucks while deleting service due to JS error
[
https://issues.apache.org/jira/browse/AMBARI-17820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-17820:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Patch committed to trunk and branch-2.4
> UI sometimes stucks while deleting service due to JS error
> --
>
> Key: AMBARI-17820
> URL: https://issues.apache.org/jira/browse/AMBARI-17820
> 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-17820.1.patch
>
>
> Patch includes following change:
> {code}
> sourceIds.forEach(function(item, index) {
> if (!dataIds.contains(item)) {
> - source.removeAt(index);
> + var sourceItem = source.findProperty('id',item);
> + source.removeObject(sourceItem);
> }
>});
> {code}
> The issue was because sourceIds array being iterated was assumed to have same
> length as source array whose elements are being conditionally removed.
> The bug was that when condition was satisfied and an element was removed,
> source array became smaller and its elements were shifted left due to element
> removal. This made possibility that on last iteration of the loop if the
> condition to remove element is again satisfied then source array will not
> have element on the index. So source.removeAt(index); will throw no element
> at index exception
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17820) UI sometimes stucks while deleting service due to JS error
[
https://issues.apache.org/jira/browse/AMBARI-17820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386527#comment-15386527
]
Zhe (Joe) Wang commented on AMBARI-17820:
-
+1 for patch
> UI sometimes stucks while deleting service due to JS error
> --
>
> Key: AMBARI-17820
> URL: https://issues.apache.org/jira/browse/AMBARI-17820
> 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-17820.1.patch
>
>
> Patch includes following change:
> {code}
> sourceIds.forEach(function(item, index) {
> if (!dataIds.contains(item)) {
> - source.removeAt(index);
> + var sourceItem = source.findProperty('id',item);
> + source.removeObject(sourceItem);
> }
>});
> {code}
> The issue was because sourceIds array being iterated was assumed to have same
> length as source array whose elements are being conditionally removed.
> The bug was that when condition was satisfied and an element was removed,
> source array became smaller and its elements were shifted left due to element
> removal. This made possibility that on last iteration of the loop if the
> condition to remove element is again satisfied then source array will not
> have element on the index. So source.removeAt(index); will throw no element
> at index exception
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17820) UI sometimes stucks while deleting service due to JS error
[
https://issues.apache.org/jira/browse/AMBARI-17820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-17820:
Description:
Patch includes following change:
{code}
sourceIds.forEach(function(item, index) {
if (!dataIds.contains(item)) {
- source.removeAt(index);
+ var sourceItem = source.findProperty('id',item);
+ source.removeObject(sourceItem);
}
});
{code}
The issue was because sourceIds array being iterated was assumed to have same
length as source array whose elements are being conditionally removed.
The bug was that when condition was satisfied and an element was removed,
source array became smaller and its elements were shifted left due to element
removal. This made possibility that on last iteration of the loop if the
condition to remove element is again satisfied then source array will not have
element on the index. So source.removeAt(index); will throw no element at index
exception
was:
Patch includes following change:
{code}
- source.removeAt(index);
+ var sourceItem = source.findProperty('id',item);
+ source.removeObject(sourceItem);
{code}
The isse
> UI sometimes stucks while deleting service due to JS error
> --
>
> Key: AMBARI-17820
> URL: https://issues.apache.org/jira/browse/AMBARI-17820
> 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-17820.1.patch
>
>
> Patch includes following change:
> {code}
> sourceIds.forEach(function(item, index) {
> if (!dataIds.contains(item)) {
> - source.removeAt(index);
> + var sourceItem = source.findProperty('id',item);
> + source.removeObject(sourceItem);
> }
>});
> {code}
> The issue was because sourceIds array being iterated was assumed to have same
> length as source array whose elements are being conditionally removed.
> The bug was that when condition was satisfied and an element was removed,
> source array became smaller and its elements were shifted left due to element
> removal. This made possibility that on last iteration of the loop if the
> condition to remove element is again satisfied then source array will not
> have element on the index. So source.removeAt(index); will throw no element
> at index exception
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17820) UI sometimes stucks while deleting service due to JS error
[
https://issues.apache.org/jira/browse/AMBARI-17820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-17820:
Description:
Patch includes following change:
{code}
- source.removeAt(index);
+ var sourceItem = source.findProperty('id',item);
+ source.removeObject(sourceItem);
{code}
The isse
> UI sometimes stucks while deleting service due to JS error
> --
>
> Key: AMBARI-17820
> URL: https://issues.apache.org/jira/browse/AMBARI-17820
> 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-17820.1.patch
>
>
> Patch includes following change:
> {code}
> - source.removeAt(index);
> + var sourceItem = source.findProperty('id',item);
> + source.removeObject(sourceItem);
> {code}
> The isse
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17820) UI sometimes stucks while deleting service due to JS error
[ https://issues.apache.org/jira/browse/AMBARI-17820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17820: Status: Patch Available (was: Open) Verfied that patch fixes the issue on a deployed cluster Verified that ambari-web unit tests passes with the patch: 29220 tests complete (30 seconds) 154 tests pending > UI sometimes stucks while deleting service due to JS error > -- > > Key: AMBARI-17820 > URL: https://issues.apache.org/jira/browse/AMBARI-17820 > 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-17820.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-16027: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 66a2b9761693399069488338f70f498641ee00cf branch-2.4, commit f7fe36477fd1fe4bc67eed9c61b13963a8d757a4 > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17820) UI sometimes stucks while deleting service due to JS error
[ https://issues.apache.org/jira/browse/AMBARI-17820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17820: Attachment: AMBARI-17820.1.patch > UI sometimes stucks while deleting service due to JS error > -- > > Key: AMBARI-17820 > URL: https://issues.apache.org/jira/browse/AMBARI-17820 > 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-17820.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17820) UI sometimes stucks while deleting service due to JS error
Jaimin D Jetly created AMBARI-17820: --- Summary: UI sometimes stucks while deleting service due to JS error Key: AMBARI-17820 URL: https://issues.apache.org/jira/browse/AMBARI-17820 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] [Updated] (AMBARI-17808) Kerberos Client fails to install
[
https://issues.apache.org/jira/browse/AMBARI-17808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-17808:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 96a29c816e1a9b3a6096f5f24c94f5a3552b4a67
Author: Robert Levas
Date: Wed Jul 20 15:05:04 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit 5d4ea49b97c4ab6c0ece81726662f7dea78fa7a0
Author: Robert Levas
Date: Wed Jul 20 15:05:52 2016 -0400
{noformat}
> Kerberos Client fails to install
>
>
> Key: AMBARI-17808
> URL: https://issues.apache.org/jira/browse/AMBARI-17808
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Labels: kerberos
> Fix For: 2.4.0
>
> Attachments: AMBARI-17808_branch-2.4_01.patch,
> AMBARI-17808_trunk_01.patch
>
>
> Log
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_client.py",
> line 80, in
> KerberosClient().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_client.py",
> line 28, in install
> self.install_packages(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 545, in install_packages
> if Script.check_package_condition(package):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 583, in check_package_condition
> return chooser_method()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/package_conditions.py",
> line 93, in should_install_kerberos_server
> return 'role' in config and not
> _has_applicable_local_component("KERBEROS_CLIENT")
> TypeError: _has_applicable_local_component() takes exactly 2 arguments (1
> given)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17804) ATS goes down after deleting Smartsense and restarting services with stale configs
[ https://issues.apache.org/jira/browse/AMBARI-17804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-17804: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.4 > ATS goes down after deleting Smartsense and restarting services with stale > configs > -- > > Key: AMBARI-17804 > URL: https://issues.apache.org/jira/browse/AMBARI-17804 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17804.patch > > > During service deletes, occasionally the YARN config changes and ATS stops. > ATS started up fine after changing the value of to > *yarn.timeline-service.entity-group-fs-store.group-id-plugin-classpath* > to > */usr/hdp/2.5.0.0-1009/spark/hdpLib/** -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17802) Blueprint deployment configures "org.apache.atlas.hive.hook.HiveHook" twice for "hive.exec.post.hooks" config
[ https://issues.apache.org/jira/browse/AMBARI-17802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17802: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 0d926322f9905b36c0b267e451958150c1954eed branch-2.4, commit 8cdd83594ba2880d745b472ba6667a9805afd53e > Blueprint deployment configures "org.apache.atlas.hive.hook.HiveHook" twice > for "hive.exec.post.hooks" config > - > > Key: AMBARI-17802 > URL: https://issues.apache.org/jira/browse/AMBARI-17802 > Project: Ambari > Issue Type: Bug > Components: blueprints, stacks >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > Attachments: AMBARI-17802.branch-2.4.patch, AMBARI-17802.trunk.patch > > > STR: > Install Ambari 2.4 > Blueprint for HDP 2.5 with Atlas and Hive > Because both Blueprints and Stack Advisor have code to append > "org.apache.atlas.hive.hook.HiveHook" to hive-site's "hive.exec.post.hooks" > config, the value appears twice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17814) Spark Livy should wait for ATS start for BP deployments
[
https://issues.apache.org/jira/browse/AMBARI-17814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386410#comment-15386410
]
Hadoop QA commented on AMBARI-17814:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12819123/AMBARI-17814.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7940//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7940//console
This message is automatically generated.
> Spark Livy should wait for ATS start for BP deployments
> ---
>
> Key: AMBARI-17814
> URL: https://issues.apache.org/jira/browse/AMBARI-17814
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.4.0
>
> Attachments: AMBARI-17814.patch
>
>
> Spark Livy should wait for ATS start for BP deployments
> We should do something like:
> {code}
> if params.has_ats:
> Logger.info("Verifying DFS directories where ATS stores time line data
> for active and completed applications.")
> self.wait_for_dfs_directories_created(params.entity_groupfs_store_dir,
> params.entity_groupfs_active_dir)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17308) Ambari Logfeeder outputs a lot of errors due to parse date
[
https://issues.apache.org/jira/browse/AMBARI-17308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17308:
-
Affects Version/s: 2.4.0
> Ambari Logfeeder outputs a lot of errors due to parse date
> --
>
> Key: AMBARI-17308
> URL: https://issues.apache.org/jira/browse/AMBARI-17308
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk, 2.4.0
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>
> In logsearch_feeder service log, we got errors like below
> {code}
> 2016-06-20 15:28:09,368 ERROR file=ambari-audit.log
> org.apache.ambari.logfeeder.mapper.MapperDate LogFeederUtil.java:356 - Error
> applying date transformation. isEpoch=false,
> dateFormat=-MM-dd'T'HH:mm:ss.SSSZ, value=2016-06-20T15:28:08.000.
> mapClass=map_date, input=input:source=file,
> path=/var/log/ambari-server/ambari-audit.log, fieldName=logtime. Messages
> suppressed before: 2
> java.text.ParseException: Unparseable date: "2016-06-20T15:28:08.000"
> at java.text.DateFormat.parse(DateFormat.java:366)
> at
> org.apache.ambari.logfeeder.mapper.MapperDate.apply(MapperDate.java:83)
> at org.apache.ambari.logfeeder.filter.Filter.apply(Filter.java:154)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.applyMessage(FilterGrok.java:291)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.flush(FilterGrok.java:320)
> at org.apache.ambari.logfeeder.input.Input.flush(Input.java:125)
> at
> org.apache.ambari.logfeeder.input.InputFile.processFile(InputFile.java:430)
> at org.apache.ambari.logfeeder.input.InputFile.start(InputFile.java:260)
> at org.apache.ambari.logfeeder.input.Input.run(Input.java:100)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> ambari-audit.log is like below
> {code}
> 2016-07-21T01:52:49.875+09, User(admin), RemoteIp(192.168.72.1),
> Operation(Repository update), RequestType(PUT),
> url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu14/repositories/HDP-2.5),
> ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu14), Repo
> id(HDP-2.5), Base
> URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu14/2.x/BUILDS/2.5.0.0-1025)
> 2016-07-21T01:52:49.905+09, User(admin), RemoteIp(192.168.72.1),
> Operation(Repository update), RequestType(PUT),
> url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu16/repositories/HDP-2.5),
> ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu16), Repo
> id(HDP-2.5), Base
> URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu16/2.x/BUILDS/2.5.0.0-1025)
> 2016-07-21T01:52:50.015+09, User(admin), RemoteIp(192.168.72.1),
> Operation(Repository update), RequestType(PUT),
> url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu14/repositories/HDP-UTILS-1.1.0.21),
> ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu14), Repo
> id(HDP-UTILS-1.1.0.21), Base
> URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ubuntu14)
> {code}
> I think date format of the ambari-audit.log ({{2016-07-21T01:52:49.875+09}})
> should be like {{2016-07-21T01:52:49.875+0900}}, since grok-pattern can't
> handle {{2016-07-21T01:52:49.875+09}} format.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17291) zookeeper.quorum in storm-metrics2.properties is broken
[
https://issues.apache.org/jira/browse/AMBARI-17291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-17291:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thank you for the patch [~masatana]. I have pushed it to trunk.
{code}
commit 0079796ad541824db1cf9c72461da3e651cdd788
Author: Aravindan Vijayan
Date: Wed Jul 20 11:40:22 2016 -0700
AMBARI-17291 zookeeper.quorum in storm-metrics2.properties is broken
(Masahiro Tanaka via avijayan)
{code}
Please close the review.
> zookeeper.quorum in storm-metrics2.properties is broken
> ---
>
> Key: AMBARI-17291
> URL: https://issues.apache.org/jira/browse/AMBARI-17291
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, ambari-server
>Affects Versions: trunk
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-17291.1.patch, AMBARI-17291.patch
>
>
> When installed Storm and Ambari Metrics (and ZooKeeper, for dependency),
> {{zookeeper.quorum}} in /etc/storm/conf/storm-metrics2.properties is looks
> like this.
> {code}
> zookeeper.quorum=[:2181,':2181,c:2181,7:2181,2:2181,0:2181,1:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,2:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,3:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,]:2181
> {code}
> storm.zookeeper.servers is
> {{['c7201.ambari.apache.org','c7202.ambari.apache.org','c7203.ambari.apache.org']}}
> Steps to reproduce.
> Install Ambari Server (I used
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos7/2.x/latest/trunk/ambaribn.repo)
> Setup and start Ambari Server (ambari-server setup -s and ambari-server start)
> Install Storm and ZooKeeper via Ambari Server (HDP2.4)
> Install Ambari Metrics
> Restart all required
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17291) zookeeper.quorum in storm-metrics2.properties is broken
[
https://issues.apache.org/jira/browse/AMBARI-17291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-17291:
---
Fix Version/s: trunk
> zookeeper.quorum in storm-metrics2.properties is broken
> ---
>
> Key: AMBARI-17291
> URL: https://issues.apache.org/jira/browse/AMBARI-17291
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, ambari-server
>Affects Versions: trunk
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-17291.1.patch, AMBARI-17291.patch
>
>
> When installed Storm and Ambari Metrics (and ZooKeeper, for dependency),
> {{zookeeper.quorum}} in /etc/storm/conf/storm-metrics2.properties is looks
> like this.
> {code}
> zookeeper.quorum=[:2181,':2181,c:2181,7:2181,2:2181,0:2181,1:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,2:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,3:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,]:2181
> {code}
> storm.zookeeper.servers is
> {{['c7201.ambari.apache.org','c7202.ambari.apache.org','c7203.ambari.apache.org']}}
> Steps to reproduce.
> Install Ambari Server (I used
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos7/2.x/latest/trunk/ambaribn.repo)
> Setup and start Ambari Server (ambari-server setup -s and ambari-server start)
> Install Storm and ZooKeeper via Ambari Server (HDP2.4)
> Install Ambari Metrics
> Restart all required
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17308) Ambari Logfeeder outputs a lot of errors due to parse date
[
https://issues.apache.org/jira/browse/AMBARI-17308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17308:
-
Description:
In logsearch_feeder service log, we got errors like below
{code}
2016-06-20 15:28:09,368 ERROR file=ambari-audit.log
org.apache.ambari.logfeeder.mapper.MapperDate LogFeederUtil.java:356 - Error
applying date transformation. isEpoch=false,
dateFormat=-MM-dd'T'HH:mm:ss.SSSZ, value=2016-06-20T15:28:08.000.
mapClass=map_date, input=input:source=file,
path=/var/log/ambari-server/ambari-audit.log, fieldName=logtime. Messages
suppressed before: 2
java.text.ParseException: Unparseable date: "2016-06-20T15:28:08.000"
at java.text.DateFormat.parse(DateFormat.java:366)
at
org.apache.ambari.logfeeder.mapper.MapperDate.apply(MapperDate.java:83)
at org.apache.ambari.logfeeder.filter.Filter.apply(Filter.java:154)
at
org.apache.ambari.logfeeder.filter.FilterGrok.applyMessage(FilterGrok.java:291)
at
org.apache.ambari.logfeeder.filter.FilterGrok.flush(FilterGrok.java:320)
at org.apache.ambari.logfeeder.input.Input.flush(Input.java:125)
at
org.apache.ambari.logfeeder.input.InputFile.processFile(InputFile.java:430)
at org.apache.ambari.logfeeder.input.InputFile.start(InputFile.java:260)
at org.apache.ambari.logfeeder.input.Input.run(Input.java:100)
at java.lang.Thread.run(Thread.java:745)
{code}
ambari-audit.log is like below
{code}
2016-07-21T01:52:49.875+09, User(admin), RemoteIp(192.168.72.1),
Operation(Repository update), RequestType(PUT),
url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu14/repositories/HDP-2.5),
ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu14), Repo
id(HDP-2.5), Base
URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu14/2.x/BUILDS/2.5.0.0-1025)
2016-07-21T01:52:49.905+09, User(admin), RemoteIp(192.168.72.1),
Operation(Repository update), RequestType(PUT),
url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu16/repositories/HDP-2.5),
ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu16), Repo
id(HDP-2.5), Base
URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu16/2.x/BUILDS/2.5.0.0-1025)
2016-07-21T01:52:50.015+09, User(admin), RemoteIp(192.168.72.1),
Operation(Repository update), RequestType(PUT),
url(http://192.168.72.101:8080/api/v1/stacks/HDP/versions/2.5/operating_systems/ubuntu14/repositories/HDP-UTILS-1.1.0.21),
ResultStatus(200 OK), Stack(HDP), Stack version(2.5), OS(ubuntu14), Repo
id(HDP-UTILS-1.1.0.21), Base
URL(http://s3.amazonaws.com/dev.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ubuntu14)
{code}
I think date format of the ambari-audit.log ({{2016-07-21T01:52:49.875+09}})
should be like {{2016-07-21T01:52:49.875+0900}}, since grok-pattern can't
handle {{2016-07-21T01:52:49.875+09}} format.
was:
In logsearch_feeder service log, we got errors like below
{code}
2016-06-20 15:28:09,368 ERROR file=ambari-audit.log
org.apache.ambari.logfeeder.mapper.MapperDate LogFeederUtil.java:356 - Error
applying date transformation. isEpoch=false,
dateFormat=-MM-dd'T'HH:mm:ss.SSSZ, value=2016-06-20T15:28:08.000.
mapClass=map_date, input=input:source=file,
path=/var/log/ambari-server/ambari-audit.log, fieldName=logtime. Messages
suppressed before: 2
java.text.ParseException: Unparseable date: "2016-06-20T15:28:08.000"
at java.text.DateFormat.parse(DateFormat.java:366)
at
org.apache.ambari.logfeeder.mapper.MapperDate.apply(MapperDate.java:83)
at org.apache.ambari.logfeeder.filter.Filter.apply(Filter.java:154)
at
org.apache.ambari.logfeeder.filter.FilterGrok.applyMessage(FilterGrok.java:291)
at
org.apache.ambari.logfeeder.filter.FilterGrok.flush(FilterGrok.java:320)
at org.apache.ambari.logfeeder.input.Input.flush(Input.java:125)
at
org.apache.ambari.logfeeder.input.InputFile.processFile(InputFile.java:430)
at org.apache.ambari.logfeeder.input.InputFile.start(InputFile.java:260)
at org.apache.ambari.logfeeder.input.Input.run(Input.java:100)
at java.lang.Thread.run(Thread.java:745)
{code}
> Ambari Logfeeder outputs a lot of errors due to parse date
> --
>
> Key: AMBARI-17308
> URL: https://issues.apache.org/jira/browse/AMBARI-17308
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>
> In logsearch_feeder service log, we got errors like below
> {code}
> 2016-06-20 15:28:09,368 ERROR file=ambari-audit.log
> org.apache.ambari.logfeeder.mapper.MapperDate LogFeederUtil.java:356 - Error
> applying date transformation. isEpoch=false,
>
[jira] [Updated] (AMBARI-17798) RU/EU: Add falcon to as oozie admin user for 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-17798: Attachment: AMBARI-17798.patch > RU/EU: Add falcon to as oozie admin user for 2.5 > - > > Key: AMBARI-17798 > URL: https://issues.apache.org/jira/browse/AMBARI-17798 > Project: Ambari > Issue Type: Bug >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Attachments: AMBARI-17798.patch > > > AMBARI-17783 handles fresh install. Need to handle for EU/RU -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17783) Add falcon to oozie admin user for HDP 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-17783: Attachment: AMBARI-17798.patch > Add falcon to oozie admin user for HDP 2.5 > -- > > Key: AMBARI-17783 > URL: https://issues.apache.org/jira/browse/AMBARI-17783 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Murali Ramasami >Assignee: Venkat Ranganathan > Fix For: 2.4.0 > > Attachments: AMBARI-17783.patch > > > we need to add falcon and falcon-admin in the oozie_admin_users of oozie > advanced env section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17783) Add falcon to oozie admin user for HDP 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-17783: Attachment: (was: AMBARI-17798.patch) > Add falcon to oozie admin user for HDP 2.5 > -- > > Key: AMBARI-17783 > URL: https://issues.apache.org/jira/browse/AMBARI-17783 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Murali Ramasami >Assignee: Venkat Ranganathan > Fix For: 2.4.0 > > Attachments: AMBARI-17783.patch > > > we need to add falcon and falcon-admin in the oozie_admin_users of oozie > advanced env section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17817) Storm Ambari View should use proxy for secure clusters
[ https://issues.apache.org/jira/browse/AMBARI-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-17817: - Status: Patch Available (was: Open) > Storm Ambari View should use proxy for secure clusters > -- > > Key: AMBARI-17817 > URL: https://issues.apache.org/jira/browse/AMBARI-17817 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Attachments: AMBARI-17817.patch > > > We observed that in secure cluster where ambari has SSL configured. Storm > Ambari view fails to make http calls to Storm REST API as it won't be allowed > to make calls from https origin to http destination. > When we used ambari proxy this issue resolved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
