[jira] [Updated] (AMBARI-22327) Allow different OS types and versions for Hybrid setup
[ https://issues.apache.org/jira/browse/AMBARI-22327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22327: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Allow different OS types and versions for Hybrid setup > -- > > Key: AMBARI-22327 > URL: https://issues.apache.org/jira/browse/AMBARI-22327 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22327.patch > > > For setting up Ambari hybrid cluster we need to allow different OS types for > agent hosts as compared to the server OS type. > The strict check during bootstrap needs to be changed in os_check_type.py -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22448) Oozie Jobs on Hive Fail With Missing Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-22448:
---
Status: Patch Available (was: Open)
> Oozie Jobs on Hive Fail With Missing Tarball
>
>
> Key: AMBARI-22448
> URL: https://issues.apache.org/jira/browse/AMBARI-22448
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6 1
>
> Attachments: AMBARI-22448.patch
>
>
> STR:
> - Install an HDP 2.6.3.0 cluster with Oozie, HIve, MapR, Yarn, ZK, HDFS
> - Patch only Oozie to a new version, such as 2.6.3.1-1
> - Attempt to run an Oozie job on Hive
> The workflow job will fail with:
> {code}
> org.apache.oozie.action.ActionExecutorException: JA008: File does not exist:
> hdfs://jhurley-pu-1.openstacklocal:8020/hdp/apps/2.6.3.1-1/mapreduce/mapreduce.tar.gz
> at
> org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:457)
> at
> org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:441)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1211)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1382)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> This is because Oozie appears to be trying to use a version of the MapReduce
> tarball which matches its version. However, since it does not ship its
> version, it cannot find it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22448) Oozie Jobs on Hive Fail With Missing Tarball
[
https://issues.apache.org/jira/browse/AMBARI-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-22448:
---
Attachment: AMBARI-22448.patch
> Oozie Jobs on Hive Fail With Missing Tarball
>
>
> Key: AMBARI-22448
> URL: https://issues.apache.org/jira/browse/AMBARI-22448
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6 1
>
> Attachments: AMBARI-22448.patch
>
>
> STR:
> - Install an HDP 2.6.3.0 cluster with Oozie, HIve, MapR, Yarn, ZK, HDFS
> - Patch only Oozie to a new version, such as 2.6.3.1-1
> - Attempt to run an Oozie job on Hive
> The workflow job will fail with:
> {code}
> org.apache.oozie.action.ActionExecutorException: JA008: File does not exist:
> hdfs://jhurley-pu-1.openstacklocal:8020/hdp/apps/2.6.3.1-1/mapreduce/mapreduce.tar.gz
> at
> org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:457)
> at
> org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:441)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1211)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1382)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> This is because Oozie appears to be trying to use a version of the MapReduce
> tarball which matches its version. However, since it does not ship its
> version, it cannot find it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22448) Oozie Jobs on Hive Fail With Missing Tarball
Nate Cole created AMBARI-22448:
--
Summary: Oozie Jobs on Hive Fail With Missing Tarball
Key: AMBARI-22448
URL: https://issues.apache.org/jira/browse/AMBARI-22448
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Priority: Critical
Fix For: 2.6 1
STR:
- Install an HDP 2.6.3.0 cluster with Oozie, HIve, MapR, Yarn, ZK, HDFS
- Patch only Oozie to a new version, such as 2.6.3.1-1
- Attempt to run an Oozie job on Hive
The workflow job will fail with:
{code}
org.apache.oozie.action.ActionExecutorException: JA008: File does not exist:
hdfs://jhurley-pu-1.openstacklocal:8020/hdp/apps/2.6.3.1-1/mapreduce/mapreduce.tar.gz
at
org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:457)
at
org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:441)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1211)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1382)
at
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
at
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
at org.apache.oozie.command.XCommand.call(XCommand.java:287)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
This is because Oozie appears to be trying to use a version of the MapReduce
tarball which matches its version. However, since it does not ship its version,
it cannot find it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22383) Remove Auto-Installation of LZO Libraries
[ https://issues.apache.org/jira/browse/AMBARI-22383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252751#comment-16252751 ] Hudson commented on AMBARI-22383: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #454 (See [https://builds.apache.org/job/Ambari-branch-2.6/454/]) Revert "AMBARI-22383. Remove Auto-Installation of LZO Libraries (ncole)" (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fe7c17941b1544d10e5170fd031a3a9f4623e035]) * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/install_params.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/HDFS/metainfo.xml * (edit) ambari-common/src/main/python/resource_management/libraries/functions/__init__.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/services/OOZIE/package/scripts/oozie.py * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/services/HDFS/package/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/HDFS/package/scripts/params.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/package_conditions.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/OOZIE/package/scripts/oozie.py * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.1/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/services/OOZIE/package/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HDFS/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py * (edit) ambari-server/src/test/python/custom_actions/TestRemoveBits.py * (edit) ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HDFS/package/scripts/hdfs.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs.py * (edit) ambari-server/src/main/resources/custom_actions/scripts/remove_bits.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/OOZIE/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py * (edit) ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/HDFS/package/scripts/install_params.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HDFS/package/scripts/install_params.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/OOZIE/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py * (add) ambari-common/src/main/python/resource_management/libraries/functions/get_lzo_packages.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/HDFS/package/scripts/hdfs.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/OOZIE/package/scripts/oozie.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3.GlusterFS/services/HDFS/metainfo.xml > Remove Auto-Installation of LZO Libraries > - > > Key: AMBARI-22383 > URL: https://issues.apache.org/jira/browse/AMBARI-22383 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22383.patch > > > The LZO library licenses are not compatible with Ambari's
[jira] [Commented] (AMBARI-22383) Remove Auto-Installation of LZO Libraries
[ https://issues.apache.org/jira/browse/AMBARI-22383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252739#comment-16252739 ] Hudson commented on AMBARI-22383: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8392 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8392/]) Revert "AMBARI-22383. Remove Auto-Installation of LZO Libraries (ncole)" (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ba00ed956706cc80deff58f22799ed54a8bcadd8]) * (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/custom_actions/scripts/remove_bits.py * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/oozie.py * (add) ambari-common/src/main/python/resource_management/libraries/functions/get_lzo_packages.py * (edit) ambari-server/src/main/resources/common-services/TEZ/0.9.0.3.0/package/scripts/tez_client.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/package_conditions.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/metainfo.xml * (edit) ambari-common/src/main/python/resource_management/libraries/functions/__init__.py * (edit) ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3.GlusterFS/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/DRUID/0.10.1/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/oozie_server_upgrade.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/install_params.py * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py * (edit) ambari-server/src/main/resources/common-services/DRUID/0.10.1/package/scripts/druid.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py * (edit) ambari-server/src/test/python/custom_actions/TestRemoveBits.py * (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/hdfs.py * (edit) ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/metainfo.xml > Remove Auto-Installation of LZO Libraries > - > > Key: AMBARI-22383 > URL: https://issues.apache.org/jira/browse/AMBARI-22383 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22383.patch > > > The LZO library licenses are not compatible with Ambari's license and should > not be assumed to be available in Apache-based repositories. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22447) Ambari Infra, AMS, LogSearch are missing from list of services to be installed
[
https://issues.apache.org/jira/browse/AMBARI-22447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252725#comment-16252725
]
Hadoop QA commented on AMBARI-22447:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897640/AMBARI-22447.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12670//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12670//console
This message is automatically generated.
> Ambari Infra, AMS, LogSearch are missing from list of services to be installed
> --
>
> Key: AMBARI-22447
> URL: https://issues.apache.org/jira/browse/AMBARI-22447
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Attachments: AMBARI-22447.patch
>
>
> Ambari Infra service is missing from list of services to be installed, This
> is one of the necessary services for Atlas and Ranger, other-wise need to
> setup Solr manually.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22321) Add Registry StackFeatures to HDP StackFeatures
[
https://issues.apache.org/jira/browse/AMBARI-22321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252716#comment-16252716
]
Hudson commented on AMBARI-22321:
-
ABORTED: Integrated in Jenkins build Ambari-branch-2.6 #453 (See
[https://builds.apache.org/job/Ambari-branch-2.6/453/])
AMBARI-22321 : Changed ambari version from 2.6.0.0 to 2.6.3.0. Addendum
(mradhakrishnan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=62876f5763224be90915f03f12dfd219cce21913])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json
> Add Registry StackFeatures to HDP StackFeatures
> ---
>
> Key: AMBARI-22321
> URL: https://issues.apache.org/jira/browse/AMBARI-22321
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.6.1
>
>
> {code}
> {
> "name": "registry_remove_rootpath",
> "description": "Registry remove root path setting",
> "min_version": "2.6.0.0"
> },
> {
> "name": "registry_allowed_resources_support",
> "description": "Registry allowed resources",
> "min_version": "2.6.0.0"
> },
> {
> "name": "registry_rewriteuri_filter_support",
> "description": "Registry RewriteUri servlet filter",
> "min_version": "2.6.0.0"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22447) Ambari Infra, AMS, LogSearch are missing from list of services to be installed
[ https://issues.apache.org/jira/browse/AMBARI-22447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22447: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to AMBARI-2.99.99.0 > Ambari Infra, AMS, LogSearch are missing from list of services to be installed > -- > > Key: AMBARI-22447 > URL: https://issues.apache.org/jira/browse/AMBARI-22447 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Attachments: AMBARI-22447.patch > > > Ambari Infra service is missing from list of services to be installed, This > is one of the necessary services for Atlas and Ranger, other-wise need to > setup Solr manually. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22447) Ambari Infra, AMS, LogSearch are missing from list of services to be installed
[ https://issues.apache.org/jira/browse/AMBARI-22447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22447: --- Status: Patch Available (was: Open) > Ambari Infra, AMS, LogSearch are missing from list of services to be installed > -- > > Key: AMBARI-22447 > URL: https://issues.apache.org/jira/browse/AMBARI-22447 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Attachments: AMBARI-22447.patch > > > Ambari Infra service is missing from list of services to be installed, This > is one of the necessary services for Atlas and Ranger, other-wise need to > setup Solr manually. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22447) Ambari Infra, AMS, LogSearch are missing from list of services to be installed
[ https://issues.apache.org/jira/browse/AMBARI-22447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22447: --- Attachment: AMBARI-22447.patch > Ambari Infra, AMS, LogSearch are missing from list of services to be installed > -- > > Key: AMBARI-22447 > URL: https://issues.apache.org/jira/browse/AMBARI-22447 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Attachments: AMBARI-22447.patch > > > Ambari Infra service is missing from list of services to be installed, This > is one of the necessary services for Atlas and Ranger, other-wise need to > setup Solr manually. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22447) Ambari Infra, AMS, LogSearch are missing from list of services to be installed
Vitaly Brodetskyi created AMBARI-22447: -- Summary: Ambari Infra, AMS, LogSearch are missing from list of services to be installed Key: AMBARI-22447 URL: https://issues.apache.org/jira/browse/AMBARI-22447 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Blocker Ambari Infra service is missing from list of services to be installed, This is one of the necessary services for Atlas and Ranger, other-wise need to setup Solr manually. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22446) Ambari Incorrectly Warns about tez.tez-ui.history-url.base
[
https://issues.apache.org/jira/browse/AMBARI-22446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
amarnath reddy pappu reassigned AMBARI-22446:
-
Assignee: amarnath reddy pappu
> Ambari Incorrectly Warns about tez.tez-ui.history-url.base
> --
>
> Key: AMBARI-22446
> URL: https://issues.apache.org/jira/browse/AMBARI-22446
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.5.2
> Environment: OS: RHEL-6 (64 Bit)
> Tez: 0.7.0
> Ambari: 2.5.2.0
>Reporter: Tamil Selvan Kandasamy
>Assignee: amarnath reddy pappu
>Priority: Minor
> Labels: triage
>
> In the ambari cluster where SSL in enabled, and ambari port is 8443, it
> wrongly displays the warning as below:
> ***
> tez.tez-ui.history-url.base:
> It is recommended to set value
> https://:8765/#/main/view/TEZ/tez_cluster_instance for property
> tez.tez-ui.history-url.base
> ***
> Before enabling SSL, Ambari was running on port 8765, and looks like
> "tez.tez-ui.history-url.base" is still looking for older port.
> Though we were able to connect Tez UI using:
> https://:8443/#/main/view/TEZ/tez_cluster_instance
> Hence, here ambari is providing a wrong warning.
> Code snippet that is causing this issue is
> https://github.com/apache/ambari/blob/release-2.5.1/ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
> In below code we are always checking client.api.port for port - if https is
> enabled that it should check the port at "client.api.ssl.port" instead of
> "client.api.port"
> {code:java}
> if serverProperties:
> if 'client.api.port' in serverProperties:
> server_port = serverProperties['client.api.port']
> if 'views.dir' in serverProperties:
> views_dir = serverProperties['views.dir']
> if 'api.ssl' in serverProperties:
> if serverProperties['api.ssl'].lower() == 'true':
> server_protocol = 'https'
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22446) Ambari Incorrectly Warns about tez.tez-ui.history-url.base
Tamil Selvan Kandasamy created AMBARI-22446:
---
Summary: Ambari Incorrectly Warns about tez.tez-ui.history-url.base
Key: AMBARI-22446
URL: https://issues.apache.org/jira/browse/AMBARI-22446
Project: Ambari
Issue Type: Bug
Components: ambari-sever
Affects Versions: 2.5.2
Environment: OS: RHEL-6 (64 Bit)
Tez: 0.7.0
Ambari: 2.5.2.0
Reporter: Tamil Selvan Kandasamy
Priority: Minor
In the ambari cluster where SSL in enabled, and ambari port is 8443, it wrongly
displays the warning as below:
***
tez.tez-ui.history-url.base:
It is recommended to set value
https://:8765/#/main/view/TEZ/tez_cluster_instance for property
tez.tez-ui.history-url.base
***
Before enabling SSL, Ambari was running on port 8765, and looks like
"tez.tez-ui.history-url.base" is still looking for older port.
Though we were able to connect Tez UI using:
https://:8443/#/main/view/TEZ/tez_cluster_instance
Hence, here ambari is providing a wrong warning.
Code snippet that is causing this issue is
https://github.com/apache/ambari/blob/release-2.5.1/ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
In below code we are always checking client.api.port for port - if https is
enabled that it should check the port at "client.api.ssl.port" instead of
"client.api.port"
{code:java}
if serverProperties:
if 'client.api.port' in serverProperties:
server_port = serverProperties['client.api.port']
if 'views.dir' in serverProperties:
views_dir = serverProperties['views.dir']
if 'api.ssl' in serverProperties:
if serverProperties['api.ssl'].lower() == 'true':
server_protocol = 'https'
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
Vivek Ratnavel Subramanian created AMBARI-22445: --- Summary: Warn the user appropriately for default MySQL server install for Hive Key: AMBARI-22445 URL: https://issues.apache.org/jira/browse/AMBARI-22445 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Priority: Blocker Fix For: 2.6.1 The mysql connector license is not compatible with Ambari's license and Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22444) Add Native Libraries To Tez Tarball
Jonathan Hurley created AMBARI-22444:
Summary: Add Native Libraries To Tez Tarball
Key: AMBARI-22444
URL: https://issues.apache.org/jira/browse/AMBARI-22444
Project: Ambari
Issue Type: Bug
Affects Versions: 2.6.1
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Blocker
Fix For: 2.6.1
As part of the investigation for getting patch upgrades working in Ambari
2.6.1, it was determined that the Tez tarball will need to have the hadoop
native libraries added to it so that they can be detected from the tarball.
STR:
- Install ZK, MapR, Tez, Yarn, Hive
- Enable a non-LZO codec, like Snappy
- Patch Hive to a new version
- Change the following properties in {{tez-site}}:
-- tez.am.launch.env = LD_LIBRARY=./tezlib/lib/native
-- tez.task.launch.env = LD_LIBRARY=./tezlib/lib/native
When Hive commands run, they will attempt to load the native snappy libraries
from the Tez tarball and will fail with:
{code}
Caused by: java.io.IOException: Unable to get CompressorType for codec
(org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to missing
native libraries for the codec.
at
org.apache.tez.runtime.library.common.sort.impl.ExternalSorter.(ExternalSorter.java:217)
{code}
In order to fix this, the Tez tarball should include the native hadoop
libraries as well:
{code}
├── tez
│ ├── lib
│ │ ├── native
│ │ │ ├── libhadoop.a
│ │ │ ├── libhadoop.so -> libhadoop.so.1.0.0
│ │ │ ├── libhadoop.so.1.0.0
│ │ │ ├── libhadooppipes.a
│ │ │ ├── libhadooputils.a
│ │ │ ├── libhdfs.a
│ │ │ ├── libhdfs.so -> libhdfs.so.0.0.0
│ │ │ ├── libhdfs.so.0.0.0
│ │ │ ├── libsnappy.so -> libsnappy.so.1.1.4
│ │ │ ├── libsnappy.so.1 -> libsnappy.so.1.1.4
│ │ │ └── libsnappy.so.1.1.4
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22418) Make Ambari configuration API consistent with existing API.
[
https://issues.apache.org/jira/browse/AMBARI-22418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252177#comment-16252177
]
Hadoop QA commented on AMBARI-22418:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897615/AMBARI-22418_trunk_01.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 15 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12669//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12669//console
This message is automatically generated.
> Make Ambari configuration API consistent with existing API.
> ---
>
> Key: AMBARI-22418
> URL: https://issues.apache.org/jira/browse/AMBARI-22418
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 3.0.0
>
> Attachments: AMBARI-22418_trunk_01.patch
>
>
> Make Ambari configuration API consistent with existing API.
> The current API entry point (as of AMBARI-21307) is
> {{/api/v1/ambariconfigs}}. This should be more inline with the existing entry
> point for Ambari server related data...
> {{/api/v1/services/AMBARI/components/AMBARI_SERVER}}.
> The new API entry point for Ambari server related configuration data should
> be {{/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations}}.
> Example Rest API calls:
> *Create/Set configuration*
> Used to create a new or explicitly set properties an existing Ambari Server
> configuration
> {noformat:title=URL}
> POST /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "category" : "ldap-configuration",
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Update configuration*
> Used to update existing properties or add new properties to an existing
> Ambari Server configuration
> {noformat:title=URL}
> PUT
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Delete configuration*
> Deletes an existing Ambari Server configuration
> {noformat:title=URL}
> DELETE
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> *Get configurations*
> Used to retrieve a list of the existing Ambari Server configurations
> {noformat:title=URL}
> GET /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations;,
> "items" : [
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration;,
> "Configuration" : {
> "category" : "ldap-configuration",
> "component_name" : "AMBARI_SERVER",
> "service_name" : "AMBARI"
> }
> }
> ]
> }
> {code}
> *Get configuration*
> Used to retrieve a the details
[jira] [Commented] (AMBARI-22321) Add Registry StackFeatures to HDP StackFeatures
[
https://issues.apache.org/jira/browse/AMBARI-22321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252136#comment-16252136
]
Hudson commented on AMBARI-22321:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8390 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8390/])
AMBARI-22321 : Changed ambari version from 2.6.0.0 to 2.6.3.0. Addendum
(mradhakrishnan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=869e1aaeaaf8a03a374bfe8d7fd992e1a048aaad])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json
> Add Registry StackFeatures to HDP StackFeatures
> ---
>
> Key: AMBARI-22321
> URL: https://issues.apache.org/jira/browse/AMBARI-22321
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.6.1
>
>
> {code}
> {
> "name": "registry_remove_rootpath",
> "description": "Registry remove root path setting",
> "min_version": "2.6.0.0"
> },
> {
> "name": "registry_allowed_resources_support",
> "description": "Registry allowed resources",
> "min_version": "2.6.0.0"
> },
> {
> "name": "registry_rewriteuri_filter_support",
> "description": "Registry RewriteUri servlet filter",
> "min_version": "2.6.0.0"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22432) Getting NPE when trying to get services information from service group
[ https://issues.apache.org/jira/browse/AMBARI-22432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan resolved AMBARI-22432. Resolution: Fixed > Getting NPE when trying to get services information from service group > -- > > Key: AMBARI-22432 > URL: https://issues.apache.org/jira/browse/AMBARI-22432 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 3.0.0 > > > Install lates ambari build from feature branch. Add HDFS,YARN,MP and ZK > services. After cluster will be deployed run this request in command line: > curl -X GET -u admin:admin -H "X-Requested-By: ambari" > http://localhost:8080/api/v1/clusters/cl1/servicegroups/core/services/ZOOKEEPER > Getting NPE here: > 13 Nov 2017 17:40:48,727 ERROR [ambari-client-thread-35] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HTTP container > java.lang.NullPointerException > at > org.apache.ambari.server.controller.AmbariManagementControllerImpl.getConfigurations(AmbariManagementControllerImpl.java:1562) > at > org.apache.ambari.server.controller.AmbariManagementControllerImpl.getConfigurations(AmbariManagementControllerImpl.java:4016) > Problem is in fact that clusterConfigEntity doesn't have serviceId (service > id == null). So method cacheConfigurations doesn't work. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22418) Make Ambari configuration API consistent with existing API.
[
https://issues.apache.org/jira/browse/AMBARI-22418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252041#comment-16252041
]
Robert Levas commented on AMBARI-22418:
---
Note: [^AMBARI-22418_trunk_01.patch] fixes a stack advisor issue introduced
with the patch for AMBARI-2234.
> Make Ambari configuration API consistent with existing API.
> ---
>
> Key: AMBARI-22418
> URL: https://issues.apache.org/jira/browse/AMBARI-22418
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 3.0.0
>
> Attachments: AMBARI-22418_trunk_01.patch
>
>
> Make Ambari configuration API consistent with existing API.
> The current API entry point (as of AMBARI-21307) is
> {{/api/v1/ambariconfigs}}. This should be more inline with the existing entry
> point for Ambari server related data...
> {{/api/v1/services/AMBARI/components/AMBARI_SERVER}}.
> The new API entry point for Ambari server related configuration data should
> be {{/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations}}.
> Example Rest API calls:
> *Create/Set configuration*
> Used to create a new or explicitly set properties an existing Ambari Server
> configuration
> {noformat:title=URL}
> POST /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "category" : "ldap-configuration",
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Update configuration*
> Used to update existing properties or add new properties to an existing
> Ambari Server configuration
> {noformat:title=URL}
> PUT
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Delete configuration*
> Deletes an existing Ambari Server configuration
> {noformat:title=URL}
> DELETE
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> *Get configurations*
> Used to retrieve a list of the existing Ambari Server configurations
> {noformat:title=URL}
> GET /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations;,
> "items" : [
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration;,
> "Configuration" : {
> "category" : "ldap-configuration",
> "component_name" : "AMBARI_SERVER",
> "service_name" : "AMBARI"
> }
> }
> ]
> }
> {code}
> *Get configuration*
> Used to retrieve a the details about an existing Ambari Server configuration
> {noformat:title=URL}
> GET
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration;,
> "Configuration" : {
> "category" : "ldap-configuration",
> "component_name" : "AMBARI_SERVER",
> "service_name" : "AMBARI",
> "properties" : {
> "ambari.ldap.base.dn" : "dc=example,dc=com",
> "ambari.ldap.bindanonymously" : "true",
> "ambari.ldap.group.member.attribute" : "uniqueMember",
> "ambari.ldap.group.name.attribute" : "cn",
> "ambari.ldap.group.object.class" : "groupOfUniqueNames",
> "ambari.ldap.group.search.base" :
[jira] [Updated] (AMBARI-22418) Make Ambari configuration API consistent with existing API.
[
https://issues.apache.org/jira/browse/AMBARI-22418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22418:
--
Status: Patch Available (was: In Progress)
> Make Ambari configuration API consistent with existing API.
> ---
>
> Key: AMBARI-22418
> URL: https://issues.apache.org/jira/browse/AMBARI-22418
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 3.0.0
>
> Attachments: AMBARI-22418_trunk_01.patch
>
>
> Make Ambari configuration API consistent with existing API.
> The current API entry point (as of AMBARI-21307) is
> {{/api/v1/ambariconfigs}}. This should be more inline with the existing entry
> point for Ambari server related data...
> {{/api/v1/services/AMBARI/components/AMBARI_SERVER}}.
> The new API entry point for Ambari server related configuration data should
> be {{/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations}}.
> Example Rest API calls:
> *Create/Set configuration*
> Used to create a new or explicitly set properties an existing Ambari Server
> configuration
> {noformat:title=URL}
> POST /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "category" : "ldap-configuration",
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Update configuration*
> Used to update existing properties or add new properties to an existing
> Ambari Server configuration
> {noformat:title=URL}
> PUT
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Delete configuration*
> Deletes an existing Ambari Server configuration
> {noformat:title=URL}
> DELETE
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> *Get configurations*
> Used to retrieve a list of the existing Ambari Server configurations
> {noformat:title=URL}
> GET /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations;,
> "items" : [
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration;,
> "Configuration" : {
> "category" : "ldap-configuration",
> "component_name" : "AMBARI_SERVER",
> "service_name" : "AMBARI"
> }
> }
> ]
> }
> {code}
> *Get configuration*
> Used to retrieve a the details about an existing Ambari Server configuration
> {noformat:title=URL}
> GET
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration;,
> "Configuration" : {
> "category" : "ldap-configuration",
> "component_name" : "AMBARI_SERVER",
> "service_name" : "AMBARI",
> "properties" : {
> "ambari.ldap.base.dn" : "dc=example,dc=com",
> "ambari.ldap.bindanonymously" : "true",
> "ambari.ldap.group.member.attribute" : "uniqueMember",
> "ambari.ldap.group.name.attribute" : "cn",
> "ambari.ldap.group.object.class" : "groupOfUniqueNames",
> "ambari.ldap.group.search.base" : "dc=example,dc=com",
> "ambari.ldap.server.port" : "389",
> "ambari.ldap.user.name.attribute" : "uid",
>
[jira] [Updated] (AMBARI-22418) Make Ambari configuration API consistent with existing API.
[
https://issues.apache.org/jira/browse/AMBARI-22418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22418:
--
Attachment: AMBARI-22418_trunk_01.patch
> Make Ambari configuration API consistent with existing API.
> ---
>
> Key: AMBARI-22418
> URL: https://issues.apache.org/jira/browse/AMBARI-22418
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 3.0.0
>
> Attachments: AMBARI-22418_trunk_01.patch
>
>
> Make Ambari configuration API consistent with existing API.
> The current API entry point (as of AMBARI-21307) is
> {{/api/v1/ambariconfigs}}. This should be more inline with the existing entry
> point for Ambari server related data...
> {{/api/v1/services/AMBARI/components/AMBARI_SERVER}}.
> The new API entry point for Ambari server related configuration data should
> be {{/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations}}.
> Example Rest API calls:
> *Create/Set configuration*
> Used to create a new or explicitly set properties an existing Ambari Server
> configuration
> {noformat:title=URL}
> POST /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "category" : "ldap-configuration",
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Update configuration*
> Used to update existing properties or add new properties to an existing
> Ambari Server configuration
> {noformat:title=URL}
> PUT
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> {code:title=Payload}
> {
> "Configuration": {
> "properties": {
> "ambari.ldap.bindanonymously": "true",
> "ambari.ldap.server.port": "389",
> "ambari.ldap.base.dn": "dc=example,dc=com",
> "ambari.ldap.user.object.class":"person",
> "ambari.ldap.user.name.attribute":"uid",
> "ambari.ldap.user.search.base": "dc=example,dc=com",
> "ambari.ldap.group.object.class":"groupOfUniqueNames",
> "ambari.ldap.group.name.attribute":"cn",
> "ambari.ldap.group.member.attribute":"uniqueMember",
> "ambari.ldap.group.search.base": "dc=example,dc=com"
> }
> }
> }
> {code}
> *Delete configuration*
> Deletes an existing Ambari Server configuration
> {noformat:title=URL}
> DELETE
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> *Get configurations*
> Used to retrieve a list of the existing Ambari Server configurations
> {noformat:title=URL}
> GET /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations
> {noformat}
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations;,
> "items" : [
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration;,
> "Configuration" : {
> "category" : "ldap-configuration",
> "component_name" : "AMBARI_SERVER",
> "service_name" : "AMBARI"
> }
> }
> ]
> }
> {code}
> *Get configuration*
> Used to retrieve a the details about an existing Ambari Server configuration
> {noformat:title=URL}
> GET
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration
> {noformat}
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/ldap-configuration;,
> "Configuration" : {
> "category" : "ldap-configuration",
> "component_name" : "AMBARI_SERVER",
> "service_name" : "AMBARI",
> "properties" : {
> "ambari.ldap.base.dn" : "dc=example,dc=com",
> "ambari.ldap.bindanonymously" : "true",
> "ambari.ldap.group.member.attribute" : "uniqueMember",
> "ambari.ldap.group.name.attribute" : "cn",
> "ambari.ldap.group.object.class" : "groupOfUniqueNames",
> "ambari.ldap.group.search.base" : "dc=example,dc=com",
> "ambari.ldap.server.port" : "389",
> "ambari.ldap.user.name.attribute" : "uid",
>
[jira] [Commented] (AMBARI-22438) Disable plugins for yum on yum list command
[ https://issues.apache.org/jira/browse/AMBARI-22438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251936#comment-16251936 ] Hudson commented on AMBARI-22438: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8389 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8389/]) AMBARI-22438 Disable plugins for yum on yum list command (dgrinenko) (hapylestat: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3297dfa6542f9cffef2ae36ef0e777fe4c3e829c]) * (edit) ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py > Disable plugins for yum on yum list command > --- > > Key: AMBARI-22438 > URL: https://issues.apache.org/jira/browse/AMBARI-22438 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko > Fix For: 2.6.1 > > Attachments: AMBARI-22438.patch > > > On the system with configured RedHat Satellite, yum command could produce > additional output, which can break packages list parser. > To avoid the issue, plugins should be disabled on calling "yum list *" command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22438) Disable plugins for yum on yum list command
[ https://issues.apache.org/jira/browse/AMBARI-22438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251931#comment-16251931 ] Hudson commented on AMBARI-22438: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #452 (See [https://builds.apache.org/job/Ambari-branch-2.6/452/]) AMBARI-22438 Disable plugins for yum on yum list command (dgrinenko) (hapylestat: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=334411fbf172fa0c4097ce01f375bc5ed2529aaf]) * (edit) ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py > Disable plugins for yum on yum list command > --- > > Key: AMBARI-22438 > URL: https://issues.apache.org/jira/browse/AMBARI-22438 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko > Fix For: 2.6.1 > > Attachments: AMBARI-22438.patch > > > On the system with configured RedHat Satellite, yum command could produce > additional output, which can break packages list parser. > To avoid the issue, plugins should be disabled on calling "yum list *" command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22438) Disable plugins for yum on yum list command
[ https://issues.apache.org/jira/browse/AMBARI-22438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251867#comment-16251867 ] Dmytro Grinenko commented on AMBARI-22438: -- Tests r not required for such kind of change. Committed: a22f66f719..334411fbf1 branch-2.6 -> branch-2.6 ed7e121f3a..3297dfa654 trunk -> trunk > Disable plugins for yum on yum list command > --- > > Key: AMBARI-22438 > URL: https://issues.apache.org/jira/browse/AMBARI-22438 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko > Fix For: 2.6.1 > > Attachments: AMBARI-22438.patch > > > On the system with configured RedHat Satellite, yum command could produce > additional output, which can break packages list parser. > To avoid the issue, plugins should be disabled on calling "yum list *" command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22438) Disable plugins for yum on yum list command
[ https://issues.apache.org/jira/browse/AMBARI-22438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-22438: - Resolution: Fixed Status: Resolved (was: Patch Available) > Disable plugins for yum on yum list command > --- > > Key: AMBARI-22438 > URL: https://issues.apache.org/jira/browse/AMBARI-22438 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko > Fix For: 2.6.1 > > Attachments: AMBARI-22438.patch > > > On the system with configured RedHat Satellite, yum command could produce > additional output, which can break packages list parser. > To avoid the issue, plugins should be disabled on calling "yum list *" command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22426) Push down Logger instances
[ https://issues.apache.org/jira/browse/AMBARI-22426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251863#comment-16251863 ] Hudson commented on AMBARI-22426: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8388 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8388/]) AMBARI-22426. Push down Logger instances (adoroszlai) (adoroszlai: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ed7e121f3aee519ee18e53b4d0b05661cca4b48a]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/BaseService.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/state/DefaultServiceCalculatedState.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ServiceResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/ganglia/GangliaPropertyProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/state/HBaseServiceCalculatedState.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackAdvisorResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/state/HDFSServiceCalculatedState.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/ViewExtractor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/DatabaseChecker.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/utils/RetryHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsDownsamplingMethod.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ThemeArtifactResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/PersistedStateImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/LoggingService.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/StackAdvisorCommand.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/ThreadPoolEnabledPropertyProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeItemResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ActionResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BaseProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/GroupResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/state/OozieServiceCalculatedState.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsCollectorHAClusterState.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractPropertyProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackArtifactResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/LdapSyncEventResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/ViewDataMigrationUtility.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/handlers/CreateHandler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KDCKerberosOperationHandler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/CompatibleRepositoryVersionResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ValidationResourceProvider.java * (edit)
[jira] [Created] (AMBARI-22443) Log Feeder: do not try to connect AMS, when it is disabled
Olivér Szabó created AMBARI-22443: - Summary: Log Feeder: do not try to connect AMS, when it is disabled Key: AMBARI-22443 URL: https://issues.apache.org/jira/browse/AMBARI-22443 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21145) Allow wildcard for log directory folder in the path component of Logfeeder input
[
https://issues.apache.org/jira/browse/AMBARI-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251852#comment-16251852
]
Juanjo Marron commented on AMBARI-21145:
Thanks for the update!
> Allow wildcard for log directory folder in the path component of Logfeeder
> input
>
>
> Key: AMBARI-21145
> URL: https://issues.apache.org/jira/browse/AMBARI-21145
> Project: Ambari
> Issue Type: Improvement
> Components: logsearch
>Affects Versions: 2.5.0
>Reporter: Keta Patel
>Assignee: Olivér Szabó
>Priority: Minor
> Fix For: 2.6.1
>
>
> The wildcard processing in Logfeeder is carried out only for the last file
> component in the log path. For a few services, where there are multiple log
> folders and log files from each of the folders is desired to be parsed in
> Logsearch UI, the lack of a wildcard processing for the previous portions
> becomes an issue. Hence, introducing wildcard processing for the log
> directory part of the "path" in the Logfeeder's input for the service will
> help resolve this issue.
> The idea is if we have a folder pattern, we will craete a thread group, and
> there will be different threads for every matching input (now only for tail
> file)
> Features (new input block settings):
> - {{path_update_interval_min}}: the period in minutes for checking new files
> (default: 5, based on detach values, its possible that a new input wont be
> monitored)
> - {{detach_interval_min}}: the period in minutes for checking which files are
> too old (default: 300)
> - {{detach_time_min: the period}} in minutes when we flag a file is too old
> (default: 2000)
> - if a path contains a {{*}} before the last {{/}}, then logfeeder will know
> that the inputs should handled in a thread group, not in a standalone thread
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22395) Log Feeder: cleanup checkpoint files periodically
[ https://issues.apache.org/jira/browse/AMBARI-22395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251840#comment-16251840 ] Hudson commented on AMBARI-22395: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #451 (See [https://builds.apache.org/job/Ambari-branch-2.6/451/]) AMBARI-22395. Log Feeder: cleanup checkpoint files periodically (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a22f66f719fd11efd5ecfec09dc5a8112f9ada1b]) * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/metrics/MetrcisManagerTest.java * (add) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/monitor/CheckpointCleanupMonitor.java * (add) ambari-logsearch/docker/test-logs/storm/worker-logs/streamline-1-TestAgg-2-3/6701/worker.log * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/metrics/LogFeederAMSClient.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/metrics/MetricsManager.java * (add) ambari-logsearch/docker/test-config/logfeeder/shipper-conf/input.config-storm.json * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/monitor/LogFileDetachMonitor.java * (edit) ambari-logsearch/docker/test-config/logfeeder/logfeeder.properties * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/FileUtil.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/monitor/AbstractLogFileMonitor.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/InputManager.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/AbstractInputFile.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/monitor/LogFilePathUpdateMonitor.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/Input.java > Log Feeder: cleanup checkpoint files periodically > - > > Key: AMBARI-22395 > URL: https://issues.apache.org/jira/browse/AMBARI-22395 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.6.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.6.1 > > > - added new config: "max_age_min" (similar as detach_time_min) to input > block. that stored in checkpoint files, during cleanup, based on that the > checkpoint file can be deleted. > - based on "max_age_min" value, during bootstrap, its possible logfeeder wont > even monitor a file in the future. > - created a new thread which periodically run the checkpoint cleanup (now in > every 2000 minutes ... its ok to run that rearly) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22437) Create an 'AD Manager' component in Ambari Metrics Service stack side.
[ https://issues.apache.org/jira/browse/AMBARI-22437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-22437. Resolution: Fixed > Create an 'AD Manager' component in Ambari Metrics Service stack side. > --- > > Key: AMBARI-22437 > URL: https://issues.apache.org/jira/browse/AMBARI-22437 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 3.0.0 > > Attachments: AMBARI-22437-2.patch > > > Goals > * Add a component called Anomaly-Detector in Ambari Metrics Service. > * Create scripts to start/stop the component > * Configuration management for Anomaly-Detector component. > * Create Ambari stack scripts to manage lifecycle of the component - install, > start, stop. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22437) Create an 'AD Manager' component in Ambari Metrics Service stack side.
[ https://issues.apache.org/jira/browse/AMBARI-22437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22437: --- Attachment: AMBARI-22437-2.patch > Create an 'AD Manager' component in Ambari Metrics Service stack side. > --- > > Key: AMBARI-22437 > URL: https://issues.apache.org/jira/browse/AMBARI-22437 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 3.0.0 > > Attachments: AMBARI-22437-2.patch > > > Goals > * Add a component called Anomaly-Detector in Ambari Metrics Service. > * Create scripts to start/stop the component > * Configuration management for Anomaly-Detector component. > * Create Ambari stack scripts to manage lifecycle of the component - install, > start, stop. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22426) Push down Logger instances
[
https://issues.apache.org/jira/browse/AMBARI-22426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251798#comment-16251798
]
Doroszlai, Attila commented on AMBARI-22426:
Committed to
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/ed7e121f3a].
> Push down Logger instances
> --
>
> Key: AMBARI-22426
> URL: https://issues.apache.org/jira/browse/AMBARI-22426
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-22426.patch
>
>
> {{Logger}} prepends classname and line number to log messages. Reusing
> {{Logger}} from other classes makes it more difficult to understand where the
> log message is coming from. This includes {{Logger}} instances inherited
> from parent classes.
> {noformat:title=example}
> 13 Nov 2017 11:55:13,571 INFO [ambari-client-thread-36]
> AbstractResourceProvider:525 - Creating Cluster 'TEST' based on blueprint
> 'blue'.
> 13 Nov 2017 11:55:13,623 ERROR [ambari-client-thread-36]
> BaseManagementHandler:79 - Caught a runtime exception while attempting to
> create a resource: null
> {noformat}
> In the above example, log is written from {{ClusterResourceProvider}} and
> {{CreateHandler}}, respectively, but one needs to search the source code for
> the messages to find this out.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21145) Allow wildcard for log directory folder in the path component of Logfeeder input
[
https://issues.apache.org/jira/browse/AMBARI-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-21145.
---
Resolution: Fixed
trunk work will be here (as the implementation will be really different):
https://issues.apache.org/jira/browse/AMBARI-22440
so i close this jira
> Allow wildcard for log directory folder in the path component of Logfeeder
> input
>
>
> Key: AMBARI-21145
> URL: https://issues.apache.org/jira/browse/AMBARI-21145
> Project: Ambari
> Issue Type: Improvement
> Components: logsearch
>Affects Versions: 2.5.0
>Reporter: Keta Patel
>Assignee: Olivér Szabó
>Priority: Minor
> Fix For: 2.6.1
>
>
> The wildcard processing in Logfeeder is carried out only for the last file
> component in the log path. For a few services, where there are multiple log
> folders and log files from each of the folders is desired to be parsed in
> Logsearch UI, the lack of a wildcard processing for the previous portions
> becomes an issue. Hence, introducing wildcard processing for the log
> directory part of the "path" in the Logfeeder's input for the service will
> help resolve this issue.
> The idea is if we have a folder pattern, we will craete a thread group, and
> there will be different threads for every matching input (now only for tail
> file)
> Features (new input block settings):
> - {{path_update_interval_min}}: the period in minutes for checking new files
> (default: 5, based on detach values, its possible that a new input wont be
> monitored)
> - {{detach_interval_min}}: the period in minutes for checking which files are
> too old (default: 300)
> - {{detach_time_min: the period}} in minutes when we flag a file is too old
> (default: 2000)
> - if a path contains a {{*}} before the last {{/}}, then logfeeder will know
> that the inputs should handled in a thread group, not in a standalone thread
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21145) Allow wildcard for log directory folder in the path component of Logfeeder input
[
https://issues.apache.org/jira/browse/AMBARI-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-21145:
--
Description:
The wildcard processing in Logfeeder is carried out only for the last file
component in the log path. For a few services, where there are multiple log
folders and log files from each of the folders is desired to be parsed in
Logsearch UI, the lack of a wildcard processing for the previous portions
becomes an issue. Hence, introducing wildcard processing for the log directory
part of the "path" in the Logfeeder's input for the service will help resolve
this issue.
The idea is if we have a folder pattern, we will craete a thread group, and
there will be different threads for every matching input (now only for tail
file)
Features (new input block settings):
- {{path_update_interval_min}}: the period in minutes for checking new files
(default: 5, based on detach values, its possible that a new input wont be
monitored)
- {{detach_interval_min}}: the period in minutes for checking which files are
too old (default: 300)
- {{detach_time_min: the period}} in minutes when we flag a file is too old
(default: 2000)
- if a path contains a {{*}} before the last {{/}}, then logfeeder will know
that the inputs should handled in a thread group, not in a standalone thread
was:The wildcard processing in Logfeeder is carried out only for the last
file component in the log path. For a few services, where there are multiple
log folders and log files from each of the folders is desired to be parsed in
Logsearch UI, the lack of a wildcard processing for the previous portions
becomes an issue. Hence, introducing wildcard processing for the log directory
part of the "path" in the Logfeeder's input for the service will help resolve
this issue.
> Allow wildcard for log directory folder in the path component of Logfeeder
> input
>
>
> Key: AMBARI-21145
> URL: https://issues.apache.org/jira/browse/AMBARI-21145
> Project: Ambari
> Issue Type: Improvement
> Components: logsearch
>Affects Versions: 2.5.0
>Reporter: Keta Patel
>Assignee: Olivér Szabó
>Priority: Minor
> Fix For: 2.6.1
>
>
> The wildcard processing in Logfeeder is carried out only for the last file
> component in the log path. For a few services, where there are multiple log
> folders and log files from each of the folders is desired to be parsed in
> Logsearch UI, the lack of a wildcard processing for the previous portions
> becomes an issue. Hence, introducing wildcard processing for the log
> directory part of the "path" in the Logfeeder's input for the service will
> help resolve this issue.
> The idea is if we have a folder pattern, we will craete a thread group, and
> there will be different threads for every matching input (now only for tail
> file)
> Features (new input block settings):
> - {{path_update_interval_min}}: the period in minutes for checking new files
> (default: 5, based on detach values, its possible that a new input wont be
> monitored)
> - {{detach_interval_min}}: the period in minutes for checking which files are
> too old (default: 300)
> - {{detach_time_min: the period}} in minutes when we flag a file is too old
> (default: 2000)
> - if a path contains a {{*}} before the last {{/}}, then logfeeder will know
> that the inputs should handled in a thread group, not in a standalone thread
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22395) Log Feeder: cleanup checkpoint files periodically
[
https://issues.apache.org/jira/browse/AMBARI-22395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-22395.
---
Resolution: Fixed
committed to branch-2.6:
{code:java}
commit a22f66f719fd11efd5ecfec09dc5a8112f9ada1b
Author: Oliver Szabo
Date: Tue Nov 14 13:21:42 2017 +0100
AMBARI-22395. Log Feeder: cleanup checkpoint files periodically (oleewere)
{code}
> Log Feeder: cleanup checkpoint files periodically
> -
>
> Key: AMBARI-22395
> URL: https://issues.apache.org/jira/browse/AMBARI-22395
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.6.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.6.1
>
>
> - added new config: "max_age_min" (similar as detach_time_min) to input
> block. that stored in checkpoint files, during cleanup, based on that the
> checkpoint file can be deleted.
> - based on "max_age_min" value, during bootstrap, its possible logfeeder wont
> even monitor a file in the future.
> - created a new thread which periodically run the checkpoint cleanup (now in
> every 2000 minutes ... its ok to run that rearly)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[ https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251759#comment-16251759 ] Hudson commented on AMBARI-22439: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #450 (See [https://builds.apache.org/job/Ambari-branch-2.6/450/]) AMBARI-22439 Host check operation is being performed on all hosts during (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=93820ddfde17651dff3bf4786634813824323144]) * (edit) ambari-web/app/controllers/wizard/step3_controller.js > Host check operation is being performed on all hosts during host add should > not get stuck > - > > Key: AMBARI-22439 > URL: https://issues.apache.org/jira/browse/AMBARI-22439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22439.patch, AMBARI-22439_branch-2.6.patch > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22442) Log Search GA
[ https://issues.apache.org/jira/browse/AMBARI-22442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó reassigned AMBARI-22442: - Assignee: Olivér Szabó > Log Search GA > - > > Key: AMBARI-22442 > URL: https://issues.apache.org/jira/browse/AMBARI-22442 > Project: Ambari > Issue Type: Epic > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22442) Log Search GA
Olivér Szabó created AMBARI-22442: - Summary: Log Search GA Key: AMBARI-22442 URL: https://issues.apache.org/jira/browse/AMBARI-22442 Project: Ambari Issue Type: Epic Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Olivér Szabó Priority: Blocker Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22435) Hive services sets incorrect permissions on the root of HDFS while setting up replication
[
https://issues.apache.org/jira/browse/AMBARI-22435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251716#comment-16251716
]
Hadoop QA commented on AMBARI-22435:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897443/AMBARI-22435-trunk.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12667//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12667//console
This message is automatically generated.
> Hive services sets incorrect permissions on the root of HDFS while setting up
> replication
> -
>
> Key: AMBARI-22435
> URL: https://issues.apache.org/jira/browse/AMBARI-22435
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Deepesh Khandelwal
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22435-trunk.patch
>
>
> While starting Hive metastore or HiveServer2 observed that the hdfs audit log
> had the following entries:
> {noformat}
> 2017-11-14 01:48:03,682 INFO FSNamesystem.audit: allowed=true ugi=hdfs
> (auth:SIMPLE) ip=/172.27.70.128 cmd=getfileinfo src=/ dst=null
> perm=null proto=webhdfs
> 2017-11-14 01:48:03,745 INFO FSNamesystem.audit: allowed=true ugi=hdfs
> (auth:SIMPLE) ip=/172.27.70.128 cmd=setPermission src=/
> dst=nullperm=hdfs:hdfs:rwxrwxrwtproto=webhdfs
> 2017-11-14 01:48:03,809 INFO FSNamesystem.audit: allowed=true ugi=hdfs
> (auth:SIMPLE) ip=/172.27.70.128 cmd=setOwnersrc=/ dst=null
> perm=hive:hadoop:rwxrwxrwt proto=webhdfs
> 2017-11-14 01:48:04,126 INFO FSNamesystem.audit: allowed=true ugi=hdfs
> (auth:SIMPLE) ip=/172.27.70.128 cmd=getfileinfo src=/ dst=null
> perm=null proto=webhdfs
> 2017-11-14 01:48:04,189 INFO FSNamesystem.audit: allowed=true ugi=hdfs
> (auth:SIMPLE) ip=/172.27.70.128 cmd=setPermission src=/
> dst=nullperm=hive:hadoop:rwx-- proto=webhdfs
> {noformat}
> The consequence of this was that for any non-hdfs user you will see the
> following error running hadoop commands:
> {noformat}
> $ hadoop fs -ls /
> ls: Permission denied: user=root, access=READ_EXECUTE,
> inode="/":hive:hadoop:drwx--
> {noformat}
> On debugging this was happening due to incomplete null/empty check on params
> hive_repl_cmrootdir and hive_repl_rootdir in
> ambari/blob/trunk/ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/package/scripts/hive.py.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[ https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251712#comment-16251712 ] Hudson commented on AMBARI-22439: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8387 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8387/]) AMBARI-22439 Host check operation is being performed on all hosts during (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d0ef1449af23e22ee6b95726ce4ca0b1f3544cc4]) * (edit) ambari-web/app/mixins/main/host/details/actions/check_host.js > Host check operation is being performed on all hosts during host add should > not get stuck > - > > Key: AMBARI-22439 > URL: https://issues.apache.org/jira/browse/AMBARI-22439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22439.patch, AMBARI-22439_branch-2.6.patch > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[ https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22439: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Host check operation is being performed on all hosts during host add should > not get stuck > - > > Key: AMBARI-22439 > URL: https://issues.apache.org/jira/browse/AMBARI-22439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22439.patch, AMBARI-22439_branch-2.6.patch > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[ https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251659#comment-16251659 ] Andrii Tkach commented on AMBARI-22439: --- committed to trunk and branch-2.6 > Host check operation is being performed on all hosts during host add should > not get stuck > - > > Key: AMBARI-22439 > URL: https://issues.apache.org/jira/browse/AMBARI-22439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22439.patch, AMBARI-22439_branch-2.6.patch > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22436) zookeeper service issue
[
https://issues.apache.org/jira/browse/AMBARI-22436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251658#comment-16251658
]
Hadoop QA commented on AMBARI-22436:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897453/AMBARI-22436.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12666//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12666//console
This message is automatically generated.
> zookeeper service issue
> ---
>
> Key: AMBARI-22436
> URL: https://issues.apache.org/jira/browse/AMBARI-22436
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-22436.patch, screenshot-1.png
>
>
> amabri-qa has not permission to write zookeeper'.log in the dir of
> /var/log/zookeeper for permission is 0755.
> so should set permission is 0777 when executing service check.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22438) Disable plugins for yum on yum list command
[
https://issues.apache.org/jira/browse/AMBARI-22438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251601#comment-16251601
]
Hadoop QA commented on AMBARI-22438:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897520/AMBARI-22438.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12665//console
This message is automatically generated.
> Disable plugins for yum on yum list command
> ---
>
> Key: AMBARI-22438
> URL: https://issues.apache.org/jira/browse/AMBARI-22438
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
> Fix For: 2.6.1
>
> Attachments: AMBARI-22438.patch
>
>
> On the system with configured RedHat Satellite, yum command could produce
> additional output, which can break packages list parser.
> To avoid the issue, plugins should be disabled on calling "yum list *" command
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[
https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251551#comment-16251551
]
Hadoop QA commented on AMBARI-22439:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897530/AMBARI-22439.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12664//console
This message is automatically generated.
> Host check operation is being performed on all hosts during host add should
> not get stuck
> -
>
> Key: AMBARI-22439
> URL: https://issues.apache.org/jira/browse/AMBARI-22439
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22439.patch, AMBARI-22439_branch-2.6.patch
>
>
> Steps to reproduce:
> 1. Have a cluster with 2/3 hosts
> 2. now try to add a new host from UI
> 3. Ambari initiates host check for all the hosts in the cluster instead of
> doing it for new host alone. if there is any issues with other hosts then
> host add will get hung and will not be able to proceed further.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22425) Ambari 3.0: Implement new design for Admin View: fix checkboxes
[ https://issues.apache.org/jira/browse/AMBARI-22425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251505#comment-16251505 ] Hudson commented on AMBARI-22425: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8386 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8386/]) AMBARI-22425 Ambari 3.0: Implement new design for Admin View: fix (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d11faab139761a3e32da773e190951d10d1166f1]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/ambariViews/create.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/modals/AddVersionModal.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/styles/main.css * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/authentication/main.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/styles/top-nav.css * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/list.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/ambariViews/edit.html > Ambari 3.0: Implement new design for Admin View: fix checkboxes > --- > > Key: AMBARI-22425 > URL: https://issues.apache.org/jira/browse/AMBARI-22425 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22425.patch, no-checkbox-visible.png > > > After applying new styles checkboxes disappeared. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22431) Able to add config type if EU/RU of the same stack (minor version upgrade)
[
https://issues.apache.org/jira/browse/AMBARI-22431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251500#comment-16251500
]
Hadoop QA commented on AMBARI-22431:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12897563/AMBARI-22431-v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12663//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12663//console
This message is automatically generated.
> Able to add config type if EU/RU of the same stack (minor version upgrade)
> --
>
> Key: AMBARI-22431
> URL: https://issues.apache.org/jira/browse/AMBARI-22431
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: 2.6.1
>
> Attachments: AMBARI-22431-v2.patch, AMBARI-22431-v3.patch,
> AMBARI-22431.patch
>
>
> EU/RU does not create/load default of new config types when the source stack
> and target stack is the same. This JIRA introduces a new config task type for
> creating/loading defaults of a new config type when stack does not change
> during EU/RU. This is particularly important for EU/RU of custom services
> where their stack may not change at all.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22431) Able to add config type if EU/RU of the same stack (minor version upgrade)
[ https://issues.apache.org/jira/browse/AMBARI-22431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22431: --- Status: Patch Available (was: In Progress) > Able to add config type if EU/RU of the same stack (minor version upgrade) > -- > > Key: AMBARI-22431 > URL: https://issues.apache.org/jira/browse/AMBARI-22431 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Di Li >Assignee: Di Li > Fix For: 2.6.1 > > Attachments: AMBARI-22431-v2.patch, AMBARI-22431-v3.patch, > AMBARI-22431.patch > > > EU/RU does not create/load default of new config types when the source stack > and target stack is the same. This JIRA introduces a new config task type for > creating/loading defaults of a new config type when stack does not change > during EU/RU. This is particularly important for EU/RU of custom services > where their stack may not change at all. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22431) Able to add config type if EU/RU of the same stack (minor version upgrade)
[ https://issues.apache.org/jira/browse/AMBARI-22431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22431: --- Attachment: AMBARI-22431-v3.patch > Able to add config type if EU/RU of the same stack (minor version upgrade) > -- > > Key: AMBARI-22431 > URL: https://issues.apache.org/jira/browse/AMBARI-22431 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Di Li >Assignee: Di Li > Fix For: 2.6.1 > > Attachments: AMBARI-22431-v2.patch, AMBARI-22431-v3.patch, > AMBARI-22431.patch > > > EU/RU does not create/load default of new config types when the source stack > and target stack is the same. This JIRA introduces a new config task type for > creating/loading defaults of a new config type when stack does not change > during EU/RU. This is particularly important for EU/RU of custom services > where their stack may not change at all. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22431) Able to add config type if EU/RU of the same stack (minor version upgrade)
[ https://issues.apache.org/jira/browse/AMBARI-22431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22431: --- Status: In Progress (was: Patch Available) > Able to add config type if EU/RU of the same stack (minor version upgrade) > -- > > Key: AMBARI-22431 > URL: https://issues.apache.org/jira/browse/AMBARI-22431 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Di Li >Assignee: Di Li > Fix For: 2.6.1 > > Attachments: AMBARI-22431-v2.patch, AMBARI-22431-v3.patch, > AMBARI-22431.patch > > > EU/RU does not create/load default of new config types when the source stack > and target stack is the same. This JIRA introduces a new config task type for > creating/loading defaults of a new config type when stack does not change > during EU/RU. This is particularly important for EU/RU of custom services > where their stack may not change at all. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22441) Integrate Alert Groups on Alert page with websocket events
Andrii Tkach created AMBARI-22441: - Summary: Integrate Alert Groups on Alert page with websocket events Key: AMBARI-22441 URL: https://issues.apache.org/jira/browse/AMBARI-22441 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 Subscribe to /events/alert_groups topic, which will update/add/delete groups of alerts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22300) Log Feeder: allow applying grok filter on default fields (like type, path, host etc.)
[
https://issues.apache.org/jira/browse/AMBARI-22300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-22300.
---
Resolution: Fixed
> Log Feeder: allow applying grok filter on default fields (like type, path,
> host etc.)
> -
>
> Key: AMBARI-22300
> URL: https://issues.apache.org/jira/browse/AMBARI-22300
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.6.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.6.1
>
>
> Log Feeder: add {{init_default_fields}} to input block, in order to initalize
> host,ip,path,type values before any grok filter applied
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22440) Log Feeder: wildcard support & checkpoint cleanup on trunk
Olivér Szabó created AMBARI-22440: - Summary: Log Feeder: wildcard support & checkpoint cleanup on trunk Key: AMBARI-22440 URL: https://issues.apache.org/jira/browse/AMBARI-22440 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 As we are using JDK 8 from Ambari 3.0, the wildcard feature can be reimplemented. The feature should contain the following features / fixes: AMBARI-21145: Allow wildcard for log directory folder in the path component of Logfeeder input AMBARI-22300: Log Feeder: allow applying grok filter on default fields (like type, path, host etc.) AMBARI-22395: Log Feeder: cleanup checkpoint files periodically -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22395) Log Feeder: cleanup checkpoint files periodically
[ https://issues.apache.org/jira/browse/AMBARI-22395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-22395: -- Description: - added new config: "max_age_min" (similar as detach_time_min) to input block. that stored in checkpoint files, during cleanup, based on that the checkpoint file can be deleted. - based on "max_age_min" value, during bootstrap, its possible logfeeder wont even monitor a file in the future. - created a new thread which periodically run the checkpoint cleanup (now in every 2000 minutes ... its ok to run that rearly) > Log Feeder: cleanup checkpoint files periodically > - > > Key: AMBARI-22395 > URL: https://issues.apache.org/jira/browse/AMBARI-22395 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.6.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.6.1 > > > - added new config: "max_age_min" (similar as detach_time_min) to input > block. that stored in checkpoint files, during cleanup, based on that the > checkpoint file can be deleted. > - based on "max_age_min" value, during bootstrap, its possible logfeeder wont > even monitor a file in the future. > - created a new thread which periodically run the checkpoint cleanup (now in > every 2000 minutes ... its ok to run that rearly) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22422) Ambari Metrics does not work with DateTieredStoreEngine
[
https://issues.apache.org/jira/browse/AMBARI-22422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251308#comment-16251308
]
Zhanwei Wang commented on AMBARI-22422:
---
Any comments on this issue?
> Ambari Metrics does not work with DateTieredStoreEngine
> ---
>
> Key: AMBARI-22422
> URL: https://issues.apache.org/jira/browse/AMBARI-22422
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.0
> Environment: centos7
>Reporter: Zhanwei Wang
> Attachments: ambari-metrics-collector-etc.tar.gz,
> ambari-metrics-collector-log.tar.gz
>
>
> I build Ambari from source code with tag release-2.6.0 and setup a three node
> centos7 cluster for test.
> With all default configurations, Ambari Metrics did not work and I found the
> following from HBase logs.
> {noformat}
> 2017-11-11 15:07:56,478 INFO
> [B.defaultRpcServer.handler=24,queue=0,port=40128] zookeeper.ZooKeeper:
> Initiating client connection, connectString=test3:61181 sessionTimeout=12
> watcher=hconnection-0x23f7d8350x0, quorum=test3:61181,
> baseZNode=/ams-hbase-unsecure
> @
>@
> at
> org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:129)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.io.IOException: Unable to load configured store engine
> 'org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine'
> at
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:128)
> at org.apache.hadoop.hbase.regionserver.HStore.(HStore.java:271)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:4958)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:905)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:902)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ... 3 more
> Caused by: java.lang.UnsupportedOperationException: Unable to find
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:36)
> at
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:123)
> ... 10 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:32)
> ... 11 more
> {noformat}
> After adding the following to ams-site.xml. Ambari Metrics work normally. And
> no more Exception found in both collector and hbase logs.
> {noformat}
>
>
> timeline.metrics.hbase.aggregate.table.compaction.policy.class
> org.apache.hadoop.hbase.regionserver.DefaultStoreEngine
>
> {noformat}
> From HBASE-19223, Date Tiered Compaction is only available starting in the
> 1.3 release.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22423) Ambari Metrics does not work after restart service
[
https://issues.apache.org/jira/browse/AMBARI-22423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251306#comment-16251306
]
Zhanwei Wang commented on AMBARI-22423:
---
Does anyone has any idea to fix this issue?
> Ambari Metrics does not work after restart service
> --
>
> Key: AMBARI-22423
> URL: https://issues.apache.org/jira/browse/AMBARI-22423
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.0
> Environment: centos7
>Reporter: Zhanwei Wang
>
> I build Ambari from source code with tag release-2.6.0 and setup a three node
> centos7 cluster for test.
> With all default configurations I manager to make Ambari Metrics work
> normally. But after restart Ambari Metrics service, HBase died with following
> exception.
> {noformat}
> 2017-11-11 16:03:36,800 INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181]
> server.NIOServerCnxn: Closed socket connection for client
> /192.168.110.7:41352 which had sessionid 0x15faa1aa2a90005
> 2017-11-11 16:03:48,253 INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181]
> server.NIOServerCnxnFactory: Accepted socket connection from
> /192.168.110.7:41390
> 2017-11-11 16:03:48,258 INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181]
> server.ZooKeeperServer: Client attempting to establish new session at
> /192.168.110.7:41390
> 2017-11-11 16:03:48,262 INFO [SyncThread:0] server.ZooKeeperServer:
> Established session 0x15faa1aa2a90006 with negotiated timeout 12 for
> client /192.168.110.7:41390
> 2017-11-11 16:03:51,437 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Master not active after 30 seconds
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:194)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:227)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2452)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[ https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251288#comment-16251288 ] Aleksandr Kovalenko commented on AMBARI-22439: -- +1 for the patch > Host check operation is being performed on all hosts during host add should > not get stuck > - > > Key: AMBARI-22439 > URL: https://issues.apache.org/jira/browse/AMBARI-22439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22439.patch, AMBARI-22439_branch-2.6.patch > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[ https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22439: -- Status: Patch Available (was: Open) > Host check operation is being performed on all hosts during host add should > not get stuck > - > > Key: AMBARI-22439 > URL: https://issues.apache.org/jira/browse/AMBARI-22439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22439.patch, AMBARI-22439_branch-2.6.patch > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[ https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22439: -- Attachment: AMBARI-22439_branch-2.6.patch > Host check operation is being performed on all hosts during host add should > not get stuck > - > > Key: AMBARI-22439 > URL: https://issues.apache.org/jira/browse/AMBARI-22439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22439.patch, AMBARI-22439_branch-2.6.patch > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[ https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22439: -- Attachment: AMBARI-22439.patch > Host check operation is being performed on all hosts during host add should > not get stuck > - > > Key: AMBARI-22439 > URL: https://issues.apache.org/jira/browse/AMBARI-22439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22439.patch, AMBARI-22439_branch-2.6.patch > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
Andrii Tkach created AMBARI-22439: - Summary: Host check operation is being performed on all hosts during host add should not get stuck Key: AMBARI-22439 URL: https://issues.apache.org/jira/browse/AMBARI-22439 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 3.0.0 Steps to reproduce: 1. Have a cluster with 2/3 hosts 2. now try to add a new host from UI 3. Ambari initiates host check for all the hosts in the cluster instead of doing it for new host alone. if there is any issues with other hosts then host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[ https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22439: -- Fix Version/s: (was: 3.0.0) 2.6.1 > Host check operation is being performed on all hosts during host add should > not get stuck > - > > Key: AMBARI-22439 > URL: https://issues.apache.org/jira/browse/AMBARI-22439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.1 > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22439) Host check operation is being performed on all hosts during host add should not get stuck
[ https://issues.apache.org/jira/browse/AMBARI-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22439: -- Affects Version/s: (was: 3.0.0) 2.5.1 > Host check operation is being performed on all hosts during host add should > not get stuck > - > > Key: AMBARI-22439 > URL: https://issues.apache.org/jira/browse/AMBARI-22439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.1 > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22425) Ambari 3.0: Implement new design for Admin View: fix checkboxes
[ https://issues.apache.org/jira/browse/AMBARI-22425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22425: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari 3.0: Implement new design for Admin View: fix checkboxes > --- > > Key: AMBARI-22425 > URL: https://issues.apache.org/jira/browse/AMBARI-22425 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22425.patch, no-checkbox-visible.png > > > After applying new styles checkboxes disappeared. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22425) Ambari 3.0: Implement new design for Admin View: fix checkboxes
[ https://issues.apache.org/jira/browse/AMBARI-22425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251127#comment-16251127 ] Andrii Tkach commented on AMBARI-22425: --- committed to trunk > Ambari 3.0: Implement new design for Admin View: fix checkboxes > --- > > Key: AMBARI-22425 > URL: https://issues.apache.org/jira/browse/AMBARI-22425 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22425.patch, no-checkbox-visible.png > > > After applying new styles checkboxes disappeared. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22438) Disable plugins for yum on yum list command
[ https://issues.apache.org/jira/browse/AMBARI-22438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-22438: - Status: Patch Available (was: In Progress) > Disable plugins for yum on yum list command > --- > > Key: AMBARI-22438 > URL: https://issues.apache.org/jira/browse/AMBARI-22438 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko > Fix For: 2.6.1 > > Attachments: AMBARI-22438.patch > > > On the system with configured RedHat Satellite, yum command could produce > additional output, which can break packages list parser. > To avoid the issue, plugins should be disabled on calling "yum list *" command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22438) Disable plugins for yum on yum list command
[ https://issues.apache.org/jira/browse/AMBARI-22438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-22438: - Attachment: AMBARI-22438.patch > Disable plugins for yum on yum list command > --- > > Key: AMBARI-22438 > URL: https://issues.apache.org/jira/browse/AMBARI-22438 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko > Fix For: 2.6.1 > > Attachments: AMBARI-22438.patch > > > On the system with configured RedHat Satellite, yum command could produce > additional output, which can break packages list parser. > To avoid the issue, plugins should be disabled on calling "yum list *" command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22438) Disable plugins for yum on yum list command
Dmytro Grinenko created AMBARI-22438: Summary: Disable plugins for yum on yum list command Key: AMBARI-22438 URL: https://issues.apache.org/jira/browse/AMBARI-22438 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.1 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: 2.6.1 On the system with configured RedHat Satellite, yum command could produce additional output, which can break packages list parser. To avoid the issue, plugins should be disabled on calling "yum list *" command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
