[jira] [Updated] (AMBARI-18386) Handle Ranger hive repo config jdbc url change for stack 2.5
[ https://issues.apache.org/jira/browse/AMBARI-18386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18386: - Attachment: AMBARI-18386.2.patch > Handle Ranger hive repo config jdbc url change for stack 2.5 > > > Key: AMBARI-18386 > URL: https://issues.apache.org/jira/browse/AMBARI-18386 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.1, 2.4.2 > > Attachments: AMBARI-18386.1.patch, AMBARI-18386.2.patch, > AMBARI-18386.patch > > > From ambari stacks for Ranger: enable ranger hive plugin takes care of using > right jdbc url for repo configs that are set for creating a repository in > Ranger for Secure and simple install of hive. > However in HiverServer2 HA env, jdbc url needs to change in repo config with > zk url. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18185) Selecting one host when topN is set, throws an error
[ https://issues.apache.org/jira/browse/AMBARI-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492276#comment-15492276 ] Hudson commented on AMBARI-18185: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #37 (See [https://builds.apache.org/job/Ambari-branch-2.5/37/]) AMBARI-18185 : Selecting one host when topN is set, throws an error. (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cd7788621d22750156e8df52a6ac94faba49d07a]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java > Selecting one host when topN is set, throws an error > > > Key: AMBARI-18185 > URL: https://issues.apache.org/jira/browse/AMBARI-18185 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18185.patch > > > topN is available by default on almost all Grafana templatized dashboards. > When viewing any of these dashboards, if only one "host" or templated option > is chosen, then AMS returns with an exception (screenshot attached). > Sample query: > collectorhost:6188/ws/v1/timeline/metrics?metricNames=cpu_system._avg=hostname=HOST=1470925360=1470946960=20=avg=false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18154) Ambari Dashboard, Cluster load widget - Incorrect value in Nodes._avg metric
[ https://issues.apache.org/jira/browse/AMBARI-18154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492274#comment-15492274 ] Hudson commented on AMBARI-18154: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #37 (See [https://builds.apache.org/job/Ambari-branch-2.5/37/]) AMBARI-18154 : Ambari Dashboard, Cluster load widget - Incorrect value (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9b08b7042da5e6985b3cd5e9734891fced552f67]) * (edit) ambari-server/src/main/resources/ganglia_properties.json * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecondTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java > Ambari Dashboard, Cluster load widget - Incorrect value in Nodes._avg metric > > > Key: AMBARI-18154 > URL: https://issues.apache.org/jira/browse/AMBARI-18154 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.0, 2.2.1, 2.2.2 >Reporter: Sandeep Nemuri >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18154.patch, Cluster_Load.png > > > *PROBLEM* : > Under Ambari Dashboard -> Cluster metrics. > It has been noticed that the metrics Nodes._avg and CPUs._avg are showing the > same data. > Below is the screenshot which shows Cluster metrics of a cluster which has > nodes 200+ and the Nodes._avg shows 18.5 as maximum value. > !Cluster_Load.png|align=center,|height=750%,width=700&! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18393) Hive Server Interactive (HSI) fails to start with 'Permission denied' for User Hive, if HSI starts before HS2.
[
https://issues.apache.org/jira/browse/AMBARI-18393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492273#comment-15492273
]
Hudson commented on AMBARI-18393:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #37 (See
[https://builds.apache.org/job/Ambari-branch-2.5/37/])
AMBARI-18393. Hive Server Interactive (HSI) fails to start with (sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7594857e40da29baa3ff80832b04b57e4ffcf90d])
* (edit) ambari-server/src/test/python/stacks/2.5/HIVE/test_hive_server_int.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_interactive.py
> Hive Server Interactive (HSI) fails to start with 'Permission denied' for
> User Hive, if HSI starts before HS2.
> --
>
> Key: AMBARI-18393
> URL: https://issues.apache.org/jira/browse/AMBARI-18393
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
>
> - Install Cluster using Blueprint including HiveServerInteractive
> - Start services fail at Hive interactive start, with below error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 535, in
> HiveServerInteractive().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 115, in start
> self.setup_security()
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 335, in setup_security
> Execute(slider_keytab_install_cmd, user=params.hive_user)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'slider install-keytab
> --keytab /etc/security/keytabs/hive.llap.zk.sm.keytab --folder hive
> --overwrite' returned 56. 2016-08-15 23:47:57,518 [main] INFO
> tools.SliderUtils - JVM initialized into secure mode with kerberos realm
> HWQE.HORTONWORKS.COM
> 2016-08-15 23:47:59,108 [main] INFO impl.TimelineClientImpl - Timeline
> service address:
> http://nat-s11-4-lkws-stackdeploy-3.openstacklocal:8188/ws/v1/timeline/
> 2016-08-15 23:48:01,584 [main] WARN shortcircuit.DomainSocketFactory - The
> short-circuit local reads feature cannot be used because libhadoop cannot be
> loaded.
> 2016-08-15 23:48:01,633 [main] INFO client.RMProxy - Connecting to
> ResourceManager at
> nat-s11-4-lkws-stackdeploy-5.openstacklocal/172.22.71.181:8050
> 2016-08-15 23:48:01,983 [main] INFO client.AHSProxy - Connecting to
> Application History server at
> nat-s11-4-lkws-stackdeploy-3.openstacklocal/172.22.71.168:10200
> 2016-08-15 23:48:03,297 [main] WARN client.SliderClient - The
> 'install-keytab' option has been deprecated. Please use 'keytab --install'.
> 2016-08-15 23:48:03,440 [main] WARN retry.RetryInvocationHandler - Exception
> while invoking ClientNamenodeProtocolTranslatorPB.mkdirs over null. Not
> retrying because try once and fail.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
> Permission denied: user=hive, access=WRITE,
> inode="/user/hive/.slider/keytabs/hive":hdfs:hdfs:drwxr-xr-x
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
> at
>
[jira] [Commented] (AMBARI-18125) AMS : Allow for certain metrics to skip aggregation determined by client
[ https://issues.apache.org/jira/browse/AMBARI-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492271#comment-15492271 ] Hudson commented on AMBARI-18125: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #37 (See [https://builds.apache.org/job/Ambari-branch-2.5/37/]) AMBARI-18125 : Allow for certain metrics to skip aggregation determined (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d21f1f6e791b4bf5a18b0a76dc7bf95e3961c2f1]) * (edit) ambari-metrics/ambari-metrics-hadoop-sink/src/main/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/SplitByMetricNamesCondition.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TestPhoenixTransactSQL.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecondTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/DefaultCondition.java * (edit) ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/host_info.py * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/EmptyCondition.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/Condition.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/DefaultConditionTest.java * (edit) ambari-metrics/ambari-metrics-hadoop-sink/src/test/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSinkTest.java * (edit) ambari-metrics/ambari-metrics-host-monitoring/src/test/python/core/TestHostInfo.py * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TimelineMetricMetadataManager.java * (edit) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/TimelineMetric.java > AMS : Allow for certain metrics to skip aggregation determined by client > > > Key: AMBARI-18125 > URL: https://issues.apache.org/jira/browse/AMBARI-18125 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18125.patch > > > _Example_: Per disk metrics / host static info (no aggregation across hosts) > The client should be able to submit a request which dimension should be > skipped. > The metadata can store this info and allow the SELECT query projection to > skip a chunk of these metrics based on what aggregation is working. > For now only across host skipping makes sense and the client part can be put > in later. > *Note*: > Sub-task, de-normalize disk metrics so that user can find out disk per host. > Grafana implication: The non-aggregated metrics can obviously be visualized > only on the templatized / host dashboard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18289) Invalid negative values for some AMS metrics
[ https://issues.apache.org/jira/browse/AMBARI-18289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492272#comment-15492272 ] Hudson commented on AMBARI-18289: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #37 (See [https://builds.apache.org/job/Ambari-branch-2.5/37/]) AMBARI-18289 : Invalid negative values for some AMS metrics. (avijayan) (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7adb5cfff607bf7914988fc3f99096d850cc0a33]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/metric_monitor.ini.j2 * (edit) ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/host_info.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py * (edit) ambari-metrics/ambari-metrics-host-monitoring/conf/unix/metric_monitor.ini * (edit) ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/config_reader.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml > Invalid negative values for some AMS metrics > > > Key: AMBARI-18289 > URL: https://issues.apache.org/jira/browse/AMBARI-18289 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18289-2.patch > > > PROBLEM > Negative values are being reported for IOPS in the "system servers" dashboard > BUG > This was a dockerized environment. Negative rate values were seen because > read/write counters were dropping below the previous values at random times. > On further investigation, it revealed that this was due to the docker volume > groups present on the host. It is expected of docker containers to add/remove > the volume groups during the lifecyle of a container. So, when a volume group > goes away, the read/write counters do not contribute to the total counter > values, thus making the value go below the last seen value. > FIX > Have a provision to discard such "special" disk partitions through a skip > pattern. Individual disk counter metrics can be used to get disk specific > counter values. If skipped, they will not contribute to the global counter > metric. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18132) Remove FIFO and Normalizer in ams-env config.
[
https://issues.apache.org/jira/browse/AMBARI-18132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492275#comment-15492275
]
Hudson commented on AMBARI-18132:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #37 (See
[https://builds.apache.org/job/Ambari-branch-2.5/37/])
AMBARI-18132 : Remove FIFO and Normalizer in ams-env config. (avijayan)
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=10861855360904d047533b072f3b5bbb731538de])
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
> Remove FIFO and Normalizer in ams-env config.
> -
>
> Key: AMBARI-18132
> URL: https://issues.apache.org/jira/browse/AMBARI-18132
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18132.patch
>
>
> It is currently
> {code}
> # HBase compaction policy enabled
> export HBASE_NORMALIZATION_ENABLED=True
> # HBase compaction policy enabled
> export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18332) Blueprints: API should make available "setting" property from blueprint
[
https://issues.apache.org/jira/browse/AMBARI-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492067#comment-15492067
]
Hudson commented on AMBARI-18332:
-
ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #36 (See
[https://builds.apache.org/job/Ambari-branch-2.5/36/])
AMBARI-18332: Blueprints: API should make available "setting" property
(nsomasundaram:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=45067817cea3800c04dfc40adec7557e1a27fb69])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintResourceProvider.java
> Blueprints: API should make available "setting" property from blueprint
> ---
>
> Key: AMBARI-18332
> URL: https://issues.apache.org/jira/browse/AMBARI-18332
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb51851.patch
>
>
> The following APIs do not retrieve *setting* section from the blueprint that
> was used during deployment:
> {code}
> http://:/api/v1/blueprints/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18389) Config compare shows incorrect value after enabling kerberos
[ https://issues.apache.org/jira/browse/AMBARI-18389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492066#comment-15492066 ] Hudson commented on AMBARI-18389: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #36 (See [https://builds.apache.org/job/Ambari-branch-2.5/36/]) AMBARI-18389 - Config compare shows incorrect value after enabling (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2c3caa77687eb39eda8f4218973b344abbff3ca8]) * (edit) ambari-web/app/models/configs/objects/service_config_property.js * (edit) ambari-web/test/models/configs/objects/service_config_property_test.js > Config compare shows incorrect value after enabling kerberos > > > Key: AMBARI-18389 > URL: https://issues.apache.org/jira/browse/AMBARI-18389 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Blocker > Fix For: 2.4.1 > > Attachments: AMBARI-18389.patch > > > Config compare shows incorrect value after enabling kerberos. > - Current version = v17 > - Click on v16 (tracked config: ams-hbase-security-site :: > hbase.coprocessor.master.classes) > - Compare with v15 > - The compare screenshot shows both v15 and v16 have the same value for the > config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service
[
https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-18368:
-
Attachment: AMBARI-18368.addendum.patch
> Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas
> Service
> -
>
> Key: AMBARI-18368
> URL: https://issues.apache.org/jira/browse/AMBARI-18368
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: trunk, 2.4.2
>
> Attachments: AMBARI-18368.addendum.patch, AMBARI-18368.patch
>
>
> Steps to Reproduce:
> * Install Ambari 2.2.2 with HDP 2.4 and HBase, Kafka, and Hive (this is very
> important)
> * Kerberize the cluster
> * Perform EU/RU to HDP 2.5
> * Add Atlas Service
> Atlas Server log contains,
> {code}
> Caused by:
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
> from server at
> http://natu146-ehbs-dgm10toeriesec-u14-1.openstacklocal:8886/solr: Can not
> find the specified config set: vertex_index
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:577)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
> at
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
> at
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1100)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:870)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:806)
> at
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
> at
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:166)
> at
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.createCollectionIfNotExists(Solr5Index.java:901)
> at
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.register(Solr5Index.java:269)
> at
> com.thinkaurelius.titan.diskstorage.indexing.IndexTransaction.register(IndexTransaction.java:83)
> at
> com.thinkaurelius.titan.graphdb.database.IndexSerializer.register(IndexSerializer.java:92)
> at
> com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.addIndexKey(ManagementSystem.java:534)
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.enhanceMixedIndex(GraphBackedSearchIndexer.java:405)
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.createIndexes(GraphBackedSearchIndexer.java:334)
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.initialize(GraphBackedSearchIndexer.java:103)
> ... 71 more
> {code}
> Atlas tables in HBase look ok.
> {code}
> su hbase
> kinit -kt /etc/security/keytabs/hbase.headless.keytab cstm-hb...@example.com
> hbase shell
> hbase(main):001:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_titan
> 2 row(s) in 1.4300 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_titan"]
> {code}
> h4. Workaround
> 1. Stop Atlas Server
> 2. Copy solr xml files to correct config folder and chown as
> $atlas_user:$hadoop_group
> {code}
> cp -R /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/solr/* /etc/atlas/conf/solr/
> cp: overwrite `/etc/atlas/conf/solr/solrconfig.xml'? n
> chown atlas:hadoop /etc/atlas/conf/solr/*
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/users-credentials.properties
> /etc/atlas/conf/
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/policy-store.txt /etc/atlas/conf/
> chown atlas:hadoop /etc/atlas/conf/users-credentials.properties
> chown atlas:hadoop /etc/atlas/conf/policy-store.txt
> {code}
> 3. Delete zookeeper znode,
> {code}
> # kinit -kt /etc/security/keytabs/atlas.service.keytab atlas/@
> # cd /usr/hdp/current/zookeeper-client/bin/
> # ./zkCli.sh -server :
> [ .. (CONNECTED) ] rmr /infra-solr/configs/atlas_configs
> {code}
> 4. Ensure Atlas application-properties are present for,
> atlas.jaas.KafkaClient.option.keyTab =
> /etc/security/keytabs/atlas.service.keytab
> atlas.jaas.KafkaClient.option.principal = atlas/_h...@example.com
> 5. Start Atlas
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service
[
https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491816#comment-15491816
]
Alejandro Fernandez edited comment on AMBARI-18368 at 9/15/16 1:41 AM:
---
There's an additional problem when Hive exists in HDP 2.4 and Atlas is not
present.
The Hive RPM installs /usr/$stack/$version/atlas with some partial packages
that contain Hive hooks, while the Atlas RPM is responsible for installing the
full content.
If the user does not have Atlas currently installed on their stack, then
/usr/$stack/current/atlas-clientwill be a broken symlink, and we should not
create the symlink /etc/atlas/conf -> /usr/$stack/current/atlas-client/conf .
If we mistakenly create this symlink, then when the user performs an EU/RU and
then adds Atlas service then the Atlas RPM will not be able to copy its
artifacts into /etc/atlas/conf directory and therefore prevent Ambari from by
copying those unmanaged contents into /etc/atlas/$version/0
Further, when installing Atlas service, we must copy the artifacts from
/etc/atlas/conf.backup/* to /etc/atlas/conf (which is now a symlink to
/usr/hdp/current/atlas-client/conf/) with the no-clobber flag.
Will reopen this Jira to provide an addendum patch for this related scenario.
was (Author: afernandez):
There's an additional problem when Hive exists in HDP 2.4 and Atlas is not
present.
The Hive RPM installs /usr/$stack/$version/atlas with some partial packages
that contain Hive hooks, while the Atlas RPM is responsible for installing the
full content.
If the user does not have Atlas currently installed on their stack, then
/usr/$stack/current/atlas-clientwill be a broken symlink, and we should not
create the symlink /etc/atlas/conf -> /usr/$stack/current/atlas-client/conf .
If we mistakenly create this symlink, then when the user performs an EU/RU and
then adds Atlas service then the Atlas RPM will not be able to copy its
artifacts into /etc/atlas/conf directory and therefore prevent Ambari from by
copying those unmanaged contents into /etc/atlas/$version/0
Will reopen this Jira to provide an addendum patch for this related scenario.
> Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas
> Service
> -
>
> Key: AMBARI-18368
> URL: https://issues.apache.org/jira/browse/AMBARI-18368
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: trunk, 2.4.2
>
> Attachments: AMBARI-18368.patch
>
>
> Steps to Reproduce:
> * Install Ambari 2.2.2 with HDP 2.4 and HBase, Kafka, and Hive (this is very
> important)
> * Kerberize the cluster
> * Perform EU/RU to HDP 2.5
> * Add Atlas Service
> Atlas Server log contains,
> {code}
> Caused by:
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
> from server at
> http://natu146-ehbs-dgm10toeriesec-u14-1.openstacklocal:8886/solr: Can not
> find the specified config set: vertex_index
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:577)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
> at
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
> at
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1100)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:870)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:806)
> at
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
> at
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:166)
> at
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.createCollectionIfNotExists(Solr5Index.java:901)
> at
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.register(Solr5Index.java:269)
> at
> com.thinkaurelius.titan.diskstorage.indexing.IndexTransaction.register(IndexTransaction.java:83)
> at
> com.thinkaurelius.titan.graphdb.database.IndexSerializer.register(IndexSerializer.java:92)
> at
> com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.addIndexKey(ManagementSystem.java:534)
> at
>
[jira] [Commented] (AMBARI-18332) Blueprints: API should make available "setting" property from blueprint
[
https://issues.apache.org/jira/browse/AMBARI-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491909#comment-15491909
]
Hudson commented on AMBARI-18332:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5673 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5673/])
AMBARI-18332: Blueprints: API should make available "setting" property
(nsomasundaram:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1b89d6866e369906902f759a7a5d2ba865e8cbe0])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintResourceProviderTest.java
> Blueprints: API should make available "setting" property from blueprint
> ---
>
> Key: AMBARI-18332
> URL: https://issues.apache.org/jira/browse/AMBARI-18332
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb51851.patch
>
>
> The following APIs do not retrieve *setting* section from the blueprint that
> was used during deployment:
> {code}
> http://:/api/v1/blueprints/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18289) Invalid negative values for some AMS metrics
[ https://issues.apache.org/jira/browse/AMBARI-18289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491910#comment-15491910 ] Hudson commented on AMBARI-18289: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5673 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5673/]) AMBARI-18289 : Invalid negative values for some AMS metrics. (avijayan) (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9455b52dd3126248ccea0d077d5da4512f4e2f21]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/metric_monitor.ini.j2 * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml * (edit) ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/config_reader.py * (edit) ambari-metrics/ambari-metrics-host-monitoring/conf/unix/metric_monitor.ini * (edit) ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/host_info.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py > Invalid negative values for some AMS metrics > > > Key: AMBARI-18289 > URL: https://issues.apache.org/jira/browse/AMBARI-18289 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18289-2.patch > > > PROBLEM > Negative values are being reported for IOPS in the "system servers" dashboard > BUG > This was a dockerized environment. Negative rate values were seen because > read/write counters were dropping below the previous values at random times. > On further investigation, it revealed that this was due to the docker volume > groups present on the host. It is expected of docker containers to add/remove > the volume groups during the lifecyle of a container. So, when a volume group > goes away, the read/write counters do not contribute to the total counter > values, thus making the value go below the last seen value. > FIX > Have a provision to discard such "special" disk partitions through a skip > pattern. Individual disk counter metrics can be used to get disk specific > counter values. If skipped, they will not contribute to the global counter > metric. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18185) Selecting one host when topN is set, throws an error
[ https://issues.apache.org/jira/browse/AMBARI-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491915#comment-15491915 ] Hudson commented on AMBARI-18185: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5673 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5673/]) AMBARI-18185 : Selecting one host when topN is set, throws an error. (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4a099342c1b5a8c1b7dbf77fda3ef0f24bfd26cd]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java > Selecting one host when topN is set, throws an error > > > Key: AMBARI-18185 > URL: https://issues.apache.org/jira/browse/AMBARI-18185 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18185.patch > > > topN is available by default on almost all Grafana templatized dashboards. > When viewing any of these dashboards, if only one "host" or templated option > is chosen, then AMS returns with an exception (screenshot attached). > Sample query: > collectorhost:6188/ws/v1/timeline/metrics?metricNames=cpu_system._avg=hostname=HOST=1470925360=1470946960=20=avg=false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18154) Ambari Dashboard, Cluster load widget - Incorrect value in Nodes._avg metric
[ https://issues.apache.org/jira/browse/AMBARI-18154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491912#comment-15491912 ] Hudson commented on AMBARI-18154: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5673 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5673/]) AMBARI-18154 : Ambari Dashboard, Cluster load widget - Incorrect value (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=aa0528ecab47850f44dd5575ab7861083e67c6ea]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecondTest.java * (edit) ambari-server/src/main/resources/ganglia_properties.json * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java > Ambari Dashboard, Cluster load widget - Incorrect value in Nodes._avg metric > > > Key: AMBARI-18154 > URL: https://issues.apache.org/jira/browse/AMBARI-18154 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.0, 2.2.1, 2.2.2 >Reporter: Sandeep Nemuri >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18154.patch, Cluster_Load.png > > > *PROBLEM* : > Under Ambari Dashboard -> Cluster metrics. > It has been noticed that the metrics Nodes._avg and CPUs._avg are showing the > same data. > Below is the screenshot which shows Cluster metrics of a cluster which has > nodes 200+ and the Nodes._avg shows 18.5 as maximum value. > !Cluster_Load.png|align=center,|height=750%,width=700&! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18132) Remove FIFO and Normalizer in ams-env config.
[
https://issues.apache.org/jira/browse/AMBARI-18132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491914#comment-15491914
]
Hudson commented on AMBARI-18132:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5673 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5673/])
AMBARI-18132 : Remove FIFO and Normalizer in ams-env config. (avijayan)
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0e3435856a2aee7951f765e90e55e027b6455c1a])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
> Remove FIFO and Normalizer in ams-env config.
> -
>
> Key: AMBARI-18132
> URL: https://issues.apache.org/jira/browse/AMBARI-18132
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18132.patch
>
>
> It is currently
> {code}
> # HBase compaction policy enabled
> export HBASE_NORMALIZATION_ENABLED=True
> # HBase compaction policy enabled
> export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18125) AMS : Allow for certain metrics to skip aggregation determined by client
[ https://issues.apache.org/jira/browse/AMBARI-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491908#comment-15491908 ] Hudson commented on AMBARI-18125: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5673 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5673/]) AMBARI-18125 : Allow for certain metrics to skip aggregation determined (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f5ad1de8689fc45980e5439d873a9331ea6f4723]) * (edit) ambari-metrics/ambari-metrics-host-monitoring/src/test/python/core/TestHostInfo.py * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TestPhoenixTransactSQL.java * (edit) ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/host_info.py * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TimelineMetricMetadataManager.java * (edit) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/TimelineMetric.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/SplitByMetricNamesCondition.java * (edit) ambari-metrics/ambari-metrics-hadoop-sink/src/test/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSinkTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/DefaultCondition.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/Condition.java * (edit) ambari-metrics/ambari-metrics-hadoop-sink/src/main/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSink.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/EmptyCondition.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecondTest.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/DefaultConditionTest.java > AMS : Allow for certain metrics to skip aggregation determined by client > > > Key: AMBARI-18125 > URL: https://issues.apache.org/jira/browse/AMBARI-18125 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18125.patch > > > _Example_: Per disk metrics / host static info (no aggregation across hosts) > The client should be able to submit a request which dimension should be > skipped. > The metadata can store this info and allow the SELECT query projection to > skip a chunk of these metrics based on what aggregation is working. > For now only across host skipping makes sense and the client part can be put > in later. > *Note*: > Sub-task, de-normalize disk metrics so that user can find out disk per host. > Grafana implication: The non-aggregated metrics can obviously be visualized > only on the templatized / host dashboard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18393) Hive Server Interactive (HSI) fails to start with 'Permission denied' for User Hive, if HSI starts before HS2.
[
https://issues.apache.org/jira/browse/AMBARI-18393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491911#comment-15491911
]
Hudson commented on AMBARI-18393:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5673 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5673/])
AMBARI-18393. Hive Server Interactive (HSI) fails to start with (sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=565685d326e5a877f8e4479736e75f59f728c9ec])
* (edit) ambari-server/src/test/python/stacks/2.5/HIVE/test_hive_server_int.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_interactive.py
> Hive Server Interactive (HSI) fails to start with 'Permission denied' for
> User Hive, if HSI starts before HS2.
> --
>
> Key: AMBARI-18393
> URL: https://issues.apache.org/jira/browse/AMBARI-18393
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
>
> - Install Cluster using Blueprint including HiveServerInteractive
> - Start services fail at Hive interactive start, with below error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 535, in
> HiveServerInteractive().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 115, in start
> self.setup_security()
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 335, in setup_security
> Execute(slider_keytab_install_cmd, user=params.hive_user)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'slider install-keytab
> --keytab /etc/security/keytabs/hive.llap.zk.sm.keytab --folder hive
> --overwrite' returned 56. 2016-08-15 23:47:57,518 [main] INFO
> tools.SliderUtils - JVM initialized into secure mode with kerberos realm
> HWQE.HORTONWORKS.COM
> 2016-08-15 23:47:59,108 [main] INFO impl.TimelineClientImpl - Timeline
> service address:
> http://nat-s11-4-lkws-stackdeploy-3.openstacklocal:8188/ws/v1/timeline/
> 2016-08-15 23:48:01,584 [main] WARN shortcircuit.DomainSocketFactory - The
> short-circuit local reads feature cannot be used because libhadoop cannot be
> loaded.
> 2016-08-15 23:48:01,633 [main] INFO client.RMProxy - Connecting to
> ResourceManager at
> nat-s11-4-lkws-stackdeploy-5.openstacklocal/172.22.71.181:8050
> 2016-08-15 23:48:01,983 [main] INFO client.AHSProxy - Connecting to
> Application History server at
> nat-s11-4-lkws-stackdeploy-3.openstacklocal/172.22.71.168:10200
> 2016-08-15 23:48:03,297 [main] WARN client.SliderClient - The
> 'install-keytab' option has been deprecated. Please use 'keytab --install'.
> 2016-08-15 23:48:03,440 [main] WARN retry.RetryInvocationHandler - Exception
> while invoking ClientNamenodeProtocolTranslatorPB.mkdirs over null. Not
> retrying because try once and fail.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
> Permission denied: user=hive, access=WRITE,
> inode="/user/hive/.slider/keytabs/hive":hdfs:hdfs:drwxr-xr-x
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
> at
>
[jira] [Reopened] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service
[
https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez reopened AMBARI-18368:
--
> Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas
> Service
> -
>
> Key: AMBARI-18368
> URL: https://issues.apache.org/jira/browse/AMBARI-18368
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: trunk, 2.4.2
>
> Attachments: AMBARI-18368.patch
>
>
> Steps to Reproduce:
> * Install Ambari 2.2.2 with HDP 2.4 and HBase, Kafka, and Hive (this is very
> important)
> * Kerberize the cluster
> * Perform EU/RU to HDP 2.5
> * Add Atlas Service
> Atlas Server log contains,
> {code}
> Caused by:
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
> from server at
> http://natu146-ehbs-dgm10toeriesec-u14-1.openstacklocal:8886/solr: Can not
> find the specified config set: vertex_index
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:577)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
> at
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
> at
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1100)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:870)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:806)
> at
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
> at
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:166)
> at
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.createCollectionIfNotExists(Solr5Index.java:901)
> at
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.register(Solr5Index.java:269)
> at
> com.thinkaurelius.titan.diskstorage.indexing.IndexTransaction.register(IndexTransaction.java:83)
> at
> com.thinkaurelius.titan.graphdb.database.IndexSerializer.register(IndexSerializer.java:92)
> at
> com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.addIndexKey(ManagementSystem.java:534)
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.enhanceMixedIndex(GraphBackedSearchIndexer.java:405)
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.createIndexes(GraphBackedSearchIndexer.java:334)
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.initialize(GraphBackedSearchIndexer.java:103)
> ... 71 more
> {code}
> Atlas tables in HBase look ok.
> {code}
> su hbase
> kinit -kt /etc/security/keytabs/hbase.headless.keytab cstm-hb...@example.com
> hbase shell
> hbase(main):001:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_titan
> 2 row(s) in 1.4300 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_titan"]
> {code}
> h4. Workaround
> 1. Stop Atlas Server
> 2. Copy solr xml files to correct config folder and chown as
> $atlas_user:$hadoop_group
> {code}
> cp -R /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/solr/* /etc/atlas/conf/solr/
> cp: overwrite `/etc/atlas/conf/solr/solrconfig.xml'? n
> chown atlas:hadoop /etc/atlas/conf/solr/*
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/users-credentials.properties
> /etc/atlas/conf/
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/policy-store.txt /etc/atlas/conf/
> chown atlas:hadoop /etc/atlas/conf/users-credentials.properties
> chown atlas:hadoop /etc/atlas/conf/policy-store.txt
> {code}
> 3. Delete zookeeper znode,
> {code}
> # kinit -kt /etc/security/keytabs/atlas.service.keytab atlas/@
> # cd /usr/hdp/current/zookeeper-client/bin/
> # ./zkCli.sh -server :
> [ .. (CONNECTED) ] rmr /infra-solr/configs/atlas_configs
> {code}
> 4. Ensure Atlas application-properties are present for,
> atlas.jaas.KafkaClient.option.keyTab =
> /etc/security/keytabs/atlas.service.keytab
> atlas.jaas.KafkaClient.option.principal = atlas/_h...@example.com
> 5. Start Atlas
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18332) Blueprints: API should make available "setting" property from blueprint
[
https://issues.apache.org/jira/browse/AMBARI-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18332:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Blueprints: API should make available "setting" property from blueprint
> ---
>
> Key: AMBARI-18332
> URL: https://issues.apache.org/jira/browse/AMBARI-18332
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb51851.patch
>
>
> The following APIs do not retrieve *setting* section from the blueprint that
> was used during deployment:
> {code}
> http://:/api/v1/blueprints/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service
[
https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491816#comment-15491816
]
Alejandro Fernandez commented on AMBARI-18368:
--
There's an additional problem when Hive exists in HDP 2.4 and Atlas is not
present.
The Hive RPM installs /usr/$stack/$version/atlas with some partial packages
that contain Hive hooks, while the Atlas RPM is responsible for installing the
full content.
If the user does not have Atlas currently installed on their stack, then
/usr/$stack/current/atlas-clientwill be a broken symlink, and we should not
create the symlink /etc/atlas/conf -> /usr/$stack/current/atlas-client/conf .
If we mistakenly create this symlink, then when the user performs an EU/RU and
then adds Atlas service then the Atlas RPM will not be able to copy its
artifacts into /etc/atlas/conf directory and therefore prevent Ambari from by
copying those unmanaged contents into /etc/atlas/$version/0
Will reopen this Jira to provide an addendum patch for this related scenario.
> Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas
> Service
> -
>
> Key: AMBARI-18368
> URL: https://issues.apache.org/jira/browse/AMBARI-18368
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: trunk, 2.4.2
>
> Attachments: AMBARI-18368.patch
>
>
> Steps to Reproduce:
> * Install Ambari 2.2.2 with HDP 2.4 and HBase, Kafka, and Hive (this is very
> important)
> * Kerberize the cluster
> * Perform EU/RU to HDP 2.5
> * Add Atlas Service
> Atlas Server log contains,
> {code}
> Caused by:
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
> from server at
> http://natu146-ehbs-dgm10toeriesec-u14-1.openstacklocal:8886/solr: Can not
> find the specified config set: vertex_index
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:577)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
> at
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
> at
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1100)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:870)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:806)
> at
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
> at
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:166)
> at
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.createCollectionIfNotExists(Solr5Index.java:901)
> at
> com.thinkaurelius.titan.diskstorage.solr.Solr5Index.register(Solr5Index.java:269)
> at
> com.thinkaurelius.titan.diskstorage.indexing.IndexTransaction.register(IndexTransaction.java:83)
> at
> com.thinkaurelius.titan.graphdb.database.IndexSerializer.register(IndexSerializer.java:92)
> at
> com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.addIndexKey(ManagementSystem.java:534)
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.enhanceMixedIndex(GraphBackedSearchIndexer.java:405)
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.createIndexes(GraphBackedSearchIndexer.java:334)
> at
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.initialize(GraphBackedSearchIndexer.java:103)
> ... 71 more
> {code}
> Atlas tables in HBase look ok.
> {code}
> su hbase
> kinit -kt /etc/security/keytabs/hbase.headless.keytab cstm-hb...@example.com
> hbase shell
> hbase(main):001:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_titan
> 2 row(s) in 1.4300 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_titan"]
> {code}
> h4. Workaround
> 1. Stop Atlas Server
> 2. Copy solr xml files to correct config folder and chown as
> $atlas_user:$hadoop_group
> {code}
> cp -R /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/solr/* /etc/atlas/conf/solr/
> cp: overwrite `/etc/atlas/conf/solr/solrconfig.xml'? n
> chown atlas:hadoop /etc/atlas/conf/solr/*
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/users-credentials.properties
> /etc/atlas/conf/
> cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/policy-store.txt /etc/atlas/conf/
> chown atlas:hadoop
[jira] [Updated] (AMBARI-18368) Atlas web UI alert after performing stack upgrade to HDP 2.5 and adding Atlas Service
[
https://issues.apache.org/jira/browse/AMBARI-18368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-18368:
-
Description:
Steps to Reproduce:
* Install Ambari 2.2.2 with HDP 2.4 and HBase, Kafka, and Hive (this is very
important)
* Kerberize the cluster
* Perform EU/RU to HDP 2.5
* Add Atlas Service
Atlas Server log contains,
{code}
Caused by:
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
from server at
http://natu146-ehbs-dgm10toeriesec-u14-1.openstacklocal:8886/solr: Can not find
the specified config set: vertex_index
at
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:577)
at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
at
org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
at
org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
at
org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1100)
at
org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:870)
at
org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:806)
at
org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
at
org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:166)
at
com.thinkaurelius.titan.diskstorage.solr.Solr5Index.createCollectionIfNotExists(Solr5Index.java:901)
at
com.thinkaurelius.titan.diskstorage.solr.Solr5Index.register(Solr5Index.java:269)
at
com.thinkaurelius.titan.diskstorage.indexing.IndexTransaction.register(IndexTransaction.java:83)
at
com.thinkaurelius.titan.graphdb.database.IndexSerializer.register(IndexSerializer.java:92)
at
com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.addIndexKey(ManagementSystem.java:534)
at
org.apache.atlas.repository.graph.GraphBackedSearchIndexer.enhanceMixedIndex(GraphBackedSearchIndexer.java:405)
at
org.apache.atlas.repository.graph.GraphBackedSearchIndexer.createIndexes(GraphBackedSearchIndexer.java:334)
at
org.apache.atlas.repository.graph.GraphBackedSearchIndexer.initialize(GraphBackedSearchIndexer.java:103)
... 71 more
{code}
Atlas tables in HBase look ok.
{code}
su hbase
kinit -kt /etc/security/keytabs/hbase.headless.keytab cstm-hb...@example.com
hbase shell
hbase(main):001:0> list
TABLE
ATLAS_ENTITY_AUDIT_EVENTS
atlas_titan
2 row(s) in 1.4300 seconds
=> ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_titan"]
{code}
h4. Workaround
1. Stop Atlas Server
2. Copy solr xml files to correct config folder and chown as
$atlas_user:$hadoop_group
{code}
cp -R /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/solr/* /etc/atlas/conf/solr/
cp: overwrite `/etc/atlas/conf/solr/solrconfig.xml'? n
chown atlas:hadoop /etc/atlas/conf/solr/*
cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/users-credentials.properties
/etc/atlas/conf/
cp /usr/hdp/2.5.0.0-/etc/atlas/conf.dist/policy-store.txt /etc/atlas/conf/
chown atlas:hadoop /etc/atlas/conf/users-credentials.properties
chown atlas:hadoop /etc/atlas/conf/policy-store.txt
{code}
3. Delete zookeeper znode,
{code}
# kinit -kt /etc/security/keytabs/atlas.service.keytab atlas/@
# cd /usr/hdp/current/zookeeper-client/bin/
# ./zkCli.sh -server :
[ .. (CONNECTED) ] rmr /infra-solr/configs/atlas_configs
{code}
4. Ensure Atlas application-properties are present for,
atlas.jaas.KafkaClient.option.keyTab =
/etc/security/keytabs/atlas.service.keytab
atlas.jaas.KafkaClient.option.principal = atlas/_h...@example.com
5. Start Atlas
was:
Steps to Reproduce:
* Install Ambari 2.2.2 with HDP 2.4 (HBase, Solr)
* Kerberize the cluster
* Perform EU/RU to HDP 2.5
* Add Atlas Service
Atlas Server log contains,
{code}
Caused by:
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
from server at
http://natu146-ehbs-dgm10toeriesec-u14-1.openstacklocal:8886/solr: Can not find
the specified config set: vertex_index
at
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:577)
at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
at
org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
at
org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
at
org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1100)
at
[jira] [Updated] (AMBARI-18394) Blueprint-deployed cluster with NameNode HA out-of-the-box fails when starting Namenode during EU/RU
[ https://issues.apache.org/jira/browse/AMBARI-18394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18394: - Component/s: blueprints > Blueprint-deployed cluster with NameNode HA out-of-the-box fails when > starting Namenode during EU/RU > > > Key: AMBARI-18394 > URL: https://issues.apache.org/jira/browse/AMBARI-18394 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.2.2 >Reporter: Alejandro Fernandez > Fix For: trunk > > > STR: > * Use Blueprints to deploy cluster with NameNode HA out-of-the-box > * Attempt an EU/RU > The problem is that during a Blueprint deployment, it keeps the following 2 > configs in hadoop-env > dfs_ha_initial_namenode_active > dfs_ha_initial_namenode_standby > When it's time to perform an EU/RU (or start NN in general), then it thinks > that NameNode HA is still not complete. > Blueprint with HA out of the box needs a step to delete these configs after > the deployment is done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18394) Blueprint-deployed cluster with NameNode HA out-of-the-box fails when starting Namenode during EU/RU
Alejandro Fernandez created AMBARI-18394: Summary: Blueprint-deployed cluster with NameNode HA out-of-the-box fails when starting Namenode during EU/RU Key: AMBARI-18394 URL: https://issues.apache.org/jira/browse/AMBARI-18394 Project: Ambari Issue Type: Bug Affects Versions: 2.2.2 Reporter: Alejandro Fernandez Fix For: trunk STR: * Use Blueprints to deploy cluster with NameNode HA out-of-the-box * Attempt an EU/RU The problem is that during a Blueprint deployment, it keeps the following 2 configs in hadoop-env dfs_ha_initial_namenode_active dfs_ha_initial_namenode_standby When it's time to perform an EU/RU (or start NN in general), then it thinks that NameNode HA is still not complete. Blueprint with HA out of the box needs a step to delete these configs after the deployment is done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18389) Config compare shows incorrect value after enabling kerberos
[ https://issues.apache.org/jira/browse/AMBARI-18389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491669#comment-15491669 ] Hudson commented on AMBARI-18389: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5672 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5672/]) AMBARI-18389 - Config compare shows incorrect value after enabling (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9496772d9f662daefcb78f971a201df0172c2430]) * (edit) ambari-web/app/models/configs/objects/service_config_property.js * (edit) ambari-web/test/models/configs/objects/service_config_property_test.js > Config compare shows incorrect value after enabling kerberos > > > Key: AMBARI-18389 > URL: https://issues.apache.org/jira/browse/AMBARI-18389 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Blocker > Fix For: 2.4.1 > > Attachments: AMBARI-18389.patch > > > Config compare shows incorrect value after enabling kerberos. > - Current version = v17 > - Click on v16 (tracked config: ams-hbase-security-site :: > hbase.coprocessor.master.classes) > - Compare with v15 > - The compare screenshot shows both v15 and v16 have the same value for the > config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18393) Hive Server Interactive (HSI) fails to start with 'Permission denied' for User Hive, if HSI starts before HS2.
[
https://issues.apache.org/jira/browse/AMBARI-18393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491642#comment-15491642
]
Swapan Shridhar commented on AMBARI-18393:
--
Checkin:
trunk:
{code}
commit 565685d326e5a877f8e4479736e75f59f728c9ec
Author: Swapan Shridhar
Date: Wed Sep 14 15:37:51 2016 -0700
AMBARI-18393. Hive Server Interactive (HSI) fails to start with 'Permission
denied' for User Hive, if HSI starts before HS2.
{code}
branch-2.5:
{code}
commit 7594857e40da29baa3ff80832b04b57e4ffcf90d
Author: Swapan Shridhar
Date: Wed Sep 14 15:37:51 2016 -0700
AMBARI-18393. Hive Server Interactive (HSI) fails to start with 'Permission
denied' for User Hive, if HSI starts before HS2.
{code}
> Hive Server Interactive (HSI) fails to start with 'Permission denied' for
> User Hive, if HSI starts before HS2.
> --
>
> Key: AMBARI-18393
> URL: https://issues.apache.org/jira/browse/AMBARI-18393
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
>
> - Install Cluster using Blueprint including HiveServerInteractive
> - Start services fail at Hive interactive start, with below error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 535, in
> HiveServerInteractive().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 115, in start
> self.setup_security()
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 335, in setup_security
> Execute(slider_keytab_install_cmd, user=params.hive_user)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 71, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'slider install-keytab
> --keytab /etc/security/keytabs/hive.llap.zk.sm.keytab --folder hive
> --overwrite' returned 56. 2016-08-15 23:47:57,518 [main] INFO
> tools.SliderUtils - JVM initialized into secure mode with kerberos realm
> HWQE.HORTONWORKS.COM
> 2016-08-15 23:47:59,108 [main] INFO impl.TimelineClientImpl - Timeline
> service address:
> http://nat-s11-4-lkws-stackdeploy-3.openstacklocal:8188/ws/v1/timeline/
> 2016-08-15 23:48:01,584 [main] WARN shortcircuit.DomainSocketFactory - The
> short-circuit local reads feature cannot be used because libhadoop cannot be
> loaded.
> 2016-08-15 23:48:01,633 [main] INFO client.RMProxy - Connecting to
> ResourceManager at
> nat-s11-4-lkws-stackdeploy-5.openstacklocal/172.22.71.181:8050
> 2016-08-15 23:48:01,983 [main] INFO client.AHSProxy - Connecting to
> Application History server at
> nat-s11-4-lkws-stackdeploy-3.openstacklocal/172.22.71.168:10200
> 2016-08-15 23:48:03,297 [main] WARN client.SliderClient - The
> 'install-keytab' option has been deprecated. Please use 'keytab --install'.
> 2016-08-15 23:48:03,440 [main] WARN retry.RetryInvocationHandler - Exception
> while invoking ClientNamenodeProtocolTranslatorPB.mkdirs over null. Not
> retrying because try once and fail.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
> Permission denied: user=hive, access=WRITE,
> inode="/user/hive/.slider/keytabs/hive":hdfs:hdfs:drwxr-xr-x
>
[jira] [Updated] (AMBARI-18289) Invalid negative values for some AMS metrics
[ https://issues.apache.org/jira/browse/AMBARI-18289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18289: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5 and trunk. > Invalid negative values for some AMS metrics > > > Key: AMBARI-18289 > URL: https://issues.apache.org/jira/browse/AMBARI-18289 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18289-2.patch > > > PROBLEM > Negative values are being reported for IOPS in the "system servers" dashboard > BUG > This was a dockerized environment. Negative rate values were seen because > read/write counters were dropping below the previous values at random times. > On further investigation, it revealed that this was due to the docker volume > groups present on the host. It is expected of docker containers to add/remove > the volume groups during the lifecyle of a container. So, when a volume group > goes away, the read/write counters do not contribute to the total counter > values, thus making the value go below the last seen value. > FIX > Have a provision to discard such "special" disk partitions through a skip > pattern. Individual disk counter metrics can be used to get disk specific > counter values. If skipped, they will not contribute to the global counter > metric. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17458) Add support for distributed collector to Ambari REST API
[ https://issues.apache.org/jira/browse/AMBARI-17458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17458: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk. > Add support for distributed collector to Ambari REST API > > > Key: AMBARI-17458 > URL: https://issues.apache.org/jira/browse/AMBARI-17458 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Siddharth Wagle >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > > _Tasks_: > - Add a Zookeeper watcher for the AMS znode > - Find available collectors and round-robin the READ calls from > AMSPropertyProvider > - Tolerate failure by switching to available collector -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18378) View instance cloning functionality
[
https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491594#comment-15491594
]
Hadoop QA commented on AMBARI-18378:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12828511/AMBARI-18378.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8678//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8678//console
This message is automatically generated.
> View instance cloning functionality
> ---
>
> Key: AMBARI-18378
> URL: https://issues.apache.org/jira/browse/AMBARI-18378
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-admin, ambari-views
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Labels: patch
> Fix For: trunk
>
> Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg,
> ViewCloneInstance.jpg
>
>
> This task is for providing an option to clone / copy a view instance.
> A new "copy" icon will appear next to a view instance. Clicking on this opens
> up the existing view with instance name and display name of the view appended
> with _Copy.
> This will be useful when creating multiple view instances with mild
> configuration differences between them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18185) Selecting one host when topN is set, throws an error
[ https://issues.apache.org/jira/browse/AMBARI-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18185: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5 and trunk. > Selecting one host when topN is set, throws an error > > > Key: AMBARI-18185 > URL: https://issues.apache.org/jira/browse/AMBARI-18185 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18185.patch > > > topN is available by default on almost all Grafana templatized dashboards. > When viewing any of these dashboards, if only one "host" or templated option > is chosen, then AMS returns with an exception (screenshot attached). > Sample query: > collectorhost:6188/ws/v1/timeline/metrics?metricNames=cpu_system._avg=hostname=HOST=1470925360=1470946960=20=avg=false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18132) Remove FIFO and Normalizer in ams-env config.
[
https://issues.apache.org/jira/browse/AMBARI-18132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18132:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5 and trunk.
> Remove FIFO and Normalizer in ams-env config.
> -
>
> Key: AMBARI-18132
> URL: https://issues.apache.org/jira/browse/AMBARI-18132
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18132.patch
>
>
> It is currently
> {code}
> # HBase compaction policy enabled
> export HBASE_NORMALIZATION_ENABLED=True
> # HBase compaction policy enabled
> export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18154) Ambari Dashboard, Cluster load widget - Incorrect value in Nodes._avg metric
[ https://issues.apache.org/jira/browse/AMBARI-18154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18154: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5 and trunk. > Ambari Dashboard, Cluster load widget - Incorrect value in Nodes._avg metric > > > Key: AMBARI-18154 > URL: https://issues.apache.org/jira/browse/AMBARI-18154 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.0, 2.2.1, 2.2.2 >Reporter: Sandeep Nemuri >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18154.patch, Cluster_Load.png > > > *PROBLEM* : > Under Ambari Dashboard -> Cluster metrics. > It has been noticed that the metrics Nodes._avg and CPUs._avg are showing the > same data. > Below is the screenshot which shows Cluster metrics of a cluster which has > nodes 200+ and the Nodes._avg shows 18.5 as maximum value. > !Cluster_Load.png|align=center,|height=750%,width=700&! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18125) AMS : Allow for certain metrics to skip aggregation determined by client
[ https://issues.apache.org/jira/browse/AMBARI-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18125: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5 and trunk. > AMS : Allow for certain metrics to skip aggregation determined by client > > > Key: AMBARI-18125 > URL: https://issues.apache.org/jira/browse/AMBARI-18125 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18125.patch > > > _Example_: Per disk metrics / host static info (no aggregation across hosts) > The client should be able to submit a request which dimension should be > skipped. > The metadata can store this info and allow the SELECT query projection to > skip a chunk of these metrics based on what aggregation is working. > For now only across host skipping makes sense and the client part can be put > in later. > *Note*: > Sub-task, de-normalize disk metrics so that user can find out disk per host. > Grafana implication: The non-aggregated metrics can obviously be visualized > only on the templatized / host dashboard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18367) Create authentication filter to encapsulate the various Ambari authentication methods
[
https://issues.apache.org/jira/browse/AMBARI-18367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491566#comment-15491566
]
Hadoop QA commented on AMBARI-18367:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12828479/AMBARI-18367_trunk_01.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8676//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8676//console
This message is automatically generated.
> Create authentication filter to encapsulate the various Ambari authentication
> methods
> -
>
> Key: AMBARI-18367
> URL: https://issues.apache.org/jira/browse/AMBARI-18367
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: authentication, kerberos, security
> Fix For: 2.5.0
>
> Attachments: AMBARI-18367_branch-2.5_01.patch,
> AMBARI-18367_trunk_01.patch
>
>
> Create a Spring authentication filter to encapsulate the various Ambari
> authentication methods since the Spring filter chain allows for a single
> authentication filter and Ambari needs to allow for multiple, optional,
> authentication filters to handle one of (but not limited to) the following
> authentication methods:
> * Basic Auth
> * SSO (JWT)
> * Kerberos token
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18393) Hive Server Interactive (HSI) fails to start with 'Permission denied' for User Hive, if HSI starts before HS2.
Swapan Shridhar created AMBARI-18393:
Summary: Hive Server Interactive (HSI) fails to start with
'Permission denied' for User Hive, if HSI starts before HS2.
Key: AMBARI-18393
URL: https://issues.apache.org/jira/browse/AMBARI-18393
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Swapan Shridhar
Assignee: Swapan Shridhar
Fix For: 2.5.0
- Install Cluster using Blueprint including HiveServerInteractive
- Start services fail at Hive interactive start, with below error:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
line 535, in
HiveServerInteractive().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
line 115, in start
self.setup_security()
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
line 335, in setup_security
Execute(slider_keytab_install_cmd, user=params.hive_user)
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 273, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 71, in inner
result = function(command, **kwargs)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 93, in checked_call
tries=tries, try_sleep=try_sleep)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 141, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 294, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'slider install-keytab
--keytab /etc/security/keytabs/hive.llap.zk.sm.keytab --folder hive
--overwrite' returned 56. 2016-08-15 23:47:57,518 [main] INFO
tools.SliderUtils - JVM initialized into secure mode with kerberos realm
HWQE.HORTONWORKS.COM
2016-08-15 23:47:59,108 [main] INFO impl.TimelineClientImpl - Timeline service
address: http://nat-s11-4-lkws-stackdeploy-3.openstacklocal:8188/ws/v1/timeline/
2016-08-15 23:48:01,584 [main] WARN shortcircuit.DomainSocketFactory - The
short-circuit local reads feature cannot be used because libhadoop cannot be
loaded.
2016-08-15 23:48:01,633 [main] INFO client.RMProxy - Connecting to
ResourceManager at
nat-s11-4-lkws-stackdeploy-5.openstacklocal/172.22.71.181:8050
2016-08-15 23:48:01,983 [main] INFO client.AHSProxy - Connecting to
Application History server at
nat-s11-4-lkws-stackdeploy-3.openstacklocal/172.22.71.168:10200
2016-08-15 23:48:03,297 [main] WARN client.SliderClient - The 'install-keytab'
option has been deprecated. Please use 'keytab --install'.
2016-08-15 23:48:03,440 [main] WARN retry.RetryInvocationHandler - Exception
while invoking ClientNamenodeProtocolTranslatorPB.mkdirs over null. Not
retrying because try once and fail.
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
Permission denied: user=hive, access=WRITE,
inode="/user/hive/.slider/keytabs/hive":hdfs:hdfs:drwxr-xr-x
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:292)
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:213)
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1827)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1811)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1794)
at
org.apache.hadoop.hdfs.server.namenode.FSDirMkdirOp.mkdirs(FSDirMkdirOp.java:71)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirs(FSNamesystem.java:4011)
at
[jira] [Updated] (AMBARI-18389) Config compare shows incorrect value after enabling kerberos
[ https://issues.apache.org/jira/browse/AMBARI-18389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18389: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, 2.4 and 2.5 > Config compare shows incorrect value after enabling kerberos > > > Key: AMBARI-18389 > URL: https://issues.apache.org/jira/browse/AMBARI-18389 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Blocker > Fix For: 2.4.1 > > Attachments: AMBARI-18389.patch > > > Config compare shows incorrect value after enabling kerberos. > - Current version = v17 > - Click on v16 (tracked config: ams-hbase-security-site :: > hbase.coprocessor.master.classes) > - Compare with v15 > - The compare screenshot shows both v15 and v16 have the same value for the > config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services
[
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491501#comment-15491501
]
Matt commented on AMBARI-15538:
---
Just tested the patch. Confirming that it works for HAWQ use case!
> Support service-specific repo for add-on services
> -
>
> Key: AMBARI-15538
> URL: https://issues.apache.org/jira/browse/AMBARI-15538
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Jayush Luniya
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch6-trunk.diff
>
>
> The approach for custom-services to specify their own repo location will be
> to provide a {{/repos/repoinfo.xml}} inside the stack-version they will be
> in. This repo file will be loaded by Ambari during startup into the
> {{/api/v1/stacks/HDP/versions/2.4/repository_versions}} repos. *Service repo
> files have a restriction that their (repo-name, base-url) locations should be
> unique and not conflict*. When conflicts do occur, they will not be loaded
> into the stacks model.
> Now the management-pack will provide such repos/ folder in
> {{mpacks/custom-services/8.0.0/repos}} which will be linked into the stacks/
> folder.
> {{ambari/ambari-server/src/main/resources/stacks/HDP/2.3/services/SERVICE_NAME/repos
> -> mpacks/custom-services/8.0.0/repos}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18388) UI: add missing unit tests for models/configs/* and models/stack_version/* files
[
https://issues.apache.org/jira/browse/AMBARI-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491409#comment-15491409
]
Hudson commented on AMBARI-18388:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5671 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5671/])
AMBARI-18388. Link UI: add missing unit tests for models/configs/* and (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=08e426ac790957e3fab3edeef128a331fd5860bc])
* (edit) ambari-web/test/init_computed_aliases.js
* (add) ambari-web/test/models/configs/theme/section_test.js
* (edit) ambari-web/app/assets/test/tests.js
* (delete) ambari-web/test/models/configs/sub_section_test.js
* (add) ambari-web/test/aliases/computed/concat.js
* (add) ambari-web/test/models/configs/theme/sub_section_test.js
* (add) ambari-web/test/models/stack_version/service_simple_test.js
* (add) ambari-web/test/models/stack_version/version_test.js
* (add) ambari-web/test/aliases/computed/empty.js
* (edit) ambari-web/test/aliases/computed/equal.js
* (add) ambari-web/test/models/configs/theme/sub_section_tab_test.js
* (edit) ambari-web/app/models/stack_version/service_simple.js
* (delete) ambari-web/test/models/configs/section_test.js
* (edit) ambari-web/app/models/stack_version/version.js
> UI: add missing unit tests for models/configs/* and models/stack_version/*
> files
>
>
> Key: AMBARI-18388
> URL: https://issues.apache.org/jira/browse/AMBARI-18388
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-18388.patch
>
>
> Cover the following files with unit tests:
> - {{ambari-web/app/models/configs/theme/sub_section_tab.js}};
> - {{ambari-web/app/models/stack_version/service_simple.js}};
> - {{ambari-web/app/models/stack_version/version.js}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18389) Config compare shows incorrect value after enabling kerberos
[ https://issues.apache.org/jira/browse/AMBARI-18389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18389: -- Attachment: (was: AMBARI-18389.patch) > Config compare shows incorrect value after enabling kerberos > > > Key: AMBARI-18389 > URL: https://issues.apache.org/jira/browse/AMBARI-18389 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Blocker > Fix For: 2.4.1 > > Attachments: AMBARI-18389.patch > > > Config compare shows incorrect value after enabling kerberos. > - Current version = v17 > - Click on v16 (tracked config: ams-hbase-security-site :: > hbase.coprocessor.master.classes) > - Compare with v15 > - The compare screenshot shows both v15 and v16 have the same value for the > config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18389) Config compare shows incorrect value after enabling kerberos
[ https://issues.apache.org/jira/browse/AMBARI-18389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18389: -- Attachment: AMBARI-18389.patch > Config compare shows incorrect value after enabling kerberos > > > Key: AMBARI-18389 > URL: https://issues.apache.org/jira/browse/AMBARI-18389 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Blocker > Fix For: 2.4.1 > > Attachments: AMBARI-18389.patch > > > Config compare shows incorrect value after enabling kerberos. > - Current version = v17 > - Click on v16 (tracked config: ams-hbase-security-site :: > hbase.coprocessor.master.classes) > - Compare with v15 > - The compare screenshot shows both v15 and v16 have the same value for the > config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-15538:
---
Priority: Critical (was: Major)
> Support service-specific repo for add-on services
> -
>
> Key: AMBARI-15538
> URL: https://issues.apache.org/jira/browse/AMBARI-15538
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Jayush Luniya
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch6-trunk.diff
>
>
> The approach for custom-services to specify their own repo location will be
> to provide a {{/repos/repoinfo.xml}} inside the stack-version they will be
> in. This repo file will be loaded by Ambari during startup into the
> {{/api/v1/stacks/HDP/versions/2.4/repository_versions}} repos. *Service repo
> files have a restriction that their (repo-name, base-url) locations should be
> unique and not conflict*. When conflicts do occur, they will not be loaded
> into the stacks model.
> Now the management-pack will provide such repos/ folder in
> {{mpacks/custom-services/8.0.0/repos}} which will be linked into the stacks/
> folder.
> {{ambari/ambari-server/src/main/resources/stacks/HDP/2.3/services/SERVICE_NAME/repos
> -> mpacks/custom-services/8.0.0/repos}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18386) Handle Ranger hive repo config jdbc url change for stack 2.5
[
https://issues.apache.org/jira/browse/AMBARI-18386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491340#comment-15491340
]
Hadoop QA commented on AMBARI-18386:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12828487/AMBARI-18386.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8675//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8675//console
This message is automatically generated.
> Handle Ranger hive repo config jdbc url change for stack 2.5
>
>
> Key: AMBARI-18386
> URL: https://issues.apache.org/jira/browse/AMBARI-18386
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.4.1, 2.4.2
>
> Attachments: AMBARI-18386.1.patch, AMBARI-18386.patch
>
>
> From ambari stacks for Ranger: enable ranger hive plugin takes care of using
> right jdbc url for repo configs that are set for creating a repository in
> Ranger for Secure and simple install of hive.
> However in HiverServer2 HA env, jdbc url needs to change in repo config with
> zk url.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18392) Cluster failure due to APP_TIMELINE_SERVER and RESOURCEMANAGER failed to start
[
https://issues.apache.org/jira/browse/AMBARI-18392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18392:
---
Attachment: AMBARI-18392.patch
> Cluster failure due to APP_TIMELINE_SERVER and RESOURCEMANAGER failed to start
> --
>
> Key: AMBARI-18392
> URL: https://issues.apache.org/jira/browse/AMBARI-18392
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18392.patch
>
>
> Exception Trace
> {code}
> Error accessing file:/usr/hdp/2.5.1.0-28/oozie/share/lib/spark
> azure: java.io.IOException: Error accessing
> file:/usr/hdp/2.5.1.0-28/oozie/share/lib/spark
> azure: at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1536)
> azure: at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1574)
> azure: at
> org.apache.hadoop.fs.ChecksumFileSystem.listStatus(ChecksumFileSystem.java:676)
> azure: at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:357)
> azure: at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:359)
> azure: at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:359)
> azure: at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:341)
> azure: at
> org.apache.hadoop.fs.FileSystem.copyFromLocalFile(FileSystem.java:1986)
> azure: at
> org.apache.hadoop.fs.FileSystem.copyFromLocalFile(FileSystem.java:1954)
> azure: at
> org.apache.hadoop.fs.FileSystem.copyFromLocalFile(FileSystem.java:1919)
> azure: at
> org.apache.ambari.fast_hdfs_resource.Resource.createResource(Resource.java:216)
> azure: at org.apache.ambari.fast_hdfs_resource.Runner.main(Runner.java:83)
> azure: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> azure: at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> azure: at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> azure: at java.lang.reflect.Method.invoke(Method.java:498)
> azure: at org.apache.hadoop.util.RunJar.run(RunJar.java:233)
> azure: at org.apache.hadoop.util.RunJar.main(RunJar.java:148)
> {code}
> RC
> Not all the required directories were created on the DFS as part of the sys
> prep thus both Application Timeline server and Resource Manager are failing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18392) Cluster failure due to APP_TIMELINE_SERVER and RESOURCEMANAGER failed to start
Aravindan Vijayan created AMBARI-18392:
--
Summary: Cluster failure due to APP_TIMELINE_SERVER and
RESOURCEMANAGER failed to start
Key: AMBARI-18392
URL: https://issues.apache.org/jira/browse/AMBARI-18392
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Blocker
Fix For: 2.5.0
Exception Trace
{code}
Error accessing file:/usr/hdp/2.5.1.0-28/oozie/share/lib/spark
azure: java.io.IOException: Error accessing
file:/usr/hdp/2.5.1.0-28/oozie/share/lib/spark
azure: at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1536)
azure: at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1574)
azure: at
org.apache.hadoop.fs.ChecksumFileSystem.listStatus(ChecksumFileSystem.java:676)
azure: at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:357)
azure: at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:359)
azure: at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:359)
azure: at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:341)
azure: at
org.apache.hadoop.fs.FileSystem.copyFromLocalFile(FileSystem.java:1986)
azure: at
org.apache.hadoop.fs.FileSystem.copyFromLocalFile(FileSystem.java:1954)
azure: at
org.apache.hadoop.fs.FileSystem.copyFromLocalFile(FileSystem.java:1919)
azure: at
org.apache.ambari.fast_hdfs_resource.Resource.createResource(Resource.java:216)
azure: at org.apache.ambari.fast_hdfs_resource.Runner.main(Runner.java:83)
azure: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
azure: at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
azure: at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
azure: at java.lang.reflect.Method.invoke(Method.java:498)
azure: at org.apache.hadoop.util.RunJar.run(RunJar.java:233)
azure: at org.apache.hadoop.util.RunJar.main(RunJar.java:148)
{code}
RC
Not all the required directories were created on the DFS as part of the sys
prep thus both Application Timeline server and Resource Manager are failing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18384) Analyze and Optimize Ambari Server Unit Tests - Group 3
[
https://issues.apache.org/jira/browse/AMBARI-18384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491297#comment-15491297
]
Hadoop QA commented on AMBARI-18384:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12828472/AMBARI-18384.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8674//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8674//console
This message is automatically generated.
> Analyze and Optimize Ambari Server Unit Tests - Group 3
> ---
>
> Key: AMBARI-18384
> URL: https://issues.apache.org/jira/browse/AMBARI-18384
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: trunk
>
> Attachments: AMBARI-18384.patch
>
>
> ||Test||Count||Time (s)||
> |org.apache.ambari.server.security.authorization.TestUsers|31|50.4|
> |org.apache.ambari.server.upgrade.UpgradeCatalog210Test |18|46.497|
> |org.apache.ambari.server.state.svccomphost.ServiceComponentHostTest|15|43.899|
> |org.apache.ambari.server.serveraction.upgrades.UpgradeActionTest|9|35.136|
> |org.apache.ambari.server.agent.TestHeartbeatMonitor|6|28.146|
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18390) Configuration warnings during "Add Service" Wizard includes seemingly nonsensical heapsize recommendations
[
https://issues.apache.org/jira/browse/AMBARI-18390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zack Marsh updated AMBARI-18390:
Attachment: log.zip
Attaching log files from the Ambari server host.
> Configuration warnings during "Add Service" Wizard includes seemingly
> nonsensical heapsize recommendations
> --
>
> Key: AMBARI-18390
> URL: https://issues.apache.org/jira/browse/AMBARI-18390
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
> Environment: SLES11 SP3
>Reporter: Zack Marsh
> Attachments: Ambari_Metrics_Warnings_1.png,
> Ambari_Metrics_Warnings_2.png, Ambari_Metrics_Warnings_3.png, log.zip
>
>
> On an HDP 2.5.0.0 + Ambari 2.4.0.1 cluster, I'm prompted with
> misconfiguration warnings while adding a service (e.g. Kafka in this case).
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 896
> 246061 MB RAM is unused on the host zeus.labs.teradata.com based on
> components assigned.
> Consider allocating 48905 MB to metrics_collector_heapsize in ams-env, 32768
> MB to hbase_master_heapsize in ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 256
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_1.png for a screenshot of Ambari's
> warnings.
> So per the recommendations, I set:
> * metrics_collector_heapsize = 48905 MB
> * hbase_master_heapsize = 32768 MB
> * hbase_master_xmn_size = 3968 MB
> Saved changes and restarted Ambari Metrics.
> Now when I try adding a service again, I'm prompted with the following
> warnings:
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 32768
> 165796 MB RAM is unused on the host zeus1.labs.teradata.com based on
> components assigned. Consider allocating 81245 MB to
> metrics_collector_heapsize in ams-env, 32768 MB to hbase_master_heapsize in
> ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 3968
> Value is lesser than the recommended minimum Xmn size of 4025 (12% of
> hbase_master_heapsize + hbase_regionserver_heapsize)
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_2.png for a screenshot of Ambari's
> warnings.
> Set:
> * metrics_collector_heapsize = 81245 MB
> * hbase_master_xmn_size = 4025 MB
> Saved changes and restarted Ambari Metrics.
> Now when I try adding a service for a third time, I'm prompted with the
> following warnings:
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 32768
> 133456 MB RAM is unused on the host zeus1.labs.teradata.com based on
> components assigned. Consider allocating 107117 MB to
> metrics_collector_heapsize in ams-env, 32768 MB to hbase_master_heapsize in
> ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 4025
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_3.png for a screenshot of Ambari's
> warnings.
> At this point I stopped because the recommended settings were already
> non-sensical.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18390) Configuration warnings during "Add Service" Wizard includes seemingly nonsensical heapsize recommendations
[
https://issues.apache.org/jira/browse/AMBARI-18390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zack Marsh updated AMBARI-18390:
Attachment: Ambari_Metrics_Warnings_1.png
Ambari_Metrics_Warnings_2.png
Ambari_Metrics_Warnings_3.png
> Configuration warnings during "Add Service" Wizard includes seemingly
> nonsensical heapsize recommendations
> --
>
> Key: AMBARI-18390
> URL: https://issues.apache.org/jira/browse/AMBARI-18390
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
> Environment: SLES11 SP3
>Reporter: Zack Marsh
> Attachments: Ambari_Metrics_Warnings_1.png,
> Ambari_Metrics_Warnings_2.png, Ambari_Metrics_Warnings_3.png, log.zip
>
>
> On an HDP 2.5.0.0 + Ambari 2.4.0.1 cluster, I'm prompted with
> misconfiguration warnings while adding a service (e.g. Kafka in this case).
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 896
> 246061 MB RAM is unused on the host zeus.labs.teradata.com based on
> components assigned.
> Consider allocating 48905 MB to metrics_collector_heapsize in ams-env, 32768
> MB to hbase_master_heapsize in ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 256
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_1.png for a screenshot of Ambari's
> warnings.
> So per the recommendations, I set:
> * metrics_collector_heapsize = 48905 MB
> * hbase_master_heapsize = 32768 MB
> * hbase_master_xmn_size = 3968 MB
> Saved changes and restarted Ambari Metrics.
> Now when I try adding a service again, I'm prompted with the following
> warnings:
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 32768
> 165796 MB RAM is unused on the host zeus1.labs.teradata.com based on
> components assigned. Consider allocating 81245 MB to
> metrics_collector_heapsize in ams-env, 32768 MB to hbase_master_heapsize in
> ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 3968
> Value is lesser than the recommended minimum Xmn size of 4025 (12% of
> hbase_master_heapsize + hbase_regionserver_heapsize)
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_2.png for a screenshot of Ambari's
> warnings.
> Set:
> * metrics_collector_heapsize = 81245 MB
> * hbase_master_xmn_size = 4025 MB
> Saved changes and restarted Ambari Metrics.
> Now when I try adding a service for a third time, I'm prompted with the
> following warnings:
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 32768
> 133456 MB RAM is unused on the host zeus1.labs.teradata.com based on
> components assigned. Consider allocating 107117 MB to
> metrics_collector_heapsize in ams-env, 32768 MB to hbase_master_heapsize in
> ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 4025
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_3.png for a screenshot of Ambari's
> warnings.
> At this point I stopped because the recommended settings were already
> non-sensical.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18390) Configuration warnings during "Add Service" Wizard includes seemingly nonsensical heapsize recommendations
[
https://issues.apache.org/jira/browse/AMBARI-18390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zack Marsh updated AMBARI-18390:
Summary: Configuration warnings during "Add Service" Wizard includes
seemingly nonsensical heapsize recommendations (was: Configuration warnings
during "Add Service" Wizard include seemingly nonsensical heapsize
recommendations)
> Configuration warnings during "Add Service" Wizard includes seemingly
> nonsensical heapsize recommendations
> --
>
> Key: AMBARI-18390
> URL: https://issues.apache.org/jira/browse/AMBARI-18390
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
> Environment: SLES11 SP3
>Reporter: Zack Marsh
>
> On an HDP 2.5.0.0 + Ambari 2.4.0.1 cluster, I'm prompted with
> misconfiguration warnings while adding a service (e.g. Kafka in this case).
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 896
> 246061 MB RAM is unused on the host zeus.labs.teradata.com based on
> components assigned.
> Consider allocating 48905 MB to metrics_collector_heapsize in ams-env, 32768
> MB to hbase_master_heapsize in ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 256
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_1.png for a screenshot of Ambari's
> warnings.
> So per the recommendations, I set:
> * metrics_collector_heapsize = 48905 MB
> * hbase_master_heapsize = 32768 MB
> * hbase_master_xmn_size = 3968 MB
> Saved changes and restarted Ambari Metrics.
> Now when I try adding a service again, I'm prompted with the following
> warnings:
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 32768
> 165796 MB RAM is unused on the host zeus1.labs.teradata.com based on
> components assigned. Consider allocating 81245 MB to
> metrics_collector_heapsize in ams-env, 32768 MB to hbase_master_heapsize in
> ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 3968
> Value is lesser than the recommended minimum Xmn size of 4025 (12% of
> hbase_master_heapsize + hbase_regionserver_heapsize)
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_2.png for a screenshot of Ambari's
> warnings.
> Set:
> * metrics_collector_heapsize = 81245 MB
> * hbase_master_xmn_size = 4025 MB
> Saved changes and restarted Ambari Metrics.
> Now when I try adding a service for a third time, I'm prompted with the
> following warnings:
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 32768
> 133456 MB RAM is unused on the host zeus1.labs.teradata.com based on
> components assigned. Consider allocating 107117 MB to
> metrics_collector_heapsize in ams-env, 32768 MB to hbase_master_heapsize in
> ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 4025
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_3.png for a screenshot of Ambari's
> warnings.
> At this point I stopped because the recommended settings were already
> non-sensical.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18391) Prerequisite checks should only check services that are getting upgraded
Nate Cole created AMBARI-18391: -- Summary: Prerequisite checks should only check services that are getting upgraded Key: AMBARI-18391 URL: https://issues.apache.org/jira/browse/AMBARI-18391 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Priority: Critical Fix For: 3.0.0 Prerequisite checks, when used for a service, should check that they are also in the VDF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18390) Configuration warnings during "Add Service" Wizard include seemingly nonsensical heapsize recommendations
Zack Marsh created AMBARI-18390:
---
Summary: Configuration warnings during "Add Service" Wizard
include seemingly nonsensical heapsize recommendations
Key: AMBARI-18390
URL: https://issues.apache.org/jira/browse/AMBARI-18390
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.4.0
Environment: SLES11 SP3
Reporter: Zack Marsh
On an HDP 2.5.0.0 + Ambari 2.4.0.1 cluster, I'm prompted with misconfiguration
warnings while adding a service (e.g. Kafka in this case).
{code}
Warning, Ambari Metrics, hbase_master_heapsize, 896
246061 MB RAM is unused on the host zeus.labs.teradata.com based on components
assigned.
Consider allocating 48905 MB to metrics_collector_heapsize in ams-env, 32768 MB
to hbase_master_heapsize in ams-hbase-env
HBase Master Heap Size. In embedded mode, total heap size is sum of master and
regionserver heap sizes.
{code}
{code}
Warning, Ambari Metrics, hbase_master_xmn_size, 256
Consider allocating 3968 MB to use up some unused memory on host
HBase Master maximum value for young generation heap size.
{code}
See attached file Ambari_Metrics_Warnings_1.png for a screenshot of Ambari's
warnings.
So per the recommendations, I set:
* metrics_collector_heapsize = 48905 MB
* hbase_master_heapsize = 32768 MB
* hbase_master_xmn_size = 3968 MB
Saved changes and restarted Ambari Metrics.
Now when I try adding a service again, I'm prompted with the following warnings:
{code}
Warning,Ambari Metrics, hbase_master_heapsize, 32768
165796 MB RAM is unused on the host zeus1.labs.teradata.com based on components
assigned. Consider allocating 81245 MB to metrics_collector_heapsize in
ams-env, 32768 MB to hbase_master_heapsize in ams-hbase-env
HBase Master Heap Size. In embedded mode, total heap size is sum of master and
regionserver heap sizes.
{code}
{code}
Warning,Ambari Metrics, hbase_master_xmn_size, 3968
Value is lesser than the recommended minimum Xmn size of 4025 (12% of
hbase_master_heapsize + hbase_regionserver_heapsize)
Consider allocating 3968 MB to use up some unused memory on host
HBase Master maximum value for young generation heap size.
{code}
See attached file Ambari_Metrics_Warnings_2.png for a screenshot of Ambari's
warnings.
Set:
* metrics_collector_heapsize = 81245 MB
* hbase_master_xmn_size = 4025 MB
Saved changes and restarted Ambari Metrics.
Now when I try adding a service for a third time, I'm prompted with the
following warnings:
{code}
Warning,Ambari Metrics, hbase_master_heapsize, 32768
133456 MB RAM is unused on the host zeus1.labs.teradata.com based on components
assigned. Consider allocating 107117 MB to metrics_collector_heapsize in
ams-env, 32768 MB to hbase_master_heapsize in ams-hbase-env
HBase Master Heap Size. In embedded mode, total heap size is sum of master and
regionserver heap sizes.
{code}
{code}
Warning,Ambari Metrics, hbase_master_xmn_size, 4025
Consider allocating 3968 MB to use up some unused memory on host
HBase Master maximum value for young generation heap size.
{code}
See attached file Ambari_Metrics_Warnings_3.png for a screenshot of Ambari's
warnings.
At this point I stopped because the recommended settings were already
non-sensical.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18389) Config compare shows incorrect value after enabling kerberos
[ https://issues.apache.org/jira/browse/AMBARI-18389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18389: -- Status: Patch Available (was: Open) > Config compare shows incorrect value after enabling kerberos > > > Key: AMBARI-18389 > URL: https://issues.apache.org/jira/browse/AMBARI-18389 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Blocker > Fix For: 2.4.1 > > Attachments: AMBARI-18389.patch > > > Config compare shows incorrect value after enabling kerberos. > - Current version = v17 > - Click on v16 (tracked config: ams-hbase-security-site :: > hbase.coprocessor.master.classes) > - Compare with v15 > - The compare screenshot shows both v15 and v16 have the same value for the > config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18389) Config compare shows incorrect value after enabling kerberos
[ https://issues.apache.org/jira/browse/AMBARI-18389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18389: -- Attachment: AMBARI-18389.patch > Config compare shows incorrect value after enabling kerberos > > > Key: AMBARI-18389 > URL: https://issues.apache.org/jira/browse/AMBARI-18389 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Blocker > Fix For: 2.4.1 > > Attachments: AMBARI-18389.patch > > > Config compare shows incorrect value after enabling kerberos. > - Current version = v17 > - Click on v16 (tracked config: ams-hbase-security-site :: > hbase.coprocessor.master.classes) > - Compare with v15 > - The compare screenshot shows both v15 and v16 have the same value for the > config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18389) Config compare shows incorrect value after enabling kerberos
Richard Zang created AMBARI-18389: - Summary: Config compare shows incorrect value after enabling kerberos Key: AMBARI-18389 URL: https://issues.apache.org/jira/browse/AMBARI-18389 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Richard Zang Assignee: Richard Zang Priority: Blocker Fix For: 2.4.1 Config compare shows incorrect value after enabling kerberos. - Current version = v17 - Click on v16 (tracked config: ams-hbase-security-site :: hbase.coprocessor.master.classes) - Compare with v15 - The compare screenshot shows both v15 and v16 have the same value for the config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18378) View instance cloning functionality
[ https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18378: Attachment: (was: AMBARI-18378.patch) > View instance cloning functionality > --- > > Key: AMBARI-18378 > URL: https://issues.apache.org/jira/browse/AMBARI-18378 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-views >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg, > ViewCloneInstance.jpg > > > This task is for providing an option to clone / copy a view instance. > A new "copy" icon will appear next to a view instance. Clicking on this opens > up the existing view with instance name and display name of the view appended > with _Copy. > This will be useful when creating multiple view instances with mild > configuration differences between them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18378) View instance cloning functionality
[ https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18378: Attachment: AMBARI-18378.patch > View instance cloning functionality > --- > > Key: AMBARI-18378 > URL: https://issues.apache.org/jira/browse/AMBARI-18378 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-views >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg, > ViewCloneInstance.jpg > > > This task is for providing an option to clone / copy a view instance. > A new "copy" icon will appear next to a view instance. Clicking on this opens > up the existing view with instance name and display name of the view appended > with _Copy. > This will be useful when creating multiple view instances with mild > configuration differences between them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18378) View instance cloning functionality
[ https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18378: Status: Open (was: Patch Available) > View instance cloning functionality > --- > > Key: AMBARI-18378 > URL: https://issues.apache.org/jira/browse/AMBARI-18378 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-views >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg, > ViewCloneInstance.jpg > > > This task is for providing an option to clone / copy a view instance. > A new "copy" icon will appear next to a view instance. Clicking on this opens > up the existing view with instance name and display name of the view appended > with _Copy. > This will be useful when creating multiple view instances with mild > configuration differences between them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18378) View instance cloning functionality
[ https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18378: Status: Patch Available (was: Open) > View instance cloning functionality > --- > > Key: AMBARI-18378 > URL: https://issues.apache.org/jira/browse/AMBARI-18378 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-views >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg, > ViewCloneInstance.jpg > > > This task is for providing an option to clone / copy a view instance. > A new "copy" icon will appear next to a view instance. Clicking on this opens > up the existing view with instance name and display name of the view appended > with _Copy. > This will be useful when creating multiple view instances with mild > configuration differences between them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18385) Add HDF management pack
[ https://issues.apache.org/jira/browse/AMBARI-18385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491189#comment-15491189 ] Hudson commented on AMBARI-18385: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5670 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5670/]) AMBARI-18385: Add HDF management pack (jluniya) (jluniya: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=752e7c46391e1a50f99ab5e3513dfdfc813f6228]) * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/nifi-env.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/nifi-flow-env.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/nifi-login-identity-providers-env.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/ranger-nifi-security.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/ranger-nifi-policymgr-ssl.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/nifi-bootstrap-notification-services-env.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/nifi-node-logback-env.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/nifi-ambari-ssl-config.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/nifi-state-management-env.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/nifi-ambari-config.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/nifi-authorizers-env.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/nifi-bootstrap-env.xml * (edit) contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/configuration/ranger-nifi-audit.xml > Add HDF management pack > --- > > Key: AMBARI-18385 > URL: https://issues.apache.org/jira/browse/AMBARI-18385 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: trunk >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: trunk > > Attachments: AMBARI-18385.patch > > > Add HDF management pack to Ambari -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18388) UI: add missing unit tests for models/configs/* and models/stack_version/* files
[
https://issues.apache.org/jira/browse/AMBARI-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-18388:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk
> UI: add missing unit tests for models/configs/* and models/stack_version/*
> files
>
>
> Key: AMBARI-18388
> URL: https://issues.apache.org/jira/browse/AMBARI-18388
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-18388.patch
>
>
> Cover the following files with unit tests:
> - {{ambari-web/app/models/configs/theme/sub_section_tab.js}};
> - {{ambari-web/app/models/stack_version/service_simple.js}};
> - {{ambari-web/app/models/stack_version/version.js}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18388) UI: add missing unit tests for models/configs/* and models/stack_version/* files
[
https://issues.apache.org/jira/browse/AMBARI-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491079#comment-15491079
]
Hadoop QA commented on AMBARI-18388:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12828481/AMBARI-18388.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 10 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-web
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8673//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8673//console
This message is automatically generated.
> UI: add missing unit tests for models/configs/* and models/stack_version/*
> files
>
>
> Key: AMBARI-18388
> URL: https://issues.apache.org/jira/browse/AMBARI-18388
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-18388.patch
>
>
> Cover the following files with unit tests:
> - {{ambari-web/app/models/configs/theme/sub_section_tab.js}};
> - {{ambari-web/app/models/stack_version/service_simple.js}};
> - {{ambari-web/app/models/stack_version/version.js}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18365) Add Ambari configuration options to support Kerberos token authentication
[
https://issues.apache.org/jira/browse/AMBARI-18365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491066#comment-15491066
]
Hudson commented on AMBARI-18365:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #35 (See
[https://builds.apache.org/job/Ambari-branch-2.5/35/])
Revert "AMBARI-18365. Add Ambari configuration options to support (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c0e0a5331889d4a7578d54dee15e9cd0396e])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
AMBARI-18365. Add Ambari configuration options to support Kerberos token
(rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=170b293403ec4fa11353b58d95c65dc5761bb989])
* (add)
ambari-server/src/main/java/org/apache/ambari/server/security/authentication/kerberos/AmbariKerberosAuthenticationProperties.java
* (add)
ambari-server/src/test/java/org/apache/ambari/server/security/authentication/kerberos/AmbariKerberosAuthenticationPropertiesTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
> Add Ambari configuration options to support Kerberos token authentication
> -
>
> Key: AMBARI-18365
> URL: https://issues.apache.org/jira/browse/AMBARI-18365
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: authentication, kerberos, security
> Fix For: 2.5.0
>
> Attachments: AMBARI-18365_branch-2.5_01.patch,
> AMBARI-18365_branch-2.5_02.patch, AMBARI-18365_trunk_01.patch,
> AMBARI-18365_trunk_02.patch
>
>
> Add the followng Ambari configuration options to support Kerberos token
> authentication
> * {{authentication.kerberos.enabled}}
> ** Determines whether to use Kerberos (SPNEGO) authentication when connecting
> Ambari: {{true}} to enable this feature; {{false}}, otherwise
> * {{authentication.kerberos.spnego.principal}}
> ** The Kerberos principal name to use when verifying user-supplied Kerberos
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.spnego.keytab.file}}
> ** The Kerberos keytab file to use when verifying user-supplied Kerberos
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.user.types}}
> ** A comma-delimited (ordered) list of preferred user types to use when
> finding the Ambari user account for the user-supplied Kerberos identity
> during authentication via SPNEGO
> * {{authentication.kerberos.auth_to_local.rules}}
> ** The auth-to-local rules set to use when translating a user's principal
> name to a local user name during authentication via SPNEGO.
> NOTE: These properties are in the {{ambari.properties}} file since this
> feature may be enabled whether the rest of the cluster has Kerberos enabled
> or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18378) View instance cloning functionality
[
https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491041#comment-15491041
]
Hadoop QA commented on AMBARI-18378:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12828497/AMBARI-18378.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8672//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8672//console
This message is automatically generated.
> View instance cloning functionality
> ---
>
> Key: AMBARI-18378
> URL: https://issues.apache.org/jira/browse/AMBARI-18378
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-admin, ambari-views
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Labels: patch
> Fix For: trunk
>
> Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg,
> ViewCloneInstance.jpg
>
>
> This task is for providing an option to clone / copy a view instance.
> A new "copy" icon will appear next to a view instance. Clicking on this opens
> up the existing view with instance name and display name of the view appended
> with _Copy.
> This will be useful when creating multiple view instances with mild
> configuration differences between them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18378) View instance cloning functionality
[ https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18378: Attachment: (was: AMBARI-18378.patch) > View instance cloning functionality > --- > > Key: AMBARI-18378 > URL: https://issues.apache.org/jira/browse/AMBARI-18378 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-views >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg, > ViewCloneInstance.jpg > > > This task is for providing an option to clone / copy a view instance. > A new "copy" icon will appear next to a view instance. Clicking on this opens > up the existing view with instance name and display name of the view appended > with _Copy. > This will be useful when creating multiple view instances with mild > configuration differences between them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18378) View instance cloning functionality
[ https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18378: Status: Patch Available (was: Open) > View instance cloning functionality > --- > > Key: AMBARI-18378 > URL: https://issues.apache.org/jira/browse/AMBARI-18378 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-views >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg, > ViewCloneInstance.jpg > > > This task is for providing an option to clone / copy a view instance. > A new "copy" icon will appear next to a view instance. Clicking on this opens > up the existing view with instance name and display name of the view appended > with _Copy. > This will be useful when creating multiple view instances with mild > configuration differences between them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18378) View instance cloning functionality
[ https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18378: Attachment: AMBARI-18378.patch > View instance cloning functionality > --- > > Key: AMBARI-18378 > URL: https://issues.apache.org/jira/browse/AMBARI-18378 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-views >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg, > ViewCloneInstance.jpg > > > This task is for providing an option to clone / copy a view instance. > A new "copy" icon will appear next to a view instance. Clicking on this opens > up the existing view with instance name and display name of the view appended > with _Copy. > This will be useful when creating multiple view instances with mild > configuration differences between them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18378) View instance cloning functionality
[ https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18378: Status: Open (was: Patch Available) > View instance cloning functionality > --- > > Key: AMBARI-18378 > URL: https://issues.apache.org/jira/browse/AMBARI-18378 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-views >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg, > ViewCloneInstance.jpg > > > This task is for providing an option to clone / copy a view instance. > A new "copy" icon will appear next to a view instance. Clicking on this opens > up the existing view with instance name and display name of the view appended > with _Copy. > This will be useful when creating multiple view instances with mild > configuration differences between them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18378) View instance cloning functionality
[ https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18378: Attachment: (was: AMBARI-18378) > View instance cloning functionality > --- > > Key: AMBARI-18378 > URL: https://issues.apache.org/jira/browse/AMBARI-18378 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-views >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg, > ViewCloneInstance.jpg > > > This task is for providing an option to clone / copy a view instance. > A new "copy" icon will appear next to a view instance. Clicking on this opens > up the existing view with instance name and display name of the view appended > with _Copy. > This will be useful when creating multiple view instances with mild > configuration differences between them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18378) View instance cloning functionality
[ https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18378: Status: Open (was: Patch Available) > View instance cloning functionality > --- > > Key: AMBARI-18378 > URL: https://issues.apache.org/jira/browse/AMBARI-18378 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-views >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg, > ViewCloneInstance.jpg > > > This task is for providing an option to clone / copy a view instance. > A new "copy" icon will appear next to a view instance. Clicking on this opens > up the existing view with instance name and display name of the view appended > with _Copy. > This will be useful when creating multiple view instances with mild > configuration differences between them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18378) View instance cloning functionality
[ https://issues.apache.org/jira/browse/AMBARI-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18378: Attachment: AMBARI-18378.patch > View instance cloning functionality > --- > > Key: AMBARI-18378 > URL: https://issues.apache.org/jira/browse/AMBARI-18378 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-views >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-18378.patch, ViewCloneIcon.jpg, > ViewCloneInstance.jpg > > > This task is for providing an option to clone / copy a view instance. > A new "copy" icon will appear next to a view instance. Clicking on this opens > up the existing view with instance name and display name of the view appended > with _Copy. > This will be useful when creating multiple view instances with mild > configuration differences between them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18388) UI: add missing unit tests for models/configs/* and models/stack_version/* files
[
https://issues.apache.org/jira/browse/AMBARI-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490903#comment-15490903
]
Hadoop QA commented on AMBARI-18388:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12828481/AMBARI-18388.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 10 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8671//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8671//console
This message is automatically generated.
> UI: add missing unit tests for models/configs/* and models/stack_version/*
> files
>
>
> Key: AMBARI-18388
> URL: https://issues.apache.org/jira/browse/AMBARI-18388
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-18388.patch
>
>
> Cover the following files with unit tests:
> - {{ambari-web/app/models/configs/theme/sub_section_tab.js}};
> - {{ambari-web/app/models/stack_version/service_simple.js}};
> - {{ambari-web/app/models/stack_version/version.js}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS
[
https://issues.apache.org/jira/browse/AMBARI-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490891#comment-15490891
]
Pushpinder Heer commented on AMBARI-18151:
--
After i manually copied the files in atlas/hive/hooks it worked. but now
running into:
https://issues.apache.org/jira/browse/ATLAS-1086
> Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need
> to be copied to Oozie Share Lib in HDFS
> ---
>
> Key: AMBARI-18151
> URL: https://issues.apache.org/jira/browse/AMBARI-18151
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18151.patch
>
>
> After the Falcon-Atlas hook has been enabled, the following properties are
> added.
> startup.properties
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.extensions.ExtensionService,\
> org.apache.falcon.service.LifecyclePolicyMap,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
> org.apache.falcon.rerun.service.LateRunService,\
> org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService,\
> org.apache.atlas.falcon.service.AtlasService
> {noformat}
> falcon-env.sh
> {noformat}
> # Add the Atlas Falcon hook to the Falcon classpath
> export
> FALCON_EXTRA_CLASS_PATH=/usr/hdp/current/atlas-client/hook/falcon/*:${FALCON_EXTRA_CLASS_PATH}
> {noformat}
> Whenever Oozie submits Hive actions, they fail and the application logs show
> {noformat}
> hive.exec.post.hooks Class not found:org.apache.atlas.hive.hook.HiveHook
> FAILED: Hive Internal Error:
> java.lang.ClassNotFoundException(org.apache.atlas.hive.hook.HiveHook)
> java.lang.ClassNotFoundException: org.apache.atlas.hive.hook.HiveHook
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:60)
> at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1384)
> at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1368)
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1595)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
> at
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
> at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
> at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
> at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:314)
> at
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:412)
> at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:428)
> at
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:717)
> at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
> at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
> at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:335)
> at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:312)
> at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
> at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
> 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
> org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
> at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
> at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
> at
[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services
[
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490866#comment-15490866
]
Hudson commented on AMBARI-15538:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5669 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5669/])
AMBARI-15538. Support service-specific repo for add-on services. (Balazs
(stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0e4515c42ba950ee73bd6511b43cc8eec7481348])
* (add)
ambari-server/src/test/resources/org/apache/ambari/server/stack/UpdateActiveRepoVersionOnStartupTest_initialRepos.json
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/StackDirectory.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/RepositoryVersionHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java
* (add) ambari-server/src/test/resources/common-services/ADDON/1.0/metainfo.xml
* (edit) ambari-server/src/main/resources/version_definition.xsd
* (edit)
contrib/management-packs/microsoft-r_mpack/src/main/resources/common-services/MICROSOFT_R/8.0.0/package/scripts/microsoft_r.py
* (add)
ambari-server/src/main/java/org/apache/ambari/server/stack/UpdateActiveRepoVersionOnStartup.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/RepositoryInfo.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/StackServiceDirectory.java
* (add)
ambari-server/src/test/java/org/apache/ambari/server/stack/StackModuleTest.java
* (add)
contrib/management-packs/microsoft-r_mpack/src/main/resources/common-services/MICROSOFT_R/8.0.0/configuration/microsoft-r-env.xml
* (add)
ambari-server/src/test/resources/common-services/ADDON/1.0/configuration/addon-env.xml
* (add)
ambari-server/src/test/resources/stacks_with_common_services/HDP/0.2/services/ADDON/repos/repoinfo.xml
* (add)
contrib/management-packs/microsoft-r_mpack/src/main/resources/custom-services/MICROSOFT_R/8.0.0/repos/repoinfo.xml
* (add)
ambari-server/src/test/java/org/apache/ambari/server/stack/UpdateActiveRepoVersionOnStartupTest.java
* (add)
ambari-server/src/test/java/org/apache/ambari/server/stack/RepoUtilTest.java
* (add) ambari-server/src/main/java/org/apache/ambari/server/stack/RepoUtil.java
* (add)
ambari-server/src/test/resources/stacks_with_common_services/HDP/0.2/services/ADDON/metainfo.xml
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerCommonServicesTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/StackInfo.java
> Support service-specific repo for add-on services
> -
>
> Key: AMBARI-15538
> URL: https://issues.apache.org/jira/browse/AMBARI-15538
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Jayush Luniya
>Assignee: Balázs Bence Sári
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch6-trunk.diff
>
>
> The approach for custom-services to specify their own repo location will be
> to provide a {{/repos/repoinfo.xml}} inside the stack-version they will be
> in. This repo file will be loaded by Ambari during startup into the
> {{/api/v1/stacks/HDP/versions/2.4/repository_versions}} repos. *Service repo
> files have a restriction that their (repo-name, base-url) locations should be
> unique and not conflict*. When conflicts do occur, they will not be loaded
> into the stacks model.
> Now the management-pack will provide such repos/ folder in
> {{mpacks/custom-services/8.0.0/repos}} which will be linked into the stacks/
> folder.
> {{ambari/ambari-server/src/main/resources/stacks/HDP/2.3/services/SERVICE_NAME/repos
> -> mpacks/custom-services/8.0.0/repos}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18379) Cover host views with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-18379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490863#comment-15490863 ] Hudson commented on AMBARI-18379: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5669 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5669/]) AMBARI-18379 Cover host views with unit tests. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2ad42074f1633c5c6f56cf979bdaa49440457566]) * (edit) ambari-web/app/views/main/host/combo_search_box.js * (edit) ambari-web/app/views/main/host/hosts_table_menu_view.js * (edit) ambari-web/test/views/main/host/stack_versions_view_test.js * (edit) ambari-web/test/views/main/host/combo_search_box_test.js * (add) ambari-web/test/views/main/host/log_metrics_test.js * (edit) ambari-web/app/views/main/host/log_metrics.js * (add) ambari-web/test/views/main/host/hosts_table_menu_view_test.js * (add) ambari-web/test/views/main/host/logs_view_test.js * (edit) ambari-web/app/assets/test/tests.js * (edit) ambari-web/test/views/main/host/host_alerts_view_test.js * (edit) ambari-web/test/views/main/host/summary_test.js > Cover host views with unit tests > > > Key: AMBARI-18379 > URL: https://issues.apache.org/jira/browse/AMBARI-18379 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-18379.patch > > > Cover following files: > * /ambari-web/app/views/main/host/host_alerts_view.js > * /ambari-web/app/views/main/host/summary.js > * /ambari-web/app/views/main/host/stack_versions_view.js > * /ambari-web/app/views/main/host/logs_view.js > * /ambari-web/app/views/main/host/hosts_table_menu_view.js > * /ambari-web/app/views/main/host/log_metrics.js > * /ambari-web/app/views/main/host/combo_search_box.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18384) Analyze and Optimize Ambari Server Unit Tests - Group 3
[
https://issues.apache.org/jira/browse/AMBARI-18384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490868#comment-15490868
]
Hadoop QA commented on AMBARI-18384:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12828472/AMBARI-18384.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8670//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8670//console
This message is automatically generated.
> Analyze and Optimize Ambari Server Unit Tests - Group 3
> ---
>
> Key: AMBARI-18384
> URL: https://issues.apache.org/jira/browse/AMBARI-18384
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: trunk
>
> Attachments: AMBARI-18384.patch
>
>
> ||Test||Count||Time (s)||
> |org.apache.ambari.server.security.authorization.TestUsers|31|50.4|
> |org.apache.ambari.server.upgrade.UpgradeCatalog210Test |18|46.497|
> |org.apache.ambari.server.state.svccomphost.ServiceComponentHostTest|15|43.899|
> |org.apache.ambari.server.serveraction.upgrades.UpgradeActionTest|9|35.136|
> |org.apache.ambari.server.agent.TestHeartbeatMonitor|6|28.146|
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18365) Add Ambari configuration options to support Kerberos token authentication
[
https://issues.apache.org/jira/browse/AMBARI-18365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490864#comment-15490864
]
Hudson commented on AMBARI-18365:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5669 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5669/])
AMBARI-18365. Add Ambari configuration options to support Kerberos token
(rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5beed88e1a7ab422d619a445f8f8e892844d5fa4])
* (add)
ambari-server/src/main/java/org/apache/ambari/server/security/authentication/kerberos/AmbariKerberosAuthenticationProperties.java
* (add)
ambari-server/src/test/java/org/apache/ambari/server/security/authentication/kerberos/AmbariKerberosAuthenticationPropertiesTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java
> Add Ambari configuration options to support Kerberos token authentication
> -
>
> Key: AMBARI-18365
> URL: https://issues.apache.org/jira/browse/AMBARI-18365
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: authentication, kerberos, security
> Fix For: 2.5.0
>
> Attachments: AMBARI-18365_branch-2.5_01.patch,
> AMBARI-18365_branch-2.5_02.patch, AMBARI-18365_trunk_01.patch,
> AMBARI-18365_trunk_02.patch
>
>
> Add the followng Ambari configuration options to support Kerberos token
> authentication
> * {{authentication.kerberos.enabled}}
> ** Determines whether to use Kerberos (SPNEGO) authentication when connecting
> Ambari: {{true}} to enable this feature; {{false}}, otherwise
> * {{authentication.kerberos.spnego.principal}}
> ** The Kerberos principal name to use when verifying user-supplied Kerberos
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.spnego.keytab.file}}
> ** The Kerberos keytab file to use when verifying user-supplied Kerberos
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.user.types}}
> ** A comma-delimited (ordered) list of preferred user types to use when
> finding the Ambari user account for the user-supplied Kerberos identity
> during authentication via SPNEGO
> * {{authentication.kerberos.auth_to_local.rules}}
> ** The auth-to-local rules set to use when translating a user's principal
> name to a local user name during authentication via SPNEGO.
> NOTE: These properties are in the {{ambari.properties}} file since this
> feature may be enabled whether the rest of the cluster has Kerberos enabled
> or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18386) Handle Ranger hive repo config jdbc url change for stack 2.5
[ https://issues.apache.org/jira/browse/AMBARI-18386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18386: - Attachment: AMBARI-18386.1.patch > Handle Ranger hive repo config jdbc url change for stack 2.5 > > > Key: AMBARI-18386 > URL: https://issues.apache.org/jira/browse/AMBARI-18386 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.1, 2.4.2 > > Attachments: AMBARI-18386.1.patch, AMBARI-18386.patch > > > From ambari stacks for Ranger: enable ranger hive plugin takes care of using > right jdbc url for repo configs that are set for creating a repository in > Ranger for Secure and simple install of hive. > However in HiverServer2 HA env, jdbc url needs to change in repo config with > zk url. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18386) Handle Ranger hive repo config jdbc url change for stack 2.5
[ https://issues.apache.org/jira/browse/AMBARI-18386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18386: - Attachment: (was: AMBARI-18386.1.patch) > Handle Ranger hive repo config jdbc url change for stack 2.5 > > > Key: AMBARI-18386 > URL: https://issues.apache.org/jira/browse/AMBARI-18386 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.1, 2.4.2 > > Attachments: AMBARI-18386.patch > > > From ambari stacks for Ranger: enable ranger hive plugin takes care of using > right jdbc url for repo configs that are set for creating a repository in > Ranger for Secure and simple install of hive. > However in HiverServer2 HA env, jdbc url needs to change in repo config with > zk url. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18386) Handle Ranger hive repo config jdbc url change for stack 2.5
[ https://issues.apache.org/jira/browse/AMBARI-18386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18386: - Summary: Handle Ranger hive repo config jdbc url change for stack 2.5 (was: Handle Ranger hive repo config jdbc url, when hiveserver2 HA is enabled) > Handle Ranger hive repo config jdbc url change for stack 2.5 > > > Key: AMBARI-18386 > URL: https://issues.apache.org/jira/browse/AMBARI-18386 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.1, 2.4.2 > > Attachments: AMBARI-18386.patch > > > From ambari stacks for Ranger: enable ranger hive plugin takes care of using > right jdbc url for repo configs that are set for creating a repository in > Ranger for Secure and simple install of hive. > However in HiverServer2 HA env, jdbc url needs to change in repo config with > zk url. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18386) Handle Ranger hive repo config jdbc url, when hiveserver2 HA is enabled
[ https://issues.apache.org/jira/browse/AMBARI-18386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18386: - Attachment: AMBARI-18386.1.patch > Handle Ranger hive repo config jdbc url, when hiveserver2 HA is enabled > --- > > Key: AMBARI-18386 > URL: https://issues.apache.org/jira/browse/AMBARI-18386 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.1, 2.4.2 > > Attachments: AMBARI-18386.1.patch, AMBARI-18386.patch > > > From ambari stacks for Ranger: enable ranger hive plugin takes care of using > right jdbc url for repo configs that are set for creating a repository in > Ranger for Secure and simple install of hive. > However in HiverServer2 HA env, jdbc url needs to change in repo config with > zk url. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18386) Handle Ranger hive repo config jdbc url, when hiveserver2 HA is enabled
[ https://issues.apache.org/jira/browse/AMBARI-18386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18386: - Status: Patch Available (was: In Progress) > Handle Ranger hive repo config jdbc url, when hiveserver2 HA is enabled > --- > > Key: AMBARI-18386 > URL: https://issues.apache.org/jira/browse/AMBARI-18386 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.1, 2.4.2 > > Attachments: AMBARI-18386.1.patch, AMBARI-18386.patch > > > From ambari stacks for Ranger: enable ranger hive plugin takes care of using > right jdbc url for repo configs that are set for creating a repository in > Ranger for Secure and simple install of hive. > However in HiverServer2 HA env, jdbc url needs to change in repo config with > zk url. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18386) Handle Ranger hive repo config jdbc url, when hiveserver2 HA is enabled
[ https://issues.apache.org/jira/browse/AMBARI-18386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18386: - Status: In Progress (was: Patch Available) > Handle Ranger hive repo config jdbc url, when hiveserver2 HA is enabled > --- > > Key: AMBARI-18386 > URL: https://issues.apache.org/jira/browse/AMBARI-18386 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.1, 2.4.2 > > Attachments: AMBARI-18386.patch > > > From ambari stacks for Ranger: enable ranger hive plugin takes care of using > right jdbc url for repo configs that are set for creating a repository in > Ranger for Secure and simple install of hive. > However in HiverServer2 HA env, jdbc url needs to change in repo config with > zk url. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18365) Add Ambari configuration options to support Kerberos token authentication
[
https://issues.apache.org/jira/browse/AMBARI-18365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490820#comment-15490820
]
Robert Levas commented on AMBARI-18365:
---
Failed to add new files to branch-2.5:
Reverted {{70d2223a9bb39da3a9b8d7eaf05bbad3698a92c0}} from branch 2.5:
{noformat}
commit c0e0a5331889d4a7578d54dee15e9cd0396e
Author: Robert Levas
Date: Wed Sep 14 12:08:39 2016 -0400
{noformat}
Commited to branch 2.5:
{noformat}
commit 170b293403ec4fa11353b58d95c65dc5761bb989
Author: Robert Levas
Date: Wed Sep 14 12:09:20 2016 -0400
{noformat}
> Add Ambari configuration options to support Kerberos token authentication
> -
>
> Key: AMBARI-18365
> URL: https://issues.apache.org/jira/browse/AMBARI-18365
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: authentication, kerberos, security
> Fix For: 2.5.0
>
> Attachments: AMBARI-18365_branch-2.5_01.patch,
> AMBARI-18365_branch-2.5_02.patch, AMBARI-18365_trunk_01.patch,
> AMBARI-18365_trunk_02.patch
>
>
> Add the followng Ambari configuration options to support Kerberos token
> authentication
> * {{authentication.kerberos.enabled}}
> ** Determines whether to use Kerberos (SPNEGO) authentication when connecting
> Ambari: {{true}} to enable this feature; {{false}}, otherwise
> * {{authentication.kerberos.spnego.principal}}
> ** The Kerberos principal name to use when verifying user-supplied Kerberos
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.spnego.keytab.file}}
> ** The Kerberos keytab file to use when verifying user-supplied Kerberos
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.user.types}}
> ** A comma-delimited (ordered) list of preferred user types to use when
> finding the Ambari user account for the user-supplied Kerberos identity
> during authentication via SPNEGO
> * {{authentication.kerberos.auth_to_local.rules}}
> ** The auth-to-local rules set to use when translating a user's principal
> name to a local user name during authentication via SPNEGO.
> NOTE: These properties are in the {{ambari.properties}} file since this
> feature may be enabled whether the rest of the cluster has Kerberos enabled
> or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18388) UI: add missing unit tests for models/configs/* and models/stack_version/* files
[
https://issues.apache.org/jira/browse/AMBARI-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490783#comment-15490783
]
Aleksandr Kovalenko commented on AMBARI-18388:
--
+1 for the patch
> UI: add missing unit tests for models/configs/* and models/stack_version/*
> files
>
>
> Key: AMBARI-18388
> URL: https://issues.apache.org/jira/browse/AMBARI-18388
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-18388.patch
>
>
> Cover the following files with unit tests:
> - {{ambari-web/app/models/configs/theme/sub_section_tab.js}};
> - {{ambari-web/app/models/stack_version/service_simple.js}};
> - {{ambari-web/app/models/stack_version/version.js}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18209) UI: add missing unit tests for models
[
https://issues.apache.org/jira/browse/AMBARI-18209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490779#comment-15490779
]
Hudson commented on AMBARI-18209:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #34 (See
[https://builds.apache.org/job/Ambari-branch-2.5/34/])
AMBARI-18209. UI: add missing unit tests for models (alexantonenko) (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=092c9cf52edebb84817dcb0b5302608c83b24998])
* (edit) ambari-web/app/models/widget_property.js
* (add) ambari-web/test/models/cluster_test.js
* (add) ambari-web/test/models/slave_component_test.js
* (add) ambari-web/test/models/root_service_test.js
* (add) ambari-web/test/models/client_component_test.js
* (add) ambari-web/test/models/master_component_test.js
* (edit) ambari-web/app/models/cluster.js
* (add) ambari-web/test/models/stack_test.js
* (edit) ambari-web/app/models/master_component.js
* (edit) ambari-web/app/models/client_component.js
* (edit) ambari-web/app/models/root_service.js
* (add) ambari-web/test/models/widget_test.js
* (edit) ambari-web/app/assets/test/tests.js
* (add) ambari-web/test/models/widget_property_test.js
* (edit) ambari-web/app/models/slave_component.js
> UI: add missing unit tests for models
> -
>
> Key: AMBARI-18209
> URL: https://issues.apache.org/jira/browse/AMBARI-18209
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-18209.patch
>
>
> Cover the following files with unit tests:
> - {{ambari-web/app/models/client_component.js}};
> - {{ambari-web/app/models/cluster.js}};
> - {{ambari-web/app/models/master_component.js}};
> - {{ambari-web/app/models/root_service.js}};
> - {{ambari-web/app/models/slave_component.js}};
> - {{ambari-web/app/models/stack.js}};
> - {{ambari-web/app/models/widget.js}};
> - {{ambari-web/app/models/widget_property.js}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18330) Add optional digital clock widget attached to page.
[ https://issues.apache.org/jira/browse/AMBARI-18330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490780#comment-15490780 ] Hudson commented on AMBARI-18330: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #34 (See [https://builds.apache.org/job/Ambari-branch-2.5/34/]) AMBARI-18330. Add optional digital clock widget attached to page. (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3ebb8d496c3be688bf81c2a8102372c089b9c547]) * (edit) ambari-web/app/views.js * (add) ambari-web/app/views/common/clock_view.js * (edit) ambari-web/app/config.js * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/templates/application.hbs > Add optional digital clock widget attached to page. > --- > > Key: AMBARI-18330 > URL: https://issues.apache.org/jira/browse/AMBARI-18330 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-18330.patch > > > Add optional digital clock widget attached to page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18365) Add Ambari configuration options to support Kerberos token authentication
[
https://issues.apache.org/jira/browse/AMBARI-18365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490778#comment-15490778
]
Hudson commented on AMBARI-18365:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #34 (See
[https://builds.apache.org/job/Ambari-branch-2.5/34/])
AMBARI-18365. Add Ambari configuration options to support Kerberos token
(rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=70d2223a9bb39da3a9b8d7eaf05bbad3698a92c0])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
> Add Ambari configuration options to support Kerberos token authentication
> -
>
> Key: AMBARI-18365
> URL: https://issues.apache.org/jira/browse/AMBARI-18365
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: authentication, kerberos, security
> Fix For: 2.5.0
>
> Attachments: AMBARI-18365_branch-2.5_01.patch,
> AMBARI-18365_branch-2.5_02.patch, AMBARI-18365_trunk_01.patch,
> AMBARI-18365_trunk_02.patch
>
>
> Add the followng Ambari configuration options to support Kerberos token
> authentication
> * {{authentication.kerberos.enabled}}
> ** Determines whether to use Kerberos (SPNEGO) authentication when connecting
> Ambari: {{true}} to enable this feature; {{false}}, otherwise
> * {{authentication.kerberos.spnego.principal}}
> ** The Kerberos principal name to use when verifying user-supplied Kerberos
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.spnego.keytab.file}}
> ** The Kerberos keytab file to use when verifying user-supplied Kerberos
> tokens for authentication via SPNEGO
> * {{authentication.kerberos.user.types}}
> ** A comma-delimited (ordered) list of preferred user types to use when
> finding the Ambari user account for the user-supplied Kerberos identity
> during authentication via SPNEGO
> * {{authentication.kerberos.auth_to_local.rules}}
> ** The auth-to-local rules set to use when translating a user's principal
> name to a local user name during authentication via SPNEGO.
> NOTE: These properties are in the {{ambari.properties}} file since this
> feature may be enabled whether the rest of the cluster has Kerberos enabled
> or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18158) Add UI unit tests for App.HttpClient
[ https://issues.apache.org/jira/browse/AMBARI-18158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490777#comment-15490777 ] Hudson commented on AMBARI-18158: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #34 (See [https://builds.apache.org/job/Ambari-branch-2.5/34/]) AMBARI-18158. Add UI unit tests for App.HttpClient (alexantonenko) (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a4f74942972908f29663de07c4b9818854b538f0]) * (edit) ambari-web/test/controllers/global/errors_handler_controller_test.js * (edit) ambari-web/app/assets/test/tests.js * (add) ambari-web/test/utils/http_client_test.js * (edit) ambari-web/app/utils/http_client.js > Add UI unit tests for App.HttpClient > > > Key: AMBARI-18158 > URL: https://issues.apache.org/jira/browse/AMBARI-18158 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-18158.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18320) Frequently getting an Ambari consistency check error when changing configuration
[
https://issues.apache.org/jira/browse/AMBARI-18320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490781#comment-15490781
]
Hudson commented on AMBARI-18320:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #34 (See
[https://builds.apache.org/job/Ambari-branch-2.5/34/])
AMBARI-18320. Frequently getting an Ambari consistency check error when
(hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e01fb601997c126ac68dc2a656ad99420f46dc85])
* (edit) ambari-web/app/controllers/main/service/info/configs.js
> Frequently getting an Ambari consistency check error when changing
> configuration
>
>
> Key: AMBARI-18320
> URL: https://issues.apache.org/jira/browse/AMBARI-18320
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-18320.patch
>
>
> I have installed Cloudbreak clusters in AWS.
> Ambari version: ambari-server-2.4.0.0-1157.x86_64
> Generally, when making changes to any configuration, I get a warning box on
> Consistency Check failing due to an "unknown error".
> Looking at the logs, I am seeing something like this:
> {code}
> 24 Aug 2016 07:01:53,034 ERROR [ambari-client-thread-68]
> BaseManagementHandler:61 - Caught a system exception while attempting to
> create a resource: Stack Advisor reported an error: Fail: Couldn't retrieve
> YARN's 'yarn.nodemanager.resource.memory-mb' config.
> StdOut file: /var/run/ambari-server/stack-recommendations/54/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/54/stackadvisor.err
> org.apache.ambari.server.controller.spi.SystemException: Stack Advisor
> reported an error: Fail: Couldn't retrieve YARN's
> 'yarn.nodemanager.resource.memory-mb' config.
> StdOut file: /var/run/ambari-server/stack-recommendations/54/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/54/stackadvisor.err
> at
> org.apache.ambari.server.controller.internal.ValidationResourceProvider.createResources(ValidationResourceProvider.java:91)
> 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:145)
> 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.ValidationService.getValidation(ValidationService.java:58)
> at sun.reflect.GeneratedMethodAccessor749.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>
[jira] [Updated] (AMBARI-18330) Add optional digital clock widget attached to page.
[ https://issues.apache.org/jira/browse/AMBARI-18330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18330: - Fix Version/s: (was: trunk) 2.5.0 > Add optional digital clock widget attached to page. > --- > > Key: AMBARI-18330 > URL: https://issues.apache.org/jira/browse/AMBARI-18330 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-18330.patch > > > Add optional digital clock widget attached to page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18330) Add optional digital clock widget attached to page.
[ https://issues.apache.org/jira/browse/AMBARI-18330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490735#comment-15490735 ] Antonenko Alexander commented on AMBARI-18330: -- committed to 2.5 > Add optional digital clock widget attached to page. > --- > > Key: AMBARI-18330 > URL: https://issues.apache.org/jira/browse/AMBARI-18330 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-18330.patch > > > Add optional digital clock widget attached to page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18388) UI: add missing unit tests for models/configs/* and models/stack_version/* files
[
https://issues.apache.org/jira/browse/AMBARI-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-18388:
-
Status: Patch Available (was: Open)
> UI: add missing unit tests for models/configs/* and models/stack_version/*
> files
>
>
> Key: AMBARI-18388
> URL: https://issues.apache.org/jira/browse/AMBARI-18388
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-18388.patch
>
>
> Cover the following files with unit tests:
> - {{ambari-web/app/models/configs/theme/sub_section_tab.js}};
> - {{ambari-web/app/models/stack_version/service_simple.js}};
> - {{ambari-web/app/models/stack_version/version.js}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18388) UI: add missing unit tests for models/configs/* and models/stack_version/* files
[
https://issues.apache.org/jira/browse/AMBARI-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-18388:
-
Attachment: AMBARI-18388.patch
> UI: add missing unit tests for models/configs/* and models/stack_version/*
> files
>
>
> Key: AMBARI-18388
> URL: https://issues.apache.org/jira/browse/AMBARI-18388
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-18388.patch
>
>
> Cover the following files with unit tests:
> - {{ambari-web/app/models/configs/theme/sub_section_tab.js}};
> - {{ambari-web/app/models/stack_version/service_simple.js}};
> - {{ambari-web/app/models/stack_version/version.js}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18388) UI: add missing unit tests for models/configs/* and models/stack_version/* files
Antonenko Alexander created AMBARI-18388:
Summary: UI: add missing unit tests for models/configs/* and
models/stack_version/* files
Key: AMBARI-18388
URL: https://issues.apache.org/jira/browse/AMBARI-18388
Project: Ambari
Issue Type: Task
Components: ambari-web
Affects Versions: 2.4.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
Fix For: 3.0.0
Cover the following files with unit tests:
- {{ambari-web/app/models/configs/theme/sub_section_tab.js}};
- {{ambari-web/app/models/stack_version/service_simple.js}};
- {{ambari-web/app/models/stack_version/version.js}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18209) UI: add missing unit tests for models
[
https://issues.apache.org/jira/browse/AMBARI-18209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490718#comment-15490718
]
Antonenko Alexander commented on AMBARI-18209:
--
committed to 2.5
> UI: add missing unit tests for models
> -
>
> Key: AMBARI-18209
> URL: https://issues.apache.org/jira/browse/AMBARI-18209
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-18209.patch
>
>
> Cover the following files with unit tests:
> - {{ambari-web/app/models/client_component.js}};
> - {{ambari-web/app/models/cluster.js}};
> - {{ambari-web/app/models/master_component.js}};
> - {{ambari-web/app/models/root_service.js}};
> - {{ambari-web/app/models/slave_component.js}};
> - {{ambari-web/app/models/stack.js}};
> - {{ambari-web/app/models/widget.js}};
> - {{ambari-web/app/models/widget_property.js}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18209) UI: add missing unit tests for models
[
https://issues.apache.org/jira/browse/AMBARI-18209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-18209:
-
Fix Version/s: (was: trunk)
2.5.0
> UI: add missing unit tests for models
> -
>
> Key: AMBARI-18209
> URL: https://issues.apache.org/jira/browse/AMBARI-18209
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-18209.patch
>
>
> Cover the following files with unit tests:
> - {{ambari-web/app/models/client_component.js}};
> - {{ambari-web/app/models/cluster.js}};
> - {{ambari-web/app/models/master_component.js}};
> - {{ambari-web/app/models/root_service.js}};
> - {{ambari-web/app/models/slave_component.js}};
> - {{ambari-web/app/models/stack.js}};
> - {{ambari-web/app/models/widget.js}};
> - {{ambari-web/app/models/widget_property.js}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-18158) Add UI unit tests for App.HttpClient
[ https://issues.apache.org/jira/browse/AMBARI-18158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490710#comment-15490710 ] Antonenko Alexander edited comment on AMBARI-18158 at 9/14/16 3:27 PM: --- committed to 2.5 was (Author: aantonenko): AMBARI-18158 > Add UI unit tests for App.HttpClient > > > Key: AMBARI-18158 > URL: https://issues.apache.org/jira/browse/AMBARI-18158 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-18158.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18158) Add UI unit tests for App.HttpClient
[ https://issues.apache.org/jira/browse/AMBARI-18158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490710#comment-15490710 ] Antonenko Alexander commented on AMBARI-18158: -- AMBARI-18158 > Add UI unit tests for App.HttpClient > > > Key: AMBARI-18158 > URL: https://issues.apache.org/jira/browse/AMBARI-18158 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-18158.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18158) Add UI unit tests for App.HttpClient
[ https://issues.apache.org/jira/browse/AMBARI-18158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18158: - Fix Version/s: (was: trunk) 2.5.0 > Add UI unit tests for App.HttpClient > > > Key: AMBARI-18158 > URL: https://issues.apache.org/jira/browse/AMBARI-18158 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-18158.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18320) Frequently getting an Ambari consistency check error when changing configuration
[
https://issues.apache.org/jira/browse/AMBARI-18320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-18320:
-
Fix Version/s: (was: trunk)
2.5.0
> Frequently getting an Ambari consistency check error when changing
> configuration
>
>
> Key: AMBARI-18320
> URL: https://issues.apache.org/jira/browse/AMBARI-18320
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-18320.patch
>
>
> I have installed Cloudbreak clusters in AWS.
> Ambari version: ambari-server-2.4.0.0-1157.x86_64
> Generally, when making changes to any configuration, I get a warning box on
> Consistency Check failing due to an "unknown error".
> Looking at the logs, I am seeing something like this:
> {code}
> 24 Aug 2016 07:01:53,034 ERROR [ambari-client-thread-68]
> BaseManagementHandler:61 - Caught a system exception while attempting to
> create a resource: Stack Advisor reported an error: Fail: Couldn't retrieve
> YARN's 'yarn.nodemanager.resource.memory-mb' config.
> StdOut file: /var/run/ambari-server/stack-recommendations/54/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/54/stackadvisor.err
> org.apache.ambari.server.controller.spi.SystemException: Stack Advisor
> reported an error: Fail: Couldn't retrieve YARN's
> 'yarn.nodemanager.resource.memory-mb' config.
> StdOut file: /var/run/ambari-server/stack-recommendations/54/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/54/stackadvisor.err
> at
> org.apache.ambari.server.controller.internal.ValidationResourceProvider.createResources(ValidationResourceProvider.java:91)
> 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:145)
> 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.ValidationService.getValidation(ValidationService.java:58)
> at sun.reflect.GeneratedMethodAccessor749.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at
>
[jira] [Commented] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS
[
https://issues.apache.org/jira/browse/AMBARI-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490699#comment-15490699
]
Pushpinder Heer commented on AMBARI-18151:
--
Was this ever merged into 2.4.0? I realize it states that, but I'm running
into this exact problem on 2.4.0.
> Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need
> to be copied to Oozie Share Lib in HDFS
> ---
>
> Key: AMBARI-18151
> URL: https://issues.apache.org/jira/browse/AMBARI-18151
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18151.patch
>
>
> After the Falcon-Atlas hook has been enabled, the following properties are
> added.
> startup.properties
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.extensions.ExtensionService,\
> org.apache.falcon.service.LifecyclePolicyMap,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
> org.apache.falcon.rerun.service.LateRunService,\
> org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.metadata.MetadataMappingService,\
> org.apache.atlas.falcon.service.AtlasService
> {noformat}
> falcon-env.sh
> {noformat}
> # Add the Atlas Falcon hook to the Falcon classpath
> export
> FALCON_EXTRA_CLASS_PATH=/usr/hdp/current/atlas-client/hook/falcon/*:${FALCON_EXTRA_CLASS_PATH}
> {noformat}
> Whenever Oozie submits Hive actions, they fail and the application logs show
> {noformat}
> hive.exec.post.hooks Class not found:org.apache.atlas.hive.hook.HiveHook
> FAILED: Hive Internal Error:
> java.lang.ClassNotFoundException(org.apache.atlas.hive.hook.HiveHook)
> java.lang.ClassNotFoundException: org.apache.atlas.hive.hook.HiveHook
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:60)
> at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1384)
> at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1368)
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1595)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
> at
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
> at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
> at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
> at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:314)
> at
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:412)
> at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:428)
> at
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:717)
> at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
> at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
> at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:335)
> at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:312)
> at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
> at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
> 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
> org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
> at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
> at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
> at
