[jira] [Updated] (AMBARI-23017) [PERF] Deployment of PERF stack leads to Out of Sync
[ https://issues.apache.org/jira/browse/AMBARI-23017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23017: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > [PERF] Deployment of PERF stack leads to Out of Sync > > > Key: AMBARI-23017 > URL: https://issues.apache.org/jira/browse/AMBARI-23017 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-23017.patch > > Time Spent: 1h 40m > Remaining Estimate: 0h > > While deploying PERF stack, PERF 1.0 stack is not installed and shows up as > Out of sync -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22962) Ambari Upgrade: LogSearch + Ambari Infra (2.6 -> 2.7)
[ https://issues.apache.org/jira/browse/AMBARI-22962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369778#comment-16369778 ] Hudson commented on AMBARI-22962: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8754 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8754/]) AMBARI-22962. ADDENDUM - move directories theme json file (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ee603f27c81b447e16112a7190e8c0d996680cd4]) * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/themes/directories.json * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/themes/directories.json > Ambari Upgrade: LogSearch + Ambari Infra (2.6 -> 2.7) > - > > Key: AMBARI-22962 > URL: https://issues.apache.org/jira/browse/AMBARI-22962 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra, ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23027) Add backup/copy znode command for infra-solr-client
Olivér Szabó created AMBARI-23027: - Summary: Add backup/copy znode command for infra-solr-client Key: AMBARI-23027 URL: https://issues.apache.org/jira/browse/AMBARI-23027 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-22951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22951: - Resolution: Fixed Status: Resolved (was: Patch Available) > Export JAVA_HOME env variable in shell script for Ranger > > > Key: AMBARI-22951 > URL: https://issues.apache.org/jira/browse/AMBARI-22951 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-22951.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Need to export JAVA_HOME variable in ranger-admin-env.sh, so that > [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] > knows which java to be used for processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23026) WEB type alerts authentication in Kerberos secured cluster
David F. Quiroga created AMBARI-23026: - Summary: WEB type alerts authentication in Kerberos secured cluster Key: AMBARI-23026 URL: https://issues.apache.org/jira/browse/AMBARI-23026 Project: Ambari Issue Type: Bug Components: alerts Affects Versions: 2.5.2, trunk, 2.6.2 Environment: Ambari 2.5.2 Hortonworks HDP-2.5.3.0-37 Reporter: David F. Quiroga In a Kerberized cluster some web endpoints (App Timeline Web UI, ResourceManger Web UI, etc.) require authentication. Any Ambari alerts checking those endpoints must then be able to authenticate. This was addressed in AMBARI-9586, however the default principal and keytab used in the alerts.json is that of the "bare" SPNEGO principal HTTP/_HOST@REALM. My understanding is that the HTTP service principal is used to authenticate users to a service, not used to authenticate to another service. 1. Since most endpoints involved are Web UI, would it be more appropriate to use the smokeuser in the alerts? 2. This was first observed in Ranger Audit, the YARN Ranger Plug-in showed many access denied from HTTP user. [This post|https://community.hortonworks.com/content/supportkb/150206/ranger-audit-logs-refers-to-access-denied-for-http.html] provided some direction as to where those requests were coming from. We have updated the ResourceManger Web UI alert definition to use cluster-env/smokeuser_keytab and cluster-env/smokeuser_principal_name and this has resolved the initial HTTP access denied. Would it also be advisable to make the change in the other secure Web UI alert definitions? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22897) Tez view button doesnt works in ambari views 1.5
[ https://issues.apache.org/jira/browse/AMBARI-22897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369705#comment-16369705 ] Akhil S Naik commented on AMBARI-22897: --- In Hive views 1.5 we are using the .render into method After the upgrade of ember to version 1.11.4 its causing this BUG of ember : https://github.com/emberjs/ember.js/issues/10780 Need to workaround as emberjs is currently depreciating the render into . > Tez view button doesnt works in ambari views 1.5 > > > Key: AMBARI-22897 > URL: https://issues.apache.org/jira/browse/AMBARI-22897 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 > Environment: Ambari 2.6.1 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Attachments: Screen Shot 2018-02-01 at 8.00.17 PM.png > > > *Issue :* > Login to ambari version 2.6.1 navigate to hive view 1.5 > When click on tez button or visualization or visual explain or settings > button > the page throws a script error and it become a blank page > *Root Cause :* > when click on the tez button, visualization or any other side button , > the following error is thrown from ember : > Assertion Failed: You attempted to render into 'index' but it was not found > attached the image error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22897) Tez view button doesnt works in ambari views 1.5
[ https://issues.apache.org/jira/browse/AMBARI-22897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik reassigned AMBARI-22897: - Assignee: Akhil S Naik > Tez view button doesnt works in ambari views 1.5 > > > Key: AMBARI-22897 > URL: https://issues.apache.org/jira/browse/AMBARI-22897 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 > Environment: Ambari 2.6.1 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Attachments: Screen Shot 2018-02-01 at 8.00.17 PM.png > > > *Issue :* > Login to ambari version 2.6.1 navigate to hive view 1.5 > When click on tez button or visualization or visual explain or settings > button > the page throws a script error and it become a blank page > *Root Cause :* > when click on the tez button, visualization or any other side button , > the following error is thrown from ember : > Assertion Failed: You attempted to render into 'index' but it was not found > attached the image error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23019) Use lucene version 6.6.2 instead of 6.6.0 in index migration script
[ https://issues.apache.org/jira/browse/AMBARI-23019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23019. --- Resolution: Fixed > Use lucene version 6.6.2 instead of 6.6.0 in index migration script > --- > > Key: AMBARI-23019 > URL: https://issues.apache.org/jira/browse/AMBARI-23019 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23019) Use lucene version 6.6.2 instead of 6.6.0 in index migration script
[ https://issues.apache.org/jira/browse/AMBARI-23019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369580#comment-16369580 ] Hudson commented on AMBARI-23019: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #8753 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8753/]) AMBARI-23019. Use lucene version 6.6.2 instead of 6.6.0 in index (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2644a3947c66cd13473a24f1bf8c6b161f56ca17]) * (edit) ambari-infra/ambari-infra-solr-client/pom.xml * (edit) ambari-infra/ambari-infra-solr-client/src/main/resources/solrIndexHelper.sh > Use lucene version 6.6.2 instead of 6.6.0 in index migration script > --- > > Key: AMBARI-23019 > URL: https://issues.apache.org/jira/browse/AMBARI-23019 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22962) Ambari Upgrade: LogSearch + Ambari Infra (2.6 -> 2.7)
[ https://issues.apache.org/jira/browse/AMBARI-22962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369581#comment-16369581 ] Hudson commented on AMBARI-22962: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #8753 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8753/]) [AMBARI-22962] - Ambari Upgrade: LogSearch + Ambari Infra (2.6 -> 2.7) (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=147330c6c4cbe73fd3212150ad48282846fc83ee]) * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/metainfo.xml * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/templates/infra-solr-security.json.j2 * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/scripts/infra_solr_client.py * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/quicklinks/quicklinks.json * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/configuration/infra-solr-log4j.xml * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/configuration/infra-solr-xml.xml * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/templates/infra_solr_jaas.conf.j2 * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/status_params.py * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/templates/infra-solr-security.json.j2 * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/kerberos.json * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/templates/input.config-ambari-infra.json.j2 * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/properties/solr-client-log4j.properties.j2 * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/scripts/status_params.py * (delete) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/AMBARI_INFRA/metainfo.xml * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/configuration/infra-solr-env.xml * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/scripts/params.py * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/role_command_order.json * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/service_advisor.py * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/configuration/infra-solr-xml.xml * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/alerts.json * (edit) ambari-server/src/main/resources/common-services/RANGER/0.6.0/kerberos.json * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/configuration/infra-solr-security-json.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/AMBARI_INFRA_SOLR/metainfo.xml * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/scripts/service_check.py * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/themes/theme.json * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/kerberos.json * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/role_command_order.json * (add) ambari-server/src/test/resources/org/apache/ambari/server/upgrade/kerberos_descriptor.json * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr.py * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/themes/theme.json * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog270Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog270.java * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr_client.py * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/alerts.json * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/configuration/infra-solr-client-log4j.xml * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/properties/infra-solr-env.sh.j2 * (delete) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/properties/solr-log4j.properties.j2 * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/configuration/infra-solr-client-log4j.xml * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/params.py * (add) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/configuration/infra-solr-security-json.xml * (add)
[jira] [Commented] (AMBARI-23022) Ambari UI deploy fails during startup of Ambari Metrics
[
https://issues.apache.org/jira/browse/AMBARI-23022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369401#comment-16369401
]
Hudson commented on AMBARI-23022:
-
ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #8752 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8752/])
AMBARI-23022 : Ambari UI deploy fails during startup of Ambari Metrics.
(avijayan:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=95fe6549e09b15a5872c4a79ce027c5cef2ff190])
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/hadoop-metrics2-hbase.properties.j2
> Ambari UI deploy fails during startup of Ambari Metrics
> ---
>
> Key: AMBARI-23022
> URL: https://issues.apache.org/jira/browse/AMBARI-23022
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> HDP version:HDP-3.0.0.0-702
> Ambari version: 2.99.99.0-77
> {noformat}
> /var/lib/ambari-agent/data/errors-52.txt:
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 90, in
> AmsCollector().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 371, in execute
> self.execute_prefix_function(self.command_name, 'post', env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 392, in execute_prefix_function
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 434, in post_start
> raise Fail("Pid file {0} doesn't exist after starting of the
> component.".format(pid_file))
> resource_management.core.exceptions.Fail: Pid file
> /var/run/ambari-metrics-collector//hbase-ams-master.pid doesn't exist after
> starting of the component.
> {noformat}
> /var/lib/ambari-agent/data/output-52.txt:
> {noformat}
> 2018-01-11 13:03:40,753 - Stack Feature Version Info: Cluster Stack=3.0,
> Command Stack=None, Command Version=3.0.0.0-702 -> 3.0.0.0-702
> 2018-01-11 13:03:40,755 - Using hadoop conf dir:
> /usr/hdp/3.0.0.0-702/hadoop/conf
> 2018-01-11 13:03:40,884 - Stack Feature Version Info: Cluster Stack=3.0,
> Command Stack=None, Command Version=3.0.0.0-702 -> 3.0.0.0-702
> 2018-01-11 13:03:40,885 - Using hadoop conf dir:
> /usr/hdp/3.0.0.0-702/hadoop/conf
> 2018-01-11 13:03:40,886 - Group['hdfs'] {}
> 2018-01-11 13:03:40,887 - Group['hadoop'] {}
> 2018-01-11 13:03:40,887 - Group['users'] {}
> 2018-01-11 13:03:40,887 - User['hive'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,890 - User['infra-solr'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,891 - User['zookeeper'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,892 - User['atlas'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,893 - User['ams'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,893 - User['ambari-qa'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'users'], 'uid': None}
> 2018-01-11 13:03:40,894 - User['kafka'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,894 - User['tez'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'users'], 'uid': None}
> 2018-01-11 13:03:40,895 - User['hdfs'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
> 2018-01-11 13:03:40,895 - User['yarn'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,896 - User['mapred'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,897 - User['hbase'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,897 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2018-01-11 13:03:40,898 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2018-01-11 13:03:40,903 - Skipping
>
[jira] [Updated] (AMBARI-23025) NN Federation Wizard: implement step2
[ https://issues.apache.org/jira/browse/AMBARI-23025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23025: Labels: pull-request-available (was: ) > NN Federation Wizard: implement step2 > - > > Key: AMBARI-23025 > URL: https://issues.apache.org/jira/browse/AMBARI-23025 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > > Provide step2 with ability for user to select hosts for new host components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23025) NN Federation Wizard: implement step2
Aleksandr Kovalenko created AMBARI-23025: Summary: NN Federation Wizard: implement step2 Key: AMBARI-23025 URL: https://issues.apache.org/jira/browse/AMBARI-23025 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Provide step2 with ability for user to select hosts for new host components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22998) Wrong user used to execute the Spark/Livy Server service check
[
https://issues.apache.org/jira/browse/AMBARI-22998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22998:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Wrong user used to execute the Spark/Livy Server service check
> --
>
> Key: AMBARI-22998
> URL: https://issues.apache.org/jira/browse/AMBARI-22998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.6.2, 2.7.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> {code:title=common-services/SPARK/1.2.1/package/scripts/service_check.py:36}
> livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> Execute(livy_kinit_cmd, user=params.livy_user)
> {code}
> Notice the Kerberos identity is for the smoke user, but the exec is for the
> livy user. This will replace the livy user's interactive Kerberos ticket
> cache.
> This should be
> {code}
> smoke_user_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> Execute(smoke_user_kinit_cmd, user=params.smoke_user)
> {code}
> Where {{smoke_user}} is
> {code}
> smoke_user = config['configurations']['cluster-env']['smokeuser']
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23024) Log Serach UI: Implement Metadata patterns screen
Istvan Tobias created AMBARI-23024: -- Summary: Log Serach UI: Implement Metadata patterns screen Key: AMBARI-23024 URL: https://issues.apache.org/jira/browse/AMBARI-23024 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Implement a feature where the user can list all the metadata patterns and can add new or edit an existing one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23023) Lifecycle-Bulk: BE allows deletion of all the instances of a component
Attila Magyar created AMBARI-23023: -- Summary: Lifecycle-Bulk: BE allows deletion of all the instances of a component Key: AMBARI-23023 URL: https://issues.apache.org/jira/browse/AMBARI-23023 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Attila Magyar Assignee: Attila Magyar Fix For: 3.0.0, 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23017) [PERF] Deployment of PERF stack leads to Out of Sync
[ https://issues.apache.org/jira/browse/AMBARI-23017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369197#comment-16369197 ] Hudson commented on AMBARI-23017: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #616 (See [https://builds.apache.org/job/Ambari-branch-2.6/616/]) AMBARI-23017. [PERF] Deployment of PERF stack leads to Out of Sync (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=cc5063876e6365156c34cedcf6730d2f65ff59f8]) * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/properties/stack_packages.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/AMBARI_METRICS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHDFS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHBASE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEZOOKEEPER/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEYARN/metainfo.xml > [PERF] Deployment of PERF stack leads to Out of Sync > > > Key: AMBARI-23017 > URL: https://issues.apache.org/jira/browse/AMBARI-23017 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-23017.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > > While deploying PERF stack, PERF 1.0 stack is not installed and shows up as > Out of sync -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23020) Missing LDAP configuration property warning should be a debug statement
[
https://issues.apache.org/jira/browse/AMBARI-23020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23020:
Labels: pull-request-available (was: )
> Missing LDAP configuration property warning should be a debug statement
> ---
>
> Key: AMBARI-23020
> URL: https://issues.apache.org/jira/browse/AMBARI-23020
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> Missing LDAP configuration property warning should be a debug statement. The
> Ambari server log is being filled with statements like:
> {noformat}
>
> 16 Feb 2018 14:01:36,617 WARN [main] AmbariLdapConfiguration:47 - Ldap
> configuration property [ambari.ldap.connectivity.server.host] hasn't been
> set; using default value
> {noformat}
> The log level for these messages should be lowered to at least DEBUG.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23022) Ambari UI deploy fails during startup of Ambari Metrics
[
https://issues.apache.org/jira/browse/AMBARI-23022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan resolved AMBARI-23022.
Resolution: Fixed
Pushed to trunk.
> Ambari UI deploy fails during startup of Ambari Metrics
> ---
>
> Key: AMBARI-23022
> URL: https://issues.apache.org/jira/browse/AMBARI-23022
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> HDP version:HDP-3.0.0.0-702
> Ambari version: 2.99.99.0-77
> {noformat}
> /var/lib/ambari-agent/data/errors-52.txt:
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 90, in
> AmsCollector().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 371, in execute
> self.execute_prefix_function(self.command_name, 'post', env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 392, in execute_prefix_function
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 434, in post_start
> raise Fail("Pid file {0} doesn't exist after starting of the
> component.".format(pid_file))
> resource_management.core.exceptions.Fail: Pid file
> /var/run/ambari-metrics-collector//hbase-ams-master.pid doesn't exist after
> starting of the component.
> {noformat}
> /var/lib/ambari-agent/data/output-52.txt:
> {noformat}
> 2018-01-11 13:03:40,753 - Stack Feature Version Info: Cluster Stack=3.0,
> Command Stack=None, Command Version=3.0.0.0-702 -> 3.0.0.0-702
> 2018-01-11 13:03:40,755 - Using hadoop conf dir:
> /usr/hdp/3.0.0.0-702/hadoop/conf
> 2018-01-11 13:03:40,884 - Stack Feature Version Info: Cluster Stack=3.0,
> Command Stack=None, Command Version=3.0.0.0-702 -> 3.0.0.0-702
> 2018-01-11 13:03:40,885 - Using hadoop conf dir:
> /usr/hdp/3.0.0.0-702/hadoop/conf
> 2018-01-11 13:03:40,886 - Group['hdfs'] {}
> 2018-01-11 13:03:40,887 - Group['hadoop'] {}
> 2018-01-11 13:03:40,887 - Group['users'] {}
> 2018-01-11 13:03:40,887 - User['hive'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,890 - User['infra-solr'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,891 - User['zookeeper'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,892 - User['atlas'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,893 - User['ams'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,893 - User['ambari-qa'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'users'], 'uid': None}
> 2018-01-11 13:03:40,894 - User['kafka'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,894 - User['tez'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'users'], 'uid': None}
> 2018-01-11 13:03:40,895 - User['hdfs'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
> 2018-01-11 13:03:40,895 - User['yarn'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,896 - User['mapred'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,897 - User['hbase'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,897 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2018-01-11 13:03:40,898 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2018-01-11 13:03:40,903 - Skipping
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] due to not_if
> 2018-01-11 13:03:40,903 - Directory['/tmp/hbase-hbase'] {'owner': 'hbase',
> 'create_parents': True, 'mode': 0775, 'cd_access': 'a'}
> 2018-01-11 13:03:40,904 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content':
[jira] [Updated] (AMBARI-23022) Ambari UI deploy fails during startup of Ambari Metrics
[
https://issues.apache.org/jira/browse/AMBARI-23022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23022:
Labels: pull-request-available (was: )
> Ambari UI deploy fails during startup of Ambari Metrics
> ---
>
> Key: AMBARI-23022
> URL: https://issues.apache.org/jira/browse/AMBARI-23022
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> HDP version:HDP-3.0.0.0-702
> Ambari version: 2.99.99.0-77
> {noformat}
> /var/lib/ambari-agent/data/errors-52.txt:
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 90, in
> AmsCollector().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 371, in execute
> self.execute_prefix_function(self.command_name, 'post', env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 392, in execute_prefix_function
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 434, in post_start
> raise Fail("Pid file {0} doesn't exist after starting of the
> component.".format(pid_file))
> resource_management.core.exceptions.Fail: Pid file
> /var/run/ambari-metrics-collector//hbase-ams-master.pid doesn't exist after
> starting of the component.
> {noformat}
> /var/lib/ambari-agent/data/output-52.txt:
> {noformat}
> 2018-01-11 13:03:40,753 - Stack Feature Version Info: Cluster Stack=3.0,
> Command Stack=None, Command Version=3.0.0.0-702 -> 3.0.0.0-702
> 2018-01-11 13:03:40,755 - Using hadoop conf dir:
> /usr/hdp/3.0.0.0-702/hadoop/conf
> 2018-01-11 13:03:40,884 - Stack Feature Version Info: Cluster Stack=3.0,
> Command Stack=None, Command Version=3.0.0.0-702 -> 3.0.0.0-702
> 2018-01-11 13:03:40,885 - Using hadoop conf dir:
> /usr/hdp/3.0.0.0-702/hadoop/conf
> 2018-01-11 13:03:40,886 - Group['hdfs'] {}
> 2018-01-11 13:03:40,887 - Group['hadoop'] {}
> 2018-01-11 13:03:40,887 - Group['users'] {}
> 2018-01-11 13:03:40,887 - User['hive'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,890 - User['infra-solr'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,891 - User['zookeeper'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,892 - User['atlas'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,893 - User['ams'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,893 - User['ambari-qa'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'users'], 'uid': None}
> 2018-01-11 13:03:40,894 - User['kafka'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,894 - User['tez'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'users'], 'uid': None}
> 2018-01-11 13:03:40,895 - User['hdfs'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
> 2018-01-11 13:03:40,895 - User['yarn'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,896 - User['mapred'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,897 - User['hbase'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,897 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2018-01-11 13:03:40,898 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2018-01-11 13:03:40,903 - Skipping
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] due to not_if
> 2018-01-11 13:03:40,903 - Directory['/tmp/hbase-hbase'] {'owner': 'hbase',
> 'create_parents': True, 'mode': 0775, 'cd_access': 'a'}
> 2018-01-11 13:03:40,904 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2018-01-11
[jira] [Assigned] (AMBARI-23022) Ambari UI deploy fails during startup of Ambari Metrics
[
https://issues.apache.org/jira/browse/AMBARI-23022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan reassigned AMBARI-23022:
--
Assignee: Aravindan Vijayan
> Ambari UI deploy fails during startup of Ambari Metrics
> ---
>
> Key: AMBARI-23022
> URL: https://issues.apache.org/jira/browse/AMBARI-23022
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Major
>
> {noformat}
> HDP version:HDP-3.0.0.0-702
> Ambari version: 2.99.99.0-77
> {noformat}
> /var/lib/ambari-agent/data/errors-52.txt:
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 90, in
> AmsCollector().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 371, in execute
> self.execute_prefix_function(self.command_name, 'post', env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 392, in execute_prefix_function
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 434, in post_start
> raise Fail("Pid file {0} doesn't exist after starting of the
> component.".format(pid_file))
> resource_management.core.exceptions.Fail: Pid file
> /var/run/ambari-metrics-collector//hbase-ams-master.pid doesn't exist after
> starting of the component.
> {noformat}
> /var/lib/ambari-agent/data/output-52.txt:
> {noformat}
> 2018-01-11 13:03:40,753 - Stack Feature Version Info: Cluster Stack=3.0,
> Command Stack=None, Command Version=3.0.0.0-702 -> 3.0.0.0-702
> 2018-01-11 13:03:40,755 - Using hadoop conf dir:
> /usr/hdp/3.0.0.0-702/hadoop/conf
> 2018-01-11 13:03:40,884 - Stack Feature Version Info: Cluster Stack=3.0,
> Command Stack=None, Command Version=3.0.0.0-702 -> 3.0.0.0-702
> 2018-01-11 13:03:40,885 - Using hadoop conf dir:
> /usr/hdp/3.0.0.0-702/hadoop/conf
> 2018-01-11 13:03:40,886 - Group['hdfs'] {}
> 2018-01-11 13:03:40,887 - Group['hadoop'] {}
> 2018-01-11 13:03:40,887 - Group['users'] {}
> 2018-01-11 13:03:40,887 - User['hive'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,890 - User['infra-solr'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,891 - User['zookeeper'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,892 - User['atlas'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,893 - User['ams'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,893 - User['ambari-qa'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'users'], 'uid': None}
> 2018-01-11 13:03:40,894 - User['kafka'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,894 - User['tez'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'users'], 'uid': None}
> 2018-01-11 13:03:40,895 - User['hdfs'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
> 2018-01-11 13:03:40,895 - User['yarn'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,896 - User['mapred'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,897 - User['hbase'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-01-11 13:03:40,897 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2018-01-11 13:03:40,898 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2018-01-11 13:03:40,903 - Skipping
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] due to not_if
> 2018-01-11 13:03:40,903 - Directory['/tmp/hbase-hbase'] {'owner': 'hbase',
> 'create_parents': True, 'mode': 0775, 'cd_access': 'a'}
> 2018-01-11 13:03:40,904 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2018-01-11 13:03:40,905 -
[jira] [Created] (AMBARI-23022) Ambari UI deploy fails during startup of Ambari Metrics
Aravindan Vijayan created AMBARI-23022:
--
Summary: Ambari UI deploy fails during startup of Ambari Metrics
Key: AMBARI-23022
URL: https://issues.apache.org/jira/browse/AMBARI-23022
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 3.0.0
Reporter: Aravindan Vijayan
{noformat}
HDP version:HDP-3.0.0.0-702
Ambari version: 2.99.99.0-77
{noformat}
/var/lib/ambari-agent/data/errors-52.txt:
{noformat}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 90, in
AmsCollector().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 371, in execute
self.execute_prefix_function(self.command_name, 'post', env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 392, in execute_prefix_function
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 434, in post_start
raise Fail("Pid file {0} doesn't exist after starting of the
component.".format(pid_file))
resource_management.core.exceptions.Fail: Pid file
/var/run/ambari-metrics-collector//hbase-ams-master.pid doesn't exist after
starting of the component.
{noformat}
/var/lib/ambari-agent/data/output-52.txt:
{noformat}
2018-01-11 13:03:40,753 - Stack Feature Version Info: Cluster Stack=3.0,
Command Stack=None, Command Version=3.0.0.0-702 -> 3.0.0.0-702
2018-01-11 13:03:40,755 - Using hadoop conf dir:
/usr/hdp/3.0.0.0-702/hadoop/conf
2018-01-11 13:03:40,884 - Stack Feature Version Info: Cluster Stack=3.0,
Command Stack=None, Command Version=3.0.0.0-702 -> 3.0.0.0-702
2018-01-11 13:03:40,885 - Using hadoop conf dir:
/usr/hdp/3.0.0.0-702/hadoop/conf
2018-01-11 13:03:40,886 - Group['hdfs'] {}
2018-01-11 13:03:40,887 - Group['hadoop'] {}
2018-01-11 13:03:40,887 - Group['users'] {}
2018-01-11 13:03:40,887 - User['hive'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-01-11 13:03:40,890 - User['infra-solr'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-01-11 13:03:40,891 - User['zookeeper'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-01-11 13:03:40,892 - User['atlas'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-01-11 13:03:40,893 - User['ams'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-01-11 13:03:40,893 - User['ambari-qa'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'users'], 'uid': None}
2018-01-11 13:03:40,894 - User['kafka'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-01-11 13:03:40,894 - User['tez'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'users'], 'uid': None}
2018-01-11 13:03:40,895 - User['hdfs'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
2018-01-11 13:03:40,895 - User['yarn'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-01-11 13:03:40,896 - User['mapred'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-01-11 13:03:40,897 - User['hbase'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-01-11 13:03:40,897 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
2018-01-11 13:03:40,898 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
ambari-qa
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
0'] {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
2018-01-11 13:03:40,903 - Skipping
Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
0'] due to not_if
2018-01-11 13:03:40,903 - Directory['/tmp/hbase-hbase'] {'owner': 'hbase',
'create_parents': True, 'mode': 0775, 'cd_access': 'a'}
2018-01-11 13:03:40,904 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
2018-01-11 13:03:40,905 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
2018-01-11 13:03:40,906 - call['/var/lib/ambari-agent/tmp/changeUid.sh hbase']
{}
2018-01-11 13:03:40,913 - call returned (0, '1002')
2018-01-11 13:03:40,914 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh hbase
/home/hbase,/tmp/hbase,/usr/bin/hbase,/var/log/hbase,/tmp/hbase-hbase 1002']
{'not_if': '(test $(id -u hbase) -gt 1000) || (false)'}
2018-01-11
[jira] [Created] (AMBARI-23021) ServiceInfo/credential_store_supported applied to maintenance_state
Doroszlai, Attila created AMBARI-23021:
--
Summary: ServiceInfo/credential_store_supported applied to
maintenance_state
Key: AMBARI-23021
URL: https://issues.apache.org/jira/browse/AMBARI-23021
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Doroszlai, Attila
Try to update {{credential_store_supported}} property of a service:
{noformat}
$ curl -X PUT -d @-
"http://$AMBARI_SERVER:8080/api/v1/clusters/TEST/services/HDFS; <
[jira] [Updated] (AMBARI-22944) Wrong variable in KerberosKeytabDescriptor#toMap()
[
https://issues.apache.org/jira/browse/AMBARI-22944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22944:
Labels: pull-request-available (was: )
> Wrong variable in KerberosKeytabDescriptor#toMap()
> --
>
> Key: AMBARI-22944
> URL: https://issues.apache.org/jira/browse/AMBARI-22944
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Ted Yu
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> {code:title=org/apache/ambari/server/state/kerberos/KerberosKeytabDescriptor.java:466}
> if (!owner.isEmpty()) {
> map.put(KEY_GROUP, group);
> }
> {code}
> The if statement checks wrong variable.
> Should read
> {code}
> if (!group.isEmpty()) {
> map.put(KEY_GROUP, group);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23020) Missing LDAP configuration property warning should be a debug statement
Sandor Molnar created AMBARI-23020:
--
Summary: Missing LDAP configuration property warning should be a
debug statement
Key: AMBARI-23020
URL: https://issues.apache.org/jira/browse/AMBARI-23020
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.0
Missing LDAP configuration property warning should be a debug statement. The
Ambari server log is being filled with statements like:
{noformat}
16 Feb 2018 14:01:36,617 WARN [main] AmbariLdapConfiguration:47 - Ldap
configuration property [ambari.ldap.connectivity.server.host] hasn't been set;
using default value
{noformat}
The log level for these messages should be lowered to at least DEBUG.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23019) Use lucene version 6.6.2 instead of 6.6.0 in index migration script
[ https://issues.apache.org/jira/browse/AMBARI-23019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23019: Labels: pull-request-available (was: ) > Use lucene version 6.6.2 instead of 6.6.0 in index migration script > --- > > Key: AMBARI-23019 > URL: https://issues.apache.org/jira/browse/AMBARI-23019 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23019) Use lucene version 6.6.2 instead of 6.6.0 in index migration script
Olivér Szabó created AMBARI-23019: - Summary: Use lucene version 6.6.2 instead of 6.6.0 in index migration script Key: AMBARI-23019 URL: https://issues.apache.org/jira/browse/AMBARI-23019 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22819) Issues with storm jaas files and recursive ch_(mod/own) calls
[
https://issues.apache.org/jira/browse/AMBARI-22819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369011#comment-16369011
]
Hudson commented on AMBARI-22819:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #615 (See
[https://builds.apache.org/job/Ambari-branch-2.6/615/])
AMBARI-22819. Issues with storm jaas files and recursive ch_(mod/own)
(echekanskiy:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f4a4dca591d18076c0afb26807d2961bc4ac1d46])
* (edit) ambari-server/src/test/python/stacks/2.1/STORM/test_storm_base.py
* (edit)
ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/storm.py
* (add) ambari-common/src/main/python/ambari_commons/unicode_tolerant_fs.py
* (edit)
ambari-server/src/test/python/stacks/2.1/STORM/test_storm_jaas_configuration.py
* (edit) ambari-common/src/main/python/resource_management/core/sudo.py
* (edit) ambari-server/src/test/python/stacks/2.1/STORM/test_storm_nimbus.py
* (edit)
ambari-server/src/test/python/stacks/2.1/STORM/test_storm_supervisor_prod.py
* (edit) ambari-server/src/test/python/stacks/2.3/STORM/test_storm_base.py
> Issues with storm jaas files and recursive ch_(mod/own) calls
> -
>
> Key: AMBARI-22819
> URL: https://issues.apache.org/jira/browse/AMBARI-22819
> Project: Ambari
> Issue Type: Bug
> Components: security
>Affects Versions: 2.5.1
>Reporter: Sandeep Nemuri
>Assignee: Eugene Chekanskiy
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Post disabling the kerberos Ambari is not deleting the storm_jaas.conf and
> client_jaas.conf files from storm conf directory.
> Offset lag section in Storm UI is not populating because of the jaas conf.
> {code}
> Unable to get offset lags for kafka. Reason:
> org.apache.zookeeper.KeeperException$AuthFailedException: KeeperErrorCode =
> AuthFailed for /brokers/topics/hortonworks/partitions at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:123) at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at
> org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1590) at
> org.apache.curator.shaded.framework.imps.GetChildrenBuilderImpl$3.call(GetChildrenBuilderImpl.java:230)
> at
> org.apache.curator.shaded.framework.imps.GetChildrenBuilderImpl$3.call(GetChildrenBuilderImpl.java:219)
> at org.apache.curator.shaded.RetryLoop.callWithRetry(RetryLoop.java:109) at
> org.apache.curator.shaded.framework.imps.GetChildrenBuilderImpl.pathInForeground(GetChildrenBuilderImpl.java:216)
> at
> org.apache.curator.shaded.framework.imps.GetChildrenBuilderImpl.forPath(GetChildrenBuilderImpl.java:207)
> at
> org.apache.curator.shaded.framework.imps.GetChildrenBuilderImpl.forPath(GetChildrenBuilderImpl.java:40)
> at
> org.apache.storm.kafka.monitor.KafkaOffsetLagUtil.getLeadersAndTopicPartitions(KafkaOffsetLagUtil.java:323)
> at
> org.apache.storm.kafka.monitor.KafkaOffsetLagUtil.getOffsetLags(KafkaOffsetLagUtil.java:257)
> at
> org.apache.storm.kafka.monitor.KafkaOffsetLagUtil.main(KafkaOffsetLagUtil.java:126)
> {code}
> Storm's /usr/hdp/current/storm-client/bin/storm-kafka-monitor checks if the
> storm_jaas.conf exists in storm configuration directory and then uses it.
> {code:java}
> STORM_JAAS_CONF_PARAM=""
> JAAS_FILE="${STORM_CONF_DIR}/storm_jaas.conf"
> if [ -f $JAAS_FILE ]; then
> STORM_JAAS_CONF_PARAM="-Djava.security.auth.login.config=${JAAS_FILE}"
> fi
> {code}
> Issue will be resolved if we delete the storm_jaas.conf file manually.
> As well storm jaas configs must be readable by world to allow some mpacks
> work properly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22842) Provide field / component UI metadata from backend
[
https://issues.apache.org/jira/browse/AMBARI-22842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-22842.
---
Resolution: Fixed
> Provide field / component UI metadata from backend
> --
>
> Key: AMBARI-22842
> URL: https://issues.apache.org/jira/browse/AMBARI-22842
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Original Estimate: 48h
> Time Spent: 4h 10m
> Remaining Estimate: 43h 50m
>
> Adding new options for the backend to get field / component metadata:
> {code:java}
> logsearch.web.service_logs.group.labels=k1:v1,k2:v2
> logsearch.web.service_logs.component.labels=k1:v1,k2:v2
> logsearch.web.service_logs.field.labels=k1:v1,k2:v2
> logsearch.web.service_logs.field.excludes=v1,v2,v3
> logsearch.web.service_logs.field.visible=v1,v2,v3
> logsearch.web.service_logs.field.filterable.excludes=v1,v2
> logsearch.web.audit_logs.component.labels=k1:v1,k2:v2
> logsearch.web.audit_logs.field.labels=K1#k1:v1,k2:v2;K2#k1:v1,k3:v3
> logsearch.web.audit_logs.field.common.labels=k1:v1,k2:v2
> logsearch.web.audit_logs.field.visible=k1:v1,v2,v3;k2:v1,v2
> logsearch.web.audit_logs.field.common.visible=v1,v2,v3
> logsearch.web.audit_logs.field.excludes=k1:v1,v2,v3;k2:v1,v2
> logsearch.web.audit_logs.field.common.excludes=v1,v2,v3
> logsearch.web.audit_logs.field.filterable.excludes==k1:v1,v2,v3;k2:v1,v2
> logsearch.web.audit_logs.field.common.filterable.common.excludes=v1,v2,v3
> logsearch.web.labels.fallback.enabled=true
> logsearch.web.labels.service_logs.field.fallback.prefixes=ws_,std_
> logsearch.web.labels.service_logs.field.fallback.prefixes=sdi_
> {code}
> Field metadata:
> - name: real field name
> - label (visible name on the UI for the field)
> - visible (by default it should be visible in tables)
> - filterable (it can be filterable from the searchbox) - always true by
> default, if not set, contains everything which is not excluded
> (audit field metadata has common values, because different metadata can be
> used for different audit types)
> with exclude properties you can remove fields from the response, those are
> also not filtered, but you can set fields to non-filtered if they are in the
> response with filterable.exclude options
> Component metadata:
> - name - label map: real component name with the name that should be seen on
> the UI
> for service component there is an additional field: group, different
> components can be grouped togather (like: metrics_collector and
> metrics_grafana can be in the same AMS group)
> `api/v1/service/logs/schema/fields` and `api/v1/audit/logs/schema/fields`
> will contain field metadata
> `api/v1/service/logs/components` and `api/v1/audit/logs/components` will
> contain component metadata
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22842) Provide field / component UI metadata from backend
[ https://issues.apache.org/jira/browse/AMBARI-22842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368985#comment-16368985 ] Hudson commented on AMBARI-22842: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8751 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8751/]) AMBARI-22842. Provide field / component UI metadata from backend (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=794bc557e4910815a51b27c8dab015beda6ea4db]) * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/common/LabelFallbackHandler.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder-plugin-api/src/main/java/org/apache/ambari/logfeeder/plugin/filter/Filter.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/configsets/hadoop_logs/conf/managed-schema * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/doc/DocConstants.java * (add) ambari-logsearch/.gitignore * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/UIMappingConfig.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/metadata/ComponentMetadata.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/response/ServiceLogData.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/rest/ServiceLogsResource.java * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/common/HadoopServiceConfigHelper.java * (edit) ambari-logsearch/docker/test-config/logfeeder/shipper-conf/input.config-hst.json * (edit) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/model/inputconfig/InputDescriptor.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/metadata/Metadata.java * (delete) ambari-logsearch/ambari-logsearch-server/src/test/resources/HadoopServiceConfig.json * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/metadata/ServiceComponentMetadataWrapper.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/metadata/Groupable.java * (add) ambari-logsearch/ambari-logsearch-server/src/test/java/org/apache/ambari/logsearch/common/LabelFallbackHandlerTest.java * (edit) ambari-logsearch/docker/test-config/logfeeder/shipper-conf/input.config-zookeeper.json * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/solr/model/SolrServiceLogData.java * (edit) ambari-logsearch/docker/test-config/logfeeder/shipper-conf/input.config-secure_log.json * (edit) ambari-logsearch/docker/test-config/logfeeder/shipper-conf/input.config-ambari.json * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/manager/AuditLogsManager.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/metadata/FieldMetadata.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/rest/AuditLogsResource.java * (delete) ambari-logsearch/ambari-logsearch-server/src/main/resources/HadoopServiceConfig.json * (edit) ambari-logsearch/ambari-logsearch-config-zookeeper/src/main/java/org/apache/ambari/logsearch/config/zookeeper/model/inputconfig/impl/InputDescriptorImpl.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/common/PropertiesSplitter.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputManagerImpl.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/metadata/AuditFieldMetadataResponse.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/solr/ResponseDataGenerator.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/metadata/Visible.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder-plugin-api/src/main/java/org/apache/ambari/logfeeder/plugin/input/Input.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/metadata/Labelable.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/solr/SolrConstants.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/metadata/Filterable.java * (add) ambari-logsearch/ambari-logsearch-server/src/test/java/org/apache/ambari/logsearch/common/PropertiesSplitterTest.java * (edit) ambari-logsearch/docker/test-config/logfeeder/shipper-conf/input.config-system_message.json * (edit)
[jira] [Commented] (AMBARI-22825) Log Search UI: add different options of field name display
[ https://issues.apache.org/jira/browse/AMBARI-22825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368987#comment-16368987 ] Hudson commented on AMBARI-22825: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8751 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8751/]) AMBARI-22825 Add different options of field name display (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=4df8e38835e08fd42d8958a59f33d1d22c11aae1]) * (delete) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/log-field.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.spec.ts * (delete) ambari-logsearch/ambari-logsearch-web/src/app/mock-data.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/log-index-filter/log-index-filter.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/yarn.lock * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/audit-logs-entries/audit-logs-entries.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/package.json * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-range-picker/time-range-picker.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/test-config.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/audit-logs-table/audit-logs-table.component.spec.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/mock-data-by-url.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/service-logs-table/service-logs-table.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/timezone-picker/timezone-picker.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-list/dropdown-list.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/utils.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-list/dropdown-list.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/top-menu/top-menu.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/history-manager.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/storage/audit-logs-fields.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/component-generator.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/component-generator.service.ts * (delete) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/audit-log-field.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/log-context/log-context.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/mock-api-data.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/object.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/filter-dropdown/filter-dropdown.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.html * (delete) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/service-log-field.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/user-settings.service.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/store.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/context-menu/context-menu.component.spec.ts > Log Search UI: add different options of field name display > -- > > Key: AMBARI-22825 > URL: https://issues.apache.org/jira/browse/AMBARI-22825 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Fix For: 3.0.0 > > Original Estimate: 168h > Time Spent: 240h > Remaining Estimate: 0h > > Display more user friendly column/field names on the service and audit logs > screen. > Eg.: Instead of showing 'line_number' we should display 'Line Number'. > Use fallback when it is not available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22814) Add different options of component name display
[ https://issues.apache.org/jira/browse/AMBARI-22814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368986#comment-16368986 ] Hudson commented on AMBARI-22814: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8751 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8751/]) AMBARI-22814 Add different options of component name display (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7883bc522eac3da3f998258f91851693913d08ef]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/http-client.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/service-logs-table/service-logs-table.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/app.module.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/pipes/component-label.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/utils.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/node-item.ts * (add) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/node-group.ts > Add different options of component name display > --- > > Key: AMBARI-22814 > URL: https://issues.apache.org/jira/browse/AMBARI-22814 > Project: Ambari > Issue Type: Bug > Components: logsearch >Affects Versions: 3.0.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Original Estimate: 168h > Time Spent: 96.5h > Remaining Estimate: 71.5h > > The ams_collector should show up as “AMS: Metrics Collector”, and > hdfs_namenode should show up as “HDFS: NameNode” - the mapping should be > mutable, but we should show it everywhere, and we should have a long name > “Service: Component” and a short name “Component” > Example: > Log Feeder: hdfs_namenode > Long Name: HDFS: NameNode > Short Name: NameNode > Abbreviation: NN -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23018) Add more Solr alerts using Solr (< 6.4 version) metrics API
Krisztian Kasa created AMBARI-23018: --- Summary: Add more Solr alerts using Solr (< 6.4 version) metrics API Key: AMBARI-23018 URL: https://issues.apache.org/jira/browse/AMBARI-23018 Project: Ambari Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23017) [PERF] Deployment of PERF stack leads to Out of Sync
[ https://issues.apache.org/jira/browse/AMBARI-23017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23017: Labels: pull-request-available (was: ) > [PERF] Deployment of PERF stack leads to Out of Sync > > > Key: AMBARI-23017 > URL: https://issues.apache.org/jira/browse/AMBARI-23017 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-23017.patch > > > While deploying PERF stack, PERF 1.0 stack is not installed and shows up as > Out of sync -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23017) [PERF] Deployment of PERF stack leads to Out of Sync
[ https://issues.apache.org/jira/browse/AMBARI-23017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23017: - Status: Patch Available (was: Open) > [PERF] Deployment of PERF stack leads to Out of Sync > > > Key: AMBARI-23017 > URL: https://issues.apache.org/jira/browse/AMBARI-23017 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.6.2 > > Attachments: AMBARI-23017.patch > > > While deploying PERF stack, PERF 1.0 stack is not installed and shows up as > Out of sync -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23017) [PERF] Deployment of PERF stack leads to Out of Sync
Andrew Onischuk created AMBARI-23017: Summary: [PERF] Deployment of PERF stack leads to Out of Sync Key: AMBARI-23017 URL: https://issues.apache.org/jira/browse/AMBARI-23017 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.6.2 Attachments: AMBARI-23017.patch While deploying PERF stack, PERF 1.0 stack is not installed and shows up as Out of sync -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23017) [PERF] Deployment of PERF stack leads to Out of Sync
[ https://issues.apache.org/jira/browse/AMBARI-23017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23017: - Attachment: AMBARI-23017.patch > [PERF] Deployment of PERF stack leads to Out of Sync > > > Key: AMBARI-23017 > URL: https://issues.apache.org/jira/browse/AMBARI-23017 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.6.2 > > Attachments: AMBARI-23017.patch > > > While deploying PERF stack, PERF 1.0 stack is not installed and shows up as > Out of sync -- This message was sent by Atlassian JIRA (v7.6.3#76005)
