[jira] [Commented] (AMBARI-17269) Hive Query is not running in Hive View 2.0.0 Instance (JDBC)
[ https://issues.apache.org/jira/browse/AMBARI-17269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335464#comment-15335464 ] Hudson commented on AMBARI-17269: - FAILURE: Integrated in Ambari-trunk-Commit #5099 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5099/]) AMBARI-17269. INSERT and SELECT not working. jobid was used in actor (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=511f9ccee06455b390912f1d669c2026d14b768d]) * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/JdbcConnector.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/jobs/viewJobs/JobControllerImpl.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/message/HiveJob.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/message/SQLStatementJob.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/ConnectionSystem.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/message/GetColumnMetadataJob.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/OperationController.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/client/DDLDelegatorImpl.java > Hive Query is not running in Hive View 2.0.0 Instance (JDBC) > > > Key: AMBARI-17269 > URL: https://issues.apache.org/jira/browse/AMBARI-17269 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.4.0 > > Attachments: AMBARI-17269.branch-2.4.patch > > > No query (SELECT or INSERT) are running in Hive View 2.0.0. > Queries were failing because, jobid was used in actor names to make it unique > but jobid is not a unique identifier across instances. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17284) Hive Metastore Upgrade Fails Because Of Missing Hive Interactive Directory
[
https://issues.apache.org/jira/browse/AMBARI-17284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335463#comment-15335463
]
Hudson commented on AMBARI-17284:
-
FAILURE: Integrated in Ambari-trunk-Commit #5099 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5099/])
AMBARI-17284 - Hive Metastore Upgrade Fails Because Of Missing Hive (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fac89e7400e2dc0a0673ffd4a86b413f99857b18])
* ambari-server/src/test/python/stacks/utils/RMFTestCase.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py
*
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_service_check.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_metastore.py
*
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py
*
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_service.py
* ambari-server/src/test/python/stacks/2.1/HIVE/test_hive_metastore.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_webhcat_server.py
> Hive Metastore Upgrade Fails Because Of Missing Hive Interactive Directory
> --
>
> Key: AMBARI-17284
> URL: https://issues.apache.org/jira/browse/AMBARI-17284
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17284.patch
>
>
> During an upgrade from HDP 2.3/2.4 to HDP 2.5, the following error is seen:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 254, in
> HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 662, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 114, in pre_upgrade_restart
> self.upgrade_schema(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 189, in upgrade_schema
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 73, in configure
> hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 274, in hive
> jdbc_connector(params.target_hive2, params.hive2_previous_jdbc_jar)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 463, in jdbc_connector
> sudo = True)
> 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 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cp
> --remove-destination /var/lib/ambari-agent/tmp/mysql-connector-java.jar
> /usr/hdp/current/hive-server2-hive2/lib/mysql-connector-java.jar' returned 1.
> cp: cannot create regular file
> `/usr/hdp/current/hive-server2-hive2/lib/mysql-connector-java.jar': No
[jira] [Commented] (AMBARI-17271) Hive Jdbc View: Add code to include 'hive.server2.proxy.user' to connection param by default
[ https://issues.apache.org/jira/browse/AMBARI-17271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335462#comment-15335462 ] Hudson commented on AMBARI-17271: - FAILURE: Integrated in Ambari-trunk-Commit #5099 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5099/]) AMBARI-17271. Hive Jdbc View: Add code to include (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dbf0b16578637b9aa25756e46865c8861f6b41eb]) * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/ConnectionFactory.java > Hive Jdbc View: Add code to include 'hive.server2.proxy.user' to connection > param by default > - > > Key: AMBARI-17271 > URL: https://issues.apache.org/jira/browse/AMBARI-17271 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.4.0 > > Attachments: AMBARI-17271.branch-2.4.patch > > > To make the instances work in kerberized environment, we need to add the > proxy user in the session params which will go with the connection url. > To make this seemless we need to add the 'hive.server2.proxy.user" parameter > to the jdbc url in the kerberized cluster if user has not provided it in > session parameter configuration while creating the instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335461#comment-15335461 ] Hudson commented on AMBARI-17186: - FAILURE: Integrated in Ambari-trunk-Commit #5099 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5099/]) AMBARI-17186. Tez View: Improve proxy logging. (Sreenath Somarajapuram (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=75d44052aafd9ae913ac1f02f55a215bdb8709e5]) * contrib/views/tez/src/main/java/org/apache/ambari/view/tez/rest/BaseRedirectionResource.java * contrib/views/tez/src/main/java/org/apache/ambari/view/tez/exceptions/ATSUrlFetchException.java * contrib/views/tez/src/main/java/org/apache/ambari/view/tez/ViewControllerImpl.java * contrib/views/tez/src/main/java/org/apache/ambari/view/tez/exceptions/ConfigurationFetchException.java * contrib/views/tez/src/main/java/org/apache/ambari/view/tez/exceptions/ActiveRMFetchException.java * contrib/views/tez/src/main/java/org/apache/ambari/view/tez/rest/BaseProxyResource.java > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17109) Capacity scheduler view - problem with queue percent rounding
[ https://issues.apache.org/jira/browse/AMBARI-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335460#comment-15335460 ] Hudson commented on AMBARI-17109: - FAILURE: Integrated in Ambari-trunk-Commit #5099 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5099/]) AMBARI-17109. Capacity scheduler view - problem with queue percent (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=aaa435c361741ac5e1ea20fc533641bde79b95f0]) * contrib/views/capacity-scheduler/src/main/resources/ui/app/components/totalCapacity.js * contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queues.js > Capacity scheduler view - problem with queue percent rounding > - > > Key: AMBARI-17109 > URL: https://issues.apache.org/jira/browse/AMBARI-17109 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.1.0 >Reporter: Akhil PB > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17109.1.patch, AMBARI-17109.2.patch, > CapSchedViewCalc.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17249) Storm metrics sink should include worker host and port to metric name when metrics are coming from SystemBolt
[
https://issues.apache.org/jira/browse/AMBARI-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335428#comment-15335428
]
Hadoop QA commented on AMBARI-17249:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811281/AMBARI-17249-v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-metrics/ambari-metrics-storm-sink.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7400//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7400//console
This message is automatically generated.
> Storm metrics sink should include worker host and port to metric name when
> metrics are coming from SystemBolt
> -
>
> Key: AMBARI-17249
> URL: https://issues.apache.org/jira/browse/AMBARI-17249
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Attachments: AMBARI-17249-v1.patch
>
>
> Background: SystemBolt is reserved component for each worker which exposes
> worker level metrics like Memory, GC, and uptime, and so on.
> All SystemBolts have -1 as task id, so identifying SystemBolt components to
> task id as same as normal components will fail.
> Since each worker is identified by (worker host, port) pair, we can add
> hostname and port to metric name to make metric name unique.
> Since it's only for SystemBolt, instead of adding hostname and port to all of
> metrics, we can add these to specific metrics which are coming from
> SystemBolt.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17208) Add logging for the command executed during PXF service check
[ https://issues.apache.org/jira/browse/AMBARI-17208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17208: Resolution: Fixed Status: Resolved (was: Patch Available) > Add logging for the command executed during PXF service check > - > > Key: AMBARI-17208 > URL: https://issues.apache.org/jira/browse/AMBARI-17208 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17208.patch > > > Add logging for the command executed during PXF service check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17290) Ambari Metrics Flume Sink test failed at trunk
Masahiro Tanaka created AMBARI-17290:
Summary: Ambari Metrics Flume Sink test failed at trunk
Key: AMBARI-17290
URL: https://issues.apache.org/jira/browse/AMBARI-17290
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: trunk
Environment: CentOS6 (Used Dockerfile in dev-support)
Reporter: Masahiro Tanaka
I ran {{mvn clean test}} and I got an error.
{code}
---
T E S T S
---
Running org.apache.hadoop.metrics2.sink.flume.FlumeTimelineMetricsSinkTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.456 sec <<<
FAILURE! - in org.apache.hadoop.metrics2.sink.flume.FlumeTimelineMetricsSinkTest
initializationError(org.apache.hadoop.metrics2.sink.flume.FlumeTimelineMetricsSinkTest)
Time elapsed: 0.006 sec <<< ERROR!
java.lang.IllegalStateException: Failed to transform class with name
org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink. Reason:
findLiveCollectorHostsFromKnownCollector (Ljava/lang/S
tring;Ljava/lang/String;)Ljava/util/Collection; in
org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed to
resolve types
Caused by: javassist.CannotCompileException:
findLiveCollectorHostsFromKnownCollector
(Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
org.apache.hadoop.metrics2.sink.timeline.AbstractTi
melineMetricsSink: failed to resolve types
Caused by: javassist.bytecode.BadBytecode:
findLiveCollectorHostsFromKnownCollector
(Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
org.apache.hadoop.metrics2.sink.timeline.AbstractTime
lineMetricsSink: failed to resolve types
Caused by: javassist.bytecode.BadBytecode: failed to resolve types
Caused by: javassist.NotFoundException: com.google.common.reflect.TypeToken
Results :
Tests in error:
FlumeTimelineMetricsSinkTest.initializationError » IllegalState Failed to
tran...
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17249) Storm metrics sink should include worker host and port to metric name when metrics are coming from SystemBolt
[ https://issues.apache.org/jira/browse/AMBARI-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17249: -- Status: Patch Available (was: Open) Attached patch. Waiting for CI. > Storm metrics sink should include worker host and port to metric name when > metrics are coming from SystemBolt > - > > Key: AMBARI-17249 > URL: https://issues.apache.org/jira/browse/AMBARI-17249 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: AMBARI-17249-v1.patch > > > Background: SystemBolt is reserved component for each worker which exposes > worker level metrics like Memory, GC, and uptime, and so on. > All SystemBolts have -1 as task id, so identifying SystemBolt components to > task id as same as normal components will fail. > Since each worker is identified by (worker host, port) pair, we can add > hostname and port to metric name to make metric name unique. > Since it's only for SystemBolt, instead of adding hostname and port to all of > metrics, we can add these to specific metrics which are coming from > SystemBolt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17249) Storm metrics sink should include worker host and port to metric name when metrics are coming from SystemBolt
[ https://issues.apache.org/jira/browse/AMBARI-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17249: -- Attachment: AMBARI-17249-v1.patch > Storm metrics sink should include worker host and port to metric name when > metrics are coming from SystemBolt > - > > Key: AMBARI-17249 > URL: https://issues.apache.org/jira/browse/AMBARI-17249 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: AMBARI-17249-v1.patch > > > Background: SystemBolt is reserved component for each worker which exposes > worker level metrics like Memory, GC, and uptime, and so on. > All SystemBolts have -1 as task id, so identifying SystemBolt components to > task id as same as normal components will fail. > Since each worker is identified by (worker host, port) pair, we can add > hostname and port to metric name to make metric name unique. > Since it's only for SystemBolt, instead of adding hostname and port to all of > metrics, we can add these to specific metrics which are coming from > SystemBolt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm
[ https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335366#comment-15335366 ] Jungtaek Lim commented on AMBARI-17080: --- Build failing is due to SNAPSHOT reference. Storm 1.1.0 SNAPSHOT is pushed correctly, but build doesn't refer SNAPSHOT repository. It seems to refer only hortonworks repo. https://repository.apache.org/content/groups/snapshots/org/apache/storm/storm-core/1.1.0-SNAPSHOT/ > Support Storm 1.0 in Ambari Metrics for Storm > - > > Key: AMBARI-17080 > URL: https://issues.apache.org/jira/browse/AMBARI-17080 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: AMBARI-17080-v1.patch, AMBARI-17080-v2.patch > > > Since there was package name change on Apache Storm 1.0.0, Ambari Metrics > Reporter / Sink for Storm will not work when Ambari supports Apache Storm > 1.0.0 or upper. > This issue is for addressing this. > Please note that it will incur compile failure unless Ambari Metrics pom file > depends on Storm 1.x version, so decision for version of Storm should be made > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm
[
https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335356#comment-15335356
]
Jungtaek Lim commented on AMBARI-17080:
---
Additionally, we need to modify some parameters for Storm:
- metrics.reporter.register : should be removed
- storm.cluster.metrics.consumer.register : should be added with default value
here
- {code}[{"class":
"org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter"}]{code}
- topology.metrics.consumer.register : can be added again, with or without
default value
- {code}[{'class':
'org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink',
'parallelism.hint': 1}]{code}
Regarding topology.metrics.consumer.register, I addressed several patches for
performance on storm side, but if we're still in doubt about performance drop,
it would be possible to leave it to empty array, and document how to set up
topology metrics consumer.
I don't have an experience about changing parameter, so I'd be happy if someone
guides me how to do it. If someone could resolve this for me I'd be happy, too.
> Support Storm 1.0 in Ambari Metrics for Storm
> -
>
> Key: AMBARI-17080
> URL: https://issues.apache.org/jira/browse/AMBARI-17080
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Attachments: AMBARI-17080-v1.patch, AMBARI-17080-v2.patch
>
>
> Since there was package name change on Apache Storm 1.0.0, Ambari Metrics
> Reporter / Sink for Storm will not work when Ambari supports Apache Storm
> 1.0.0 or upper.
> This issue is for addressing this.
> Please note that it will incur compile failure unless Ambari Metrics pom file
> depends on Storm 1.x version, so decision for version of Storm should be made
> first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm
[
https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335356#comment-15335356
]
Jungtaek Lim edited comment on AMBARI-17080 at 6/17/16 3:55 AM:
Additionally, we need to modify some parameters for Storm:
- metrics.reporter.register : should be removed
- storm.cluster.metrics.consumer.register : should be added with default value
here
- {code}[{"class":
"org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter"}]{code}
- topology.metrics.consumer.register : can be added again, with or without
default value
- {code}[{"class":
"org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink",
"parallelism.hint": 1}]{code}
Regarding topology.metrics.consumer.register, I addressed several patches for
performance on storm side, but if we're still in doubt about performance drop,
it would be possible to leave it to empty array, and document how to set up
topology metrics consumer.
I don't have an experience about changing parameter, so I'd be happy if someone
guides me how to do it. If someone could resolve this for me I'd be happy, too.
was (Author: kabhwan):
Additionally, we need to modify some parameters for Storm:
- metrics.reporter.register : should be removed
- storm.cluster.metrics.consumer.register : should be added with default value
here
- {code}[{"class":
"org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter"}]{code}
- topology.metrics.consumer.register : can be added again, with or without
default value
- {code}[{'class':
'org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink',
'parallelism.hint': 1}]{code}
Regarding topology.metrics.consumer.register, I addressed several patches for
performance on storm side, but if we're still in doubt about performance drop,
it would be possible to leave it to empty array, and document how to set up
topology metrics consumer.
I don't have an experience about changing parameter, so I'd be happy if someone
guides me how to do it. If someone could resolve this for me I'd be happy, too.
> Support Storm 1.0 in Ambari Metrics for Storm
> -
>
> Key: AMBARI-17080
> URL: https://issues.apache.org/jira/browse/AMBARI-17080
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Attachments: AMBARI-17080-v1.patch, AMBARI-17080-v2.patch
>
>
> Since there was package name change on Apache Storm 1.0.0, Ambari Metrics
> Reporter / Sink for Storm will not work when Ambari supports Apache Storm
> 1.0.0 or upper.
> This issue is for addressing this.
> Please note that it will incur compile failure unless Ambari Metrics pom file
> depends on Storm 1.x version, so decision for version of Storm should be made
> first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17287) UI: 'llap' queue is not shown in dropdown even though recommendation says so. Shows 'llap' queue after save.
[ https://issues.apache.org/jira/browse/AMBARI-17287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335347#comment-15335347 ] Hudson commented on AMBARI-17287: - FAILURE: Integrated in Ambari-trunk-Commit #5098 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5098/]) AMBARI-17287. UI: 'llap' queue is not shown in dropdown even though (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=14df3d2bdcd71aba158ef5fa6753eabd679e77bf]) * ambari-web/app/views/common/configs/widgets/combo_config_widget_view.js > UI: 'llap' queue is not shown in dropdown even though recommendation says so. > Shows 'llap' queue after save. > > > Key: AMBARI-17287 > URL: https://issues.apache.org/jira/browse/AMBARI-17287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17287.patch > > > This issue happens because even though options of configs are updated from > stack advisor response, options of combobox widget view are not updated > dynamically after the view is rendered once. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17288) Redundant element on create version page
[ https://issues.apache.org/jira/browse/AMBARI-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335348#comment-15335348 ] Hudson commented on AMBARI-17288: - FAILURE: Integrated in Ambari-trunk-Commit #5098 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5098/]) AMBARI-17288 Redundant element on create version page (zhewang) (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5e50c84cc4fed6b594967fe573210a2f0d3f99fa]) * ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html > Redundant element on create version page > > > Key: AMBARI-17288 > URL: https://issues.apache.org/jira/browse/AMBARI-17288 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17288.v0.patch > > > Redundant element on create version page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm
[
https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335339#comment-15335339
]
Hadoop QA commented on AMBARI-17080:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811275/AMBARI-17080-v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7398//console
This message is automatically generated.
> Support Storm 1.0 in Ambari Metrics for Storm
> -
>
> Key: AMBARI-17080
> URL: https://issues.apache.org/jira/browse/AMBARI-17080
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Attachments: AMBARI-17080-v1.patch, AMBARI-17080-v2.patch
>
>
> Since there was package name change on Apache Storm 1.0.0, Ambari Metrics
> Reporter / Sink for Storm will not work when Ambari supports Apache Storm
> 1.0.0 or upper.
> This issue is for addressing this.
> Please note that it will incur compile failure unless Ambari Metrics pom file
> depends on Storm 1.x version, so decision for version of Storm should be made
> first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17284) Hive Metastore Upgrade Fails Because Of Missing Hive Interactive Directory
[
https://issues.apache.org/jira/browse/AMBARI-17284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-17284:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Hive Metastore Upgrade Fails Because Of Missing Hive Interactive Directory
> --
>
> Key: AMBARI-17284
> URL: https://issues.apache.org/jira/browse/AMBARI-17284
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17284.patch
>
>
> During an upgrade from HDP 2.3/2.4 to HDP 2.5, the following error is seen:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 254, in
> HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 662, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 114, in pre_upgrade_restart
> self.upgrade_schema(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 189, in upgrade_schema
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 73, in configure
> hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 274, in hive
> jdbc_connector(params.target_hive2, params.hive2_previous_jdbc_jar)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 463, in jdbc_connector
> sudo = True)
> 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 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cp
> --remove-destination /var/lib/ambari-agent/tmp/mysql-connector-java.jar
> /usr/hdp/current/hive-server2-hive2/lib/mysql-connector-java.jar' returned 1.
> cp: cannot create regular file
> `/usr/hdp/current/hive-server2-hive2/lib/mysql-connector-java.jar': No such
> file or directory
> {code}
> This is because with HDP 2.5, Hive introduced a new component called
> {{hive-server2-hive2}}:
> {code}
> /usr/hdp/current/hive-metastore -> /usr/hdp/2.5.0.0-1234/hive
> /usr/hdp/current/hive-server2 -> /usr/hdp/2.5.0.0-1234/hive
> /usr/hdp/current/hive-server2-hive2 -> /usr/hdp/2.5.0.0-1234/hive2
> {code}
> Normally, this would be fine. However, we must use the {{schematool}} from
> {{hive2}} and not {{hive}}:
> {code}
> /usr/hdp/2.5.0.0-1234/hive2/bin/schematool
> {code}
> Since Metastore is uggraded first, it's trying to write the custom JDBC
> connector to
> {{/usr/hdp/current/hive-server2-hive2/lib}}
> But since this component doesn't exist or hasn't been {{hdp-select}}'d yet,
> it fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm
[ https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335326#comment-15335326 ] Jungtaek Lim commented on AMBARI-17080: --- Please note that there's a bug on Cluster Metrics Consumer and STORM-1911 will handle this. Unfortunately this patch is affected so need to modify patch once more. Since it'll be a small fix, I would like to continue review process. > Support Storm 1.0 in Ambari Metrics for Storm > - > > Key: AMBARI-17080 > URL: https://issues.apache.org/jira/browse/AMBARI-17080 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: AMBARI-17080-v1.patch, AMBARI-17080-v2.patch > > > Since there was package name change on Apache Storm 1.0.0, Ambari Metrics > Reporter / Sink for Storm will not work when Ambari supports Apache Storm > 1.0.0 or upper. > This issue is for addressing this. > Please note that it will incur compile failure unless Ambari Metrics pom file > depends on Storm 1.x version, so decision for version of Storm should be made > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17286) Service config links should use public host name
[
https://issues.apache.org/jira/browse/AMBARI-17286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335322#comment-15335322
]
Hadoop QA commented on AMBARI-17286:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811244/AMBARI-17286.v0.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 2 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/7397//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7397//console
This message is automatically generated.
> Service config links should use public host name
>
>
> Key: AMBARI-17286
> URL: https://issues.apache.org/jira/browse/AMBARI-17286
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17286.v0.patch
>
>
> Service config links (e.g. tez.tez-ui.history-url.base) need to use the
> Ambari server's public name / IP instead of the private one. (Since
> tez.tez-ui.history-url.base is used to navigate from RM UI to Tez View.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm
[ https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17080: -- Attachment: AMBARI-17080-v2.patch Submitting patch. NOTE: v2 is compatible with Apache Storm 1.1.0 SNAPSHOT which contains "Cluster Metrics Consumer" feature. > Support Storm 1.0 in Ambari Metrics for Storm > - > > Key: AMBARI-17080 > URL: https://issues.apache.org/jira/browse/AMBARI-17080 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: AMBARI-17080-v1.patch, AMBARI-17080-v2.patch > > > Since there was package name change on Apache Storm 1.0.0, Ambari Metrics > Reporter / Sink for Storm will not work when Ambari supports Apache Storm > 1.0.0 or upper. > This issue is for addressing this. > Please note that it will incur compile failure unless Ambari Metrics pom file > depends on Storm 1.x version, so decision for version of Storm should be made > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17284) Hive Metastore Upgrade Fails Because Of Missing Hive Interactive Directory
[
https://issues.apache.org/jira/browse/AMBARI-17284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-17284:
-
Attachment: AMBARI-17284.patch
> Hive Metastore Upgrade Fails Because Of Missing Hive Interactive Directory
> --
>
> Key: AMBARI-17284
> URL: https://issues.apache.org/jira/browse/AMBARI-17284
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17284.patch
>
>
> During an upgrade from HDP 2.3/2.4 to HDP 2.5, the following error is seen:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 254, in
> HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 662, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 114, in pre_upgrade_restart
> self.upgrade_schema(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 189, in upgrade_schema
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 73, in configure
> hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 274, in hive
> jdbc_connector(params.target_hive2, params.hive2_previous_jdbc_jar)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 463, in jdbc_connector
> sudo = True)
> 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 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cp
> --remove-destination /var/lib/ambari-agent/tmp/mysql-connector-java.jar
> /usr/hdp/current/hive-server2-hive2/lib/mysql-connector-java.jar' returned 1.
> cp: cannot create regular file
> `/usr/hdp/current/hive-server2-hive2/lib/mysql-connector-java.jar': No such
> file or directory
> {code}
> This is because with HDP 2.5, Hive introduced a new component called
> {{hive-server2-hive2}}:
> {code}
> /usr/hdp/current/hive-metastore -> /usr/hdp/2.5.0.0-1234/hive
> /usr/hdp/current/hive-server2 -> /usr/hdp/2.5.0.0-1234/hive
> /usr/hdp/current/hive-server2-hive2 -> /usr/hdp/2.5.0.0-1234/hive2
> {code}
> Normally, this would be fine. However, we must use the {{schematool}} from
> {{hive2}} and not {{hive}}:
> {code}
> /usr/hdp/2.5.0.0-1234/hive2/bin/schematool
> {code}
> Since Metastore is uggraded first, it's trying to write the custom JDBC
> connector to
> {{/usr/hdp/current/hive-server2-hive2/lib}}
> But since this component doesn't exist or hasn't been {{hdp-select}}'d yet,
> it fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17284) Hive Metastore Upgrade Fails Because Of Missing Hive Interactive Directory
[
https://issues.apache.org/jira/browse/AMBARI-17284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-17284:
-
Status: Patch Available (was: Open)
> Hive Metastore Upgrade Fails Because Of Missing Hive Interactive Directory
> --
>
> Key: AMBARI-17284
> URL: https://issues.apache.org/jira/browse/AMBARI-17284
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17284.patch
>
>
> During an upgrade from HDP 2.3/2.4 to HDP 2.5, the following error is seen:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 254, in
> HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 662, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 114, in pre_upgrade_restart
> self.upgrade_schema(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 189, in upgrade_schema
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 73, in configure
> hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 274, in hive
> jdbc_connector(params.target_hive2, params.hive2_previous_jdbc_jar)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 463, in jdbc_connector
> sudo = True)
> 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 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cp
> --remove-destination /var/lib/ambari-agent/tmp/mysql-connector-java.jar
> /usr/hdp/current/hive-server2-hive2/lib/mysql-connector-java.jar' returned 1.
> cp: cannot create regular file
> `/usr/hdp/current/hive-server2-hive2/lib/mysql-connector-java.jar': No such
> file or directory
> {code}
> This is because with HDP 2.5, Hive introduced a new component called
> {{hive-server2-hive2}}:
> {code}
> /usr/hdp/current/hive-metastore -> /usr/hdp/2.5.0.0-1234/hive
> /usr/hdp/current/hive-server2 -> /usr/hdp/2.5.0.0-1234/hive
> /usr/hdp/current/hive-server2-hive2 -> /usr/hdp/2.5.0.0-1234/hive2
> {code}
> Normally, this would be fine. However, we must use the {{schematool}} from
> {{hive2}} and not {{hive}}:
> {code}
> /usr/hdp/2.5.0.0-1234/hive2/bin/schematool
> {code}
> Since Metastore is uggraded first, it's trying to write the custom JDBC
> connector to
> {{/usr/hdp/current/hive-server2-hive2/lib}}
> But since this component doesn't exist or hasn't been {{hdp-select}}'d yet,
> it fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17289) VDF: UI Edits #2
[
https://issues.apache.org/jira/browse/AMBARI-17289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335295#comment-15335295
]
Hadoop QA commented on AMBARI-17289:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811264/AMBARI-17289.v0.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/7396//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7396//console
This message is automatically generated.
> VDF: UI Edits #2
>
>
> Key: AMBARI-17289
> URL: https://issues.apache.org/jira/browse/AMBARI-17289
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17289.v0.patch
>
>
> The CSS styling for Name on Register Version cleanup
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12697) Rolling upgrade: Ambari UI should be able to display rolling upgrade history
[
https://issues.apache.org/jira/browse/AMBARI-12697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335275#comment-15335275
]
Hadoop QA commented on AMBARI-12697:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811206/AMBARI-12697.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 6 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/7395//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7395//console
This message is automatically generated.
> Rolling upgrade: Ambari UI should be able to display rolling upgrade history
>
>
> Key: AMBARI-12697
> URL: https://issues.apache.org/jira/browse/AMBARI-12697
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-web
>Affects Versions: 2.1.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-12697.patch, Upgrade_History_UI.pdf
>
>
> Ambari UI shows operation history in the ops prompt. All upgrade and
> downgrade attempts are not shown on the UI once user finalizes it and close
> the upgrade/downgrade UI.
> The information is in the database already. This JIRA is to propose a way to
> add UI elements to display a list of upgrades/downgrades associated with the
> cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-13238) MySQL service status needs to be more robust
[
https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335260#comment-15335260
]
Hadoop QA commented on AMBARI-13238:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811215/AMBARI-13238.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7394//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7394//console
This message is automatically generated.
> MySQL service status needs to be more robust
>
>
> Key: AMBARI-13238
> URL: https://issues.apache.org/jira/browse/AMBARI-13238
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.1.0, 2.2.0
>Reporter: Thomas Friedrich
>Assignee: Juanjo Marron
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-13238.patch
>
>
> The mysql service check in mysql_service.py simply checks for the existence
> of a mysqld process. If an unrelated mysqld service is running on the same
> node and Hive is configured to run with a MySQL db, the Hive start action
> won't start the MySQL server instance and the metastore connection fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17109) Capacity scheduler view - problem with queue percent rounding
[ https://issues.apache.org/jira/browse/AMBARI-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-17109: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.4, trunk. > Capacity scheduler view - problem with queue percent rounding > - > > Key: AMBARI-17109 > URL: https://issues.apache.org/jira/browse/AMBARI-17109 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.1.0 >Reporter: Akhil PB > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17109.1.patch, AMBARI-17109.2.patch, > CapSchedViewCalc.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17271) Hive Jdbc View: Add code to include 'hive.server2.proxy.user' to connection param by default
[ https://issues.apache.org/jira/browse/AMBARI-17271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-17271: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.4, trunk. > Hive Jdbc View: Add code to include 'hive.server2.proxy.user' to connection > param by default > - > > Key: AMBARI-17271 > URL: https://issues.apache.org/jira/browse/AMBARI-17271 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.4.0 > > Attachments: AMBARI-17271.branch-2.4.patch > > > To make the instances work in kerberized environment, we need to add the > proxy user in the session params which will go with the connection url. > To make this seemless we need to add the 'hive.server2.proxy.user" parameter > to the jdbc url in the kerberized cluster if user has not provided it in > session parameter configuration while creating the instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17269) Hive Query is not running in Hive View 2.0.0 Instance (JDBC)
[ https://issues.apache.org/jira/browse/AMBARI-17269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-17269: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.4, trunk. > Hive Query is not running in Hive View 2.0.0 Instance (JDBC) > > > Key: AMBARI-17269 > URL: https://issues.apache.org/jira/browse/AMBARI-17269 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.4.0 > > Attachments: AMBARI-17269.branch-2.4.patch > > > No query (SELECT or INSERT) are running in Hive View 2.0.0. > Queries were failing because, jobid was used in actor names to make it unique > but jobid is not a unique identifier across instances. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17208) Add logging for the command executed during PXF service check
[
https://issues.apache.org/jira/browse/AMBARI-17208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335232#comment-15335232
]
Hadoop QA commented on AMBARI-17208:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12810087/AMBARI-17208.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/7393//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7393//console
This message is automatically generated.
> Add logging for the command executed during PXF service check
> -
>
> Key: AMBARI-17208
> URL: https://issues.apache.org/jira/browse/AMBARI-17208
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 2.4.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: 2.4.0
>
> Attachments: AMBARI-17208.patch
>
>
> Add logging for the command executed during PXF service check
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17200) Tez, Pig, Hive, MapReduce service checks will fail on non standard queue names
[
https://issues.apache.org/jira/browse/AMBARI-17200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335216#comment-15335216
]
Hadoop QA commented on AMBARI-17200:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811137/AMBARI-17200.patch.1
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7391//console
This message is automatically generated.
> Tez, Pig, Hive, MapReduce service checks will fail on non standard queue names
> --
>
> Key: AMBARI-17200
> URL: https://issues.apache.org/jira/browse/AMBARI-17200
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17200.patch, AMBARI-17200.patch.1
>
>
> If user will change queue names in a way when default queue will be missing -
> Tez, Hive and Pig service checks will fail coz no default queue found
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17248) Reduce the idle time before first command from next stage is executed on a host
[
https://issues.apache.org/jira/browse/AMBARI-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335214#comment-15335214
]
Hadoop QA commented on AMBARI-17248:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811144/AMBARI-17248.trunk.v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7390//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7390//console
This message is automatically generated.
> Reduce the idle time before first command from next stage is executed on a
> host
> ---
>
> Key: AMBARI-17248
> URL: https://issues.apache.org/jira/browse/AMBARI-17248
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.4.0
>
> Attachments: AMBARI-17248.trunk.v3.patch
>
>
> Commands to be executed by ambari-agents are being sent down by the server in
> the response message to agent heartbeat messages.
> The server processes the received heartbeat, it checks if there are next
> commands scheduled to be executed by ambari-agent and adds those to the
> heartbeat response for the ambari-agent.
> The server organises the commands that can be executed in parallel into
> stages. Ambari server ensures that only the commands of a single stage is
> scheduled to be executed by the agent and starts scheduling the commands of
> the next stage only after all commands of current stage has finished
> successfully.
> The processing of command status received with the heartbeat message happens
> asynchronously to heartbeat response in HeartBeatProcessor and
> ActionScheduler creation thus when the heartbeat response is created the
> commands for the next stage are not scheduled yet. This means that the next
> commands will be sent to agent only with the next heartbeat.
> Agents currently sends a heartbeat to the server on command a completion or
> at a timeout = self.netutil.HEARTBEAT_IDDLE_INTERVAL_SEC –
> self.netutil.MINIMUM_INTERVAL_BETWEEN_HEARTBEATS interval which is ~10
> seconds if there are no commands to be executed.
> This means that when the server receives a heartbeat triggered by the
> completion of the last command from the current stage the server will send
> the commands for the next stage only 10 seconds later when the next heartbeat
> is received. This leads to agents spending considerable amount of time idle
> when there are multiple stages to be executed.
> Agents should heartbeat at a higher rate while there are still pending stages
> to be executed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17288) Redundant element on create version page
[ https://issues.apache.org/jira/browse/AMBARI-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17288: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 5e50c84cc4fed6b594967fe573210a2f0d3f99fa > Redundant element on create version page > > > Key: AMBARI-17288 > URL: https://issues.apache.org/jira/browse/AMBARI-17288 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17288.v0.patch > > > Redundant element on create version page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17289) VDF: UI Edits #2
[ https://issues.apache.org/jira/browse/AMBARI-17289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17289: Attachment: AMBARI-17289.v0.patch ambari-admin: Executed 76 of 76 SUCCESS (0.15 secs / 0.358 secs) Manual testing done. > VDF: UI Edits #2 > > > Key: AMBARI-17289 > URL: https://issues.apache.org/jira/browse/AMBARI-17289 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17289.v0.patch > > > The CSS styling for Name on Register Version cleanup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17289) VDF: UI Edits #2
[ https://issues.apache.org/jira/browse/AMBARI-17289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17289: Status: Patch Available (was: Open) > VDF: UI Edits #2 > > > Key: AMBARI-17289 > URL: https://issues.apache.org/jira/browse/AMBARI-17289 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17289.v0.patch > > > The CSS styling for Name on Register Version cleanup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17289) VDF: UI Edits #2
Zhe (Joe) Wang created AMBARI-17289: --- Summary: VDF: UI Edits #2 Key: AMBARI-17289 URL: https://issues.apache.org/jira/browse/AMBARI-17289 Project: Ambari Issue Type: Task Components: ambari-admin Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Fix For: 2.4.0 The CSS styling for Name on Register Version cleanup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17287) UI: 'llap' queue is not shown in dropdown even though recommendation says so. Shows 'llap' queue after save.
[ https://issues.apache.org/jira/browse/AMBARI-17287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17287: Status: Patch Available (was: Open) Verified that patch fixes the issue on a cluster. Verified that ambar-web unit tests passes successfully: 28633 tests complete (29 seconds) 154 tests pending > UI: 'llap' queue is not shown in dropdown even though recommendation says so. > Shows 'llap' queue after save. > > > Key: AMBARI-17287 > URL: https://issues.apache.org/jira/browse/AMBARI-17287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17287.patch > > > This issue happens because even though options of configs are updated from > stack advisor response, options of combobox widget view are not updated > dynamically after the view is rendered once. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16731) Should close file object in security.py
[
https://issues.apache.org/jira/browse/AMBARI-16731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335077#comment-15335077
]
Masahiro Tanaka commented on AMBARI-16731:
--
Hi [~aonishuk], [~u39kun], [~swagle], [~mahadev], could you review this ?
> Should close file object in security.py
> ---
>
> Key: AMBARI-16731
> URL: https://issues.apache.org/jira/browse/AMBARI-16731
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Minor
> Labels: patch-available
> Attachments: AMBARI-16371.patch, AMBARI-16731.1.patch
>
>
> {{reqSignCrt}} method opens CSR file with {{open}} function but that doesn't
> close it.
> And, {{loadSrvrCrt}} method opens a file but this is unclosed too.
> They waste resources and may cause a problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17287) UI: 'llap' queue is not shown in dropdown even though recommendation says so. Shows 'llap' queue after save.
[ https://issues.apache.org/jira/browse/AMBARI-17287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17287: Attachment: AMBARI-17287.patch > UI: 'llap' queue is not shown in dropdown even though recommendation says so. > Shows 'llap' queue after save. > > > Key: AMBARI-17287 > URL: https://issues.apache.org/jira/browse/AMBARI-17287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17287.patch > > > This issue happens because even though options of configs are updated from > stack advisor response, options of combobox widget view are not updated > dynamically after the view is rendered once. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17288) Redundant element on create version page
[ https://issues.apache.org/jira/browse/AMBARI-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17288: Status: Patch Available (was: Open) > Redundant element on create version page > > > Key: AMBARI-17288 > URL: https://issues.apache.org/jira/browse/AMBARI-17288 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17288.v0.patch > > > Redundant element on create version page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17288) Redundant element on create version page
[ https://issues.apache.org/jira/browse/AMBARI-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17288: Attachment: AMBARI-17288.v0.patch ambari-admin: Executed 76 of 76 SUCCESS (0.121 secs / 0.368 secs) Manual testing done. > Redundant element on create version page > > > Key: AMBARI-17288 > URL: https://issues.apache.org/jira/browse/AMBARI-17288 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17288.v0.patch > > > Redundant element on create version page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17288) Redundant element on create version page
Zhe (Joe) Wang created AMBARI-17288: --- Summary: Redundant element on create version page Key: AMBARI-17288 URL: https://issues.apache.org/jira/browse/AMBARI-17288 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Fix For: 2.4.0 Redundant element on create version page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17245) Failed to start Hive metastore due to UnicodeDecodeError
[
https://issues.apache.org/jira/browse/AMBARI-17245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335045#comment-15335045
]
Masahiro Tanaka commented on AMBARI-17245:
--
I think this is related to AMBARI-14823
> Failed to start Hive metastore due to UnicodeDecodeError
>
>
> Key: AMBARI-17245
> URL: https://issues.apache.org/jira/browse/AMBARI-17245
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6.5, LANG=ja_JP.UTF-8
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17245.patch
>
>
> When we start hivemestore in the environment described above, we got an error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 254, in
> HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 686, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 61, in start
> hive_service('metastore', action='start', upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_service.py",
> line 70, in hive_service
> pid = get_user_call_output.get_user_call_output(format("cat {pid_file}"),
> user=params.hive_user, is_checked_call=False)[1]
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 59, in get_user_call_output
> err_msg = Logger.filter_text(("Execution of '%s' returned %d. %s") %
> (command_string, code, all_output))
> File "/usr/lib/python2.6/site-packages/resource_management/core/logger.py",
> line 101, in filter_text
> text = text.replace(unprotected_string, protected_string)
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe3 in position 117:
> ordinal not in range(128)
> {code}
> I think the reason why this error occurs is because
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py".
> This script calls system command (e.g. {{cat}}), writes stdout & stderr in
> the tempfile, and read it. The outputs (stdout, stderr) are in UTF-8 encoded
> Japanese in the above environment.
> When reading string from file, python regards the file as ASCII encoded by
> default. But if the file is utf-8 encoded, this causes an error.
> We should decode UTF-8 when reading the file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs
[
https://issues.apache.org/jira/browse/AMBARI-17280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335029#comment-15335029
]
Hadoop QA commented on AMBARI-17280:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811157/AMBARI-17280.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServiceComponentTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7389//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7389//console
This message is automatically generated.
> RU to write out client configs that are dependencies of Hive, ATS, and Oozie
> during upgrades that change configs
>
>
> Key: AMBARI-17280
> URL: https://issues.apache.org/jira/browse/AMBARI-17280
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.2.0
>Reporter: Ana Gillan
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17280.branch-2.4.patch, AMBARI-17280.trunk.patch
>
>
> During RU, HiveServer2 is restarted but the newer tez configs have not yet
> been saved, which is incorrect because Hive has a dependency on Tez.
> This is important when configs change during a major stack upgrade, e.g., HDP
> 2.4 -> 2.5. What happens today is,
> * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from
> /etc/tez/2.4.0.0-1/0/ to the new folder
> * If configs change during RU, then Hive is restarted and the classpath means
> that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0
> folder
> This problem exists for all of these components:
> HiveServer: depends on Tez and MapReduce clients
> ATS: depends on Tez and Spark clients
> Oozie: depends on Tez, Spark, and MapReduce clients
> This problem only exists when configs change (so crossing major stack
> version) and during RU (because it is allowed to change configs during the
> middle of restarting services).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17282) Use customized display name as version string
[ https://issues.apache.org/jira/browse/AMBARI-17282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335022#comment-15335022 ] Hudson commented on AMBARI-17282: - FAILURE: Integrated in Ambari-trunk-Commit #5096 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5096/]) AMBARI-17282. Use customized display name as version string (ncole) (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a94ebcfb64c27fa668aa5527090cf9b0f35537e1]) * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProviderTest.java * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProvider.java > Use customized display name as version string > - > > Key: AMBARI-17282 > URL: https://issues.apache.org/jira/browse/AMBARI-17282 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17282.patch > > > The user can specify the display name when creating a version using VDF. In > that case, use that for the repository version string as well. This does not > cause problems as the version will get replaced at install time. We just > need a way to provide uniqueness in the DB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17266) StackDeploys: Suse: after enabling ranger plugin save button is always present
[ https://issues.apache.org/jira/browse/AMBARI-17266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335021#comment-15335021 ] Hudson commented on AMBARI-17266: - FAILURE: Integrated in Ambari-trunk-Commit #5096 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5096/]) AMBARI-17266 - StackDeploys: Suse: after enabling ranger plugin save (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fcb7e7d134fccfce693c51d629df760b14034fa1]) * ambari-web/app/utils/config.js > StackDeploys: Suse: after enabling ranger plugin save button is always present > -- > > Key: AMBARI-17266 > URL: https://issues.apache.org/jira/browse/AMBARI-17266 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-17266.patch > > > 1. Deploy cluster using BP > 2. enable ranger plugins > 3. save configs > Expected: Configs should be saved and save button should be disabled > Actual: even after save and clicking Ok on confirmation "Save" button is > enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17129) Set necessary HBase configuration to enable SPNEGO authentication if desired
[ https://issues.apache.org/jira/browse/AMBARI-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335020#comment-15335020 ] Hudson commented on AMBARI-17129: - FAILURE: Integrated in Ambari-trunk-Commit #5096 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5096/]) AMBARI-17129. Set necessary HBase configuration to enable SPNEGO (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=89870f28a204b782f5d25eb09e6e3c5bfa496acc]) * ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java * ambari-server/src/main/resources/stacks/HDP/2.5/services/HBASE/kerberos.json * ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java * ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/alerts.json > Set necessary HBase configuration to enable SPNEGO authentication if desired > > > Key: AMBARI-17129 > URL: https://issues.apache.org/jira/browse/AMBARI-17129 > Project: Ambari > Issue Type: Improvement >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-17129.001.patch, AMBARI-17129.002.patch, > AMBARI-17129.003.patch > > > Over in HBASE-5291, I implemented support to enable SPNEGO authentication of > the HBase web UIs. > We should update the HBase configuration when Kerberos is enabled such that, > if the user chooses to enable the SPNEGO auth, the principal and keytab > information is already present in the configuration. If the SPNEGO auth is > not enabled, then these properties won't affect anything if they are set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17287) UI: 'llap' queue is not shown in dropdown even though recommendation says so. Shows 'llap' queue after save.
[ https://issues.apache.org/jira/browse/AMBARI-17287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17287: Description: This issue happens because even though options of configs are updated from stack advisor response, options of combobox widget view are not updated dynamically after the view is rendered once. > UI: 'llap' queue is not shown in dropdown even though recommendation says so. > Shows 'llap' queue after save. > > > Key: AMBARI-17287 > URL: https://issues.apache.org/jira/browse/AMBARI-17287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > > This issue happens because even though options of configs are updated from > stack advisor response, options of combobox widget view are not updated > dynamically after the view is rendered once. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17287) UI: 'llap' queue is not shown in dropdown even though recommendation says so. Shows 'llap' queue after save.
Jaimin D Jetly created AMBARI-17287: --- Summary: UI: 'llap' queue is not shown in dropdown even though recommendation says so. Shows 'llap' queue after save. Key: AMBARI-17287 URL: https://issues.apache.org/jira/browse/AMBARI-17287 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Jaimin D Jetly Assignee: Jaimin D Jetly Priority: Critical Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17286) Service config links should use public host name
[ https://issues.apache.org/jira/browse/AMBARI-17286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17286: Status: Patch Available (was: Open) > Service config links should use public host name > > > Key: AMBARI-17286 > URL: https://issues.apache.org/jira/browse/AMBARI-17286 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17286.v0.patch > > > Service config links (e.g. tez.tez-ui.history-url.base) need to use the > Ambari server's public name / IP instead of the private one. (Since > tez.tez-ui.history-url.base is used to navigate from RM UI to Tez View.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17286) Service config links should use public host name
[ https://issues.apache.org/jira/browse/AMBARI-17286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17286: Attachment: AMBARI-17286.v0.patch Unit tests for stack advisor passed Total run:162 Total errors:0 Total failures:0 OK Manual testing done. > Service config links should use public host name > > > Key: AMBARI-17286 > URL: https://issues.apache.org/jira/browse/AMBARI-17286 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17286.v0.patch > > > Service config links (e.g. tez.tez-ui.history-url.base) need to use the > Ambari server's public name / IP instead of the private one. (Since > tez.tez-ui.history-url.base is used to navigate from RM UI to Tez View.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17286) Service config links should use public host name
Zhe (Joe) Wang created AMBARI-17286: --- Summary: Service config links should use public host name Key: AMBARI-17286 URL: https://issues.apache.org/jira/browse/AMBARI-17286 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Fix For: 2.4.0 Service config links (e.g. tez.tez-ui.history-url.base) need to use the Ambari server's public name / IP instead of the private one. (Since tez.tez-ui.history-url.base is used to navigate from RM UI to Tez View.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-17260) Remove CascadeType in ServiceComponentHistoryEntity for ServiceComponentDesiredStateEntity
[
https://issues.apache.org/jira/browse/AMBARI-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reopened AMBARI-17260:
--
Reverted from trunk and branch-2.4 due to introduction of unit test failures.
See https://builds.apache.org/job/Ambari-trunk-Commit/5088/
> Remove CascadeType in ServiceComponentHistoryEntity for
> ServiceComponentDesiredStateEntity
> --
>
> Key: AMBARI-17260
> URL: https://issues.apache.org/jira/browse/AMBARI-17260
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Ajit Kumar
>Assignee: Ajit Kumar
> Fix For: 2.4.0
>
>
> Service deletion throws '500: Server Error' due to foreign key constraint
> violation :
> {code}
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> Cannot delete or update a parent row: a foreign key constraint fails
> (`ambaricustom`.`servicecomponent_history`, CONSTRAINT
> `FK_sc_history_component_id` FOREIGN KEY (`component_id`) REFERENCES
> `servicecomponentdesiredstate` (`id`))
> Error Code: 1451
> Call: DELETE FROM servicecomponentdesiredstate WHERE (id = ?)
> bind => [1 parameter bound]
> at
> org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
> {code}
> Removing CascadeType in ServiceComponentHistoryEntity for
> ServiceComponentDesiredStateEntity should fix this.
> Repro steps:
> 1. Deploy HDP-2.4 cluster with Ambari 2.4.0.0
> 2. Perform Express Upgrade to HDP 2.5
> 3. Try to delete Hive service (after stopping it)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs
Alexander Denissov created AMBARI-17285: --- Summary: Custom service repos in repoinfo.xml got overwritten by public VDFs Key: AMBARI-17285 URL: https://issues.apache.org/jira/browse/AMBARI-17285 Project: Ambari Issue Type: Bug Reporter: Alexander Denissov Ambari 2.4 introduced Version Definition Files that break the functionality of adding a custom service repo, since custom services do not have an entry in the public VDF. In the case of HAWQ, the plugin is installed on Ambari host and it adds the new repo information to the repoinfo.xml of all available stacks on the file system. Once Ambari cluster creation wizard queries the latest repo info from the public URLs, it will get the info for all stack repos, but not the custom ones. So, the logic should be: 1. Use default repoinfo (from file system) as the base 2. Query public VDF, if available 3. For each entry in public VDF overwrite values in the default repoinfo 4. Entries in default repoinfo that do not have corresponding entries in VDF should stay intact This way custom services can be added via file edit and the latest information can still be retrieved and applied for the standard stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[
https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334810#comment-15334810
]
Hadoop QA commented on AMBARI-12885:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811160/AMBARI-12885.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7387//console
This message is automatically generated.
> Dynamic stack extensions - install and upgrade support for custom services
> --
>
> Key: AMBARI-12885
> URL: https://issues.apache.org/jira/browse/AMBARI-12885
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-agent, ambari-server, ambari-web
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Attachments: AMBARI-12885 Example.pdf, AMBARI-12885.patch, Dynamic
> Stack Extensions - High Level Design v5.pdf
>
>
> The purpose of this proposal is to facilitate adding custom services to an
> existing stack. Ideally this would support adding and upgrading custom
> services separately from the core services defined in the stack. In
> particular we are looking at custom services that need to support several
> different stacks (different distributions of Ambari). The release cycle of
> the custom services may be different from that of the core stack; that is, a
> custom service may be upgraded at a different rate than the core distribution
> itself and may be upgraded multiple times within the lifespan of a single
> release of the core distribution.
> One possible approach to handling this would be dynamically extending a stack
> (after install time). It would be best to extend the stack in packages where
> a stack extension package can have one or more custom services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17279) BG operations windown appeared after 90 seconds on clicking start all services
[
https://issues.apache.org/jira/browse/AMBARI-17279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334808#comment-15334808
]
Hadoop QA commented on AMBARI-17279:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811146/AMBARI-17279.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ConfigHelperTest
org.apache.ambari.server.state.ServiceComponentTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7386//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7386//console
This message is automatically generated.
> BG operations windown appeared after 90 seconds on clicking start all services
> --
>
> Key: AMBARI-17279
> URL: https://issues.apache.org/jira/browse/AMBARI-17279
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17279.patch
>
>
> STR:
> 1) Stop all services using Stop all services button, and cancel from BG
> operations window
> 2) Stop all services
> 3) Start all services and cancel from BG operations window
> 4) Start all services.
> The BG operations window appeared after about 90 seconds. The test waited for
> 30 seconds and failed
> Artifacts : /test-logs/ambari-serv/artifacts/screenshots/com.hw.ambari.ui.tests.monitoring
> .TestCancelRequestsAllServices/>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17281) [Grafana] topN implementation for templatized dashboards
[ https://issues.apache.org/jira/browse/AMBARI-17281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334806#comment-15334806 ] Hudson commented on AMBARI-17281: - FAILURE: Integrated in Ambari-trunk-Commit #5095 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5095/]) AMBARI-17281. [Grafana] topN implementation for templatized dashboards. (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d4ded26d5a55ce36db281b2b32e831b936aefea0]) * ambari-metrics/ambari-metrics-grafana/ambari-metrics/datasource.js > [Grafana] topN implementation for templatized dashboards > > > Key: AMBARI-17281 > URL: https://issues.apache.org/jira/browse/AMBARI-17281 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: ambari-2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17281.patch > > > Implement UI changes to support topN querying in Grafana for templatized > dashboards that support per-host level templating. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17129) Set necessary HBase configuration to enable SPNEGO authentication if desired
[
https://issues.apache.org/jira/browse/AMBARI-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-17129:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 89870f28a204b782f5d25eb09e6e3c5bfa496acc
Author: Josh Elser
Date: Thu Jun 16 17:36:32 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit dbc865b4851fe1a75a2a1c843bd2d0220b1344ce
Author: Josh Elser
Date: Thu Jun 16 17:37:27 2016 -0400
{noformat}
> Set necessary HBase configuration to enable SPNEGO authentication if desired
>
>
> Key: AMBARI-17129
> URL: https://issues.apache.org/jira/browse/AMBARI-17129
> Project: Ambari
> Issue Type: Improvement
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Critical
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17129.001.patch, AMBARI-17129.002.patch,
> AMBARI-17129.003.patch
>
>
> Over in HBASE-5291, I implemented support to enable SPNEGO authentication of
> the HBase web UIs.
> We should update the HBase configuration when Kerberos is enabled such that,
> if the user chooses to enable the SPNEGO auth, the principal and keytab
> information is already present in the configuration. If the SPNEGO auth is
> not enabled, then these properties won't affect anything if they are set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17274) As part of atlas startup,"/usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh" script is executed by ambari, which fails with "java.io.FileNotFoundException"
[
https://issues.apache.org/jira/browse/AMBARI-17274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-17274:
---
Status: Patch Available (was: In Progress)
> As part of atlas
> startup,"/usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh" script is
> executed by ambari, which fails with "java.io.FileNotFoundException"
> ---
>
> Key: AMBARI-17274
> URL: https://issues.apache.org/jira/browse/AMBARI-17274
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> Below is the error log.
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 173, in
> MetadataServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 69, in start
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 53, in configure
> metadata()
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
> line 101, in metadata
> upload_conf_set('basic_configs', random_num)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
> line 122, in upload_conf_set
> user=params.metadata_user)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/solr_cloud_util.py",
> line 49, in upload_configuration_to_zk
> user=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 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export
> JAVA_HOME=/usr/jdk64/jdk1.8.0_77 ;
> /usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh -z
> os-d7-unsecure-atlas-3.openstacklocal:2181,os-d7-unsecure-atlas-1.openstacklocal:2181/ambari-solr
> --upload-config -d
> /usr/lib/ambari-logsearch-solr/server/solr/configsets/basic_configs/conf -cs
> basic_configs -rt 5 -i 10' returned 1. log4j:ERROR setFile(null,true) call
> failed.
> java.io.FileNotFoundException: (No such file or directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.(FileOutputStream.java:213)
> at java.io.FileOutputStream.(FileOutputStream.java:133)
> at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
> at
> org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:207)
> at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
> at
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
> at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
> at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
> at
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
> at
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
> at
> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
> at
>
[jira] [Updated] (AMBARI-13238) MySQL service status needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13238: --- Attachment: AMBARI-13238.patch > MySQL service status needs to be more robust > > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13238) MySQL service status needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13238: --- Attachment: (was: AMBARI-13238.patch) > MySQL service status needs to be more robust > > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Fix For: 3.0.0 > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17282) Use customized display name as version string
[ https://issues.apache.org/jira/browse/AMBARI-17282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-17282: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Use customized display name as version string > - > > Key: AMBARI-17282 > URL: https://issues.apache.org/jira/browse/AMBARI-17282 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17282.patch > > > The user can specify the display name when creating a version using VDF. In > that case, use that for the repository version string as well. This does not > cause problems as the version will get replaced at install time. We just > need a way to provide uniqueness in the DB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17284) Hive Metastore Upgrade Fails Because Of Missing Hive Interactive Directory
Jonathan Hurley created AMBARI-17284:
Summary: Hive Metastore Upgrade Fails Because Of Missing Hive
Interactive Directory
Key: AMBARI-17284
URL: https://issues.apache.org/jira/browse/AMBARI-17284
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.4.0
During an upgrade from HDP 2.3/2.4 to HDP 2.5, the following error is seen:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
line 254, in
HiveMetastore().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 257, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 662, in restart
self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
line 114, in pre_upgrade_restart
self.upgrade_schema(env)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
line 189, in upgrade_schema
self.configure(env)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
line 73, in configure
hive(name = 'metastore')
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
line 89, in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
line 274, in hive
jdbc_connector(params.target_hive2, params.hive2_previous_jdbc_jar)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
line 463, in jdbc_connector
sudo = True)
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 70, in inner
result = function(command, **kwargs)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 92, in checked_call
tries=tries, try_sleep=try_sleep)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 140, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 293, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'cp --remove-destination
/var/lib/ambari-agent/tmp/mysql-connector-java.jar
/usr/hdp/current/hive-server2-hive2/lib/mysql-connector-java.jar' returned 1.
cp: cannot create regular file
`/usr/hdp/current/hive-server2-hive2/lib/mysql-connector-java.jar': No such
file or directory
{code}
This is because with HDP 2.5, Hive introduced a new component called
{{hive-server2-hive2}}:
{code}
/usr/hdp/current/hive-metastore -> /usr/hdp/2.5.0.0-1234/hive
/usr/hdp/current/hive-server2 -> /usr/hdp/2.5.0.0-1234/hive
/usr/hdp/current/hive-server2-hive2 -> /usr/hdp/2.5.0.0-1234/hive2
{code}
Normally, this would be fine. However, we must use the {{schematool}} from
{{hive2}} and not {{hive}}:
{code}
/usr/hdp/2.5.0.0-1234/hive2/bin/schematool
{code}
Since Metastore is uggraded first, it's trying to write the custom JDBC
connector to
{{/usr/hdp/current/hive-server2-hive2/lib}}
But since this component doesn't exist or hasn't been {{hdp-select}}'d yet, it
fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17283) Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server Interactive' Panel and Textboxes (editable) in HIVE Advanced section.
[ https://issues.apache.org/jira/browse/AMBARI-17283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17283: - Attachment: AMBARI-17283.patch > Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server > Interactive' Panel and Textboxes (editable) in HIVE Advanced section. > > > Key: AMBARI-17283 > URL: https://issues.apache.org/jira/browse/AMBARI-17283 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17283.patch > > > Following configs need to be shown as Labels on Hive Server Interactive Panel. > - hive-interactive-site/hive.llap.daemon.yarn.container.mb > - hive-interactive-site/hive.llap.daemon.num.executors > - hive-interactive-site/hive.llap.io.memory.size > - hive-interactive-env/num_llap_nodes > User will have the option to edit them on HIVE Advanced page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12697) Rolling upgrade: Ambari UI should be able to display rolling upgrade history
[ https://issues.apache.org/jira/browse/AMBARI-12697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-12697: --- Attachment: AMBARI-12697.patch > Rolling upgrade: Ambari UI should be able to display rolling upgrade history > > > Key: AMBARI-12697 > URL: https://issues.apache.org/jira/browse/AMBARI-12697 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, ambari-web >Affects Versions: 2.1.0 >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-12697.patch, Upgrade_History_UI.pdf > > > Ambari UI shows operation history in the ops prompt. All upgrade and > downgrade attempts are not shown on the UI once user finalizes it and close > the upgrade/downgrade UI. > The information is in the database already. This JIRA is to propose a way to > add UI elements to display a list of upgrades/downgrades associated with the > cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12697) Rolling upgrade: Ambari UI should be able to display rolling upgrade history
[ https://issues.apache.org/jira/browse/AMBARI-12697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-12697: --- Fix Version/s: trunk Status: Patch Available (was: Open) > Rolling upgrade: Ambari UI should be able to display rolling upgrade history > > > Key: AMBARI-12697 > URL: https://issues.apache.org/jira/browse/AMBARI-12697 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, ambari-web >Affects Versions: 2.1.0 >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-12697.patch, Upgrade_History_UI.pdf > > > Ambari UI shows operation history in the ops prompt. All upgrade and > downgrade attempts are not shown on the UI once user finalizes it and close > the upgrade/downgrade UI. > The information is in the database already. This JIRA is to propose a way to > add UI elements to display a list of upgrades/downgrades associated with the > cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17266) StackDeploys: Suse: after enabling ranger plugin save button is always present
[ https://issues.apache.org/jira/browse/AMBARI-17266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-17266: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.4 fcb7e7d134fccfce693c51d629df760b14034fa1 > StackDeploys: Suse: after enabling ranger plugin save button is always present > -- > > Key: AMBARI-17266 > URL: https://issues.apache.org/jira/browse/AMBARI-17266 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-17266.patch > > > 1. Deploy cluster using BP > 2. enable ranger plugins > 3. save configs > Expected: Configs should be saved and save button should be disabled > Actual: even after save and clicking Ok on confirmation "Save" button is > enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17283) Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server Interactive' Panel and Textboxes (editable) in HIVE Advanced section.
[ https://issues.apache.org/jira/browse/AMBARI-17283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17283: - Description: Following configs need to be shown as Labels on Hive Server Interactive Panel. - hive-interactive-site/hive.llap.daemon.yarn.container.mb - hive-interactive-site/hive.llap.daemon.num.executors - hive-interactive-site/hive.llap.io.memory.size - hive-interactive-env/num_llap_nodes User will have the option to edit them on HIVE Advanced page. was: - Following configs need to be shown as Labels on Hive Server Interactive Panel. hive-interactive-site/hive.llap.daemon.yarn.container.mb hive-interactive-site/hive.llap.daemon.num.executors hive-interactive-site/hive.llap.io.memory.size hive-interactive-env/num_llap_nodes - User will have the option to edit them on HIVE Advanced page. > Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server > Interactive' Panel and Textboxes (editable) in HIVE Advanced section. > > > Key: AMBARI-17283 > URL: https://issues.apache.org/jira/browse/AMBARI-17283 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > > Following configs need to be shown as Labels on Hive Server Interactive Panel. > - hive-interactive-site/hive.llap.daemon.yarn.container.mb > - hive-interactive-site/hive.llap.daemon.num.executors > - hive-interactive-site/hive.llap.io.memory.size > - hive-interactive-env/num_llap_nodes > User will have the option to edit them on HIVE Advanced page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17283) Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server Interactive' Panel and Textboxes (editable) in HIVE Advanced section.
[ https://issues.apache.org/jira/browse/AMBARI-17283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17283: - Summary: Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server Interactive' Panel and Textboxes (editable) in HIVE Advanced section. (was: Show LLAP calculated configs as 'Labels' (non-editable) on Hive Server Interactive Panel and Textboxes (editable) in HIVE Advanced section.) > Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server > Interactive' Panel and Textboxes (editable) in HIVE Advanced section. > > > Key: AMBARI-17283 > URL: https://issues.apache.org/jira/browse/AMBARI-17283 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17283) Show LLAP calculated configs as 'Labels' (non-editable) on Hive Server Interactive Panel and Textboxes (editable) in HIVE Advanced section.
Swapan Shridhar created AMBARI-17283: Summary: Show LLAP calculated configs as 'Labels' (non-editable) on Hive Server Interactive Panel and Textboxes (editable) in HIVE Advanced section. Key: AMBARI-17283 URL: https://issues.apache.org/jira/browse/AMBARI-17283 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17273) With Atlas HA enabled, atlas instance fails to come up with "Unable to find IDs matching any local host and port binding among id1"
[
https://issues.apache.org/jira/browse/AMBARI-17273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334612#comment-15334612
]
Hudson commented on AMBARI-17273:
-
FAILURE: Integrated in Ambari-trunk-Commit #5094 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5094/])
AMBARI-17273 - With Atlas HA enabled, atlas instance fails to come up
(tbeerbower:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=eec84460f391ece3d9018ecf552ef66b6b270159])
*
ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/application-properties.xml
* ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
*
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py
* ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
> With Atlas HA enabled, atlas instance fails to come up with "Unable to find
> IDs matching any local host and port binding among id1"
> ---
>
> Key: AMBARI-17273
> URL: https://issues.apache.org/jira/browse/AMBARI-17273
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> Atlas fails to come up with below error. This is because if ID information
> for all atlas instances is not generated and updated in
> atlas-application.properties.
> {noformat}
> 2016-06-14 10:48:23,249 WARN - [main:] ~ Failed startup of context
> o.e.j.w.WebAppContext@2ad31d76{/,file:/grid/0/hdp/2.5.0.0-723/atlas/server/webapp/atlas/,STARTING}{/usr/hdp/current/atlas-server/server/webapp/atlas}
> (WebAppContext:514)
> java.lang.RuntimeException: org.apache.atlas.AtlasException: Could not find
> server id for this instance. Unable to find IDs matching any local host and
> port binding among id1
> at org.apache.atlas.service.Services.start(Services.java:48)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.startServices(GuiceServletConfig.java:142)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:136)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
> at org.apache.atlas.Atlas.main(Atlas.java:113)
> Caused by: org.apache.atlas.AtlasException: Could not find server id for this
> instance. Unable to find IDs matching any local host and port binding among
> id1
> at
> org.apache.atlas.ha.AtlasServerIdSelector.selectServerId(AtlasServerIdSelector.java:77)
> at
> org.apache.atlas.web.service.ActiveInstanceElectorService.start(ActiveInstanceElectorService.java:105)
> at org.apache.atlas.service.Services.start(Services.java:45)
> ... 19 more
> 2016-06-14 10:48:23,284 INFO - [main:] ~ Started
> ServerConnector@255af999{HTTP/1.1}{0.0.0.0:21000} (ServerConnector:266)
> {noformat}
> Atlas-application.properties not updated with all other instance information
> leading to atlas startup failure
> {noformat}
> [root@ayubTesting-3 ~]# cat /etc/atlas/conf/atlas-application.properties
> # Generated by Apache Ambari. Tue Jun 14 10:47:47 2016
> atlas.audit.hbase.tablename=ATLAS_ENTITY_AUDIT_EVENTS
> atlas.audit.hbase.zookeeper.quorum=ayubtesting-2.openstacklocal,ayubtesting-3.openstacklocal
> atlas.audit.zookeeper.session.timeout.ms=1000
>
[jira] [Commented] (AMBARI-17262) Atlas Integration : Remove {{atlas_conf_dir}} from HADOOP_CLASSPATH in hive-env.
[
https://issues.apache.org/jira/browse/AMBARI-17262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334613#comment-15334613
]
Hudson commented on AMBARI-17262:
-
FAILURE: Integrated in Ambari-trunk-Commit #5094 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5094/])
AMBARI-17262 - Remove {{atlas_conf_dir}} from HADOOP_CLASSPATH in (tbeerbower:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6950a8a942e47892bcf094df08d0f8d5aab9ae2b])
*
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-env.xml
> Atlas Integration : Remove {{atlas_conf_dir}} from HADOOP_CLASSPATH in
> hive-env.
>
>
> Key: AMBARI-17262
> URL: https://issues.apache.org/jira/browse/AMBARI-17262
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> In Hive configuration ‘Advanced hive-env’ :
> {code}
> export
> HADOOP_CLASSPATH={{atlas_conf_dir}}:{{atlas_home_dir}}/hook/hive:${HADOOP_CLASSPATH}
> {code}
> remove
> {code}
> {{atlas_conf_dir}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17278) Unable to delete permission with type VIEW
[
https://issues.apache.org/jira/browse/AMBARI-17278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334597#comment-15334597
]
Hadoop QA commented on AMBARI-17278:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811129/AMBARI-17278.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/7385//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7385//console
This message is automatically generated.
> Unable to delete permission with type VIEW
> --
>
> Key: AMBARI-17278
> URL: https://issues.apache.org/jira/browse/AMBARI-17278
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin, ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17278.patch
>
>
> When we are removing some user, UI sends request to remove all privileges
> associated with user. But if there is some privilege with type VIEW server
> returns:
> {noformat}
> {
> "status" : 500,
> "message" : "org.apache.ambari.server.controller.spi.SystemException: An
> internal system exception occurred: Caught exception deleting privilege."
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17257) Ambari Server setup of proxyuser should set default values
[
https://issues.apache.org/jira/browse/AMBARI-17257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334571#comment-15334571
]
Hadoop QA commented on AMBARI-17257:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/1288/AMBARI-17257.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7384//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7384//console
This message is automatically generated.
> Ambari Server setup of proxyuser should set default values
> --
>
> Key: AMBARI-17257
> URL: https://issues.apache.org/jira/browse/AMBARI-17257
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: ambari-2.4.0
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-17257.patch
>
>
> The resolution of RMP-4514 sets '*' for proxyuser.hosts settings. Stack
> advisor should be modified to be more restrictive, instead of '*' set ambari
> server host name in the following properties:
> {code}
> hadoop.proxyuser.${ambari_proxy_user}.hosts="{{ hostname of ambari server }}"
> webhcat.proxyuser.${ambari_proxy_user}.hosts="{{ hostname of ambari server }}"
> yarn.timeline-service.http-authentication.proxyuser.${ambari_proxy_user}.hosts="{{
> hostname of ambari server }}"
> {code}
> Also this setting below is not required, so it will be removed:
> {code}
> "yarn.timeline-service.http-authentication.proxyuser.ambari-server.users":
> "*",
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17281) [Grafana] topN implementation for templatized dashboards
[ https://issues.apache.org/jira/browse/AMBARI-17281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-17281: - Resolution: Fixed Status: Resolved (was: Patch Available) +1'd on ReviewBoard. Committed to trunk and branch-2.4.0. > [Grafana] topN implementation for templatized dashboards > > > Key: AMBARI-17281 > URL: https://issues.apache.org/jira/browse/AMBARI-17281 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: ambari-2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17281.patch > > > Implement UI changes to support topN querying in Grafana for templatized > dashboards that support per-host level templating. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17181) Add some of value-attributes to property files in AMBARI_METRICS
[
https://issues.apache.org/jira/browse/AMBARI-17181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334526#comment-15334526
]
Hadoop QA commented on AMBARI-17181:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12810982/after_screenshot.PNG
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7383//console
This message is automatically generated.
> Add some of value-attributes to property files in AMBARI_METRICS
>
>
> Key: AMBARI-17181
> URL: https://issues.apache.org/jira/browse/AMBARI-17181
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics, ambari-server
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Minor
> Attachments: AMBARI-17181.1.patch, AMBARI-17181.patch,
> after_screenshot.PNG, before_screenshot.PNG
>
>
> Some of the property files in AMBARI_METRICS lack value-attributes.
> It would be nice to have value-attributes on most of the properties. If so,
> we can notice a careless mistakes in Ambari Server WebUI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17265) [Grafana] HBase Tables metric query fix
[
https://issues.apache.org/jira/browse/AMBARI-17265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334525#comment-15334525
]
Hadoop QA commented on AMBARI-17265:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811177/AMBARI-17265.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7382//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7382//console
This message is automatically generated.
> [Grafana] HBase Tables metric query fix
> ---
>
> Key: AMBARI-17265
> URL: https://issues.apache.org/jira/browse/AMBARI-17265
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: ambari-2.4.0
>Reporter: Prajwal Rao
>Assignee: Prajwal Rao
>Priority: Critical
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-17265.patch
>
>
> HBase Tables metric query needs to add the metric aggregator and metric
> transform to each metric.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17282) Use customized display name as version string
[ https://issues.apache.org/jira/browse/AMBARI-17282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-17282: --- Attachment: AMBARI-17282.patch > Use customized display name as version string > - > > Key: AMBARI-17282 > URL: https://issues.apache.org/jira/browse/AMBARI-17282 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17282.patch > > > The user can specify the display name when creating a version using VDF. In > that case, use that for the repository version string as well. This does not > cause problems as the version will get replaced at install time. We just > need a way to provide uniqueness in the DB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17282) Use customized display name as version string
[ https://issues.apache.org/jira/browse/AMBARI-17282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-17282: --- Status: Patch Available (was: Open) > Use customized display name as version string > - > > Key: AMBARI-17282 > URL: https://issues.apache.org/jira/browse/AMBARI-17282 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17282.patch > > > The user can specify the display name when creating a version using VDF. In > that case, use that for the repository version string as well. This does not > cause problems as the version will get replaced at install time. We just > need a way to provide uniqueness in the DB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17053) Add explicit ambari-server log line indicating cluster creation complete
[
https://issues.apache.org/jira/browse/AMBARI-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334503#comment-15334503
]
Hadoop QA commented on AMBARI-17053:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811023/AMBARI-17053_branch-2.4_and_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7381//console
This message is automatically generated.
> Add explicit ambari-server log line indicating cluster creation complete
>
>
> Key: AMBARI-17053
> URL: https://issues.apache.org/jira/browse/AMBARI-17053
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Daniel Gergely
>Assignee: Daniel Gergely
> Fix For: 2.4.0, 2.2-next
>
> Attachments: AMBARI-17053_2.2-next.patch,
> AMBARI-17053_branch-2.4_and_trunk.patch
>
>
> Add a log message to see when the cluster is ready to use (cluster creation
> finishes)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17269) Hive Query is not running in Hive View 2.0.0 Instance (JDBC)
[
https://issues.apache.org/jira/browse/AMBARI-17269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334502#comment-15334502
]
Hadoop QA commented on AMBARI-17269:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811052/AMBARI-17269.branch-2.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/hive-next
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7380//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7380//console
This message is automatically generated.
> Hive Query is not running in Hive View 2.0.0 Instance (JDBC)
>
>
> Key: AMBARI-17269
> URL: https://issues.apache.org/jira/browse/AMBARI-17269
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-17269.branch-2.4.patch
>
>
> No query (SELECT or INSERT) are running in Hive View 2.0.0.
> Queries were failing because, jobid was used in actor names to make it unique
> but jobid is not a unique identifier across instances.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17282) Use customized display name as version string
[ https://issues.apache.org/jira/browse/AMBARI-17282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-17282: --- Summary: Use customized display name as version string (was: Use customized display name as version) > Use customized display name as version string > - > > Key: AMBARI-17282 > URL: https://issues.apache.org/jira/browse/AMBARI-17282 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > > The user can specify the display name when creating a version using VDF. In > that case, use that for the repository version string as well. This does not > cause problems as the version will get replaced at install time. We just > need a way to provide uniqueness in the DB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17282) Use customized display name as version
Nate Cole created AMBARI-17282: -- Summary: Use customized display name as version Key: AMBARI-17282 URL: https://issues.apache.org/jira/browse/AMBARI-17282 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Priority: Critical Fix For: 2.4.0 The user can specify the display name when creating a version using VDF. In that case, use that for the repository version string as well. This does not cause problems as the version will get replaced at install time. We just need a way to provide uniqueness in the DB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17281) [Grafana] topN implementation for templatized dashboards
[ https://issues.apache.org/jira/browse/AMBARI-17281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-17281: - Status: Patch Available (was: Open) > [Grafana] topN implementation for templatized dashboards > > > Key: AMBARI-17281 > URL: https://issues.apache.org/jira/browse/AMBARI-17281 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: ambari-2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17281.patch > > > Implement UI changes to support topN querying in Grafana for templatized > dashboards that support per-host level templating. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17281) [Grafana] topN implementation for templatized dashboards
[ https://issues.apache.org/jira/browse/AMBARI-17281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-17281: - Attachment: AMBARI-17281.patch > [Grafana] topN implementation for templatized dashboards > > > Key: AMBARI-17281 > URL: https://issues.apache.org/jira/browse/AMBARI-17281 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: ambari-2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17281.patch > > > Implement UI changes to support topN querying in Grafana for templatized > dashboards that support per-host level templating. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17270) Show better error message when remote cluster attached to view is deleted
[
https://issues.apache.org/jira/browse/AMBARI-17270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334468#comment-15334468
]
Hadoop QA commented on AMBARI-17270:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811060/AMBARI-17270_branch-2.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-admin ambari-server contrib/views/hive contrib/views/hive-next:
org.apache.ambari.server.state.ServiceComponentTest
The test build failed in
contrib/views/hive-next contrib/views/hive
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7379//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7379//console
This message is automatically generated.
> Show better error message when remote cluster attached to view is deleted
> -
>
> Key: AMBARI-17270
> URL: https://issues.apache.org/jira/browse/AMBARI-17270
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17270_branch-2.4.patch, Screen Shot 2016-06-13 at
> 12.31.02 AM.png
>
>
> After deleting remote cluster, view shows null pointer exception for service
> checks:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17281) [Grafana] topN implementation for templatized dashboards
Prajwal Rao created AMBARI-17281: Summary: [Grafana] topN implementation for templatized dashboards Key: AMBARI-17281 URL: https://issues.apache.org/jira/browse/AMBARI-17281 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: ambari-2.4.0 Reporter: Prajwal Rao Assignee: Prajwal Rao Priority: Critical Fix For: ambari-2.4.0 Implement UI changes to support topN querying in Grafana for templatized dashboards that support per-host level templating. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17265) [Grafana] HBase Tables metric query fix
[ https://issues.apache.org/jira/browse/AMBARI-17265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-17265: - Status: Patch Available (was: Open) > [Grafana] HBase Tables metric query fix > --- > > Key: AMBARI-17265 > URL: https://issues.apache.org/jira/browse/AMBARI-17265 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: ambari-2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17265.patch > > > HBase Tables metric query needs to add the metric aggregator and metric > transform to each metric. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17265) [Grafana] HBase Tables metric query fix
[ https://issues.apache.org/jira/browse/AMBARI-17265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-17265: - Attachment: AMBARI-17265.patch > [Grafana] HBase Tables metric query fix > --- > > Key: AMBARI-17265 > URL: https://issues.apache.org/jira/browse/AMBARI-17265 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: ambari-2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17265.patch > > > HBase Tables metric query needs to add the metric aggregator and metric > transform to each metric. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17262) Atlas Integration : Remove {{atlas_conf_dir}} from HADOOP_CLASSPATH in hive-env.
[
https://issues.apache.org/jira/browse/AMBARI-17262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-17262:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Atlas Integration : Remove {{atlas_conf_dir}} from HADOOP_CLASSPATH in
> hive-env.
>
>
> Key: AMBARI-17262
> URL: https://issues.apache.org/jira/browse/AMBARI-17262
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> In Hive configuration ‘Advanced hive-env’ :
> {code}
> export
> HADOOP_CLASSPATH={{atlas_conf_dir}}:{{atlas_home_dir}}/hook/hive:${HADOOP_CLASSPATH}
> {code}
> remove
> {code}
> {{atlas_conf_dir}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17273) With Atlas HA enabled, atlas instance fails to come up with "Unable to find IDs matching any local host and port binding among id1"
[
https://issues.apache.org/jira/browse/AMBARI-17273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-17273:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> With Atlas HA enabled, atlas instance fails to come up with "Unable to find
> IDs matching any local host and port binding among id1"
> ---
>
> Key: AMBARI-17273
> URL: https://issues.apache.org/jira/browse/AMBARI-17273
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> Atlas fails to come up with below error. This is because if ID information
> for all atlas instances is not generated and updated in
> atlas-application.properties.
> {noformat}
> 2016-06-14 10:48:23,249 WARN - [main:] ~ Failed startup of context
> o.e.j.w.WebAppContext@2ad31d76{/,file:/grid/0/hdp/2.5.0.0-723/atlas/server/webapp/atlas/,STARTING}{/usr/hdp/current/atlas-server/server/webapp/atlas}
> (WebAppContext:514)
> java.lang.RuntimeException: org.apache.atlas.AtlasException: Could not find
> server id for this instance. Unable to find IDs matching any local host and
> port binding among id1
> at org.apache.atlas.service.Services.start(Services.java:48)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.startServices(GuiceServletConfig.java:142)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:136)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
> at org.apache.atlas.Atlas.main(Atlas.java:113)
> Caused by: org.apache.atlas.AtlasException: Could not find server id for this
> instance. Unable to find IDs matching any local host and port binding among
> id1
> at
> org.apache.atlas.ha.AtlasServerIdSelector.selectServerId(AtlasServerIdSelector.java:77)
> at
> org.apache.atlas.web.service.ActiveInstanceElectorService.start(ActiveInstanceElectorService.java:105)
> at org.apache.atlas.service.Services.start(Services.java:45)
> ... 19 more
> 2016-06-14 10:48:23,284 INFO - [main:] ~ Started
> ServerConnector@255af999{HTTP/1.1}{0.0.0.0:21000} (ServerConnector:266)
> {noformat}
> Atlas-application.properties not updated with all other instance information
> leading to atlas startup failure
> {noformat}
> [root@ayubTesting-3 ~]# cat /etc/atlas/conf/atlas-application.properties
> # Generated by Apache Ambari. Tue Jun 14 10:47:47 2016
> atlas.audit.hbase.tablename=ATLAS_ENTITY_AUDIT_EVENTS
> atlas.audit.hbase.zookeeper.quorum=ayubtesting-2.openstacklocal,ayubtesting-3.openstacklocal
> atlas.audit.zookeeper.session.timeout.ms=1000
> atlas.auth.policy.file=/etc/atlas/conf/policy-store.txt
> atlas.authentication.keytab=/etc/security/keytabs/atlas.service.keytab
> atlas.authentication.method=simple
> atlas.authentication.method.file=true
> atlas.authentication.method.file.filename=/etc/atlas/conf/users-credentials.properties
> atlas.authentication.method.kerberos=false
> atlas.authentication.method.ldap=false
> atlas.authentication.method.ldap.type=ldap
> atlas.authentication.method.ldap.url=
> atlas.authentication.principal=atlas
> atlas.authorizer.impl=simple
> atlas.cluster.name=cl1
> atlas.enableTLS=false
>
[jira] [Commented] (AMBARI-17209) Ambari should add default Spark configuration property
[
https://issues.apache.org/jira/browse/AMBARI-17209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334315#comment-15334315
]
Alejandro Fernandez commented on AMBARI-17209:
--
Please change the following in the code review,
Remove
{code}{code}
Set,
{code}{code}
> Ambari should add default Spark configuration property
> --
>
> Key: AMBARI-17209
> URL: https://issues.apache.org/jira/browse/AMBARI-17209
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Attachments: AMBARI-17209.patch
>
>
> We need to add the following to oozie-site.xml
> {code}
> oozie.service.SparkConfigurationService.spark.configurations
> "*=/etc/spark/conf
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-12885: Attachment: AMBARI-12885.patch > Dynamic stack extensions - install and upgrade support for custom services > -- > > Key: AMBARI-12885 > URL: https://issues.apache.org/jira/browse/AMBARI-12885 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server, ambari-web >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-12885 Example.pdf, AMBARI-12885.patch, Dynamic > Stack Extensions - High Level Design v5.pdf > > > The purpose of this proposal is to facilitate adding custom services to an > existing stack. Ideally this would support adding and upgrading custom > services separately from the core services defined in the stack. In > particular we are looking at custom services that need to support several > different stacks (different distributions of Ambari). The release cycle of > the custom services may be different from that of the core stack; that is, a > custom service may be upgraded at a different rate than the core distribution > itself and may be upgraded multiple times within the lifespan of a single > release of the core distribution. > One possible approach to handling this would be dynamically extending a stack > (after install time). It would be best to extend the stack in packages where > a stack extension package can have one or more custom services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-12885: Status: Patch Available (was: Open) > Dynamic stack extensions - install and upgrade support for custom services > -- > > Key: AMBARI-12885 > URL: https://issues.apache.org/jira/browse/AMBARI-12885 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server, ambari-web >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-12885 Example.pdf, AMBARI-12885.patch, Dynamic > Stack Extensions - High Level Design v5.pdf > > > The purpose of this proposal is to facilitate adding custom services to an > existing stack. Ideally this would support adding and upgrading custom > services separately from the core services defined in the stack. In > particular we are looking at custom services that need to support several > different stacks (different distributions of Ambari). The release cycle of > the custom services may be different from that of the core stack; that is, a > custom service may be upgraded at a different rate than the core distribution > itself and may be upgraded multiple times within the lifespan of a single > release of the core distribution. > One possible approach to handling this would be dynamically extending a stack > (after install time). It would be best to extend the stack in packages where > a stack extension package can have one or more custom services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-12885: Status: Open (was: Patch Available) > Dynamic stack extensions - install and upgrade support for custom services > -- > > Key: AMBARI-12885 > URL: https://issues.apache.org/jira/browse/AMBARI-12885 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server, ambari-web >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-12885 Example.pdf, Dynamic Stack Extensions - > High Level Design v5.pdf > > > The purpose of this proposal is to facilitate adding custom services to an > existing stack. Ideally this would support adding and upgrading custom > services separately from the core services defined in the stack. In > particular we are looking at custom services that need to support several > different stacks (different distributions of Ambari). The release cycle of > the custom services may be different from that of the core stack; that is, a > custom service may be upgraded at a different rate than the core distribution > itself and may be upgraded multiple times within the lifespan of a single > release of the core distribution. > One possible approach to handling this would be dynamically extending a stack > (after install time). It would be best to extend the stack in packages where > a stack extension package can have one or more custom services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-12885: Attachment: (was: AMBARI-12885.patch) > Dynamic stack extensions - install and upgrade support for custom services > -- > > Key: AMBARI-12885 > URL: https://issues.apache.org/jira/browse/AMBARI-12885 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server, ambari-web >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-12885 Example.pdf, Dynamic Stack Extensions - > High Level Design v5.pdf > > > The purpose of this proposal is to facilitate adding custom services to an > existing stack. Ideally this would support adding and upgrading custom > services separately from the core services defined in the stack. In > particular we are looking at custom services that need to support several > different stacks (different distributions of Ambari). The release cycle of > the custom services may be different from that of the core stack; that is, a > custom service may be upgraded at a different rate than the core distribution > itself and may be upgraded multiple times within the lifespan of a single > release of the core distribution. > One possible approach to handling this would be dynamically extending a stack > (after install time). It would be best to extend the stack in packages where > a stack extension package can have one or more custom services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17129) Set necessary HBase configuration to enable SPNEGO authentication if desired
[ https://issues.apache.org/jira/browse/AMBARI-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334257#comment-15334257 ] Robert Levas commented on AMBARI-17129: --- [~elserj] thanks... running unit tests now. > Set necessary HBase configuration to enable SPNEGO authentication if desired > > > Key: AMBARI-17129 > URL: https://issues.apache.org/jira/browse/AMBARI-17129 > Project: Ambari > Issue Type: Improvement >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-17129.001.patch, AMBARI-17129.002.patch, > AMBARI-17129.003.patch > > > Over in HBASE-5291, I implemented support to enable SPNEGO authentication of > the HBase web UIs. > We should update the HBase configuration when Kerberos is enabled such that, > if the user chooses to enable the SPNEGO auth, the principal and keytab > information is already present in the configuration. If the SPNEGO auth is > not enabled, then these properties won't affect anything if they are set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs
[ https://issues.apache.org/jira/browse/AMBARI-17280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17280: - Attachment: AMBARI-17280.trunk.patch AMBARI-17280.branch-2.4.patch > RU to write out client configs that are dependencies of Hive, ATS, and Oozie > during upgrades that change configs > > > Key: AMBARI-17280 > URL: https://issues.apache.org/jira/browse/AMBARI-17280 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0 >Reporter: Ana Gillan >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17280.branch-2.4.patch, AMBARI-17280.trunk.patch > > > During RU, HiveServer2 is restarted but the newer tez configs have not yet > been saved, which is incorrect because Hive has a dependency on Tez. > This is important when configs change during a major stack upgrade, e.g., HDP > 2.4 -> 2.5. What happens today is, > * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from > /etc/tez/2.4.0.0-1/0/ to the new folder > * If configs change during RU, then Hive is restarted and the classpath means > that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 > folder > This problem exists for all of these components: > HiveServer: depends on Tez and MapReduce clients > ATS: depends on Tez and Spark clients > Oozie: depends on Tez, Spark, and MapReduce clients > This problem only exists when configs change (so crossing major stack > version) and during RU (because it is allowed to change configs during the > middle of restarting services). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs
[ https://issues.apache.org/jira/browse/AMBARI-17280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17280: - Status: Patch Available (was: Open) > RU to write out client configs that are dependencies of Hive, ATS, and Oozie > during upgrades that change configs > > > Key: AMBARI-17280 > URL: https://issues.apache.org/jira/browse/AMBARI-17280 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0 >Reporter: Ana Gillan >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17280.branch-2.4.patch, AMBARI-17280.trunk.patch > > > During RU, HiveServer2 is restarted but the newer tez configs have not yet > been saved, which is incorrect because Hive has a dependency on Tez. > This is important when configs change during a major stack upgrade, e.g., HDP > 2.4 -> 2.5. What happens today is, > * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from > /etc/tez/2.4.0.0-1/0/ to the new folder > * If configs change during RU, then Hive is restarted and the classpath means > that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 > folder > This problem exists for all of these components: > HiveServer: depends on Tez and MapReduce clients > ATS: depends on Tez and Spark clients > Oozie: depends on Tez, Spark, and MapReduce clients > This problem only exists when configs change (so crossing major stack > version) and during RU (because it is allowed to change configs during the > middle of restarting services). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs
[ https://issues.apache.org/jira/browse/AMBARI-17280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17280: - Reporter: Hitesh Shah (was: Alejandro Fernandez) > RU to write out client configs that are dependencies of Hive, ATS, and Oozie > during upgrades that change configs > > > Key: AMBARI-17280 > URL: https://issues.apache.org/jira/browse/AMBARI-17280 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0 >Reporter: Hitesh Shah >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: 2.4.0 > > > During RU, HiveServer2 is restarted but the newer tez configs have not yet > been saved, which is incorrect because Hive has a dependency on Tez. > This is important when configs change during a major stack upgrade, e.g., HDP > 2.4 -> 2.5. What happens today is, > * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from > /etc/tez/2.4.0.0-1/0/ to the new folder > * If configs change during RU, then Hive is restarted and the classpath means > that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 > folder > This problem exists for all of these components: > HiveServer: depends on Tez and MapReduce clients > ATS: depends on Tez and Spark clients > Oozie: depends on Tez, Spark, and MapReduce clients > This problem only exists when configs change (so crossing major stack > version) and during RU (because it is allowed to change configs during the > middle of restarting services). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs
[ https://issues.apache.org/jira/browse/AMBARI-17280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17280: - Reporter: Ana Gillan (was: Hitesh Shah) > RU to write out client configs that are dependencies of Hive, ATS, and Oozie > during upgrades that change configs > > > Key: AMBARI-17280 > URL: https://issues.apache.org/jira/browse/AMBARI-17280 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0 >Reporter: Ana Gillan >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: 2.4.0 > > > During RU, HiveServer2 is restarted but the newer tez configs have not yet > been saved, which is incorrect because Hive has a dependency on Tez. > This is important when configs change during a major stack upgrade, e.g., HDP > 2.4 -> 2.5. What happens today is, > * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from > /etc/tez/2.4.0.0-1/0/ to the new folder > * If configs change during RU, then Hive is restarted and the classpath means > that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 > folder > This problem exists for all of these components: > HiveServer: depends on Tez and MapReduce clients > ATS: depends on Tez and Spark clients > Oozie: depends on Tez, Spark, and MapReduce clients > This problem only exists when configs change (so crossing major stack > version) and during RU (because it is allowed to change configs during the > middle of restarting services). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
