[jira] [Updated] (AMBARI-24535) File View not accessible in Ambari 2.7 after enabling 3 namenodes in HDP 3.0
[
https://issues.apache.org/jira/browse/AMBARI-24535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore updated AMBARI-24535:
---
Assignee: Nitiraj Singh Rathore
Status: Patch Available (was: Open)
Instead of hardcoded 2 namenodes, configurations now accept list of comma
separated namenode urls.
Manual testing done on 3 namenode cluster. Also test cases updated.
Submitted PR :
https://github.com/apache/ambari/pull/2351
https://github.com/apache/ambari/pull/2352
> File View not accessible in Ambari 2.7 after enabling 3 namenodes in HDP 3.0
>
>
> Key: AMBARI-24535
> URL: https://issues.apache.org/jira/browse/AMBARI-24535
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Nitiraj Singh Rathore
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *Ambari-2.7.0* supports HDFS Federation architecture
> But if we configure 3 namenode the Files view never works.
> It will fail with below exception
> {code:java}
> Service 'hdfs' check failed: HDFS080 webhdfs.ha.namenodes.list namenodes
> count is not exactly 2
> Service 'hdfs' check failed:
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS080
> webhdfs.ha.namenodes.list namenodes count is not exactly 2
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.copyHAProperties(ConfigurationBuilder.java:247)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.parseProperties(ConfigurationBuilder.java:110)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.buildConfig(ConfigurationBuilder.java:327)
>
> at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:75)
> at org.apache.ambari.view.utils.hdfs.HdfsUtil.getHdfsApi(HdfsUtil.java:157)
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.connectToHDFSApi(HdfsUtil.java:145)
>
> at
> org.apache.ambari.view.commons.hdfs.HdfsService.hdfsSmokeTest(HdfsService.java:145)
>
> at
> org.apache.ambari.view.filebrowser.HelpService.hdfsStatus(HelpService.java:95)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> {code}
> By inspecting the code , it looks like this is not supposed to work in
> filesview and it wil only allow two namenodes
> code :
> https://github.com/apache/ambari/blob/trunk/contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/ConfigurationBuilder.java#L247
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24535) File View not accessible in Ambari 2.7 after enabling 3 namenodes in HDP 3.0
[
https://issues.apache.org/jira/browse/AMBARI-24535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24535:
Labels: pull-request-available (was: )
> File View not accessible in Ambari 2.7 after enabling 3 namenodes in HDP 3.0
>
>
> Key: AMBARI-24535
> URL: https://issues.apache.org/jira/browse/AMBARI-24535
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
>
> *Ambari-2.7.0* supports HDFS Federation architecture
> But if we configure 3 namenode the Files view never works.
> It will fail with below exception
> {code:java}
> Service 'hdfs' check failed: HDFS080 webhdfs.ha.namenodes.list namenodes
> count is not exactly 2
> Service 'hdfs' check failed:
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS080
> webhdfs.ha.namenodes.list namenodes count is not exactly 2
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.copyHAProperties(ConfigurationBuilder.java:247)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.parseProperties(ConfigurationBuilder.java:110)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.buildConfig(ConfigurationBuilder.java:327)
>
> at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:75)
> at org.apache.ambari.view.utils.hdfs.HdfsUtil.getHdfsApi(HdfsUtil.java:157)
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.connectToHDFSApi(HdfsUtil.java:145)
>
> at
> org.apache.ambari.view.commons.hdfs.HdfsService.hdfsSmokeTest(HdfsService.java:145)
>
> at
> org.apache.ambari.view.filebrowser.HelpService.hdfsStatus(HelpService.java:95)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> {code}
> By inspecting the code , it looks like this is not supposed to work in
> filesview and it wil only allow two namenodes
> code :
> https://github.com/apache/ambari/blob/trunk/contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/ConfigurationBuilder.java#L247
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24665) Migrating grafana plugin for 5.x use
[ https://issues.apache.org/jira/browse/AMBARI-24665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24665. -- Resolution: Fixed > Migrating grafana plugin for 5.x use > > > Key: AMBARI-24665 > URL: https://issues.apache.org/jira/browse/AMBARI-24665 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24662) Log Search: add simple LDAP authentication support
[ https://issues.apache.org/jira/browse/AMBARI-24662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16621161#comment-16621161 ] Hudson commented on AMBARI-24662: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9985 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9985/]) AMBARI-24662. Log Search: add simple LDAP authentication support (#2347) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=990724ccde27574e2c87e852a3d4b6fb95d056bb]) * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/AuthPropsConfig.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/web/security/LogsearchAuthenticationProvider.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/resources/log4j.xml * (edit) ambari-logsearch/ambari-logsearch-server/src/main/resources/logsearch.properties * (add) ambari-logsearch/ambari-logsearch-server/src/test/java/org/apache/ambari/logsearch/common/LogSearchLdapAuthorityMapperTest.java * (edit) ambari-logsearch/docker/test-config/logsearch/logsearch-sso.properties * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/web/security/LogsearchAbstractAuthenticationProvider.java * (edit) ambari-logsearch/docker/test-config/logsearch/logsearch.properties * (edit) ambari-logsearch/docker/test-config/logsearch/logsearch-https.properties * (edit) ambari-logsearch/ambari-logsearch-server/pom.xml * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SecurityConfig.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/LogSearchLdapAuthConfig.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/web/security/LogsearchLdapAuthenticationProvider.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/common/LogSearchLdapAuthorityMapper.java > Log Search: add simple LDAP authentication support > -- > > Key: AMBARI-24662 > URL: https://issues.apache.org/jira/browse/AMBARI-24662 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24662) Log Search: add simple LDAP authentication support
[ https://issues.apache.org/jira/browse/AMBARI-24662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24662. --- Resolution: Fixed > Log Search: add simple LDAP authentication support > -- > > Key: AMBARI-24662 > URL: https://issues.apache.org/jira/browse/AMBARI-24662 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24665) Migrating grafana plugin for 5.x use
[ https://issues.apache.org/jira/browse/AMBARI-24665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24665: Labels: pull-request-available (was: ) > Migrating grafana plugin for 5.x use > > > Key: AMBARI-24665 > URL: https://issues.apache.org/jira/browse/AMBARI-24665 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24665) Migrating grafana plugin for 5.x use
Ishan Bhatt created AMBARI-24665: Summary: Migrating grafana plugin for 5.x use Key: AMBARI-24665 URL: https://issues.apache.org/jira/browse/AMBARI-24665 Project: Ambari Issue Type: Bug Components: ambari-metrics Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23466) Upgrade AMS Grafana version to 4.x
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-23466: --- Affects Version/s: (was: 3.0.0) 2.7.1 > Upgrade AMS Grafana version to 4.x > -- > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23466) Upgrade AMS Grafana version to 4.x
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-23466: -- Assignee: Aravindan Vijayan > Upgrade AMS Grafana version to 4.x > -- > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23466) Upgrade AMS Grafana version to 4.x
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-23466: --- Affects Version/s: (was: 2.7.1) > Upgrade AMS Grafana version to 4.x > -- > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23466) Upgrade AMS Grafana version to 4.x
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-23466: --- Fix Version/s: (was: 3.0.0) > Upgrade AMS Grafana version to 4.x > -- > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-18952) Register BackupObserver and BackupHFileCleaner
[ https://issues.apache.org/jira/browse/AMBARI-18952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884466#comment-15884466 ] Ted Yu edited comment on AMBARI-18952 at 9/19/18 5:40 PM: -- Note: There is cost when BackupObserver is registered - it would poll backup table (at the end of bulk load per region) for whether the underlying table has gone thru full backup. was (Author: yuzhih...@gmail.com): Note: There is cost when BackupObserver is registered - it would poll backup table (at the end of bulk load per region) for whether the underlying table has gone thru full backup . > Register BackupObserver and BackupHFileCleaner > -- > > Key: AMBARI-18952 > URL: https://issues.apache.org/jira/browse/AMBARI-18952 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Priority: Major > > Over in HBASE-14417, two new classes are added. > org.apache.hadoop.hbase.backup.BackupHFileCleaner should be registered > through hbase.master.hfilecleaner.plugins . It is responsible for keeping > bulk loaded hfiles so that incremental backup can pick them up. > org.apache.hadoop.hbase.backup.BackupObserver should be registered through > hbase.coprocessor.region.classes > It is notified when bulk load completes and writes records into hbase:backup > table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-18528) Need a way to escape config values that contain $
[
https://issues.apache.org/jira/browse/AMBARI-18528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603928#comment-15603928
]
Ted Yu edited comment on AMBARI-18528 at 9/19/18 5:40 PM:
--
Escaping the dollar sign automatically is a desirable solution .
was (Author: yuzhih...@gmail.com):
Escaping the dollar sign automatically is a desirable solution.
> Need a way to escape config values that contain $
> -
>
> Key: AMBARI-18528
> URL: https://issues.apache.org/jira/browse/AMBARI-18528
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
> Labels: zookeeper
>
> We tried specifying auth_to_local in zookeeper env input box:
> {code}
> export SERVER_JVMFLAGS="$SERVER_JVMFLAGS
> -Dzookeeper.security.auth_to_local=RULE:[2:$1@$0](hb...@c.net)s/.*/hbase/
> -Djava.security.auth.login.config={{zk_server_jaas_file}}"
> {code}
> However, when zookeeper quorum starts, the rule got interrupted with
> zkServer.sh
> We should add the capability of specifying auth_to_local in Ambari UI
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22965) Boolean#getBoolean is used to parse value
[
https://issues.apache.org/jira/browse/AMBARI-22965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-22965:
Description:
In StormTimelineMetricsReporter.java :
{code}
if (cf.containsKey(SET_INSTANCE_ID_PROPERTY)) {
setInstanceId =
Boolean.getBoolean(cf.get(SET_INSTANCE_ID_PROPERTY).toString());
{code}
According to
https://docs.oracle.com/javase/7/docs/api/java/lang/Boolean.html#getBoolean(java.lang.String):
{code}
Returns true if and only if the system property named by the argument exists
and is equal to the string "true"
{code}
This was not the intention of the quoted code.
FlumeTimelineMetricsSink.java may have the same issue.
was:
In StormTimelineMetricsReporter.java :
{code}
if (cf.containsKey(SET_INSTANCE_ID_PROPERTY)) {
setInstanceId =
Boolean.getBoolean(cf.get(SET_INSTANCE_ID_PROPERTY).toString());
{code}
According to
https://docs.oracle.com/javase/7/docs/api/java/lang/Boolean.html#getBoolean(java.lang.String):
{code}
Returns true if and only if the system property named by the argument exists
and is equal to the string "true"
{code}
This was not the intention of the quoted code.
FlumeTimelineMetricsSink.java may have the same issue.
> Boolean#getBoolean is used to parse value
> -
>
> Key: AMBARI-22965
> URL: https://issues.apache.org/jira/browse/AMBARI-22965
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
>
> In StormTimelineMetricsReporter.java :
> {code}
> if (cf.containsKey(SET_INSTANCE_ID_PROPERTY)) {
> setInstanceId =
> Boolean.getBoolean(cf.get(SET_INSTANCE_ID_PROPERTY).toString());
> {code}
> According to
> https://docs.oracle.com/javase/7/docs/api/java/lang/Boolean.html#getBoolean(java.lang.String):
> {code}
> Returns true if and only if the system property named by the argument exists
> and is equal to the string "true"
> {code}
> This was not the intention of the quoted code.
> FlumeTimelineMetricsSink.java may have the same issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24663) 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
[
https://issues.apache.org/jira/browse/AMBARI-24663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620866#comment-16620866
]
Hudson commented on AMBARI-24663:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #314 (See
[https://builds.apache.org/job/Ambari-branch-2.7/314/])
AMBARI-24663. 'ambari-server setup' does not use (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8d145e0c04917866fd76690688826cf44065370e])
* (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py
> 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
> -
>
> Key: AMBARI-24663
> URL: https://issues.apache.org/jira/browse/AMBARI-24663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> *STR*
> Installed ambari-server and configured password encryption, but chose not to
> persist master key
> {code}
> [root@h002 ~]# ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Password encryption is enabled.
> Do you want to reset Master Key? [y/n] (n): y
> Master Key not persisted.
> Enter current Master Key:
> Enter new Master Key:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? n
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {code}
> Then export environment variable
> export AMBARI_SECURITY_MASTER_KEY=hadoop
> ambari-server setup promts to enter current master key
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24664) Non-kerberized environment alert
Raffaele Saggino created AMBARI-24664: - Summary: Non-kerberized environment alert Key: AMBARI-24664 URL: https://issues.apache.org/jira/browse/AMBARI-24664 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Environment: |ZooKeeper|3.4.6| |Kafka|1.1.1| |Ranger|1.0.0| |Kerberos|1.10.3-30| Reporter: Raffaele Saggino I am running Ambari-Server on a kerberized environment and since a few days, while enabling "ranger-kafka-plugin-enabled" I receive the following warning: Ranger Kafka plugin should not be enabled in non-kerberos environment. Ambari thinks that the environment is not kerberized, a side effect of this problem seems to be Ambari not creating the repository on ranger (after Kafka has been enabled). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24662) Log Search: add simple LDAP authentication support
[ https://issues.apache.org/jira/browse/AMBARI-24662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24662: Labels: pull-request-available (was: ) > Log Search: add simple LDAP authentication support > -- > > Key: AMBARI-24662 > URL: https://issues.apache.org/jira/browse/AMBARI-24662 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24631) [Log Search UI] styles and layout fixes
[ https://issues.apache.org/jira/browse/AMBARI-24631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620558#comment-16620558 ] Hudson commented on AMBARI-24631: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9984 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9984/]) [AMBARI-24631] [Log Search UI] styles and layout fixes (#2339) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=544b07e74938584571c51ac0a109b2e6d4c33d78]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-histogram/time-histogram.component.html * (add) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/components/circle-progress-bar/circle-progress-bar.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/log-index-filter/log-index-filter.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/variables.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/log-message/log-message.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/service-logs-table/service-logs-table.component.html * (add) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/components/circle-progress-bar/circle-progress-bar.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/log-message/log-message.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-range-picker/time-range-picker.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/components/modal-dialog/modal-dialog.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/collapsible-panel/collapsible-panel.component.less * (edit) ambari-logsearch/ambari-logsearch-web/package.json * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/components/graph/time-graph.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/shared.module.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/service-logs-table/service-logs-table.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/components/graph/graph.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/assets/i18n/en.json * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/components/modal-dialog/modal-dialog.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-histogram/time-histogram.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/log-message/log-message.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/service-logs-table/service-logs-table.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/collapsible-panel/collapsible-panel.component.html * (add) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/components/circle-progress-bar/circle-progress-bar.component.less * (edit) ambari-logsearch/ambari-logsearch-web/yarn.lock * (add) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/components/circle-progress-bar/circle-progress-bar.component.html > [Log Search UI] styles and layout fixes > --- > > Key: AMBARI-24631 > URL: https://issues.apache.org/jira/browse/AMBARI-24631 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Original Estimate: 24h > Time Spent: 50h 10m > Remaining Estimate: 0h > > # Move number of events up on the page higher so it’s centered between the > top of the gray area and the beginning of the Histogram frame > # The message about triggering auto-refresh should be displayed in modal > dialog > # Filters panel should be a bit less transparent -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24663) 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
[
https://issues.apache.org/jira/browse/AMBARI-24663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24663:
Labels: pull-request-available (was: )
> 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
> -
>
> Key: AMBARI-24663
> URL: https://issues.apache.org/jira/browse/AMBARI-24663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
>
> *STR*
> Installed ambari-server and configured password encryption, but chose not to
> persist master key
> {code}
> [root@h002 ~]# ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Password encryption is enabled.
> Do you want to reset Master Key? [y/n] (n): y
> Master Key not persisted.
> Enter current Master Key:
> Enter new Master Key:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? n
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {code}
> Then export environment variable
> export AMBARI_SECURITY_MASTER_KEY=hadoop
> ambari-server setup promts to enter current master key
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
***UNCHECKED*** [jira] [Updated] (AMBARI-24663) 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
[
https://issues.apache.org/jira/browse/AMBARI-24663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-24663:
Component/s: ambari-server
> 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
> -
>
> Key: AMBARI-24663
> URL: https://issues.apache.org/jira/browse/AMBARI-24663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.7.2
>
>
> *STR*
> Installed ambari-server and configured password encryption, but chose not to
> persist master key
> {code}
> [root@h002 ~]# ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Password encryption is enabled.
> Do you want to reset Master Key? [y/n] (n): y
> Master Key not persisted.
> Enter current Master Key:
> Enter new Master Key:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? n
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {code}
> Then export environment variable
> export AMBARI_SECURITY_MASTER_KEY=hadoop
> ambari-server setup promts to enter current master key
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24663) 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
[
https://issues.apache.org/jira/browse/AMBARI-24663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-24663:
Fix Version/s: 2.7.2
> 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
> -
>
> Key: AMBARI-24663
> URL: https://issues.apache.org/jira/browse/AMBARI-24663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.7.2
>
>
> *STR*
> Installed ambari-server and configured password encryption, but chose not to
> persist master key
> {code}
> [root@h002 ~]# ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Password encryption is enabled.
> Do you want to reset Master Key? [y/n] (n): y
> Master Key not persisted.
> Enter current Master Key:
> Enter new Master Key:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? n
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {code}
> Then export environment variable
> export AMBARI_SECURITY_MASTER_KEY=hadoop
> ambari-server setup promts to enter current master key
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24663) 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
Dmitry Lysnichenko created AMBARI-24663:
---
Summary: 'ambari-server setup' does not use
AMBARI_SECURITY_MASTER_KEY env var
Key: AMBARI-24663
URL: https://issues.apache.org/jira/browse/AMBARI-24663
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
*STR*
Installed ambari-server and configured password encryption, but chose not to
persist master key
{code}
[root@h002 ~]# ambari-server setup-security
Using python /usr/bin/python
Security setup options...
===
Choose one of the following options:
[1] Enable HTTPS for Ambari server.
[2] Encrypt passwords stored in ambari.properties file.
[3] Setup Ambari kerberos JAAS configuration.
[4] Setup truststore.
[5] Import certificate to truststore.
===
Enter choice, (1-5): 2
Password encryption is enabled.
Do you want to reset Master Key? [y/n] (n): y
Master Key not persisted.
Enter current Master Key:
Enter new Master Key:
Re-enter master key:
Do you want to persist master key. If you choose not to persist, you need to
provide the Master Key while starting the ambari server as an env variable
named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
Persist [y/n] (y)? n
Adjusting ambari-server permissions and ownership...
Ambari Server 'setup-security' completed successfully.
{code}
Then export environment variable
export AMBARI_SECURITY_MASTER_KEY=hadoop
ambari-server setup promts to enter current master key
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24663) 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
[
https://issues.apache.org/jira/browse/AMBARI-24663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-24663:
Affects Version/s: 2.7.1
> 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
> -
>
> Key: AMBARI-24663
> URL: https://issues.apache.org/jira/browse/AMBARI-24663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.7.2
>
>
> *STR*
> Installed ambari-server and configured password encryption, but chose not to
> persist master key
> {code}
> [root@h002 ~]# ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Password encryption is enabled.
> Do you want to reset Master Key? [y/n] (n): y
> Master Key not persisted.
> Enter current Master Key:
> Enter new Master Key:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? n
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {code}
> Then export environment variable
> export AMBARI_SECURITY_MASTER_KEY=hadoop
> ambari-server setup promts to enter current master key
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24662) Log Search: add simple LDAP authentication support
Olivér Szabó created AMBARI-24662: - Summary: Log Search: add simple LDAP authentication support Key: AMBARI-24662 URL: https://issues.apache.org/jira/browse/AMBARI-24662 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24648) Log Search: add simple file based authorization
[ https://issues.apache.org/jira/browse/AMBARI-24648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24648. --- Resolution: Fixed > Log Search: add simple file based authorization > > > Key: AMBARI-24648 > URL: https://issues.apache.org/jira/browse/AMBARI-24648 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Make a simple way to authorize users. > At fist just create a simple one where you can list to users (who can be > admin or simple user) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
***UNCHECKED*** [jira] [Updated] (AMBARI-24661) While registering agent can miss updates from server
[ https://issues.apache.org/jira/browse/AMBARI-24661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24661: Labels: pull-request-available (was: ) > While registering agent can miss updates from server > > > Key: AMBARI-24661 > URL: https://issues.apache.org/jira/browse/AMBARI-24661 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24661.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24661) While registering agent can miss updates from server
Andrew Onischuk created AMBARI-24661: Summary: While registering agent can miss updates from server Key: AMBARI-24661 URL: https://issues.apache.org/jira/browse/AMBARI-24661 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.2 Attachments: AMBARI-24661.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24661) While registering agent can miss updates from server
[ https://issues.apache.org/jira/browse/AMBARI-24661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24661: - Attachment: AMBARI-24661.patch > While registering agent can miss updates from server > > > Key: AMBARI-24661 > URL: https://issues.apache.org/jira/browse/AMBARI-24661 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24661.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24661) While registering agent can miss updates from server
[ https://issues.apache.org/jira/browse/AMBARI-24661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24661: - Status: Patch Available (was: Open) > While registering agent can miss updates from server > > > Key: AMBARI-24661 > URL: https://issues.apache.org/jira/browse/AMBARI-24661 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.2 > > Attachments: AMBARI-24661.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-20390: Labels: pull-request-available (was: ) > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: WangJie >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-20390.patch, screenshot-1.png > > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24660) Request Schedule proceeds with next task despite tolerance being 0
Sandeep Kumar created AMBARI-24660:
--
Summary: Request Schedule proceeds with next task despite
tolerance being 0
Key: AMBARI-24660
URL: https://issues.apache.org/jira/browse/AMBARI-24660
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.1
Environment: centos
Reporter: Sandeep Kumar
Attachments: test.json
Request Schedule does not honor task_failure_tolerance value of 0, when
service component isn't present on host and moves to the next task.
*STEPS TO REPRO*
Download attached test.json file, create a cluster with a custom service and
run these command.
AMBARI_SERVER_HOST=c7001.ambari.apache.org
CLUSTER_NAME=test-cluster
USERNAME=admin
PASSWORD=admin
AMBARI_SERVER_PORT=8080
AMBARI_SERVER_PROTOCOL=http
curl -u $USERNAME:$PASSWORD -H "X-Requested-By: ambari" -X POST -d @test.json
$AMBARI_SERVER_PROTOCOL://$AMBARI_SERVER_HOST:$AMBARI_SERVER_PORT/api/v1/clusters/$CLUSTER_NAME/request_schedules
SERVER LOGS EXCEPTION
19 Sep 2018 06:56:24,841 INFO [ambari-client-thread-812]
AmbariManagementControllerImpl:4174 - Received action execution request,
clusterName=test-cluster, request=isCommand :true, action :null, command
:STOP_KRB_MASTER_USING_CC, inputs :\{HAS_RESOURCE_FILTERS=true},
resourceFilters: [RequestResourceFilter\{serviceName='MY_CUSTOM_SERVICE',
componentName='MY_CUSTOM_SERVICE_COMPONENT',
hostNames=[c7001.ambari.apache.org]}], exclusive: false, clusterName
:test-cluster
19 Sep 2018 06:56:24,846 ERROR [ambari-client-thread-812]
AbstractResourceProvider:285 - Caught AmbariException when creating a resource
org.apache.ambari.server.ServiceComponentHostNotFoundException:
ServiceComponentHost not found, clusterName=test-cluster,
serviceName=MY_CUSTOM_SERVICE,
serviceComponentName=MY_CUSTOM_SERVICE_COMPONENT,
hostName=c7001.ambari.apache.org
at
org.apache.ambari.server.state.ServiceComponentImpl.getServiceComponentHost(ServiceComponentImpl.java:322)
at
org.apache.ambari.server.controller.MaintenanceStateHelper.isOperationAllowed(MaintenanceStateHelper.java:112)
at
org.apache.ambari.server.controller.MaintenanceStateHelper.isOperationAllowed(MaintenanceStateHelper.java:88)
at
org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper$1.shouldHostBeRemoved(AmbariCustomCommandExecutionHelper.java:290)
at
org.apache.ambari.server.controller.MaintenanceStateHelper.filterHostsInMaintenanceState(MaintenanceStateHelper.java:424)
at
org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.addCustomCommandAction(AmbariCustomCommandExecutionHelper.java:285)
at
org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.addExecutionCommandsToStage(AmbariCustomCommandExecutionHelper.java:1192)
at
org.apache.ambari.server.controller.AmbariManagementControllerImpl.createAction(AmbariManagementControllerImpl.java:4229)
at
org.apache.ambari.server.controller.internal.RequestResourceProvider$1.invoke(RequestResourceProvider.java:264)
at
org.apache.ambari.server.controller.internal.RequestResourceProvider$1.invoke(RequestResourceProvider.java:193)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:455)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:278)
at
org.apache.ambari.server.controller.internal.RequestResourceProvider.createResources(RequestResourceProvider.java:193)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
at
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
at
org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
at
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
at
org.apache.ambari.server.api.services.RequestService.createRequests(RequestService.java:145)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
