[jira] [Commented] (AMBARI-19733) Regression in Spark2 keytab and {{stack_root}} for Livy2
[
https://issues.apache.org/jira/browse/AMBARI-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848098#comment-15848098
]
Hadoop QA commented on AMBARI-19733:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850348/AMBARI-19733.2.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/10358//console
This message is automatically generated.
> Regression in Spark2 keytab and {{stack_root}} for Livy2
>
>
> Key: AMBARI-19733
> URL: https://issues.apache.org/jira/browse/AMBARI-19733
> Project: Ambari
> Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19733.1.patch, AMBARI-19733.2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848097#comment-15848097
]
Hadoop QA commented on AMBARI-19810:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850347/AMBARI-19810.01.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/10357//console
This message is automatically generated.
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19780) Hive View : Logs are not complete for hive view
[ https://issues.apache.org/jira/browse/AMBARI-19780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19780: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Hive View : Logs are not complete for hive view > --- > > Key: AMBARI-19780 > URL: https://issues.apache.org/jira/browse/AMBARI-19780 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Attachments: AMBARI-19780-branch-2.5.patch, Screen Shot 2017-01-17 at > 5.20.44 PM.png, Screen Shot 2017-01-17 at 6.03.23 PM.png > > > Hive view does not show the full query logs. It overwrites the starting logs > when more logs come. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19782) Hive2: Results are not cleared on "execute"
[ https://issues.apache.org/jira/browse/AMBARI-19782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19782: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > Hive2: Results are not cleared on "execute" > --- > > Key: AMBARI-19782 > URL: https://issues.apache.org/jira/browse/AMBARI-19782 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19782_trunk.patch > > > A query might run for a long time. In the meantime the results from the > previous query are still displayed which is confusing. This should be cleared > when you submit the new query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19765) Hive2: LOGS tab is more prominently displayed than RESULTS
[ https://issues.apache.org/jira/browse/AMBARI-19765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19765: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > Hive2: LOGS tab is more prominently displayed than RESULTS > -- > > Key: AMBARI-19765 > URL: https://issues.apache.org/jira/browse/AMBARI-19765 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-19765_trunk.patch > > > Makes it look like we know your query is going to fail before results will be > relevant. The logs button should be somewhere else. > Move the results tab to the left hand side and have that tab open by default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19523) Hive View 2.0: Table manager - DDL tab should show query as readonly in query editor
[ https://issues.apache.org/jira/browse/AMBARI-19523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19523: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > Hive View 2.0: Table manager - DDL tab should show query as readonly in query > editor > > > Key: AMBARI-19523 > URL: https://issues.apache.org/jira/browse/AMBARI-19523 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-19523_trunk.patch > > > Table manager - DDL tab should show query as readonly in query editor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19753) Hive2 View - Switching tabs after executing query loses state
[ https://issues.apache.org/jira/browse/AMBARI-19753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19753: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > Hive2 View - Switching tabs after executing query loses state > - > > Key: AMBARI-19753 > URL: https://issues.apache.org/jira/browse/AMBARI-19753 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-19753_trunk.patch > > > After executing queries from Hive2 view, the loading status is shown. Now if > we switch tabs and return back to "Query" tab the state is lost and there is > not idea if the query is submitted, running or failed etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group
[ https://issues.apache.org/jira/browse/AMBARI-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-19813: --- Priority: Minor (was: Major) > findLatestServiceConfigsByStack query returns deleted config group > -- > > Key: AMBARI-19813 > URL: https://issues.apache.org/jira/browse/AMBARI-19813 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Amruta Borkar >Assignee: Amruta Borkar >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-158442.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group
[ https://issues.apache.org/jira/browse/AMBARI-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-19813: --- Priority: Major (was: Minor) > findLatestServiceConfigsByStack query returns deleted config group > -- > > Key: AMBARI-19813 > URL: https://issues.apache.org/jira/browse/AMBARI-19813 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-158442.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group
[ https://issues.apache.org/jira/browse/AMBARI-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-19813: --- Status: Patch Available (was: In Progress) > findLatestServiceConfigsByStack query returns deleted config group > -- > > Key: AMBARI-19813 > URL: https://issues.apache.org/jira/browse/AMBARI-19813 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-158442.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group
[ https://issues.apache.org/jira/browse/AMBARI-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-19813: --- Attachment: AMBARI-158442.patch > findLatestServiceConfigsByStack query returns deleted config group > -- > > Key: AMBARI-19813 > URL: https://issues.apache.org/jira/browse/AMBARI-19813 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-158442.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group
[ https://issues.apache.org/jira/browse/AMBARI-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-19813: --- Fix Version/s: trunk > findLatestServiceConfigsByStack query returns deleted config group > -- > > Key: AMBARI-19813 > URL: https://issues.apache.org/jira/browse/AMBARI-19813 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-158442.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group
Amruta Borkar created AMBARI-19813: -- Summary: findLatestServiceConfigsByStack query returns deleted config group Key: AMBARI-19813 URL: https://issues.apache.org/jira/browse/AMBARI-19813 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Amruta Borkar Assignee: Amruta Borkar -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[
https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847876#comment-15847876
]
Hadoop QA commented on AMBARI-19805:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850318/AMBARI-19805.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/10355//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10355//console
This message is automatically generated.
> Add outputFormat attribute to all PXF Hive-related profiles
> ---
>
> Key: AMBARI-19805
> URL: https://issues.apache.org/jira/browse/AMBARI-19805
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19805.patch
>
>
> There was new attribute outputFormat introduced in
> https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected
> in PXF as a common service.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19812) Ambari-agent fails to build on Windows: '2.4.2.0.0' is not a valid version string
Jeff Saremi created AMBARI-19812: Summary: Ambari-agent fails to build on Windows: '2.4.2.0.0' is not a valid version string Key: AMBARI-19812 URL: https://issues.apache.org/jira/browse/AMBARI-19812 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.4.2 Environment: Windows10 Reporter: Jeff Saremi Command line: D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-agent>mvn -B clean install package -DnewVersion=2.4.2 -DskipTests -Dpython.ver="python >= 2.6" -Drat.skip -P windows Error: [DEBUG] (f) basedir = D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-agent [DEBUG] (f) classpathScope = runtime [DEBUG] (f) executable = choco.exe [DEBUG] (f) longClasspath = false [DEBUG] (f) project = MavenProject: org.apache.ambari:ambari-agent:2.4.2.0.0 @ D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-agent\pom.xml [DEBUG] (f) session = org.apache.maven.execution.MavenSession@7965a51c [DEBUG] (f) skip = false [DEBUG] (f) workingDirectory = D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-agent\target\ambari-agent-2.4.2.0.0-choco [DEBUG] -- end configuration -- [DEBUG] Executing command line: choco.exe pack --version=2.4.2.0.0 D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-agent/target/ambari-agent-2.4.2.0.0-choco/ambari-agent.nuspec Chocolatey v0.10.3 '2.4.2.0.0' is not a valid version string. Parameter name: version [INFO] [INFO] BUILD FAILURE [INFO] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19806) After setting up hadoop credential, cannot start Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-19806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847852#comment-15847852
]
Hadoop QA commented on AMBARI-19806:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850338/rb56142.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/10354//console
This message is automatically generated.
> After setting up hadoop credential, cannot start Hive Metastore
> ---
>
> Key: AMBARI-19806
> URL: https://issues.apache.org/jira/browse/AMBARI-19806
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: rb56142.patch
>
>
> In HIVE, after javax.jdo.option.ConnectionPassword property and value is
> moved into a JCEKS file using hadoop credential store, hive-site.xml looks
> like this:
> {quote}
> hadoop.security.credential.provider.path
> jceks://file/usr/lib/hive/conf/hive.jceks
> {quote}
> instead of:
> {quote}
> javax.jdo.option.ConnectionPassword
> MyHiveConnectionPassword
> {quote}
> However, after the above change, HIVE fails to start. This is an Ambari
> deployed cluster.
> {quote}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 259, in
> HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 59, in start
> 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 326, in hive
> create_schema_cmd = format("export HIVE_CONF_DIR={hive_server_conf_dir} ;
> "
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 62, in format
> result_unprotected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.6/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.6/string.py", line 575, in _vformat
> obj = self.convert_field(obj, conversion)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 70, in convert_field_unprotected
> return self._convert_field(value, conversion, False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 85, in _convert_field
> return utils.PASSWORDS_HIDE_STRING if is_protected else
> self._convert_field(value, 'e', is_protected)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 81, in _convert_field
> return quote_bash_args(unicode(value))
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'javax.jdo.option.ConnectionPassword' was not found in configurations
> dictionary!{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19811) Ambari-server build fails on Windows: ambari-server-2.4.2.0.0-dist.tar.gz does not exist
Jeff Saremi created AMBARI-19811: Summary: Ambari-server build fails on Windows: ambari-server-2.4.2.0.0-dist.tar.gz does not exist Key: AMBARI-19811 URL: https://issues.apache.org/jira/browse/AMBARI-19811 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.2 Environment: Windows 10 Reporter: Jeff Saremi Command line: mvn -B install package -DnewVersion=2.4.2.0.0 -DskipTests -Dpython.ver="python >= 2.6" -Drat.skip -P windows It looks like the folder apache-ambari-2.4.2-src\ambari-server\target contains an ambari-server-2.4.2.0.0-dist.zip (which is the correct extension) however not a tar.gz. Somehow the Unix target paths are mixed in Windows settings Error: [DEBUG] Executing the copy-rename-maven-plugin [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 03:19 min [INFO] Finished at: 2017-01-31T16:19:15-08:00 [INFO] Final Memory: 78M/1247M [INFO] [ERROR] Failed to execute goal com.coderplus.maven.plugins:copy-rename-maven-plugin:1.0.1:rename (rename-file) on project ambari-server: sourceFile D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-server\target\repo\ambari-server-2.4.2.0.0-dist.tar.gz does not exist -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.coderplus.maven.plugins:copy-rename-maven-plugin:1.0.1:rename (rename-file) on project ambari-server: sourceFile D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-server\target\repo\ambari-server-2.4.2.0.0-dist.tar.gz does not exist at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19809) HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates conflicts since should not belong to MAPREDUCE2
[
https://issues.apache.org/jira/browse/AMBARI-19809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847831#comment-15847831
]
Hadoop QA commented on AMBARI-19809:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850344/AMBARI-19809.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/10353//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10353//console
This message is automatically generated.
> HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates
> conflicts since should not belong to MAPREDUCE2
>
>
> Key: AMBARI-19809
> URL: https://issues.apache.org/jira/browse/AMBARI-19809
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19809.patch
>
>
> STR:
> * Install Ambari trunk
> * Install HDP 3.0, e.g., centos6:
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/3.x/BUILDS/3.0.0.0-30
> * Select ZK, HDFS, YARN
> * During deployment, will see the following error in the ambari-server log
> {noformat}
> 26 Jan 2017 20:01:48,119 ERROR [ambari-client-thread-26] ClusterImpl:2662 -
> Updating configs for multiple services by a single API request isn't
> supported. Conflicting services YARN and MAPREDUCE2 for yarn-site, config
> version not created for YARN
> {noformat}
> This is because yarn-site is marked right now as belonging to both YARN and
> MAPREDUCE2, which is incorrect since it should not belong to MAPREDUCE2.
> The fix update the HDP 3.0 service definition for MAPREDUCE2 to use the
> correct configuration directory.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Status: Patch Available (was: Open)
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Fix Version/s: trunk
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Status: Open (was: Patch Available)
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19810.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19733) Regression in Spark2 keytab and {{stack_root}} for Livy2
[
https://issues.apache.org/jira/browse/AMBARI-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bikas Saha updated AMBARI-19733:
Attachment: AMBARI-19733.2.patch
> Regression in Spark2 keytab and {{stack_root}} for Livy2
>
>
> Key: AMBARI-19733
> URL: https://issues.apache.org/jira/browse/AMBARI-19733
> Project: Ambari
> Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19733.1.patch, AMBARI-19733.2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Attachment: AMBARI-19810.01.patch
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19810.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19733) Regression in Spark2 keytab and {{stack_root}} for Livy2
[
https://issues.apache.org/jira/browse/AMBARI-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bikas Saha updated AMBARI-19733:
Attachment: (was: AMBARI-19733.2.patch)
> Regression in Spark2 keytab and {{stack_root}} for Livy2
>
>
> Key: AMBARI-19733
> URL: https://issues.apache.org/jira/browse/AMBARI-19733
> Project: Ambari
> Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19733.1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Status: Patch Available (was: Open)
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19810.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Summary: Remove upgrade logic in UpdateCatalog250 for
tez-interactive-site's 'tez.runtime.io.sort.mb' and
'tez.runtime.unordered.output.buffer.size-mb' (was: Remove upgrade logic in
UpdateCatalog250 for tez-interactive-site io.sort.mb, buffer.size)
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'
> --
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Summary: Remove upgrade logic in UpdateCatalog250 for
tez-interactive-site's 'tez.runtime.io.sort.mb' and
'tez.runtime.unordered.output.buffer.size-mb'. (was: Remove upgrade logic in
UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and
'tez.runtime.unordered.output.buffer.size-mb')
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site io.sort.mb, buffer.size
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Description:
Remove the following code and its references:
{code}
+ protected void updateTEZInteractiveConfigs() throws AmbariException {
+AmbariManagementController ambariManagementController =
injector.getInstance(AmbariManagementController.class);
+Clusters clusters = ambariManagementController.getClusters();
+if (clusters != null) {
+ Map clusterMap = clusters.getClusters();
+
+ if (clusterMap != null && !clusterMap.isEmpty()) {
+for (final Cluster cluster : clusterMap.values()) {
+ Config tezInteractiveSite =
cluster.getDesiredConfigByType("tez-interactive-site");
+ if (tezInteractiveSite != null) {
+
+updateConfigurationProperties("tez-interactive-site",
Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
+
+updateConfigurationProperties("tez-interactive-site",
Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
+"100"), true, true);
+ }
+}
+ }
+}
+ }
{code}
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site io.sort.mb,
> buffer.size
> -
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19755) Perf: start/stop all actions works much slower after few days of testing
[ https://issues.apache.org/jira/browse/AMBARI-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847788#comment-15847788 ] Hudson commented on AMBARI-19755: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #860 (See [https://builds.apache.org/job/Ambari-branch-2.5/860/]) AMBARI-19755. Test Fix. Perf: start/stop all actions works much slower (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8ef727841c94fdc4a1e5b4a75e32f01fa9141527]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java > Perf: start/stop all actions works much slower after few days of testing > > > Key: AMBARI-19755 > URL: https://issues.apache.org/jira/browse/AMBARI-19755 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19755.patch > > > Fix performance for long running cluster. Because start/stop all commands > generation takes too much time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19733) Regression in Spark2 keytab and {{stack_root}} for Livy2
[
https://issues.apache.org/jira/browse/AMBARI-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bikas Saha updated AMBARI-19733:
Attachment: AMBARI-19733.2.patch
> Regression in Spark2 keytab and {{stack_root}} for Livy2
>
>
> Key: AMBARI-19733
> URL: https://issues.apache.org/jira/browse/AMBARI-19733
> Project: Ambari
> Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19733.1.patch, AMBARI-19733.2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[ https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847785#comment-15847785 ] Alejandro Fernandez commented on AMBARI-19805: -- +1 for [^AMBARI-19805.patch] > Add outputFormat attribute to all PXF Hive-related profiles > --- > > Key: AMBARI-19805 > URL: https://issues.apache.org/jira/browse/AMBARI-19805 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Oleksandr Diachenko >Assignee: Oleksandr Diachenko >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19805.patch > > > There was new attribute outputFormat introduced in > https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected > in PXF as a common service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[ https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847785#comment-15847785 ] Alejandro Fernandez edited comment on AMBARI-19805 at 2/1/17 12:36 AM: --- +1 for [^AMBARI-19805.patch] cc [~odiachenko] was (Author: afernandez): +1 for [^AMBARI-19805.patch] > Add outputFormat attribute to all PXF Hive-related profiles > --- > > Key: AMBARI-19805 > URL: https://issues.apache.org/jira/browse/AMBARI-19805 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Oleksandr Diachenko >Assignee: Oleksandr Diachenko >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19805.patch > > > There was new attribute outputFormat introduced in > https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected > in PXF as a common service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site io.sort.mb, buffer.size
[ https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19810: - Fix Version/s: 2.5.0 > Remove upgrade logic in UpdateCatalog250 for tez-interactive-site io.sort.mb, > buffer.size > - > > Key: AMBARI-19810 > URL: https://issues.apache.org/jira/browse/AMBARI-19810 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site io.sort.mb, buffer.size
[ https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19810: - Affects Version/s: 2.5.0 > Remove upgrade logic in UpdateCatalog250 for tez-interactive-site io.sort.mb, > buffer.size > - > > Key: AMBARI-19810 > URL: https://issues.apache.org/jira/browse/AMBARI-19810 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site io.sort.mb, buffer.size
Swapan Shridhar created AMBARI-19810: Summary: Remove upgrade logic in UpdateCatalog250 for tez-interactive-site io.sort.mb, buffer.size Key: AMBARI-19810 URL: https://issues.apache.org/jira/browse/AMBARI-19810 Project: Ambari Issue Type: Bug Reporter: Swapan Shridhar Assignee: Swapan Shridhar -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19755) Perf: start/stop all actions works much slower after few days of testing
[ https://issues.apache.org/jira/browse/AMBARI-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847773#comment-15847773 ] Hudson commented on AMBARI-19755: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6610 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6610/]) AMBARI-19755. Test Fix. Perf: start/stop all actions works much slower (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=01f4a69e2ecc266d839713a53e428350cddcbc69]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java > Perf: start/stop all actions works much slower after few days of testing > > > Key: AMBARI-19755 > URL: https://issues.apache.org/jira/browse/AMBARI-19755 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19755.patch > > > Fix performance for long running cluster. Because start/stop all commands > generation takes too much time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19763) Workflow Manager View : Separate log file into its own directory similar to other views
[ https://issues.apache.org/jira/browse/AMBARI-19763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847772#comment-15847772 ] Hudson commented on AMBARI-19763: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6610 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6610/]) AMBARI-19763: Workflow Manager View : Separate log file into its own (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cc42c95db84ecb115393a0dec5390245f377d7d6]) * (add) contrib/views/wfmanager/src/main/resources/view.log4j.properties * (edit) contrib/views/wfmanager/pom.xml > Workflow Manager View : Separate log file into its own directory similar to > other views > --- > > Key: AMBARI-19763 > URL: https://issues.apache.org/jira/browse/AMBARI-19763 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19763.patch > > > Workflow manager view logs entries are currently in the ambari-server.log. > It should be separated into its own folder under /var/log/ambari-server > similar to the other views. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19809) HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates conflicts since should not belong to MAPREDUCE2
[
https://issues.apache.org/jira/browse/AMBARI-19809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19809:
-
Description:
STR:
* Install Ambari trunk
* Install HDP 3.0, e.g., centos6:
http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/3.x/BUILDS/3.0.0.0-30
* Select ZK, HDFS, YARN
* During deployment, will see the following error in the ambari-server log
{noformat}
26 Jan 2017 20:01:48,119 ERROR [ambari-client-thread-26] ClusterImpl:2662 -
Updating configs for multiple services by a single API request isn't supported.
Conflicting services YARN and MAPREDUCE2 for yarn-site, config version not
created for YARN
{noformat}
This is because yarn-site is marked right now as belonging to both YARN and
MAPREDUCE2, which is incorrect since it should not belong to MAPREDUCE2.
The fix update the HDP 3.0 service definition for MAPREDUCE2 to use the correct
configuration directory.
was:
STR:
* Install Ambari trunk
* Install HDP 3.0, e.g., centos6:
http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/3.x/BUILDS/3.0.0.0-30
* Select ZK, HDFS, YARN
* During deployment, will see the following error in the ambari-server log
{noformat}
26 Jan 2017 20:01:48,119 ERROR [ambari-client-thread-26] ClusterImpl:2662 -
Updating configs for multiple services by a single API request isn't supported.
Conflicting services YARN and MAPREDUCE2 for yarn-site, config version not
created for YARN
{noformat}
This is likely due to changes I introduced in YARN's Service Advisor by
splitting it up into YARN and MAPREDUCE classes.
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py
has YARNServiceAdvisor, MAPREDUCE2ServiceAdvisor
Ideally, we can keep those 2 classes, but let's also explore ClusterImpl.java's
applyConfigs() method.
{code}
ServiceConfigVersionResponse applyConfigs(Set configs, String user,
String serviceConfigVersionNote) {
String serviceName = null;
for (Config config : configs) {
for (Entry entry : serviceConfigTypes.entries()) {
if (StringUtils.equals(entry.getValue(), config.getType())) {
if (serviceName == null) {
serviceName = entry.getKey();
break;
} else if (!serviceName.equals(entry.getKey())) {
String error = String.format("Updating configs for multiple
services by a " +
"single API request isn't supported. Conflicting services %s
and %s for %s",
serviceName, entry.getKey(),
config.getType());
IllegalArgumentException exception = new
IllegalArgumentException(error);
LOG.error(error + ", config version not created for {}",
serviceName);
throw exception;
} else {
break;
}
}
}
}
...
{code}
This is because yarn-site is marked right now as belonging to both YARN and
MAPREDUCE2, which is incorrect since it should not belong to MAPREDUCE2.
The fix update the HDP 3.0 service definition for MAPREDUCE2 to use the correct
configuration directory.
> HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates
> conflicts since should not belong to MAPREDUCE2
>
>
> Key: AMBARI-19809
> URL: https://issues.apache.org/jira/browse/AMBARI-19809
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19809.patch
>
>
> STR:
> * Install Ambari trunk
> * Install HDP 3.0, e.g., centos6:
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/3.x/BUILDS/3.0.0.0-30
> * Select ZK, HDFS, YARN
> * During deployment, will see the following error in the ambari-server log
> {noformat}
> 26 Jan 2017 20:01:48,119 ERROR [ambari-client-thread-26] ClusterImpl:2662 -
> Updating configs for multiple services by a single API request isn't
> supported. Conflicting services YARN and MAPREDUCE2 for yarn-site, config
> version not created for YARN
> {noformat}
> This is because yarn-site is marked right now as belonging to both YARN and
> MAPREDUCE2, which is incorrect since it should not belong to MAPREDUCE2.
> The fix update the HDP 3.0 service definition for MAPREDUCE2 to use the
> correct configuration directory.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19809) HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates conflicts since should not belong to MAPREDUCE2
[
https://issues.apache.org/jira/browse/AMBARI-19809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19809:
-
Attachment: AMBARI-19809.patch
> HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates
> conflicts since should not belong to MAPREDUCE2
>
>
> Key: AMBARI-19809
> URL: https://issues.apache.org/jira/browse/AMBARI-19809
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19809.patch
>
>
> STR:
> * Install Ambari trunk
> * Install HDP 3.0, e.g., centos6:
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/3.x/BUILDS/3.0.0.0-30
> * Select ZK, HDFS, YARN
> * During deployment, will see the following error in the ambari-server log
> {noformat}
> 26 Jan 2017 20:01:48,119 ERROR [ambari-client-thread-26] ClusterImpl:2662 -
> Updating configs for multiple services by a single API request isn't
> supported. Conflicting services YARN and MAPREDUCE2 for yarn-site, config
> version not created for YARN
> {noformat}
> This is likely due to changes I introduced in YARN's Service Advisor by
> splitting it up into YARN and MAPREDUCE classes.
> ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py
> has YARNServiceAdvisor, MAPREDUCE2ServiceAdvisor
> Ideally, we can keep those 2 classes, but let's also explore
> ClusterImpl.java's applyConfigs() method.
> {code}
> ServiceConfigVersionResponse applyConfigs(Set configs, String user,
> String serviceConfigVersionNote) {
> String serviceName = null;
> for (Config config : configs) {
> for (Entry entry : serviceConfigTypes.entries()) {
> if (StringUtils.equals(entry.getValue(), config.getType())) {
> if (serviceName == null) {
> serviceName = entry.getKey();
> break;
> } else if (!serviceName.equals(entry.getKey())) {
> String error = String.format("Updating configs for multiple
> services by a " +
> "single API request isn't supported. Conflicting services %s
> and %s for %s",
> serviceName, entry.getKey(),
> config.getType());
> IllegalArgumentException exception = new
> IllegalArgumentException(error);
> LOG.error(error + ", config version not created for {}",
> serviceName);
> throw exception;
> } else {
> break;
> }
> }
> }
> }
>...
> {code}
> This is because yarn-site is marked right now as belonging to both YARN and
> MAPREDUCE2, which is incorrect since it should not belong to MAPREDUCE2.
> The fix update the HDP 3.0 service definition for MAPREDUCE2 to use the
> correct configuration directory.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19809) HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates conflicts since should not belong to MAPREDUCE2
[
https://issues.apache.org/jira/browse/AMBARI-19809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19809:
-
Status: Patch Available (was: Open)
> HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates
> conflicts since should not belong to MAPREDUCE2
>
>
> Key: AMBARI-19809
> URL: https://issues.apache.org/jira/browse/AMBARI-19809
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19809.patch
>
>
> STR:
> * Install Ambari trunk
> * Install HDP 3.0, e.g., centos6:
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/3.x/BUILDS/3.0.0.0-30
> * Select ZK, HDFS, YARN
> * During deployment, will see the following error in the ambari-server log
> {noformat}
> 26 Jan 2017 20:01:48,119 ERROR [ambari-client-thread-26] ClusterImpl:2662 -
> Updating configs for multiple services by a single API request isn't
> supported. Conflicting services YARN and MAPREDUCE2 for yarn-site, config
> version not created for YARN
> {noformat}
> This is likely due to changes I introduced in YARN's Service Advisor by
> splitting it up into YARN and MAPREDUCE classes.
> ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py
> has YARNServiceAdvisor, MAPREDUCE2ServiceAdvisor
> Ideally, we can keep those 2 classes, but let's also explore
> ClusterImpl.java's applyConfigs() method.
> {code}
> ServiceConfigVersionResponse applyConfigs(Set configs, String user,
> String serviceConfigVersionNote) {
> String serviceName = null;
> for (Config config : configs) {
> for (Entry entry : serviceConfigTypes.entries()) {
> if (StringUtils.equals(entry.getValue(), config.getType())) {
> if (serviceName == null) {
> serviceName = entry.getKey();
> break;
> } else if (!serviceName.equals(entry.getKey())) {
> String error = String.format("Updating configs for multiple
> services by a " +
> "single API request isn't supported. Conflicting services %s
> and %s for %s",
> serviceName, entry.getKey(),
> config.getType());
> IllegalArgumentException exception = new
> IllegalArgumentException(error);
> LOG.error(error + ", config version not created for {}",
> serviceName);
> throw exception;
> } else {
> break;
> }
> }
> }
> }
>...
> {code}
> This is because yarn-site is marked right now as belonging to both YARN and
> MAPREDUCE2, which is incorrect since it should not belong to MAPREDUCE2.
> The fix update the HDP 3.0 service definition for MAPREDUCE2 to use the
> correct configuration directory.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19809) HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates conflicts since should not belong to MAPREDUCE2
Alejandro Fernandez created AMBARI-19809:
Summary: HDP 3.0 TP - failed to deploy YARN configs because
yarn-site creates conflicts since should not belong to MAPREDUCE2
Key: AMBARI-19809
URL: https://issues.apache.org/jira/browse/AMBARI-19809
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Fix For: 3.0.0
STR:
* Install Ambari trunk
* Install HDP 3.0, e.g., centos6:
http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/3.x/BUILDS/3.0.0.0-30
* Select ZK, HDFS, YARN
* During deployment, will see the following error in the ambari-server log
{noformat}
26 Jan 2017 20:01:48,119 ERROR [ambari-client-thread-26] ClusterImpl:2662 -
Updating configs for multiple services by a single API request isn't supported.
Conflicting services YARN and MAPREDUCE2 for yarn-site, config version not
created for YARN
{noformat}
This is likely due to changes I introduced in YARN's Service Advisor by
splitting it up into YARN and MAPREDUCE classes.
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py
has YARNServiceAdvisor, MAPREDUCE2ServiceAdvisor
Ideally, we can keep those 2 classes, but let's also explore ClusterImpl.java's
applyConfigs() method.
{code}
ServiceConfigVersionResponse applyConfigs(Set configs, String user,
String serviceConfigVersionNote) {
String serviceName = null;
for (Config config : configs) {
for (Entry entry : serviceConfigTypes.entries()) {
if (StringUtils.equals(entry.getValue(), config.getType())) {
if (serviceName == null) {
serviceName = entry.getKey();
break;
} else if (!serviceName.equals(entry.getKey())) {
String error = String.format("Updating configs for multiple
services by a " +
"single API request isn't supported. Conflicting services %s
and %s for %s",
serviceName, entry.getKey(),
config.getType());
IllegalArgumentException exception = new
IllegalArgumentException(error);
LOG.error(error + ", config version not created for {}",
serviceName);
throw exception;
} else {
break;
}
}
}
}
...
{code}
This is because yarn-site is marked right now as belonging to both YARN and
MAPREDUCE2, which is incorrect since it should not belong to MAPREDUCE2.
The fix update the HDP 3.0 service definition for MAPREDUCE2 to use the correct
configuration directory.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19763) Workflow Manager View : Separate log file into its own directory similar to other views
[ https://issues.apache.org/jira/browse/AMBARI-19763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847755#comment-15847755 ] Hudson commented on AMBARI-19763: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #859 (See [https://builds.apache.org/job/Ambari-branch-2.5/859/]) AMBARI-19763: Workflow Manager View : Separate log file into its own (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3bb3fdff77c083c5f2dec8b76c7356c717eb2b7b]) * (add) contrib/views/wfmanager/src/main/resources/view.log4j.properties * (edit) contrib/views/wfmanager/pom.xml > Workflow Manager View : Separate log file into its own directory similar to > other views > --- > > Key: AMBARI-19763 > URL: https://issues.apache.org/jira/browse/AMBARI-19763 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19763.patch > > > Workflow manager view logs entries are currently in the ambari-server.log. > It should be separated into its own folder under /var/log/ambari-server > similar to the other views. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19808) Ambari build on Windows requires Microsoft Visual C++ Compiler for Python 2.7
Jeff Saremi created AMBARI-19808: Summary: Ambari build on Windows requires Microsoft Visual C++ Compiler for Python 2.7 Key: AMBARI-19808 URL: https://issues.apache.org/jira/browse/AMBARI-19808 Project: Ambari Issue Type: Bug Components: ambari-metrics Environment: Windows 10 Reporter: Jeff Saremi ANT task fails on build-psutils-compile.xml with no clear error message If you run ANT manually in the target folder against the build xml, you'll see that i complains about python C++. Download and installation of Microsoft Visual C++ Compiler for Python 2.7 solved the problem So i'm not sure what type of issue this is. Minimally, the pre-requisite must be added to the (non-existing) documentation for Windows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19801) Build fails for Ambari Web 2.4.2.0.0 on Windows
[ https://issues.apache.org/jira/browse/AMBARI-19801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847741#comment-15847741 ] Jeff Saremi commented on AMBARI-19801: -- I investigated this further. The error comes from error Failed at the contextify@0.1.15 install script 'node-gyp rebuild' After researching this further, I came across this article: https://github.com/nodejs/node-gyp/issues/972 Which states that the minimum version of NPM which resolved this issue is 2.15.9 and not the one recommended by the Ambari team I fixed this and got passed this problem. Of course I still have issues with other modules which I will create separate bugs for > Build fails for Ambari Web 2.4.2.0.0 on Windows > --- > > Key: AMBARI-19801 > URL: https://issues.apache.org/jira/browse/AMBARI-19801 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 > Environment: Windows 10 >Reporter: Jeff Saremi > Labels: build, newbie, windows > > build fails on ambari-web: > [INFO] Ambari Main SUCCESS [ 2.940 > s] > [INFO] Apache Ambari Project POM .. SUCCESS [ 0.044 > s] > [INFO] Ambari Web . FAILURE [ 51.552 > s] > D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-web\node_modules\karma\node_modules\socket.io\node_modules\socket.io-client\node_modules\ws>if > not defined npm_config_node_gyp (node > "C:\Users\jesaremi\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" > rebuild ) else (node "" rebuild ) > Building the projects in this solution one at a time. To enable parallel > build, please add the "/m" switch. > bufferutil.cc > ..\src\bufferutil.cc(118): warning C4506: no definition for inline function > 'v8::Persistent > v8::Persistent::New(v8::Handle)' > [D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-web\node_modules\karma\node_modules\socket.io\node_modules\socket.io-client\node_modules\ws\build\bufferutil.vcxproj] > win_delay_load_hook.c > C:\Users\jesaremi\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\src\win_delay_load_hook.c(34): > error C2373: '__pfnDliNotifyHook2': redefinition; different type modifiers > [D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-web\node_modules\karma\node_modules\socket.io\node_modules\socket.io-client\node_modules\ws\build\bufferutil.vcxproj] > C:\Program Files (x86)\Microsoft Visual Studio > 14.0\VC\include\delayimp.h(134): note: see declaration of > '__pfnDliNotifyHook2' > validation.cc > ..\src\validation.cc(146): warning C4506: no definition for inline function > 'v8::Persistent > v8::Persistent::New(v8::Handle)' > [D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-web\node_modules\karma\node_modules\socket.io\node_modules\socket.io-client\node_modules\ws\build\validation.vcxproj] > win_delay_load_hook.c > C:\Users\jesaremi\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\src\win_delay_load_hook.c(34): > error C2373: '__pfnDliNotifyHook2': redefinition; different type modifiers > [D:\Users\jesaremi\Downloads\apache-ambari-2.4.2-src\ambari-web\node_modules\karma\node_modules\socket.io\node_modules\socket.io-client\node_modules\ws\build\validation.vcxproj] > C:\Program Files (x86)\Microsoft Visual Studio > 14.0\VC\include\delayimp.h(134): note: see declaration of > '__pfnDliNotifyHook2' > My Environment: > VisualStudio 2015 - Have tried this using an x64 and an x86 command prompt. > they both fail > node --version > v0.10.44 > npm --version > 2.15.1 > brunch --version > 1.7.20 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19806) After setting up hadoop credential, cannot start Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-19806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19806:
---
Status: Patch Available (was: Open)
> After setting up hadoop credential, cannot start Hive Metastore
> ---
>
> Key: AMBARI-19806
> URL: https://issues.apache.org/jira/browse/AMBARI-19806
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: rb56142.patch
>
>
> In HIVE, after javax.jdo.option.ConnectionPassword property and value is
> moved into a JCEKS file using hadoop credential store, hive-site.xml looks
> like this:
> {quote}
> hadoop.security.credential.provider.path
> jceks://file/usr/lib/hive/conf/hive.jceks
> {quote}
> instead of:
> {quote}
> javax.jdo.option.ConnectionPassword
> MyHiveConnectionPassword
> {quote}
> However, after the above change, HIVE fails to start. This is an Ambari
> deployed cluster.
> {quote}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 259, in
> HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 59, in start
> 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 326, in hive
> create_schema_cmd = format("export HIVE_CONF_DIR={hive_server_conf_dir} ;
> "
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 62, in format
> result_unprotected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.6/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.6/string.py", line 575, in _vformat
> obj = self.convert_field(obj, conversion)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 70, in convert_field_unprotected
> return self._convert_field(value, conversion, False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 85, in _convert_field
> return utils.PASSWORDS_HIDE_STRING if is_protected else
> self._convert_field(value, 'e', is_protected)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 81, in _convert_field
> return quote_bash_args(unicode(value))
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'javax.jdo.option.ConnectionPassword' was not found in configurations
> dictionary!{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19806) After setting up hadoop credential, cannot start Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-19806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19806:
---
Attachment: rb56142.patch
> After setting up hadoop credential, cannot start Hive Metastore
> ---
>
> Key: AMBARI-19806
> URL: https://issues.apache.org/jira/browse/AMBARI-19806
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: rb56142.patch
>
>
> In HIVE, after javax.jdo.option.ConnectionPassword property and value is
> moved into a JCEKS file using hadoop credential store, hive-site.xml looks
> like this:
> {quote}
> hadoop.security.credential.provider.path
> jceks://file/usr/lib/hive/conf/hive.jceks
> {quote}
> instead of:
> {quote}
> javax.jdo.option.ConnectionPassword
> MyHiveConnectionPassword
> {quote}
> However, after the above change, HIVE fails to start. This is an Ambari
> deployed cluster.
> {quote}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 259, in
> HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 59, in start
> 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 326, in hive
> create_schema_cmd = format("export HIVE_CONF_DIR={hive_server_conf_dir} ;
> "
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 62, in format
> result_unprotected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.6/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.6/string.py", line 575, in _vformat
> obj = self.convert_field(obj, conversion)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 70, in convert_field_unprotected
> return self._convert_field(value, conversion, False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 85, in _convert_field
> return utils.PASSWORDS_HIDE_STRING if is_protected else
> self._convert_field(value, 'e', is_protected)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 81, in _convert_field
> return quote_bash_args(unicode(value))
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'javax.jdo.option.ConnectionPassword' was not found in configurations
> dictionary!{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19763) Workflow Manager View : Separate log file into its own directory similar to other views
[ https://issues.apache.org/jira/browse/AMBARI-19763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19763: Resolution: Fixed Fix Version/s: trunk Status: Resolved (was: Patch Available) Pushed to branch-2.5 as commit 3bb3fdff77c083c5f2dec8b76c7356c717eb2b7b Author: Sangeeta Ravindran Date: Tue Jan 31 15:24:04 2017 -0800 AMBARI-19763: Workflow Manager View : Separate log file into its own directory similar to other views (sangeetar) Pushed to trunk as commit cc42c95db84ecb115393a0dec5390245f377d7d6 Author: Sangeeta Ravindran Date: Tue Jan 31 15:33:07 2017 -0800 AMBARI-19763: Workflow Manager View : Separate log file into its own directory similar to other views (sangeetar) > Workflow Manager View : Separate log file into its own directory similar to > other views > --- > > Key: AMBARI-19763 > URL: https://issues.apache.org/jira/browse/AMBARI-19763 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19763.patch > > > Workflow manager view logs entries are currently in the ambari-server.log. > It should be separated into its own folder under /var/log/ambari-server > similar to the other views. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19807) Build failure for ambari-metrics-assembly (2.4.2)
Jeff Saremi created AMBARI-19807: Summary: Build failure for ambari-metrics-assembly (2.4.2) Key: AMBARI-19807 URL: https://issues.apache.org/jira/browse/AMBARI-19807 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.4.2 Environment: Windows 10 Reporter: Jeff Saremi It is not clear what this exception is due to: [INFO] Ambari Main SUCCESS [ 0.819 s] [INFO] Apache Ambari Project POM .. SUCCESS [ 0.010 s] [INFO] Ambari Web . SUCCESS [ 49.025 s] [INFO] Ambari Views ... SUCCESS [ 0.524 s] [INFO] Ambari Admin View .. SUCCESS [ 7.605 s] [INFO] ambari-metrics . SUCCESS [ 0.216 s] [INFO] Ambari Metrics Common .. SUCCESS [ 0.339 s] [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 1.391 s] [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 0.895 s] [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 0.609 s] [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 0.958 s] [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 0.743 s] [INFO] Ambari Metrics Collector ... SUCCESS [ 4.498 s] [INFO] Ambari Metrics Monitor . SUCCESS [ 0.938 s] [INFO] Ambari Metrics Grafana . SUCCESS [ 17.317 s] [INFO] Ambari Metrics Assembly FAILURE [ 52.005 s] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single (grafana) on project ambari-metrics-assembly: Execution grafana of goal org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single failed. NullPointerException -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single (grafana) on project ambari-metrics-assembly: Execution grafana of goal org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single failed. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution grafana of goal org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) ... 20 more Caused by: java.lang.NullPointerException at java.io.File.(File.java:360) at org.apache.maven.plugin.assembly.io.RelativeFileLocatorStrategy.resolve(RelativeFileLocatorStrategy.java:45) at org.apache.maven.shared.io.location.Locator.resolve(Locator.java:81) at org.apache.maven.plugin.assembly.io.DefaultAssemblyReader.addAssemblyFromDescriptor(DefaultAssemblyReader.java:309) at org.ap
[jira] [Updated] (AMBARI-19806) After setting up hadoop credential, cannot start Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-19806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19806:
---
Summary: After setting up hadoop credential, cannot start Hive Metastore
(was: After setting up hadoop credential, can't start Hive Metastore)
> After setting up hadoop credential, cannot start Hive Metastore
> ---
>
> Key: AMBARI-19806
> URL: https://issues.apache.org/jira/browse/AMBARI-19806
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
>
> In HIVE, after javax.jdo.option.ConnectionPassword property and value is
> moved into a JCEKS file using hadoop credential store, hive-site.xml looks
> like this:
> {quote}
> hadoop.security.credential.provider.path
> jceks://file/usr/lib/hive/conf/hive.jceks
> {quote}
> instead of:
> {quote}
> javax.jdo.option.ConnectionPassword
> MyHiveConnectionPassword
> {quote}
> However, after the above change, HIVE fails to start. This is an Ambari
> deployed cluster.
> {quote}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 259, in
> HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 59, in start
> 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 326, in hive
> create_schema_cmd = format("export HIVE_CONF_DIR={hive_server_conf_dir} ;
> "
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 62, in format
> result_unprotected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.6/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.6/string.py", line 575, in _vformat
> obj = self.convert_field(obj, conversion)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 70, in convert_field_unprotected
> return self._convert_field(value, conversion, False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 85, in _convert_field
> return utils.PASSWORDS_HIDE_STRING if is_protected else
> self._convert_field(value, 'e', is_protected)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 81, in _convert_field
> return quote_bash_args(unicode(value))
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'javax.jdo.option.ConnectionPassword' was not found in configurations
> dictionary!{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19806) After setting up hadoop credential, can't start Hive Metastore
Nahappan Somasundaram created AMBARI-19806:
--
Summary: After setting up hadoop credential, can't start Hive
Metastore
Key: AMBARI-19806
URL: https://issues.apache.org/jira/browse/AMBARI-19806
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
Priority: Critical
Fix For: 2.5.0
In HIVE, after javax.jdo.option.ConnectionPassword property and value is moved
into a JCEKS file using hadoop credential store, hive-site.xml looks like this:
{quote}
hadoop.security.credential.provider.path
jceks://file/usr/lib/hive/conf/hive.jceks
{quote}
instead of:
{quote}
javax.jdo.option.ConnectionPassword
MyHiveConnectionPassword
{quote}
However, after the above change, HIVE fails to start. This is an Ambari
deployed cluster.
{quote}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 259, in
HiveMetastore().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 287, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
line 59, in start
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 326, in hive
create_schema_cmd = format("export HIVE_CONF_DIR={hive_server_conf_dir} ; "
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
line 95, in format
return ConfigurationFormatter().format(format_string, args, **result)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
line 62, in format
result_unprotected = self.vformat(format_string, args, all_params)
File "/usr/lib64/python2.6/string.py", line 549, in vformat
result = self._vformat(format_string, args, kwargs, used_args, 2)
File "/usr/lib64/python2.6/string.py", line 575, in _vformat
obj = self.convert_field(obj, conversion)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
line 70, in convert_field_unprotected
return self._convert_field(value, conversion, False)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
line 85, in _convert_field
return utils.PASSWORDS_HIDE_STRING if is_protected else
self._convert_field(value, 'e', is_protected)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
line 81, in _convert_field
return quote_bash_args(unicode(value))
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found in
configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter
'javax.jdo.option.ConnectionPassword' was not found in configurations
dictionary!{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19800) Add precheck for Auto-Start being disabled
[ https://issues.apache.org/jira/browse/AMBARI-19800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-19800: --- Summary: Add precheck for Auto-Start being disabled (was: Add precheck for Auto-Start being enabled) > Add precheck for Auto-Start being disabled > -- > > Key: AMBARI-19800 > URL: https://issues.apache.org/jira/browse/AMBARI-19800 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > > A new precheck is required to make sure that auto-start is disabled before > starting an upgrade. This JIRA covers the backend requirements. The UI > changes will be linked to this one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19800) Add precheck for Auto-Start being enabled
[ https://issues.apache.org/jira/browse/AMBARI-19800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-19800: --- Summary: Add precheck for Auto-Start being enabled (was: Add precheck for auto-start enabled) > Add precheck for Auto-Start being enabled > - > > Key: AMBARI-19800 > URL: https://issues.apache.org/jira/browse/AMBARI-19800 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > > A new precheck is required to make sure that auto-start is disabled before > starting an upgrade. This JIRA covers the backend requirements. The UI > changes will be linked to this one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[ https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847631#comment-15847631 ] Oleksandr Diachenko commented on AMBARI-19805: -- [~afernandez], [~adenisso], [~lavjain] please review. > Add outputFormat attribute to all PXF Hive-related profiles > --- > > Key: AMBARI-19805 > URL: https://issues.apache.org/jira/browse/AMBARI-19805 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Oleksandr Diachenko >Assignee: Oleksandr Diachenko >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19805.patch > > > There was new attribute outputFormat introduced in > https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected > in PXF as a common service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[ https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleksandr Diachenko updated AMBARI-19805: - Status: Patch Available (was: In Progress) > Add outputFormat attribute to all PXF Hive-related profiles > --- > > Key: AMBARI-19805 > URL: https://issues.apache.org/jira/browse/AMBARI-19805 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Oleksandr Diachenko >Assignee: Oleksandr Diachenko >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19805.patch > > > There was new attribute outputFormat introduced in > https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected > in PXF as a common service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[ https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleksandr Diachenko updated AMBARI-19805: - Attachment: AMBARI-19805.patch > Add outputFormat attribute to all PXF Hive-related profiles > --- > > Key: AMBARI-19805 > URL: https://issues.apache.org/jira/browse/AMBARI-19805 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Oleksandr Diachenko >Assignee: Oleksandr Diachenko >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19805.patch > > > There was new attribute outputFormat introduced in > https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected > in PXF as a common service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19719) Update rpc port for LLAP to 0 for HDP stack
[ https://issues.apache.org/jira/browse/AMBARI-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847617#comment-15847617 ] Hudson commented on AMBARI-19719: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6609 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6609/]) AMBARI-19719. Update rpc port for LLAP to 0 for HDP stack (Siddharth (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a8b8b4155b6655ef407e2f0d623722047235fc6b]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-site.xml > Update rpc port for LLAP to 0 for HDP stack > --- > > Key: AMBARI-19719 > URL: https://issues.apache.org/jira/browse/AMBARI-19719 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19719.01.patch, AMBARI-19719.trunk.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[ https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleksandr Diachenko updated AMBARI-19805: - Description: There was new attribute outputFormat introduced in https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected in PXF as a common service. > Add outputFormat attribute to all PXF Hive-related profiles > --- > > Key: AMBARI-19805 > URL: https://issues.apache.org/jira/browse/AMBARI-19805 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Oleksandr Diachenko >Assignee: Oleksandr Diachenko >Priority: Minor > Fix For: 2.5.0 > > > There was new attribute outputFormat introduced in > https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected > in PXF as a common service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19804) Typo in preinstall_checker util script in the contrib project
[
https://issues.apache.org/jira/browse/AMBARI-19804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847589#comment-15847589
]
Hadoop QA commented on AMBARI-19804:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850312/AMBARI-19804.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/10352//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10352//console
This message is automatically generated.
> Typo in preinstall_checker util script in the contrib project
> -
>
> Key: AMBARI-19804
> URL: https://issues.apache.org/jira/browse/AMBARI-19804
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19804.patch
>
>
> Typo in preinstall_checker util script in the contrib project
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
Oleksandr Diachenko created AMBARI-19805: Summary: Add outputFormat attribute to all PXF Hive-related profiles Key: AMBARI-19805 URL: https://issues.apache.org/jira/browse/AMBARI-19805 Project: Ambari Issue Type: Improvement Components: stacks Reporter: Oleksandr Diachenko Assignee: Oleksandr Diachenko Priority: Minor Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847564#comment-15847564 ] Hudson commented on AMBARI-19687: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6608 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6608/]) AMBARI-19687. Set the logger for LLAP in hdp-2.6 stack. (sseth via (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=099e34c60540079f86d353efa134ed059a3c3d27]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch, > AMBARI-19687.03.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847552#comment-15847552 ] Hudson commented on AMBARI-19687: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #858 (See [https://builds.apache.org/job/Ambari-branch-2.5/858/]) AMBARI-19687. Set the logger for LLAP in hdp-2.6 stack. (sseth via (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7ee253841aa5ea7a96f063dce5f6e3b3ac8adeda]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch, > AMBARI-19687.03.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19804) Typo in preinstall_checker util script in the contrib project
[ https://issues.apache.org/jira/browse/AMBARI-19804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19804: --- Attachment: AMBARI-19804.patch > Typo in preinstall_checker util script in the contrib project > - > > Key: AMBARI-19804 > URL: https://issues.apache.org/jira/browse/AMBARI-19804 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-19804.patch > > > Typo in preinstall_checker util script in the contrib project -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19804) Typo in preinstall_checker util script in the contrib project
[ https://issues.apache.org/jira/browse/AMBARI-19804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19804: --- Status: Patch Available (was: Open) > Typo in preinstall_checker util script in the contrib project > - > > Key: AMBARI-19804 > URL: https://issues.apache.org/jira/browse/AMBARI-19804 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-19804.patch > > > Typo in preinstall_checker util script in the contrib project -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19804) Typo in preinstall_checker util script in the contrib project
Di Li created AMBARI-19804: -- Summary: Typo in preinstall_checker util script in the contrib project Key: AMBARI-19804 URL: https://issues.apache.org/jira/browse/AMBARI-19804 Project: Ambari Issue Type: Bug Components: contrib Affects Versions: trunk Reporter: Di Li Assignee: Di Li Priority: Minor Fix For: trunk Typo in preinstall_checker util script in the contrib project -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19803) Side Nav: Long menu should be visible if longer than window height
[ https://issues.apache.org/jira/browse/AMBARI-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19803: - Attachment: (was: AMBARI-19803.patch) > Side Nav: Long menu should be visible if longer than window height > -- > > Key: AMBARI-19803 > URL: https://issues.apache.org/jira/browse/AMBARI-19803 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19803.patch > > > If the Services menu is long (or the browser window is short) , should be > able to see all menu items. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19803) Side Nav: Long menu should be visible if longer than window height
[ https://issues.apache.org/jira/browse/AMBARI-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19803: - Attachment: AMBARI-19803.patch > Side Nav: Long menu should be visible if longer than window height > -- > > Key: AMBARI-19803 > URL: https://issues.apache.org/jira/browse/AMBARI-19803 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19803.patch > > > If the Services menu is long (or the browser window is short) , should be > able to see all menu items. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19803) Side Nav: Long menu should be visible if longer than window height
[ https://issues.apache.org/jira/browse/AMBARI-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19803: - Attachment: AMBARI-19803.patch > Side Nav: Long menu should be visible if longer than window height > -- > > Key: AMBARI-19803 > URL: https://issues.apache.org/jira/browse/AMBARI-19803 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19803.patch > > > If the Services menu is long (or the browser window is short) , should be > able to see all menu items. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19803) Side Nav: Long menu should be visible if longer than window height
[ https://issues.apache.org/jira/browse/AMBARI-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847523#comment-15847523 ] Xi Wang commented on AMBARI-19803: -- 20323 passing (26s) 153 pending > Side Nav: Long menu should be visible if longer than window height > -- > > Key: AMBARI-19803 > URL: https://issues.apache.org/jira/browse/AMBARI-19803 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19803.patch > > > If the Services menu is long (or the browser window is short) , should be > able to see all menu items. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19719) Update rpc port for LLAP to 0 for HDP stack
[ https://issues.apache.org/jira/browse/AMBARI-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19719: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Update rpc port for LLAP to 0 for HDP stack > --- > > Key: AMBARI-19719 > URL: https://issues.apache.org/jira/browse/AMBARI-19719 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19719.01.patch, AMBARI-19719.trunk.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19719) Update rpc port for LLAP to 0 for HDP stack
[ https://issues.apache.org/jira/browse/AMBARI-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19719: Attachment: AMBARI-19719.trunk.01.patch Patch for trunk > Update rpc port for LLAP to 0 for HDP stack > --- > > Key: AMBARI-19719 > URL: https://issues.apache.org/jira/browse/AMBARI-19719 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19719.01.patch, AMBARI-19719.trunk.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19785) Need to have a flag from UI to show/hide ranger plugin configs
[ https://issues.apache.org/jira/browse/AMBARI-19785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847513#comment-15847513 ] Hudson commented on AMBARI-19785: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6607 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6607/]) AMBARI-19785. Need to have a flag from UI to show/hide ranger plugin (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=97119babf76ebb413d3ed0cf3236b8c71657410b]) * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/configuration/cluster-env.xml > Need to have a flag from UI to show/hide ranger plugin configs > -- > > Key: AMBARI-19785 > URL: https://issues.apache.org/jira/browse/AMBARI-19785 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19785.patch > > > UI changes are required to show/hide ranger plugin configs under component > config tab. > If Ranger is not installed on same cluster but is setup on external cluster > then cluster-env/enable_external_ranger can be set to true to expose ranger > plugin related properties for all services > This Flag *cluster-env/enable_external_range* should show ranger plugin > config-types for all services: > * ranger--plugin-properties.xml > * ranger--audit.xml > * ranger--security.xml > * ranger--policymgr-ssl.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19803) Side Nav: Long menu should be visible if longer than window height
Xi Wang created AMBARI-19803: Summary: Side Nav: Long menu should be visible if longer than window height Key: AMBARI-19803 URL: https://issues.apache.org/jira/browse/AMBARI-19803 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Xi Wang Assignee: Xi Wang Fix For: 3.0.0 If the Services menu is long (or the browser window is short) , should be able to see all menu items. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[
https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847507#comment-15847507
]
Swapan Shridhar commented on AMBARI-19687:
--
commits
trunk
{code}
commit 099e34c60540079f86d353efa134ed059a3c3d27
Author: Swapan Shridhar
Date: Tue Jan 31 12:37:47 2017 -0800
AMBARI-19687. Set the logger for LLAP in hdp-2.6 stack. (sseth via Swapan
Shridhar)
{code}
branch-2.5:
{code}
commit 7ee253841aa5ea7a96f063dce5f6e3b3ac8adeda
Author: Swapan Shridhar
Date: Tue Jan 31 12:37:47 2017 -0800
AMBARI-19687. Set the logger for LLAP in hdp-2.6 stack. (sseth via Swapan
Shridhar)
{code}
> Set the logger for LLAP in hdp-2.6 stack
>
>
> Key: AMBARI-19687
> URL: https://issues.apache.org/jira/browse/AMBARI-19687
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch,
> AMBARI-19687.03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19687: - Resolution: Fixed Status: Resolved (was: Patch Available) > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch, > AMBARI-19687.03.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19687: - Status: Patch Available (was: Open) > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch, > AMBARI-19687.03.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[
https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847503#comment-15847503
]
Swapan Shridhar commented on AMBARI-19687:
--
Added default value of "query-routing" for config "hive.llap.daemon.logger"
instead of "". Updated patch [^AMBARI-19687.03.patch].
{code}
llap_logger =
default('/configurations/hive-interactive-site/hive.llap.daemon.logger',
'query-routing')
{code}
CC [~sumitmohanty] | [~sseth]
> Set the logger for LLAP in hdp-2.6 stack
>
>
> Key: AMBARI-19687
> URL: https://issues.apache.org/jira/browse/AMBARI-19687
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch,
> AMBARI-19687.03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19687: - Status: Open (was: Patch Available) > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch, > AMBARI-19687.03.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19687: - Attachment: AMBARI-19687.03.patch > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch, > AMBARI-19687.03.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19687: - Attachment: (was: AMBARI-19687.02.patch) > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19687: - Attachment: AMBARI-19687.02.patch > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19781) Reassign wizard erases config properties attributes
[ https://issues.apache.org/jira/browse/AMBARI-19781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-19781: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Reassign wizard erases config properties attributes > --- > > Key: AMBARI-19781 > URL: https://issues.apache.org/jira/browse/AMBARI-19781 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19781_branch-2.5.patch, AMBARI-19781_trunk.patch > > > In process of reconfiguring moved component, Reassign wizard doesn't save > attributes of affected properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19785) Need to have a flag from UI to show/hide ranger plugin configs
[ https://issues.apache.org/jira/browse/AMBARI-19785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847462#comment-15847462 ] Hudson commented on AMBARI-19785: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6606 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6606/]) AMBARI-19785. Need to have a flag from UI to show/hide ranger plugin (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e5c5c6b111b3a1a215f5c457e0e1038d6d369a13]) * (edit) ambari-web/app/controllers/main/service/info/configs.js * (edit) ambari-web/app/controllers/wizard/step7_controller.js * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/configuration/cluster-env.xml > Need to have a flag from UI to show/hide ranger plugin configs > -- > > Key: AMBARI-19785 > URL: https://issues.apache.org/jira/browse/AMBARI-19785 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19785.patch > > > UI changes are required to show/hide ranger plugin configs under component > config tab. > If Ranger is not installed on same cluster but is setup on external cluster > then cluster-env/enable_external_ranger can be set to true to expose ranger > plugin related properties for all services > This Flag *cluster-env/enable_external_range* should show ranger plugin > config-types for all services: > * ranger--plugin-properties.xml > * ranger--audit.xml > * ranger--security.xml > * ranger--policymgr-ssl.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[
https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847457#comment-15847457
]
Sumit Mohanty commented on AMBARI-19687:
Patch looks good -
https://issues.apache.org/jira/secure/attachment/12850287/AMBARI-19687.02.patch
+1
One question - is {[--logger }} a valid parameter - when logger is empty string.
> Set the logger for LLAP in hdp-2.6 stack
>
>
> Key: AMBARI-19687
> URL: https://issues.apache.org/jira/browse/AMBARI-19687
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19785) Need to have a flag from UI to show/hide ranger plugin configs
[ https://issues.apache.org/jira/browse/AMBARI-19785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847455#comment-15847455 ] Hudson commented on AMBARI-19785: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #857 (See [https://builds.apache.org/job/Ambari-branch-2.5/857/]) AMBARI-19785. Need to have a flag from UI to show/hide ranger plugin (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ccf9a1c4c19675b83567b9353b5e6f2d5e718f2b]) * (edit) ambari-web/app/controllers/wizard/step7_controller.js * (edit) ambari-web/app/controllers/main/service/info/configs.js * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/configuration/cluster-env.xml > Need to have a flag from UI to show/hide ranger plugin configs > -- > > Key: AMBARI-19785 > URL: https://issues.apache.org/jira/browse/AMBARI-19785 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19785.patch > > > UI changes are required to show/hide ranger plugin configs under component > config tab. > If Ranger is not installed on same cluster but is setup on external cluster > then cluster-env/enable_external_ranger can be set to true to expose ranger > plugin related properties for all services > This Flag *cluster-env/enable_external_range* should show ranger plugin > config-types for all services: > * ranger--plugin-properties.xml > * ranger--audit.xml > * ranger--security.xml > * ranger--policymgr-ssl.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19802) Debug: agent randomly losing heartbeat with the server
[
https://issues.apache.org/jira/browse/AMBARI-19802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847456#comment-15847456
]
Hadoop QA commented on AMBARI-19802:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850284/AMBARI-19802.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-agent.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10351//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10351//console
This message is automatically generated.
> Debug: agent randomly losing heartbeat with the server
> --
>
> Key: AMBARI-19802
> URL: https://issues.apache.org/jira/browse/AMBARI-19802
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19802.patch
>
>
> During tests the agent occasionally gets into heartbeat lost state without
> any hint of the problem. The goal of this change is to add more logging
> without flooding the log files unnecessarily.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[
https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847416#comment-15847416
]
Hadoop QA commented on AMBARI-19687:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850287/AMBARI-19687.02.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/10350//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10350//console
This message is automatically generated.
> Set the logger for LLAP in hdp-2.6 stack
>
>
> Key: AMBARI-19687
> URL: https://issues.apache.org/jira/browse/AMBARI-19687
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19785) Need to have a flag from UI to show/hide ranger plugin configs
[ https://issues.apache.org/jira/browse/AMBARI-19785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19785: -- Resolution: Fixed Status: Resolved (was: Patch Available) Received +1 reviewboard. Patch committed to trunk and branch-2.5 > Need to have a flag from UI to show/hide ranger plugin configs > -- > > Key: AMBARI-19785 > URL: https://issues.apache.org/jira/browse/AMBARI-19785 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19785.patch > > > UI changes are required to show/hide ranger plugin configs under component > config tab. > If Ranger is not installed on same cluster but is setup on external cluster > then cluster-env/enable_external_ranger can be set to true to expose ranger > plugin related properties for all services > This Flag *cluster-env/enable_external_range* should show ranger plugin > config-types for all services: > * ranger--plugin-properties.xml > * ranger--audit.xml > * ranger--security.xml > * ranger--policymgr-ssl.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19702) Switch Pig default engine to tez in HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-19702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847360#comment-15847360 ] Hudson commented on AMBARI-19702: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6605 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6605/]) AMBARI-19702. ADDENDUM. Switch Pig default engine to tez in HDP 2.6 (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=772c093073b31fb0887d7072622e4c37c227e28d]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml > Switch Pig default engine to tez in HDP 2.6 > --- > > Key: AMBARI-19702 > URL: https://issues.apache.org/jira/browse/AMBARI-19702 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Daniel Dai >Assignee: Daniel Dai > Fix For: 2.5.0 > > Attachments: AMBARI-19702.1.patch, AMBARI-19702.2.patch, > AMBARI-19702.3.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19702) Switch Pig default engine to tez in HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-19702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847358#comment-15847358 ] Hudson commented on AMBARI-19702: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #856 (See [https://builds.apache.org/job/Ambari-branch-2.5/856/]) AMBARI-19702. ADDENDUM. Switch Pig default engine to tez in HDP 2.6 (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4116c4092d1e32f685dbf379f9ca2ec89718d89d]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml > Switch Pig default engine to tez in HDP 2.6 > --- > > Key: AMBARI-19702 > URL: https://issues.apache.org/jira/browse/AMBARI-19702 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Daniel Dai >Assignee: Daniel Dai > Fix For: 2.5.0 > > Attachments: AMBARI-19702.1.patch, AMBARI-19702.2.patch, > AMBARI-19702.3.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19687: - Status: Patch Available (was: Open) > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[
https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847320#comment-15847320
]
Swapan Shridhar edited comment on AMBARI-19687 at 1/31/17 7:02 PM:
---
Made [^AMBARI-19687.02.patch] on top of [^AMBARI-19687.01.patch] with below
diff:
{code}
diff --git
a/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
b/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
index 8afe5b5..956c26b 100644
---
a/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
+++
b/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
@@ -647,7 +647,7 @@ if has_hive_interactive:
num_llap_nodes =
config['configurations']['hive-interactive-env']['num_llap_nodes']
llap_daemon_container_size =
config['configurations']['hive-interactive-site']['hive.llap.daemon.yarn.container.mb']
llap_log_level =
config['configurations']['hive-interactive-env']['llap_log_level']
- llap_logger =
config['configurations']['hive-interactive-site']['hive.llap.daemon.logger']
+ llap_logger =
default('/configurations/hive-interactive-site/hive.llap.daemon.logger', '')
hive_aux_jars =
default('/configurations/hive-interactive-env/hive_aux_jars', '')
hive_llap_io_mem_size =
config['configurations']['hive-interactive-site']['hive.llap.io.memory.size']
llap_heap_size =
config['configurations']['hive-interactive-env']['llap_heap_size']
{code}
[~sumitmohanty] Review please the complete [^AMBARI-19687.02.patch]
CC [~sseth]
was (Author: swapanshridhar):
Made [^AMBARI-19687.02.patch] on top of [^AMBARI-19687.01.patch] with below
diff:
{code}
diff --git
a/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
b/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
index 8afe5b5..956c26b 100644
---
a/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
+++
b/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
@@ -647,7 +647,7 @@ if has_hive_interactive:
num_llap_nodes =
config['configurations']['hive-interactive-env']['num_llap_nodes']
llap_daemon_container_size =
config['configurations']['hive-interactive-site']['hive.llap.daemon.yarn.container.mb']
llap_log_level =
config['configurations']['hive-interactive-env']['llap_log_level']
- llap_logger =
config['configurations']['hive-interactive-site']['hive.llap.daemon.logger']
+ llap_logger =
default('/configurations/hive-interactive-site/hive.llap.daemon.logger', '')
hive_aux_jars =
default('/configurations/hive-interactive-env/hive_aux_jars', '')
hive_llap_io_mem_size =
config['configurations']['hive-interactive-site']['hive.llap.io.memory.size']
llap_heap_size =
config['configurations']['hive-interactive-env']['llap_heap_size']
{code}
[~sumitmohanty] Review please.
CC [~sseth]
> Set the logger for LLAP in hdp-2.6 stack
>
>
> Key: AMBARI-19687
> URL: https://issues.apache.org/jira/browse/AMBARI-19687
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19687: - Status: Open (was: Patch Available) > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19795) Ambari upgrade to not add ranger plugin configs under ranger plugin supported services
[
https://issues.apache.org/jira/browse/AMBARI-19795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847322#comment-15847322
]
Hadoop QA commented on AMBARI-19795:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850196/AMBARI-19795.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/10349//console
This message is automatically generated.
> Ambari upgrade to not add ranger plugin configs under ranger plugin supported
> services
> --
>
> Key: AMBARI-19795
> URL: https://issues.apache.org/jira/browse/AMBARI-19795
> Project: Ambari
> Issue Type: Bug
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Attachments: AMBARI-19795.patch
>
>
> Need to revert the changes done as a part of AMBARI-19044 for adding ranger
> plugin configs during ambari upgrade.
> Need to add properties introduced for support cloud under stack 2.6 only.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[
https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847320#comment-15847320
]
Swapan Shridhar commented on AMBARI-19687:
--
Made [^AMBARI-19687.02.patch] on top of [^AMBARI-19687.01.patch] with below
diff:
{code}
diff --git
a/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
b/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
index 8afe5b5..956c26b 100644
---
a/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
+++
b/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
@@ -647,7 +647,7 @@ if has_hive_interactive:
num_llap_nodes =
config['configurations']['hive-interactive-env']['num_llap_nodes']
llap_daemon_container_size =
config['configurations']['hive-interactive-site']['hive.llap.daemon.yarn.container.mb']
llap_log_level =
config['configurations']['hive-interactive-env']['llap_log_level']
- llap_logger =
config['configurations']['hive-interactive-site']['hive.llap.daemon.logger']
+ llap_logger =
default('/configurations/hive-interactive-site/hive.llap.daemon.logger', '')
hive_aux_jars =
default('/configurations/hive-interactive-env/hive_aux_jars', '')
hive_llap_io_mem_size =
config['configurations']['hive-interactive-site']['hive.llap.io.memory.size']
llap_heap_size =
config['configurations']['hive-interactive-env']['llap_heap_size']
{code}
[~sumitmohanty] Review please.
CC [~sseth]
> Set the logger for LLAP in hdp-2.6 stack
>
>
> Key: AMBARI-19687
> URL: https://issues.apache.org/jira/browse/AMBARI-19687
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19683) Content of yarn-env.sh on host is not same as in the downloaded config file from Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-19683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847315#comment-15847315
]
Hadoop QA commented on AMBARI-19683:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850204/AMBARI-19683_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 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10348//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10348//console
This message is automatically generated.
> Content of yarn-env.sh on host is not same as in the downloaded config file
> from Ambari UI
> --
>
> Key: AMBARI-19683
> URL: https://issues.apache.org/jira/browse/AMBARI-19683
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Dhanya Balasundaran
>Assignee: Attila Magyar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19683_branch-2.5.patch, AMBARI-19683_trunk.patch
>
>
> - Navigate to yarn services page
> - Download client config from Service Actions menu
> - Compare the contents in the downloaded file and in the yarn-env.sh on the
> host
> - Two properties that differs are :
> - HADOOP_YARN_HOME
> - YARN_OPTS
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19687: - Attachment: AMBARI-19687.02.patch > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19687: - Attachment: (was: AMBARI-19687.02.patch) > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19687) Set the logger for LLAP in hdp-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19687: - Attachment: AMBARI-19687.02.patch > Set the logger for LLAP in hdp-2.6 stack > > > Key: AMBARI-19687 > URL: https://issues.apache.org/jira/browse/AMBARI-19687 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19687.01.patch, AMBARI-19687.02.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19802) Debug: agent randomly losing heartbeat with the server
[ https://issues.apache.org/jira/browse/AMBARI-19802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-19802: --- Status: Patch Available (was: Open) > Debug: agent randomly losing heartbeat with the server > -- > > Key: AMBARI-19802 > URL: https://issues.apache.org/jira/browse/AMBARI-19802 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-19802.patch > > > During tests the agent occasionally gets into heartbeat lost state without > any hint of the problem. The goal of this change is to add more logging > without flooding the log files unnecessarily. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19802) Debug: agent randomly losing heartbeat with the server
[ https://issues.apache.org/jira/browse/AMBARI-19802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-19802: --- Attachment: AMBARI-19802.patch > Debug: agent randomly losing heartbeat with the server > -- > > Key: AMBARI-19802 > URL: https://issues.apache.org/jira/browse/AMBARI-19802 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-19802.patch > > > During tests the agent occasionally gets into heartbeat lost state without > any hint of the problem. The goal of this change is to add more logging > without flooding the log files unnecessarily. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
