[jira] [Commented] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm
[ https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362000#comment-15362000 ] Hudson commented on AMBARI-17080: - SUCCESS: Integrated in Ambari-trunk-Commit #5224 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5224/]) Revert "AMBARI-17080 Support Storm 1.0 in Ambari Metrics for Storm (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=200a250a120981bbc28d96b41095e42f21279093]) * ambari-metrics/ambari-metrics-assembly/pom.xml * ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java * ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/NumberUtil.java * ambari-metrics/ambari-metrics-storm-sink/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java * ambari-metrics/ambari-metrics-common/pom.xml * ambari-metrics/ambari-metrics-assembly/src/main/assembly/sink.xml * ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/ui_server.py * ambari-server/src/test/python/stacks/2.1/STORM/test_storm_nimbus.py * ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java * ambari-metrics/ambari-metrics-storm-sink-legacy/pom.xml * ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java * ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py * ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/assemblies/empty.xml * ambari-metrics/ambari-metrics-storm-sink-legacy/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java * ambari-metrics/pom.xml * ambari-metrics/ambari-metrics-assembly/src/main/assembly/sink-windows.xml * ambari-metrics/ambari-metrics-storm-sink/pom.xml * ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/storm.py * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/storm-site.xml * ambari-server/src/test/python/stacks/2.1/STORM/test_storm_ui_server.py * ambari-server/src/main/resources/common-services/STORM/0.9.1/package/templates/storm-metrics2.properties.j2 * ambari-server/src/main/resources/stacks/HDP/2.5/services/STORM/configuration/storm-site.xml * ambari-metrics/ambari-metrics-storm-sink/src/main/conf/storm-metrics2.properties.j2 * ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java > Support Storm 1.0 in Ambari Metrics for Storm > - > > Key: AMBARI-17080 > URL: https://issues.apache.org/jira/browse/AMBARI-17080 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-17080-trunk_6.patch, AMBARI-17080-v1.patch, > AMBARI-17080-v2.patch, AMBARI-17080-v3.patch > > > Since there was package name change on Apache Storm 1.0.0, Ambari Metrics > Reporter / Sink for Storm will not work when Ambari supports Apache Storm > 1.0.0 or upper. > This issue is for addressing this. > Please note that it will incur compile failure unless Ambari Metrics pom file > depends on Storm 1.x version, so decision for version of Storm should be made > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17557) Hive WebHCat Service Check Fails During Upgrade Due To Missing Configurations Files
[
https://issues.apache.org/jira/browse/AMBARI-17557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361968#comment-15361968
]
Hadoop QA commented on AMBARI-17557:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816102/AMBARI-17557.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7690//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7690//console
This message is automatically generated.
> Hive WebHCat Service Check Fails During Upgrade Due To Missing Configurations
> Files
> ---
>
> Key: AMBARI-17557
> URL: https://issues.apache.org/jira/browse/AMBARI-17557
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17557.patch
>
>
> During an upgrade from HDP 2.2 to HDP 2.4, the Hive WebHCat Service Check
> fails several times:
> {code}
> 2016-06-29 02:24:49,660 - Retrying after 5 seconds. Reason: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh
> natr66-cuts-c10to25rhel6unsr-10.openstacklocal ambari-qa 50111
> idtest.ambari-qa.1467167063.06.pig no_keytab false kinit no_principal
> /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke Test (pig cmd):
> Failed. : {\"error\":\"Failed to get WebHCatShim\"}http_code <500>
> Templeton Smoke Test (pig cmd): Failed. : {\"error\":\"Failed to get
> WebHCatShim\"}http_code <500>
> {code}
> Caused by:
> {code}
> FATAL | 29 Jun 2016 02:24:36,920 | org.apache.hadoop.conf.Configuration |
> error parsing conf file:/etc/hive-webhcat/conf/webhcat-site.xml
> java.io.FileNotFoundException: /etc/hive-webhcat/conf/webhcat-site.xml (No
> such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.(FileInputStream.java:146)
> at java.io.FileInputStream.(FileInputStream.java:101)
> at
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at java.net.URL.openStream(URL.java:1037)
> at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2342)
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2410)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2376)
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2283)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:888)
> at
> org.apache.hadoop.conf.Configuration.getTrimmed(Configuration.java:907)
> at org.apache.hadoop.conf.Configuration.getLong(Configuration.java:1182)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:139)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:96)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapred.JobClient.init(JobClient.java:485)
> at org.apache.hadoop.mapred.JobClient.(JobClient.java:475)
> at
> org.apache.hadoop.mapred.WebHCatJTShim23$1.run(WebHCatJTShim23.java:60)
> at
> org.apache.hadoop.mapred.WebHCatJTShim23$1.run(WebHCatJTShim23.java:57)
>
[jira] [Commented] (AMBARI-17184) HBase doesn't start because of lacking of variable
[
https://issues.apache.org/jira/browse/AMBARI-17184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361950#comment-15361950
]
Hadoop QA commented on AMBARI-17184:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816109/AMBARI-17184.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7689//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7689//console
This message is automatically generated.
> HBase doesn't start because of lacking of variable
> --
>
> Key: AMBARI-17184
> URL: https://issues.apache.org/jira/browse/AMBARI-17184
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6.5
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Critical
> Attachments: AMBARI-17184.1.patch, AMBARI-17184.patch
>
>
> When we wanted to restart HBase, we got an error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 159, in
> HbaseMaster().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 686, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 86, in start
> self.configure(env) # for security
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 41, in configure
> hbase(name='master')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py",
> line 166, in hbase
> tag = 'GANGLIA-MASTER' if name == 'master' else 'GANGLIA-RS'
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py",
> line 233, in hbase_TemplateConfig
> template_tag = tag
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/template_config.py",
> line 46, in action_create
> content = Template(template_name,
> extra_imports=self.resource.extra_imports)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 123, in action_create
> content = self._get_content()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 160, in _get_content
> return content()
> File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
> line 51, in __call__
> return self.get_content()
> File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
> line 142, in get_content
> rendered = self.template.render(self.context)
> File "/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py", line
>
[jira] [Commented] (AMBARI-17554) ambari-server update-host-name failing
[
https://issues.apache.org/jira/browse/AMBARI-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361905#comment-15361905
]
Hudson commented on AMBARI-17554:
-
ABORTED: Integrated in Ambari-trunk-Commit #5223 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5223/])
AMBARI-17554. ambari-server update-host-name failing.(vbrodetskyi)
(vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=179df466eb35b99a73e0d031487c68347c8d67fe])
*
ambari-server/src/main/java/org/apache/ambari/server/update/HostUpdateHelper.java
> ambari-server update-host-name failing
> --
>
> Key: AMBARI-17554
> URL: https://issues.apache.org/jira/browse/AMBARI-17554
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17554.patch
>
>
> Steps to reproduce :
> 1) Run the following command on one of the hosts (which is not the ambari
> server) in the cluster :
> {code}
> hostname renamedHost-0
> {code}
> 2) On the ambari-server change the host name in the /etc/hosts for the host
> whose name was changed in step1
> 3) Create a file like the following to indicate the host changed :
> {code}
> {
> "cl1" : {
> "renamedHost-0.openstacklocal" :
> "rerenamedhost-0.openstacklocal"
> }
> }
> {code}
> 4) Run ambari-server update-host-name
> The error shown :
> {code}
> 03 Jul 2016 07:24:31,914 INFO [main] Configuration:1022 - Reading password
> from existing file
> 03 Jul 2016 07:24:31,931 INFO [main] Configuration:1491 - Hosts Mapping File
> null
> 03 Jul 2016 07:24:31,932 INFO [main] HostsMap:60 - Using hostsmap file null
> 03 Jul 2016 07:24:32,742 INFO [main] ControllerModule:199 - Detected ORACLE
> as the database type from the JDBC URL
> 03 Jul 2016 07:24:34,884 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher
> 03 Jul 2016 07:24:34,895 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.EmailDispatcher
> 03 Jul 2016 07:24:34,905 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher
> 03 Jul 2016 07:24:38,223 ERROR [main] HostUpdateHelper:545 - Unexpected
> error, host names update failed
> com.google.inject.CreationException: Guice creation errors:
> 1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:324)
> 2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
> at
> org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:525)
> 2 errors
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.apache.ambari.server.update.HostUpdateHelper.main(HostUpdateHelper.java:516)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17556) Add default value for atlas.authentication.method.ldap.type in common services
[ https://issues.apache.org/jira/browse/AMBARI-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361904#comment-15361904 ] Hudson commented on AMBARI-17556: - ABORTED: Integrated in Ambari-trunk-Commit #5223 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5223/]) AMBARI-17556. Add default value for (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6aec65f7b59fb854787b4c4b23d893b5ea9a9768]) * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/configuration/application-properties.xml > Add default value for atlas.authentication.method.ldap.type in common services > -- > > Key: AMBARI-17556 > URL: https://issues.apache.org/jira/browse/AMBARI-17556 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17556.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17184) HBase doesn't start because of lacking of variable
[
https://issues.apache.org/jira/browse/AMBARI-17184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17184:
-
Attachment: AMBARI-17184.1.patch
> HBase doesn't start because of lacking of variable
> --
>
> Key: AMBARI-17184
> URL: https://issues.apache.org/jira/browse/AMBARI-17184
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6.5
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Critical
> Attachments: AMBARI-17184.1.patch, AMBARI-17184.patch
>
>
> When we wanted to restart HBase, we got an error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 159, in
> HbaseMaster().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 686, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 86, in start
> self.configure(env) # for security
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 41, in configure
> hbase(name='master')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py",
> line 166, in hbase
> tag = 'GANGLIA-MASTER' if name == 'master' else 'GANGLIA-RS'
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py",
> line 233, in hbase_TemplateConfig
> template_tag = tag
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/template_config.py",
> line 46, in action_create
> content = Template(template_name,
> extra_imports=self.resource.extra_imports)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 123, in action_create
> content = self._get_content()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 160, in _get_content
> return content()
> File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
> line 51, in __call__
> return self.get_content()
> File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
> line 142, in get_content
> rendered = self.template.render(self.context)
> File "/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py", line
> 891, in render
> return self.environment.handle_exception(exc_info, True)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/templates/hadoop-metrics2-hbase.properties-GANGLIA-MASTER.j2",
> line 76, in top-level template code
> hbase.sink.timeline.truststore.password = {{metric_truststore_password}}
> ambari_jinja2.exceptions.UndefinedError: 'metric_collector_hosts' is undefined
> {code}
> We should define {{metric_collector_hosts}} in
> ambari/ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17557) Hive WebHCat Service Check Fails During Upgrade Due To Missing Configurations Files
[
https://issues.apache.org/jira/browse/AMBARI-17557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-17557:
-
Status: Patch Available (was: Open)
> Hive WebHCat Service Check Fails During Upgrade Due To Missing Configurations
> Files
> ---
>
> Key: AMBARI-17557
> URL: https://issues.apache.org/jira/browse/AMBARI-17557
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17557.patch
>
>
> During an upgrade from HDP 2.2 to HDP 2.4, the Hive WebHCat Service Check
> fails several times:
> {code}
> 2016-06-29 02:24:49,660 - Retrying after 5 seconds. Reason: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh
> natr66-cuts-c10to25rhel6unsr-10.openstacklocal ambari-qa 50111
> idtest.ambari-qa.1467167063.06.pig no_keytab false kinit no_principal
> /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke Test (pig cmd):
> Failed. : {\"error\":\"Failed to get WebHCatShim\"}http_code <500>
> Templeton Smoke Test (pig cmd): Failed. : {\"error\":\"Failed to get
> WebHCatShim\"}http_code <500>
> {code}
> Caused by:
> {code}
> FATAL | 29 Jun 2016 02:24:36,920 | org.apache.hadoop.conf.Configuration |
> error parsing conf file:/etc/hive-webhcat/conf/webhcat-site.xml
> java.io.FileNotFoundException: /etc/hive-webhcat/conf/webhcat-site.xml (No
> such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.(FileInputStream.java:146)
> at java.io.FileInputStream.(FileInputStream.java:101)
> at
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at java.net.URL.openStream(URL.java:1037)
> at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2342)
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2410)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2376)
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2283)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:888)
> at
> org.apache.hadoop.conf.Configuration.getTrimmed(Configuration.java:907)
> at org.apache.hadoop.conf.Configuration.getLong(Configuration.java:1182)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:139)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:96)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapred.JobClient.init(JobClient.java:485)
> at org.apache.hadoop.mapred.JobClient.(JobClient.java:475)
> at
> org.apache.hadoop.mapred.WebHCatJTShim23$1.run(WebHCatJTShim23.java:60)
> at
> org.apache.hadoop.mapred.WebHCatJTShim23$1.run(WebHCatJTShim23.java:57)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
> at
> org.apache.hadoop.mapred.WebHCatJTShim23.(WebHCatJTShim23.java:57)
> at
> org.apache.hadoop.hive.shims.Hadoop23Shims.getWebHCatShim(Hadoop23Shims.java:500)
> {code}
> The reason for the missing file is that the symlinks are messed up when
> converting HDP 2.2 hard {{/etc/component/conf}} directories to symlinks:
> {code:title=Wrong}
> [root@c6402 hive-webhcat]# ll /etc/hive-webhcat/
> total 8
> drwxr-xr-x 3 root root 4096 Jul 5 00:49 2.4.2.0-236
> lrwxrwxrwx 1 root root 29 Jul 5 00:49 conf ->
> /etc/hive-hcatalog/conf.backup
> drwxr-xr-x 2 hcat hadoop 4096 Jul 4 23:25 conf.backup
> {code}
> {code:title=Right}
> [root@c6402 hive-webhcat]# ll /etc/hive-webhcat/
> total 8
> drwxr-xr-x 3 root root 4096 Jul 5 00:49 2.4.2.0-236
> lrwxrwxrwx 1 root root 29 Jul 5 00:49 conf ->
> /etc/hive-webhcat/conf.backup
>
[jira] [Updated] (AMBARI-17557) Hive WebHCat Service Check Fails During Upgrade Due To Missing Configurations Files
[
https://issues.apache.org/jira/browse/AMBARI-17557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-17557:
-
Attachment: AMBARI-17557.patch
> Hive WebHCat Service Check Fails During Upgrade Due To Missing Configurations
> Files
> ---
>
> Key: AMBARI-17557
> URL: https://issues.apache.org/jira/browse/AMBARI-17557
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17557.patch
>
>
> During an upgrade from HDP 2.2 to HDP 2.4, the Hive WebHCat Service Check
> fails several times:
> {code}
> 2016-06-29 02:24:49,660 - Retrying after 5 seconds. Reason: Execution of
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh
> natr66-cuts-c10to25rhel6unsr-10.openstacklocal ambari-qa 50111
> idtest.ambari-qa.1467167063.06.pig no_keytab false kinit no_principal
> /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke Test (pig cmd):
> Failed. : {\"error\":\"Failed to get WebHCatShim\"}http_code <500>
> Templeton Smoke Test (pig cmd): Failed. : {\"error\":\"Failed to get
> WebHCatShim\"}http_code <500>
> {code}
> Caused by:
> {code}
> FATAL | 29 Jun 2016 02:24:36,920 | org.apache.hadoop.conf.Configuration |
> error parsing conf file:/etc/hive-webhcat/conf/webhcat-site.xml
> java.io.FileNotFoundException: /etc/hive-webhcat/conf/webhcat-site.xml (No
> such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.(FileInputStream.java:146)
> at java.io.FileInputStream.(FileInputStream.java:101)
> at
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at java.net.URL.openStream(URL.java:1037)
> at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2342)
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2410)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2376)
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2283)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:888)
> at
> org.apache.hadoop.conf.Configuration.getTrimmed(Configuration.java:907)
> at org.apache.hadoop.conf.Configuration.getLong(Configuration.java:1182)
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:139)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:96)
> at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
> at
> org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
> at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
> at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
> at org.apache.hadoop.mapred.JobClient.init(JobClient.java:485)
> at org.apache.hadoop.mapred.JobClient.(JobClient.java:475)
> at
> org.apache.hadoop.mapred.WebHCatJTShim23$1.run(WebHCatJTShim23.java:60)
> at
> org.apache.hadoop.mapred.WebHCatJTShim23$1.run(WebHCatJTShim23.java:57)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
> at
> org.apache.hadoop.mapred.WebHCatJTShim23.(WebHCatJTShim23.java:57)
> at
> org.apache.hadoop.hive.shims.Hadoop23Shims.getWebHCatShim(Hadoop23Shims.java:500)
> {code}
> The reason for the missing file is that the symlinks are messed up when
> converting HDP 2.2 hard {{/etc/component/conf}} directories to symlinks:
> {code:title=Wrong}
> [root@c6402 hive-webhcat]# ll /etc/hive-webhcat/
> total 8
> drwxr-xr-x 3 root root 4096 Jul 5 00:49 2.4.2.0-236
> lrwxrwxrwx 1 root root 29 Jul 5 00:49 conf ->
> /etc/hive-hcatalog/conf.backup
> drwxr-xr-x 2 hcat hadoop 4096 Jul 4 23:25 conf.backup
> {code}
> {code:title=Right}
> [root@c6402 hive-webhcat]# ll /etc/hive-webhcat/
> total 8
> drwxr-xr-x 3 root root 4096 Jul 5 00:49 2.4.2.0-236
> lrwxrwxrwx 1 root root 29 Jul 5 00:49 conf ->
> /etc/hive-webhcat/conf.backup
>
[jira] [Updated] (AMBARI-17557) Hive WebHCat Service Check Fails During Upgrade Due To Missing Configurations Files
[
https://issues.apache.org/jira/browse/AMBARI-17557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-17557:
-
Description:
During an upgrade from HDP 2.2 to HDP 2.4, the Hive WebHCat Service Check fails
several times:
{code}
2016-06-29 02:24:49,660 - Retrying after 5 seconds. Reason: Execution of
'/var/lib/ambari-agent/tmp/templetonSmoke.sh
natr66-cuts-c10to25rhel6unsr-10.openstacklocal ambari-qa 50111
idtest.ambari-qa.1467167063.06.pig no_keytab false kinit no_principal
/var/lib/ambari-agent/tmp' returned 1. Templeton Smoke Test (pig cmd): Failed.
: {\"error\":\"Failed to get WebHCatShim\"}http_code <500>
Templeton Smoke Test (pig cmd): Failed. : {\"error\":\"Failed to get
WebHCatShim\"}http_code <500>
{code}
Caused by:
{code}
FATAL | 29 Jun 2016 02:24:36,920 | org.apache.hadoop.conf.Configuration | error
parsing conf file:/etc/hive-webhcat/conf/webhcat-site.xml
java.io.FileNotFoundException: /etc/hive-webhcat/conf/webhcat-site.xml (No such
file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:146)
at java.io.FileInputStream.(FileInputStream.java:101)
at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
at java.net.URL.openStream(URL.java:1037)
at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2342)
at
org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2410)
at
org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2376)
at
org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2283)
at org.apache.hadoop.conf.Configuration.get(Configuration.java:888)
at
org.apache.hadoop.conf.Configuration.getTrimmed(Configuration.java:907)
at org.apache.hadoop.conf.Configuration.getLong(Configuration.java:1182)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:139)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:96)
at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
at
org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
at org.apache.hadoop.mapred.JobClient.init(JobClient.java:485)
at org.apache.hadoop.mapred.JobClient.(JobClient.java:475)
at
org.apache.hadoop.mapred.WebHCatJTShim23$1.run(WebHCatJTShim23.java:60)
at
org.apache.hadoop.mapred.WebHCatJTShim23$1.run(WebHCatJTShim23.java:57)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
at
org.apache.hadoop.mapred.WebHCatJTShim23.(WebHCatJTShim23.java:57)
at
org.apache.hadoop.hive.shims.Hadoop23Shims.getWebHCatShim(Hadoop23Shims.java:500)
{code}
The reason for the missing file is that the symlinks are messed up when
converting HDP 2.2 hard {{/etc/component/conf}} directories to symlinks:
{code:title=Wrong}
[root@c6402 hive-webhcat]# ll /etc/hive-webhcat/
total 8
drwxr-xr-x 3 root root 4096 Jul 5 00:49 2.4.2.0-236
lrwxrwxrwx 1 root root 29 Jul 5 00:49 conf ->
/etc/hive-hcatalog/conf.backup
drwxr-xr-x 2 hcat hadoop 4096 Jul 4 23:25 conf.backup
{code}
{code:title=Right}
[root@c6402 hive-webhcat]# ll /etc/hive-webhcat/
total 8
drwxr-xr-x 3 root root 4096 Jul 5 00:49 2.4.2.0-236
lrwxrwxrwx 1 root root 29 Jul 5 00:49 conf -> /etc/hive-webhcat/conf.backup
drwxr-xr-x 2 hcat hadoop 4096 Jul 4 23:25 conf.backup
{code}
was:
During an upgrade from HDP 2.2 to HDP 2.4, the Hive WebHCat Service Check fails
several times:
{code}
2016-06-29 02:24:49,660 - Retrying after 5 seconds. Reason: Execution of
'/var/lib/ambari-agent/tmp/templetonSmoke.sh
natr66-cuts-c10to25rhel6unsr-10.openstacklocal ambari-qa 50111
idtest.ambari-qa.1467167063.06.pig no_keytab false kinit no_principal
/var/lib/ambari-agent/tmp' returned 1. Templeton Smoke Test (pig cmd): Failed.
: {\"error\":\"Failed to get WebHCatShim\"}http_code <500>
Templeton Smoke Test (pig cmd): Failed. : {\"error\":\"Failed to get
WebHCatShim\"}http_code <500>
{code}
Caused by:
{code}
{code}
FATAL | 29 Jun 2016
[jira] [Created] (AMBARI-17557) Hive WebHCat Service Check Fails During Upgrade Due To Missing Configurations Files
Jonathan Hurley created AMBARI-17557:
Summary: Hive WebHCat Service Check Fails During Upgrade Due To
Missing Configurations Files
Key: AMBARI-17557
URL: https://issues.apache.org/jira/browse/AMBARI-17557
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Blocker
Fix For: 2.4.0
During an upgrade from HDP 2.2 to HDP 2.4, the Hive WebHCat Service Check fails
several times:
{code}
2016-06-29 02:24:49,660 - Retrying after 5 seconds. Reason: Execution of
'/var/lib/ambari-agent/tmp/templetonSmoke.sh
natr66-cuts-c10to25rhel6unsr-10.openstacklocal ambari-qa 50111
idtest.ambari-qa.1467167063.06.pig no_keytab false kinit no_principal
/var/lib/ambari-agent/tmp' returned 1. Templeton Smoke Test (pig cmd): Failed.
: {\"error\":\"Failed to get WebHCatShim\"}http_code <500>
Templeton Smoke Test (pig cmd): Failed. : {\"error\":\"Failed to get
WebHCatShim\"}http_code <500>
{code}
Caused by:
{code}
{code}
FATAL | 29 Jun 2016 02:24:36,920 | org.apache.hadoop.conf.Configuration | error
parsing conf file:/etc/hive-webhcat/conf/webhcat-site.xml
java.io.FileNotFoundException: /etc/hive-webhcat/conf/webhcat-site.xml (No such
file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:146)
at java.io.FileInputStream.(FileInputStream.java:101)
at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
at java.net.URL.openStream(URL.java:1037)
at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2342)
at
org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2410)
at
org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2376)
at
org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2283)
at org.apache.hadoop.conf.Configuration.get(Configuration.java:888)
at
org.apache.hadoop.conf.Configuration.getTrimmed(Configuration.java:907)
at org.apache.hadoop.conf.Configuration.getLong(Configuration.java:1182)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:139)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:96)
at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112)
at
org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82)
at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75)
at org.apache.hadoop.mapred.JobClient.init(JobClient.java:485)
at org.apache.hadoop.mapred.JobClient.(JobClient.java:475)
at
org.apache.hadoop.mapred.WebHCatJTShim23$1.run(WebHCatJTShim23.java:60)
at
org.apache.hadoop.mapred.WebHCatJTShim23$1.run(WebHCatJTShim23.java:57)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
at
org.apache.hadoop.mapred.WebHCatJTShim23.(WebHCatJTShim23.java:57)
at
org.apache.hadoop.hive.shims.Hadoop23Shims.getWebHCatShim(Hadoop23Shims.java:500)
{code}
The reason for the missing file is that the symlinks are messed up when
converting HDP 2.2 hard {{/etc/component/conf}} directories to symlinks:
{code:title=Wrong}
[root@c6402 hive-webhcat]# ll /etc/hive-webhcat/
total 8
drwxr-xr-x 3 root root 4096 Jul 5 00:49 2.4.2.0-236
lrwxrwxrwx 1 root root 29 Jul 5 00:49 conf ->
/etc/hive-hcatalog/conf.backup
drwxr-xr-x 2 hcat hadoop 4096 Jul 4 23:25 conf.backup
{code}
{code:title=Right}
[root@c6402 hive-webhcat]# ll /etc/hive-webhcat/
total 8
drwxr-xr-x 3 root root 4096 Jul 5 00:49 2.4.2.0-236
lrwxrwxrwx 1 root root 29 Jul 5 00:49 conf -> /etc/hive-webhcat/conf.backup
drwxr-xr-x 2 hcat hadoop 4096 Jul 4 23:25 conf.backup
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.
[
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361858#comment-15361858
]
Hadoop QA commented on AMBARI-17253:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816089/AMBARI-17253.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7688//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7688//console
This message is automatically generated.
> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17253.1.patch, AMBARI-17253.2.patch,
> AMBARI-17253.3.patch, AMBARI-17253.4.patch, AMBARI-17253.patch
>
>
> There are too many WARNING in ZooKeeper log.
> {code}
> 2016-06-15 21:02:15,405 - WARN
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of
> stream exception
> EndOfStreamException: Unable to read additional data from client sessionid
> 0x0, likely client has closed socket
> at
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> It may be because of Ambari Alert. Ambari Alert pings to the zookeeper port
> to do monitoring.
> We should use 'ruok' to monitor zookeepers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[
https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361813#comment-15361813
]
Hadoop QA commented on AMBARI-16027:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816090/AMBARI-16027.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7687//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7687//console
This message is automatically generated.
> Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
> -
>
> Key: AMBARI-16027
> URL: https://issues.apache.org/jira/browse/AMBARI-16027
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16027.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17556) Add default value for atlas.authentication.method.ldap.type in common services
[ https://issues.apache.org/jira/browse/AMBARI-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-17556: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > Add default value for atlas.authentication.method.ldap.type in common services > -- > > Key: AMBARI-17556 > URL: https://issues.apache.org/jira/browse/AMBARI-17556 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17556.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17554) ambari-server update-host-name failing
[
https://issues.apache.org/jira/browse/AMBARI-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-17554:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.4
> ambari-server update-host-name failing
> --
>
> Key: AMBARI-17554
> URL: https://issues.apache.org/jira/browse/AMBARI-17554
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17554.patch
>
>
> Steps to reproduce :
> 1) Run the following command on one of the hosts (which is not the ambari
> server) in the cluster :
> {code}
> hostname renamedHost-0
> {code}
> 2) On the ambari-server change the host name in the /etc/hosts for the host
> whose name was changed in step1
> 3) Create a file like the following to indicate the host changed :
> {code}
> {
> "cl1" : {
> "renamedHost-0.openstacklocal" :
> "rerenamedhost-0.openstacklocal"
> }
> }
> {code}
> 4) Run ambari-server update-host-name
> The error shown :
> {code}
> 03 Jul 2016 07:24:31,914 INFO [main] Configuration:1022 - Reading password
> from existing file
> 03 Jul 2016 07:24:31,931 INFO [main] Configuration:1491 - Hosts Mapping File
> null
> 03 Jul 2016 07:24:31,932 INFO [main] HostsMap:60 - Using hostsmap file null
> 03 Jul 2016 07:24:32,742 INFO [main] ControllerModule:199 - Detected ORACLE
> as the database type from the JDBC URL
> 03 Jul 2016 07:24:34,884 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher
> 03 Jul 2016 07:24:34,895 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.EmailDispatcher
> 03 Jul 2016 07:24:34,905 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher
> 03 Jul 2016 07:24:38,223 ERROR [main] HostUpdateHelper:545 - Unexpected
> error, host names update failed
> com.google.inject.CreationException: Guice creation errors:
> 1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:324)
> 2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
> at
> org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:525)
> 2 errors
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.apache.ambari.server.update.HostUpdateHelper.main(HostUpdateHelper.java:516)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17554) ambari-server update-host-name failing
[
https://issues.apache.org/jira/browse/AMBARI-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361754#comment-15361754
]
Hadoop QA commented on AMBARI-17554:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816063/AMBARI-17554.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7686//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7686//console
This message is automatically generated.
> ambari-server update-host-name failing
> --
>
> Key: AMBARI-17554
> URL: https://issues.apache.org/jira/browse/AMBARI-17554
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17554.patch
>
>
> Steps to reproduce :
> 1) Run the following command on one of the hosts (which is not the ambari
> server) in the cluster :
> {code}
> hostname renamedHost-0
> {code}
> 2) On the ambari-server change the host name in the /etc/hosts for the host
> whose name was changed in step1
> 3) Create a file like the following to indicate the host changed :
> {code}
> {
> "cl1" : {
> "renamedHost-0.openstacklocal" :
> "rerenamedhost-0.openstacklocal"
> }
> }
> {code}
> 4) Run ambari-server update-host-name
> The error shown :
> {code}
> 03 Jul 2016 07:24:31,914 INFO [main] Configuration:1022 - Reading password
> from existing file
> 03 Jul 2016 07:24:31,931 INFO [main] Configuration:1491 - Hosts Mapping File
> null
> 03 Jul 2016 07:24:31,932 INFO [main] HostsMap:60 - Using hostsmap file null
> 03 Jul 2016 07:24:32,742 INFO [main] ControllerModule:199 - Detected ORACLE
> as the database type from the JDBC URL
> 03 Jul 2016 07:24:34,884 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher
> 03 Jul 2016 07:24:34,895 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.EmailDispatcher
> 03 Jul 2016 07:24:34,905 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher
> 03 Jul 2016 07:24:38,223 ERROR [main] HostUpdateHelper:545 - Unexpected
> error, host names update failed
> com.google.inject.CreationException: Guice creation errors:
> 1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:324)
> 2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
> at
> org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:525)
> 2 errors
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.apache.ambari.server.update.HostUpdateHelper.main(HostUpdateHelper.java:516)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-16027: Status: Patch Available (was: Open) > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-16027: Attachment: AMBARI-16027.patch > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15966) ambari-web 2.2.1 build error
[ https://issues.apache.org/jira/browse/AMBARI-15966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361724#comment-15361724 ] Sriharsha Chintalapani commented on AMBARI-15966: - same issue here node --version v5.9.0 npm --version 3.7.3 brunch version: 2.8.0 > ambari-web 2.2.1 build error > > > Key: AMBARI-15966 > URL: https://issues.apache.org/jira/browse/AMBARI-15966 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: skrho >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > > Hi Everyone~~ > Now I am building the ambari-web 2.2.1 version > My Environment is > npm : 3.8.7 > node : 4.4.3 > brunch : 2.5.3 > I have a problem when building .. > I just command > # $apache-ambari-2.2.1-src/ambari-web]#brunch build -d > There is error message > brunch:config Trying to load brunch-config +0ms > brunch:config Trying to load config +5ms > 19 Apr 08:26:28 - warn: config.files.stylesheets.defaultPaths was removed > 19 Apr 08:26:28 - warn: config.files.templates.defaultPaths was removed > 19 Apr 08:26:28 - error: Initialization error - You probably need to execute > `npm install` to install brunch plugins. SyntaxError: Setter must have > exactly one formal parameter. > at /usr/lib/node_modules/brunch/lib/plugins.js:101:17 > at Array.map (native) > at deps.filter.dependency.map > (/usr/lib/node_modules/brunch/lib/plugins.js:88:8) > at packages.filter.plugins.map.plugin.filter.deps.filter.allPlugins.filter > (/usr/lib/node_modules/brunch/lib/plugins.js:108:19) > at > Object.packages.filter.plugins.map.plugin.filter.deps.filter.exports.init.plugins.filter.map.preCompilers.push.teardownBrunch > [as init] (/usr/lib/node_modules/brunch/lib/plugins.js:131:20) > at /usr/lib/node_modules/brunch/lib/watch.js:101:19 > Please Help me~ > What can I do that? > In advanced Thank you everyone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.
[
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17253:
-
Attachment: AMBARI-17253.4.patch
> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17253.1.patch, AMBARI-17253.2.patch,
> AMBARI-17253.3.patch, AMBARI-17253.4.patch, AMBARI-17253.patch
>
>
> There are too many WARNING in ZooKeeper log.
> {code}
> 2016-06-15 21:02:15,405 - WARN
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of
> stream exception
> EndOfStreamException: Unable to read additional data from client sessionid
> 0x0, likely client has closed socket
> at
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> It may be because of Ambari Alert. Ambari Alert pings to the zookeeper port
> to do monitoring.
> We should use 'ruok' to monitor zookeepers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17516) UI - Customize Atlas Service configs shows incorrect required properties and Next button after toggling type
[ https://issues.apache.org/jira/browse/AMBARI-17516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361688#comment-15361688 ] Hudson commented on AMBARI-17516: - SUCCESS: Integrated in Ambari-trunk-Commit #5222 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5222/]) AMBARI-17516. UI - Customize Atlas Service configs shows incorrect (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=be9da0bff0372ce0a6acf3cc58c3b4a84be6558c]) * ambari-web/app/views/common/configs/widgets/config_widget_view.js * ambari-web/app/models/configs/objects/service_config_property.js * ambari-web/app/models/configs/objects/service_config.js * ambari-web/test/models/configs/objects/service_config_test.js > UI - Customize Atlas Service configs shows incorrect required properties and > Next button after toggling type > > > Key: AMBARI-17516 > URL: https://issues.apache.org/jira/browse/AMBARI-17516 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17516.patch, AMBARI-17516_updated.patch > > > STR: > * Install Ambari 2.4 > * Install HDP 2.5 and attempt to install Atlas > In the smart config section, notice that the default auth type is LDAP and > that several properties are required, so the Next button is disabled. Then > change the auth type to AD and notice that a different set of properties is > required, however, the Next button is now enabled even though those configs > don't have a value. That's a bug. > If you then click proceed and then back button, and then change the auth type > from AD to LDAP, it now shows the required properties for LDAP with "x" > button but the Next button is still enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17349) spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is set to empty
[ https://issues.apache.org/jira/browse/AMBARI-17349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiqing Yang updated AMBARI-17349: -- Attachment: (was: AMBARI-17349_v0.patch) > spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is > set to empty > - > > Key: AMBARI-17349 > URL: https://issues.apache.org/jira/browse/AMBARI-17349 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Yesha Vora > > spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions is set to > empty. > Either spark.driver.extraJavaOptions / spark.yarn.am.extraJavaOptions should > be removed from spark-defaults.conf or it should set to a valid value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17349) spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is set to empty
[ https://issues.apache.org/jira/browse/AMBARI-17349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiqing Yang updated AMBARI-17349: -- Assignee: (was: Weiqing Yang) > spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is > set to empty > - > > Key: AMBARI-17349 > URL: https://issues.apache.org/jira/browse/AMBARI-17349 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Yesha Vora > > spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions is set to > empty. > Either spark.driver.extraJavaOptions / spark.yarn.am.extraJavaOptions should > be removed from spark-defaults.conf or it should set to a valid value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17556) Add default value for atlas.authentication.method.ldap.type in common services
[ https://issues.apache.org/jira/browse/AMBARI-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-17556: --- Status: Patch Available (was: Open) > Add default value for atlas.authentication.method.ldap.type in common services > -- > > Key: AMBARI-17556 > URL: https://issues.apache.org/jira/browse/AMBARI-17556 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17556.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17556) Add default value for atlas.authentication.method.ldap.type in common services
[ https://issues.apache.org/jira/browse/AMBARI-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-17556: --- Attachment: AMBARI-17556.patch > Add default value for atlas.authentication.method.ldap.type in common services > -- > > Key: AMBARI-17556 > URL: https://issues.apache.org/jira/browse/AMBARI-17556 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17556.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17556) Add default value for atlas.authentication.method.ldap.type in common services
Vitaly Brodetskyi created AMBARI-17556: -- Summary: Add default value for atlas.authentication.method.ldap.type in common services Key: AMBARI-17556 URL: https://issues.apache.org/jira/browse/AMBARI-17556 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 2.4.0 . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17553) Configs: Error counter from Settings tab reflects to config category from Advanced tab
[
https://issues.apache.org/jira/browse/AMBARI-17553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361570#comment-15361570
]
Hadoop QA commented on AMBARI-17553:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816058/AMBARI-17553.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7684//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7684//console
This message is automatically generated.
> Configs: Error counter from Settings tab reflects to config category from
> Advanced tab
> --
>
> Key: AMBARI-17553
> URL: https://issues.apache.org/jira/browse/AMBARI-17553
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-17553.patch
>
>
> STR:
> * Install cluster with HDFS, ZooKeeper
> * Go to Services -> HDFS -> Configs -> Settings
> * Clear config NameNode directories, error counter appeared on Settings tab
> * Go to Advanced tab -> NameNode category
> AR: NameNode category has error counter
> ER: NameNode category has no errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17548) Quicklinks combobox is not present for Oozie
[ https://issues.apache.org/jira/browse/AMBARI-17548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361565#comment-15361565 ] Hudson commented on AMBARI-17548: - SUCCESS: Integrated in Ambari-trunk-Commit #5221 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5221/]) AMBARI-17548 Quicklinks combobox is not present for Oozie (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cbe8882fc9e548b08d9985f39d75a83455fb9ab4]) * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/quicklinks/quicklinks.json * ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.3/metainfo.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/OOZIE/quicklinks/quicklinks.json * ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.3/quicklinks/quicklinks.json > Quicklinks combobox is not present for Oozie > > > Key: AMBARI-17548 > URL: https://issues.apache.org/jira/browse/AMBARI-17548 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17548.patch > > > Quicklinks combobox is not present for Oozie -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17528) Fix Logfeeder visibilities
[ https://issues.apache.org/jira/browse/AMBARI-17528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361567#comment-15361567 ] Hudson commented on AMBARI-17528: - SUCCESS: Integrated in Ambari-trunk-Commit #5221 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5221/]) AMBARI-17528. Fix Logfeeder visibilities (Miklos Gergely via oleewere) (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=57b795dbc0657d49237433d2c2c7cc9369bfa958]) * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/ConfigBlock.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/reader/GZIPReader.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/Filter.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/FilterKeyValue.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/Input.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/OutputMgr.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/mapper/MapperDate.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/InputMgr.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/mapper/MapperFieldName.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/AliasUtil.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeederAMSClient.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/FilterGrok.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/Output.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeederUtil.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeeder.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/logconfig/FetchConfigFromSolr.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/mapper/Mapper.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/InputS3File.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/logconfig/filter/DefaultDataFilter.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/InputFile.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/SolrUtil.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/mapper/MapperFieldValue.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/MetricsMgr.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/logconfig/filter/ApplyLogFilter.java > Fix Logfeeder visibilities > -- > > Key: AMBARI-17528 > URL: https://issues.apache.org/jira/browse/AMBARI-17528 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-17528.patch > > > Many variables/functions have a broader visibility than needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17549) Client Install Failed icon appears even after reinstall
[ https://issues.apache.org/jira/browse/AMBARI-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361566#comment-15361566 ] Hudson commented on AMBARI-17549: - SUCCESS: Integrated in Ambari-trunk-Commit #5221 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5221/]) AMBARI-17549 Client Install Failed icon appears even after reinstall. (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7d2134bf9f579c6886b04e76b8fc55285c61d3c5]) * ambari-web/app/views/main/host/summary.js * ambari-web/test/views/main/host/summary_test.js > Client Install Failed icon appears even after reinstall > --- > > Key: AMBARI-17549 > URL: https://issues.apache.org/jira/browse/AMBARI-17549 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-17549.patch > > > When client has status install failed, special icon is appeared beside it's > name. And this icon doesn't disappear even after successful reinstall. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17516) UI - Customize Atlas Service configs shows incorrect required properties and Next button after toggling type
[ https://issues.apache.org/jira/browse/AMBARI-17516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-17516: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.4 > UI - Customize Atlas Service configs shows incorrect required properties and > Next button after toggling type > > > Key: AMBARI-17516 > URL: https://issues.apache.org/jira/browse/AMBARI-17516 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17516.patch, AMBARI-17516_updated.patch > > > STR: > * Install Ambari 2.4 > * Install HDP 2.5 and attempt to install Atlas > In the smart config section, notice that the default auth type is LDAP and > that several properties are required, so the Next button is disabled. Then > change the auth type to AD and notice that a different set of properties is > required, however, the Next button is now enabled even though those configs > don't have a value. That's a bug. > If you then click proceed and then back button, and then change the auth type > from AD to LDAP, it now shows the required properties for LDAP with "x" > button but the Next button is still enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17555) true was removed from stack definition
[ https://issues.apache.org/jira/browse/AMBARI-17555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17555: Affects Version/s: 2.4.0 > true was removed from stack definition > - > > Key: AMBARI-17555 > URL: https://issues.apache.org/jira/browse/AMBARI-17555 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.4.0 > > Attachments: AMBARI-17555.patch > > > As of now, delete=false directive of on-ambari-upgrade is used to indicate > that properties are no longer available. > We should bring back true. This is a directive for stack > inheritance. on-ambari-upgrade should only be used to indicate what happens > on ambari upgrade. > Also, I do not think there is any property as of now that needs to be deleted > during ambari upgrade. So on-ambari-upgrade directives should have > delete=false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17555) true was removed from stack definition
[ https://issues.apache.org/jira/browse/AMBARI-17555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17555: Fix Version/s: 2.4.0 > true was removed from stack definition > - > > Key: AMBARI-17555 > URL: https://issues.apache.org/jira/browse/AMBARI-17555 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.4.0 > > Attachments: AMBARI-17555.patch > > > As of now, delete=false directive of on-ambari-upgrade is used to indicate > that properties are no longer available. > We should bring back true. This is a directive for stack > inheritance. on-ambari-upgrade should only be used to indicate what happens > on ambari upgrade. > Also, I do not think there is any property as of now that needs to be deleted > during ambari upgrade. So on-ambari-upgrade directives should have > delete=false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17555) true was removed from stack definition
Dmitry Lysnichenko created AMBARI-17555: --- Summary: true was removed from stack definition Key: AMBARI-17555 URL: https://issues.apache.org/jira/browse/AMBARI-17555 Project: Ambari Issue Type: Bug Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Attachments: AMBARI-17555.patch As of now, delete=false directive of on-ambari-upgrade is used to indicate that properties are no longer available. We should bring back true. This is a directive for stack inheritance. on-ambari-upgrade should only be used to indicate what happens on ambari upgrade. Also, I do not think there is any property as of now that needs to be deleted during ambari upgrade. So on-ambari-upgrade directives should have delete=false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17555) true was removed from stack definition
[ https://issues.apache.org/jira/browse/AMBARI-17555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17555: Component/s: ambari-server > true was removed from stack definition > - > > Key: AMBARI-17555 > URL: https://issues.apache.org/jira/browse/AMBARI-17555 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.4.0 > > Attachments: AMBARI-17555.patch > > > As of now, delete=false directive of on-ambari-upgrade is used to indicate > that properties are no longer available. > We should bring back true. This is a directive for stack > inheritance. on-ambari-upgrade should only be used to indicate what happens > on ambari upgrade. > Also, I do not think there is any property as of now that needs to be deleted > during ambari upgrade. So on-ambari-upgrade directives should have > delete=false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17555) true was removed from stack definition
[ https://issues.apache.org/jira/browse/AMBARI-17555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17555: Attachment: AMBARI-17555.patch > true was removed from stack definition > - > > Key: AMBARI-17555 > URL: https://issues.apache.org/jira/browse/AMBARI-17555 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.4.0 > > Attachments: AMBARI-17555.patch > > > As of now, delete=false directive of on-ambari-upgrade is used to indicate > that properties are no longer available. > We should bring back true. This is a directive for stack > inheritance. on-ambari-upgrade should only be used to indicate what happens > on ambari upgrade. > Also, I do not think there is any property as of now that needs to be deleted > during ambari upgrade. So on-ambari-upgrade directives should have > delete=false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17555) true was removed from stack definition
[ https://issues.apache.org/jira/browse/AMBARI-17555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17555: Status: Patch Available (was: Open) > true was removed from stack definition > - > > Key: AMBARI-17555 > URL: https://issues.apache.org/jira/browse/AMBARI-17555 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Attachments: AMBARI-17555.patch > > > As of now, delete=false directive of on-ambari-upgrade is used to indicate > that properties are no longer available. > We should bring back true. This is a directive for stack > inheritance. on-ambari-upgrade should only be used to indicate what happens > on ambari upgrade. > Also, I do not think there is any property as of now that needs to be deleted > during ambari upgrade. So on-ambari-upgrade directives should have > delete=false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17552) 'Restart all' services fails due to dependency on other service components
[
https://issues.apache.org/jira/browse/AMBARI-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361527#comment-15361527
]
Hadoop QA commented on AMBARI-17552:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816052/AMBARI-17552.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7682//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7682//console
This message is automatically generated.
> 'Restart all' services fails due to dependency on other service components
> --
>
> Key: AMBARI-17552
> URL: https://issues.apache.org/jira/browse/AMBARI-17552
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17552.patch
>
>
> Looks like we have a dependency mechanism in place due to which the newly
> added "Restart all Services" operation does not work as expected in some cases
> Here is my scenario:
> 1. Deploy a cluster (HDP-2.4.2.0) with core services (HDFS, YARN, ZK, MR) and
> Ambari-2.4.0.0 (ambari-server-2.4.0.0-680.x86_64)
> 2. Add Spark, Hive, Tez, Pig to the cluster and let it finish
> 3. At the end of service addition, there is an icon against HDFS, YARN, MR
> indicating these three services need restart
> 4. Try 'Restart all Required' operation
> Result:
> Failures at ATS start, which aborts the whole restart operation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17554) ambari-server update-host-name failing
[
https://issues.apache.org/jira/browse/AMBARI-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-17554:
---
Attachment: AMBARI-17554.patch
> ambari-server update-host-name failing
> --
>
> Key: AMBARI-17554
> URL: https://issues.apache.org/jira/browse/AMBARI-17554
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17554.patch
>
>
> Steps to reproduce :
> 1) Run the following command on one of the hosts (which is not the ambari
> server) in the cluster :
> {code}
> hostname renamedHost-0
> {code}
> 2) On the ambari-server change the host name in the /etc/hosts for the host
> whose name was changed in step1
> 3) Create a file like the following to indicate the host changed :
> {code}
> {
> "cl1" : {
> "renamedHost-0.openstacklocal" :
> "rerenamedhost-0.openstacklocal"
> }
> }
> {code}
> 4) Run ambari-server update-host-name
> The error shown :
> {code}
> 03 Jul 2016 07:24:31,914 INFO [main] Configuration:1022 - Reading password
> from existing file
> 03 Jul 2016 07:24:31,931 INFO [main] Configuration:1491 - Hosts Mapping File
> null
> 03 Jul 2016 07:24:31,932 INFO [main] HostsMap:60 - Using hostsmap file null
> 03 Jul 2016 07:24:32,742 INFO [main] ControllerModule:199 - Detected ORACLE
> as the database type from the JDBC URL
> 03 Jul 2016 07:24:34,884 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher
> 03 Jul 2016 07:24:34,895 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.EmailDispatcher
> 03 Jul 2016 07:24:34,905 INFO [main] ControllerModule:607 - Binding and
> registering notification dispatcher class
> org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher
> 03 Jul 2016 07:24:38,223 ERROR [main] HostUpdateHelper:545 - Unexpected
> error, host names update failed
> com.google.inject.CreationException: Guice creation errors:
> 1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
> at
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:324)
> 2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
> while locating org.apache.ambari.server.audit.AuditLogger
> for field at
> org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
> at
> org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:525)
> 2 errors
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.apache.ambari.server.update.HostUpdateHelper.main(HostUpdateHelper.java:516)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17554) ambari-server update-host-name failing
Vitaly Brodetskyi created AMBARI-17554:
--
Summary: ambari-server update-host-name failing
Key: AMBARI-17554
URL: https://issues.apache.org/jira/browse/AMBARI-17554
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
Fix For: 2.4.0
Steps to reproduce :
1) Run the following command on one of the hosts (which is not the ambari
server) in the cluster :
{code}
hostname renamedHost-0
{code}
2) On the ambari-server change the host name in the /etc/hosts for the host
whose name was changed in step1
3) Create a file like the following to indicate the host changed :
{code}
{
"cl1" : {
"renamedHost-0.openstacklocal" :
"rerenamedhost-0.openstacklocal"
}
}
{code}
4) Run ambari-server update-host-name
The error shown :
{code}
03 Jul 2016 07:24:31,914 INFO [main] Configuration:1022 - Reading password
from existing file
03 Jul 2016 07:24:31,931 INFO [main] Configuration:1491 - Hosts Mapping File
null
03 Jul 2016 07:24:31,932 INFO [main] HostsMap:60 - Using hostsmap file null
03 Jul 2016 07:24:32,742 INFO [main] ControllerModule:199 - Detected ORACLE as
the database type from the JDBC URL
03 Jul 2016 07:24:34,884 INFO [main] ControllerModule:607 - Binding and
registering notification dispatcher class
org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher
03 Jul 2016 07:24:34,895 INFO [main] ControllerModule:607 - Binding and
registering notification dispatcher class
org.apache.ambari.server.notifications.dispatchers.EmailDispatcher
03 Jul 2016 07:24:34,905 INFO [main] ControllerModule:607 - Binding and
registering notification dispatcher class
org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher
03 Jul 2016 07:24:38,223 ERROR [main] HostUpdateHelper:545 - Unexpected error,
host names update failed
com.google.inject.CreationException: Guice creation errors:
1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
while locating org.apache.ambari.server.audit.AuditLogger
for field at
org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
at
org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:324)
2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
while locating org.apache.ambari.server.audit.AuditLogger
for field at
org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
at
org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:525)
2 errors
at
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
at
com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
at
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
at com.google.inject.Guice.createInjector(Guice.java:95)
at com.google.inject.Guice.createInjector(Guice.java:72)
at com.google.inject.Guice.createInjector(Guice.java:62)
at
org.apache.ambari.server.update.HostUpdateHelper.main(HostUpdateHelper.java:516)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17553) Configs: Error counter from Settings tab reflects to config category from Advanced tab
[ https://issues.apache.org/jira/browse/AMBARI-17553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361476#comment-15361476 ] Aleksandr Kovalenko commented on AMBARI-17553: -- +1 for the patch > Configs: Error counter from Settings tab reflects to config category from > Advanced tab > -- > > Key: AMBARI-17553 > URL: https://issues.apache.org/jira/browse/AMBARI-17553 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-17553.patch > > > STR: > * Install cluster with HDFS, ZooKeeper > * Go to Services -> HDFS -> Configs -> Settings > * Clear config NameNode directories, error counter appeared on Settings tab > * Go to Advanced tab -> NameNode category > AR: NameNode category has error counter > ER: NameNode category has no errors -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17553) Configs: Error counter from Settings tab reflects to config category from Advanced tab
[ https://issues.apache.org/jira/browse/AMBARI-17553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361472#comment-15361472 ] Andrii Tkach commented on AMBARI-17553: --- 28941 tests complete (26 seconds) 154 tests pending > Configs: Error counter from Settings tab reflects to config category from > Advanced tab > -- > > Key: AMBARI-17553 > URL: https://issues.apache.org/jira/browse/AMBARI-17553 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-17553.patch > > > STR: > * Install cluster with HDFS, ZooKeeper > * Go to Services -> HDFS -> Configs -> Settings > * Clear config NameNode directories, error counter appeared on Settings tab > * Go to Advanced tab -> NameNode category > AR: NameNode category has error counter > ER: NameNode category has no errors -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17553) Configs: Error counter from Settings tab reflects to config category from Advanced tab
[ https://issues.apache.org/jira/browse/AMBARI-17553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-17553: -- Attachment: AMBARI-17553.patch > Configs: Error counter from Settings tab reflects to config category from > Advanced tab > -- > > Key: AMBARI-17553 > URL: https://issues.apache.org/jira/browse/AMBARI-17553 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-17553.patch > > > STR: > * Install cluster with HDFS, ZooKeeper > * Go to Services -> HDFS -> Configs -> Settings > * Clear config NameNode directories, error counter appeared on Settings tab > * Go to Advanced tab -> NameNode category > AR: NameNode category has error counter > ER: NameNode category has no errors -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17553) Configs: Error counter from Settings tab reflects to config category from Advanced tab
[ https://issues.apache.org/jira/browse/AMBARI-17553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-17553: -- Status: Patch Available (was: Open) > Configs: Error counter from Settings tab reflects to config category from > Advanced tab > -- > > Key: AMBARI-17553 > URL: https://issues.apache.org/jira/browse/AMBARI-17553 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-17553.patch > > > STR: > * Install cluster with HDFS, ZooKeeper > * Go to Services -> HDFS -> Configs -> Settings > * Clear config NameNode directories, error counter appeared on Settings tab > * Go to Advanced tab -> NameNode category > AR: NameNode category has error counter > ER: NameNode category has no errors -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17553) Configs: Error counter from Settings tab reflects to config category from Advanced tab
Andrii Tkach created AMBARI-17553: - Summary: Configs: Error counter from Settings tab reflects to config category from Advanced tab Key: AMBARI-17553 URL: https://issues.apache.org/jira/browse/AMBARI-17553 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.4.0 STR: * Install cluster with HDFS, ZooKeeper * Go to Services -> HDFS -> Configs -> Settings * Clear config NameNode directories, error counter appeared on Settings tab * Go to Advanced tab -> NameNode category AR: NameNode category has error counter ER: NameNode category has no errors -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17445) Storm metrics sink: expand metrics name to contain additional informations
[
https://issues.apache.org/jira/browse/AMBARI-17445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361448#comment-15361448
]
Hadoop QA commented on AMBARI-17445:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816032/AMBARI-17445-v4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-metrics/ambari-metrics-storm-sink
ambari-metrics/ambari-metrics-storm-sink-legacy.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7680//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7680//console
This message is automatically generated.
> Storm metrics sink: expand metrics name to contain additional informations
> --
>
> Key: AMBARI-17445
> URL: https://issues.apache.org/jira/browse/AMBARI-17445
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Attachments: AMBARI-17445-changes.png, AMBARI-17445-v1.patch,
> AMBARI-17445-v2.patch, AMBARI-17445-v3.patch, AMBARI-17445-v4.patch
>
>
> With AMBARI-16946 we expanded metric name to have component name, task id,
> and key when type of metric value is Map. Topology name was placed to appId.
> While talking with [~prajwal] and [~harsha_ch], we found that we should move
> out all necessary informations like topology name, worker host, worker port
> to metric name so that they can be templatized.
> This also supercedes AMBARI-17249 since all metrics will include worker host
> and worker port to metric name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17516) UI - Customize Atlas Service configs shows incorrect required properties and Next button after toggling type
[ https://issues.apache.org/jira/browse/AMBARI-17516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-17516: - Status: Patch Available (was: Reopened) > UI - Customize Atlas Service configs shows incorrect required properties and > Next button after toggling type > > > Key: AMBARI-17516 > URL: https://issues.apache.org/jira/browse/AMBARI-17516 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17516.patch, AMBARI-17516_updated.patch > > > STR: > * Install Ambari 2.4 > * Install HDP 2.5 and attempt to install Atlas > In the smart config section, notice that the default auth type is LDAP and > that several properties are required, so the Next button is disabled. Then > change the auth type to AD and notice that a different set of properties is > required, however, the Next button is now enabled even though those configs > don't have a value. That's a bug. > If you then click proceed and then back button, and then change the auth type > from AD to LDAP, it now shows the required properties for LDAP with "x" > button but the Next button is still enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17516) UI - Customize Atlas Service configs shows incorrect required properties and Next button after toggling type
[ https://issues.apache.org/jira/browse/AMBARI-17516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-17516: - Attachment: AMBARI-17516_updated.patch > UI - Customize Atlas Service configs shows incorrect required properties and > Next button after toggling type > > > Key: AMBARI-17516 > URL: https://issues.apache.org/jira/browse/AMBARI-17516 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17516.patch, AMBARI-17516_updated.patch > > > STR: > * Install Ambari 2.4 > * Install HDP 2.5 and attempt to install Atlas > In the smart config section, notice that the default auth type is LDAP and > that several properties are required, so the Next button is disabled. Then > change the auth type to AD and notice that a different set of properties is > required, however, the Next button is now enabled even though those configs > don't have a value. That's a bug. > If you then click proceed and then back button, and then change the auth type > from AD to LDAP, it now shows the required properties for LDAP with "x" > button but the Next button is still enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17550) While changing NN, DN directories from UI, proper warning should be present for invalid values
[
https://issues.apache.org/jira/browse/AMBARI-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361430#comment-15361430
]
Hadoop QA commented on AMBARI-17550:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816043/AMBARI-17550.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7679//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7679//console
This message is automatically generated.
> While changing NN, DN directories from UI, proper warning should be present
> for invalid values
> --
>
> Key: AMBARI-17550
> URL: https://issues.apache.org/jira/browse/AMBARI-17550
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17550.patch
>
>
> While changing NN and DN directories from ambari, for example:
> changing dn directories from **/grid/0/hadoop/hdfs/data** to **/grid/0/hadoop/
> hdfs/data,/grid/0/hadoop/hdfs/data1,/grid/0/hadoop/hdfs/data2**
> The values are changed without being validated
> This leads to datanodes start failing
>
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py",
> line 174, in
> DataNode().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 709, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py",
> line 60, in start
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py",
> line 55, in configure
> datanode(action="configure")
> File
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_datanode.py",
> line 53, in datanode
> data_dir_to_mount_file_content = handle_mounted_dirs(create_dirs,
> params.dfs_data_dirs, params.data_dir_mount_file, params)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/mounted_dirs_helper.py",
> line 158, in handle_mounted_dirs
> raise Fail(message + " . Please turn off
> cluster-env/one_dir_per_partition or handle the situation manually.")
> resource_management.core.exceptions.Fail: Trying to create another
> directory on the following mount: /grid/0 . Please turn off
> cluster-env/one_dir_per_partition or handle the situation manually.
>
> The test fails because it set invalid value, and the directory was not
> created
> A warning message informing why the new directory name is invalid could be
> useful
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17541) LogSearch should also show audit logs from Apache Ranger Solr
[ https://issues.apache.org/jira/browse/AMBARI-17541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361412#comment-15361412 ] Hudson commented on AMBARI-17541: - ABORTED: Integrated in Ambari-trunk-Commit #5220 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5220/]) AMBARI-17541. LogSearch should also show audit logs from Apache Ranger (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ea07c34140d7394ec694bc71273a89c237e815de]) * ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/dao/SolrDaoBase.java * ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/dao/AuditSolrDao.java > LogSearch should also show audit logs from Apache Ranger Solr > - > > Key: AMBARI-17541 > URL: https://issues.apache.org/jira/browse/AMBARI-17541 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Don Bosco Durai >Assignee: Don Bosco Durai > Fix For: 2.4.0 > > > Currently, LogSearch parses HDFS and Ambari audit logs. Since Ranger is > already logging audits for other components, it would be good to show them > also in the same AccessLogs tab -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17046) Support loading of logs to HDFS
[ https://issues.apache.org/jira/browse/AMBARI-17046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361413#comment-15361413 ] Hudson commented on AMBARI-17046: - ABORTED: Integrated in Ambari-trunk-Commit #5220 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5220/]) AMBARI-17046. Support loading logs to HDFS (Hayat Behlim via oleewere) (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=196657bf37bfd462df11d092d831fbd975fdc777]) * ambari-logsearch/pom.xml * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/DateUtil.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/ConfigBlock.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/LogfeederHDFSUtil.java * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputHDFSFile.java * ambari-logsearch/ambari-logsearch-logfeeder/src/test/resources/samples/config/output-hdfs-config.json * ambari-logsearch/ambari-logsearch-logfeeder/pom.xml * ambari-logsearch/ambari-logsearch-logfeeder/src/main/resources/alias_config.json * ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeeder.java > Support loading of logs to HDFS > --- > > Key: AMBARI-17046 > URL: https://issues.apache.org/jira/browse/AMBARI-17046 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Don Bosco Durai >Assignee: Dharmesh Makwana > Fix For: 2.4.0 > > > Support option to copy logs to HDFS so it can be stored for longer duration > and analyzed offline. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm
[ https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361414#comment-15361414 ] Hudson commented on AMBARI-17080: - ABORTED: Integrated in Ambari-trunk-Commit #5220 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5220/]) AMBARI-17080 Support Storm 1.0 in Ambari Metrics for Storm (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5295a0e5e8f74c0a7f0c2a1f11a72363b35ba23f]) * ambari-server/src/main/resources/common-services/STORM/0.9.1/package/templates/storm-metrics2.properties.j2 * ambari-metrics/ambari-metrics-storm-sink/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java * ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java * ambari-metrics/ambari-metrics-storm-sink/src/main/conf/storm-metrics2.properties.j2 * ambari-metrics/ambari-metrics-assembly/src/main/assembly/sink-windows.xml * ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/storm.py * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/storm-site.xml * ambari-metrics/ambari-metrics-common/pom.xml * ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py * ambari-metrics/ambari-metrics-storm-sink-legacy/pom.xml * ambari-metrics/pom.xml * ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/NumberUtil.java * ambari-server/src/main/resources/stacks/HDP/2.5/services/STORM/configuration/storm-site.xml * ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/ui_server.py * ambari-metrics/ambari-metrics-storm-sink-legacy/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java * ambari-server/src/test/python/stacks/2.1/STORM/test_storm_nimbus.py * ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java * ambari-server/src/test/python/stacks/2.1/STORM/test_storm_ui_server.py * ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java * ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/assemblies/empty.xml * ambari-metrics/ambari-metrics-assembly/pom.xml * ambari-metrics/ambari-metrics-assembly/src/main/assembly/sink.xml * ambari-metrics/ambari-metrics-storm-sink/pom.xml * ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java > Support Storm 1.0 in Ambari Metrics for Storm > - > > Key: AMBARI-17080 > URL: https://issues.apache.org/jira/browse/AMBARI-17080 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-17080-trunk_6.patch, AMBARI-17080-v1.patch, > AMBARI-17080-v2.patch, AMBARI-17080-v3.patch > > > Since there was package name change on Apache Storm 1.0.0, Ambari Metrics > Reporter / Sink for Storm will not work when Ambari supports Apache Storm > 1.0.0 or upper. > This issue is for addressing this. > Please note that it will incur compile failure unless Ambari Metrics pom file > depends on Storm 1.x version, so decision for version of Storm should be made > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17552) 'Restart all' services fails due to dependency on other service components
[ https://issues.apache.org/jira/browse/AMBARI-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17552: Attachment: AMBARI-17552.patch > 'Restart all' services fails due to dependency on other service components > -- > > Key: AMBARI-17552 > URL: https://issues.apache.org/jira/browse/AMBARI-17552 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17552.patch > > > Looks like we have a dependency mechanism in place due to which the newly > added "Restart all Services" operation does not work as expected in some cases > Here is my scenario: > 1. Deploy a cluster (HDP-2.4.2.0) with core services (HDFS, YARN, ZK, MR) and > Ambari-2.4.0.0 (ambari-server-2.4.0.0-680.x86_64) > 2. Add Spark, Hive, Tez, Pig to the cluster and let it finish > 3. At the end of service addition, there is an icon against HDFS, YARN, MR > indicating these three services need restart > 4. Try 'Restart all Required' operation > Result: > Failures at ATS start, which aborts the whole restart operation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17552) 'Restart all' services fails due to dependency on other service components
[ https://issues.apache.org/jira/browse/AMBARI-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17552: Status: Patch Available (was: Open) > 'Restart all' services fails due to dependency on other service components > -- > > Key: AMBARI-17552 > URL: https://issues.apache.org/jira/browse/AMBARI-17552 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17552.patch > > > Looks like we have a dependency mechanism in place due to which the newly > added "Restart all Services" operation does not work as expected in some cases > Here is my scenario: > 1. Deploy a cluster (HDP-2.4.2.0) with core services (HDFS, YARN, ZK, MR) and > Ambari-2.4.0.0 (ambari-server-2.4.0.0-680.x86_64) > 2. Add Spark, Hive, Tez, Pig to the cluster and let it finish > 3. At the end of service addition, there is an icon against HDFS, YARN, MR > indicating these three services need restart > 4. Try 'Restart all Required' operation > Result: > Failures at ATS start, which aborts the whole restart operation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17549) Client Install Failed icon appears even after reinstall
[
https://issues.apache.org/jira/browse/AMBARI-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361405#comment-15361405
]
Hadoop QA commented on AMBARI-17549:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816040/AMBARI-17549.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7678//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7678//console
This message is automatically generated.
> Client Install Failed icon appears even after reinstall
> ---
>
> Key: AMBARI-17549
> URL: https://issues.apache.org/jira/browse/AMBARI-17549
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17549.patch
>
>
> When client has status install failed, special icon is appeared beside it's
> name. And this icon doesn't disappear even after successful reinstall.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17549) Client Install Failed icon appears even after reinstall
[ https://issues.apache.org/jira/browse/AMBARI-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17549: - Resolution: Fixed Status: Resolved (was: Patch Available) > Client Install Failed icon appears even after reinstall > --- > > Key: AMBARI-17549 > URL: https://issues.apache.org/jira/browse/AMBARI-17549 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-17549.patch > > > When client has status install failed, special icon is appeared beside it's > name. And this icon doesn't disappear even after successful reinstall. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14849) Support HBase REST gateway
[ https://issues.apache.org/jira/browse/AMBARI-14849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14849: Description: Currently admin has to use command line to start HBase REST gateway. Support for starting REST gateway through Ambari should be added. This would make operations involving REST gateway more user friendly. was: Currently admin has to use command line to start HBase REST gateway. Support for starting REST gateway through Ambari should be added. This would make operations involving REST gateway more user friendly. > Support HBase REST gateway > -- > > Key: AMBARI-14849 > URL: https://issues.apache.org/jira/browse/AMBARI-14849 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > Currently admin has to use command line to start HBase REST gateway. > Support for starting REST gateway through Ambari should be added. > This would make operations involving REST gateway more user friendly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17549) Client Install Failed icon appears even after reinstall
[ https://issues.apache.org/jira/browse/AMBARI-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361401#comment-15361401 ] Aleksandr Kovalenko commented on AMBARI-17549: -- committed to trunk > Client Install Failed icon appears even after reinstall > --- > > Key: AMBARI-17549 > URL: https://issues.apache.org/jira/browse/AMBARI-17549 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-17549.patch > > > When client has status install failed, special icon is appeared beside it's > name. And this icon doesn't disappear even after successful reinstall. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16278) Give more time for HBase system tables to be assigned
[ https://issues.apache.org/jira/browse/AMBARI-16278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-16278: Description: We have observed extended cluster downtime due to HBase system tables not being assigned at cluster start up. The default values for the following two parameters are too low: hbase.regionserver.executor.openregion.threads (default: 3) hbase.master.namespace.init.timeout (default: 30) We set hbase.regionserver.executor.openregion.threads=200 and hbase.master.namespace.init.timeout=240 in some case to work around HBASE-14190. Ambari can use 20 for hbase.regionserver.executor.openregion.threads and 240 for hbase.master.namespace.init.timeout as default value. was: We have observed extended cluster downtime due to HBase system tables not being assigned at cluster start up. The default values for the following two parameters are too low: hbase.regionserver.executor.openregion.threads (default: 3) hbase.master.namespace.init.timeout (default: 30) We set hbase.regionserver.executor.openregion.threads=200 and hbase.master.namespace.init.timeout=240 in some case to work around HBASE-14190. Ambari can use 20 for hbase.regionserver.executor.openregion.threads and 240 for hbase.master.namespace.init.timeout as default value. > Give more time for HBase system tables to be assigned > - > > Key: AMBARI-16278 > URL: https://issues.apache.org/jira/browse/AMBARI-16278 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > We have observed extended cluster downtime due to HBase system tables not > being assigned at cluster start up. > The default values for the following two parameters are too low: > hbase.regionserver.executor.openregion.threads (default: 3) > hbase.master.namespace.init.timeout (default: 30) > We set hbase.regionserver.executor.openregion.threads=200 and > hbase.master.namespace.init.timeout=240 in some case to work around > HBASE-14190. > Ambari can use 20 for hbase.regionserver.executor.openregion.threads and > 240 for hbase.master.namespace.init.timeout as default value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17346) Dependent components should be shutdown before stopping hdfs
[ https://issues.apache.org/jira/browse/AMBARI-17346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-17346: Description: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. was: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. > Dependent components should be shutdown before stopping hdfs > > > Key: AMBARI-17346 > URL: https://issues.apache.org/jira/browse/AMBARI-17346 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu > > Sometimes admin shuts down hdfs first, then hbase. > By the time hbase is shutdown, no data can be persisted (including metadata). > This results in large number of inconsistencies when hbase cluster is brought > back up. > Before hdfs is shutdown, the components dependent on hdfs should be shutdown > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17549) Client Install Failed icon appears even after reinstall
[
https://issues.apache.org/jira/browse/AMBARI-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361380#comment-15361380
]
Hadoop QA commented on AMBARI-17549:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816040/AMBARI-17549.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7677//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7677//console
This message is automatically generated.
> Client Install Failed icon appears even after reinstall
> ---
>
> Key: AMBARI-17549
> URL: https://issues.apache.org/jira/browse/AMBARI-17549
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17549.patch
>
>
> When client has status install failed, special icon is appeared beside it's
> name. And this icon doesn't disappear even after successful reinstall.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17551) AssignSlaves page doesnt let choose NodeManager evethough it complaints to add atleast one
[
https://issues.apache.org/jira/browse/AMBARI-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361346#comment-15361346
]
Hadoop QA commented on AMBARI-17551:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816048/AMBARI-17551.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7676//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7676//console
This message is automatically generated.
> AssignSlaves page doesnt let choose NodeManager evethough it complaints to
> add atleast one
> --
>
> Key: AMBARI-17551
> URL: https://issues.apache.org/jira/browse/AMBARI-17551
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: Screen Shot 2016-06-30 at 2.53.48 PM.png, pic1.png
>
>
> - Had a single node cluster with HDFS,YARN,MR and Zookeeper
> - Try to add service Ambari Metrics
> - Right after clicking Next on AssignMasters Page there comes a popup in
> AssignSlaves page that there is an issue with slaves assignment (pic1.png)
> - Click Cancel on warning and check the details. Issue was:
> {code}
> At least 1 NodeManager components should be installed in cluster.
> {code}
> Try to choose NodeManager checkbox. But its disabled. User can still proceed
> by clicking Next and Continue Anyway. But the issue showed in popup and
> NodeManager checkbox being disabled doesnt look right
> Could you please take a look at this scenario
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17551) AssignSlaves page doesnt let choose NodeManager evethough it complaints to add atleast one
[
https://issues.apache.org/jira/browse/AMBARI-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-17551:
--
Attachment: (was: AMBARI-17551.patch)
> AssignSlaves page doesnt let choose NodeManager evethough it complaints to
> add atleast one
> --
>
> Key: AMBARI-17551
> URL: https://issues.apache.org/jira/browse/AMBARI-17551
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: Screen Shot 2016-06-30 at 2.53.48 PM.png, pic1.png
>
>
> - Had a single node cluster with HDFS,YARN,MR and Zookeeper
> - Try to add service Ambari Metrics
> - Right after clicking Next on AssignMasters Page there comes a popup in
> AssignSlaves page that there is an issue with slaves assignment (pic1.png)
> - Click Cancel on warning and check the details. Issue was:
> {code}
> At least 1 NodeManager components should be installed in cluster.
> {code}
> Try to choose NodeManager checkbox. But its disabled. User can still proceed
> by clicking Next and Continue Anyway. But the issue showed in popup and
> NodeManager checkbox being disabled doesnt look right
> Could you please take a look at this scenario
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17551) AssignSlaves page doesnt let choose NodeManager evethough it complaints to add atleast one
[
https://issues.apache.org/jira/browse/AMBARI-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-17551:
--
Status: Open (was: Patch Available)
> AssignSlaves page doesnt let choose NodeManager evethough it complaints to
> add atleast one
> --
>
> Key: AMBARI-17551
> URL: https://issues.apache.org/jira/browse/AMBARI-17551
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: Screen Shot 2016-06-30 at 2.53.48 PM.png, pic1.png
>
>
> - Had a single node cluster with HDFS,YARN,MR and Zookeeper
> - Try to add service Ambari Metrics
> - Right after clicking Next on AssignMasters Page there comes a popup in
> AssignSlaves page that there is an issue with slaves assignment (pic1.png)
> - Click Cancel on warning and check the details. Issue was:
> {code}
> At least 1 NodeManager components should be installed in cluster.
> {code}
> Try to choose NodeManager checkbox. But its disabled. User can still proceed
> by clicking Next and Continue Anyway. But the issue showed in popup and
> NodeManager checkbox being disabled doesnt look right
> Could you please take a look at this scenario
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17551) AssignSlaves page doesnt let choose NodeManager evethough it complaints to add atleast one
[
https://issues.apache.org/jira/browse/AMBARI-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361327#comment-15361327
]
Andrii Tkach commented on AMBARI-17551:
---
28936 tests complete (26 seconds)
154 tests pending
> AssignSlaves page doesnt let choose NodeManager evethough it complaints to
> add atleast one
> --
>
> Key: AMBARI-17551
> URL: https://issues.apache.org/jira/browse/AMBARI-17551
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17551.patch, Screen Shot 2016-06-30 at 2.53.48
> PM.png, pic1.png
>
>
> - Had a single node cluster with HDFS,YARN,MR and Zookeeper
> - Try to add service Ambari Metrics
> - Right after clicking Next on AssignMasters Page there comes a popup in
> AssignSlaves page that there is an issue with slaves assignment (pic1.png)
> - Click Cancel on warning and check the details. Issue was:
> {code}
> At least 1 NodeManager components should be installed in cluster.
> {code}
> Try to choose NodeManager checkbox. But its disabled. User can still proceed
> by clicking Next and Continue Anyway. But the issue showed in popup and
> NodeManager checkbox being disabled doesnt look right
> Could you please take a look at this scenario
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17551) AssignSlaves page doesnt let choose NodeManager evethough it complaints to add atleast one
[
https://issues.apache.org/jira/browse/AMBARI-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-17551:
--
Status: Patch Available (was: Open)
> AssignSlaves page doesnt let choose NodeManager evethough it complaints to
> add atleast one
> --
>
> Key: AMBARI-17551
> URL: https://issues.apache.org/jira/browse/AMBARI-17551
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17551.patch, Screen Shot 2016-06-30 at 2.53.48
> PM.png, pic1.png
>
>
> - Had a single node cluster with HDFS,YARN,MR and Zookeeper
> - Try to add service Ambari Metrics
> - Right after clicking Next on AssignMasters Page there comes a popup in
> AssignSlaves page that there is an issue with slaves assignment (pic1.png)
> - Click Cancel on warning and check the details. Issue was:
> {code}
> At least 1 NodeManager components should be installed in cluster.
> {code}
> Try to choose NodeManager checkbox. But its disabled. User can still proceed
> by clicking Next and Continue Anyway. But the issue showed in popup and
> NodeManager checkbox being disabled doesnt look right
> Could you please take a look at this scenario
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17551) AssignSlaves page doesnt let choose NodeManager evethough it complaints to add atleast one
[
https://issues.apache.org/jira/browse/AMBARI-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-17551:
--
Attachment: AMBARI-17551.patch
> AssignSlaves page doesnt let choose NodeManager evethough it complaints to
> add atleast one
> --
>
> Key: AMBARI-17551
> URL: https://issues.apache.org/jira/browse/AMBARI-17551
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17551.patch, Screen Shot 2016-06-30 at 2.53.48
> PM.png, pic1.png
>
>
> - Had a single node cluster with HDFS,YARN,MR and Zookeeper
> - Try to add service Ambari Metrics
> - Right after clicking Next on AssignMasters Page there comes a popup in
> AssignSlaves page that there is an issue with slaves assignment (pic1.png)
> - Click Cancel on warning and check the details. Issue was:
> {code}
> At least 1 NodeManager components should be installed in cluster.
> {code}
> Try to choose NodeManager checkbox. But its disabled. User can still proceed
> by clicking Next and Continue Anyway. But the issue showed in popup and
> NodeManager checkbox being disabled doesnt look right
> Could you please take a look at this scenario
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17550) While changing NN, DN directories from UI, proper warning should be present for invalid values
[
https://issues.apache.org/jira/browse/AMBARI-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361319#comment-15361319
]
Hadoop QA commented on AMBARI-17550:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816043/AMBARI-17550.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7675//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7675//console
This message is automatically generated.
> While changing NN, DN directories from UI, proper warning should be present
> for invalid values
> --
>
> Key: AMBARI-17550
> URL: https://issues.apache.org/jira/browse/AMBARI-17550
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17550.patch
>
>
> While changing NN and DN directories from ambari, for example:
> changing dn directories from **/grid/0/hadoop/hdfs/data** to **/grid/0/hadoop/
> hdfs/data,/grid/0/hadoop/hdfs/data1,/grid/0/hadoop/hdfs/data2**
> The values are changed without being validated
> This leads to datanodes start failing
>
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py",
> line 174, in
> DataNode().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 709, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py",
> line 60, in start
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py",
> line 55, in configure
> datanode(action="configure")
> File
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_datanode.py",
> line 53, in datanode
> data_dir_to_mount_file_content = handle_mounted_dirs(create_dirs,
> params.dfs_data_dirs, params.data_dir_mount_file, params)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/mounted_dirs_helper.py",
> line 158, in handle_mounted_dirs
> raise Fail(message + " . Please turn off
> cluster-env/one_dir_per_partition or handle the situation manually.")
> resource_management.core.exceptions.Fail: Trying to create another
> directory on the following mount: /grid/0 . Please turn off
> cluster-env/one_dir_per_partition or handle the situation manually.
>
> The test fails because it set invalid value, and the directory was not
> created
> A warning message informing why the new directory name is invalid could be
> useful
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17551) AssignSlaves page doesnt let choose NodeManager evethough it complaints to add atleast one
[
https://issues.apache.org/jira/browse/AMBARI-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-17551:
--
Attachment: Screen Shot 2016-06-30 at 2.53.48 PM.png
pic1.png
> AssignSlaves page doesnt let choose NodeManager evethough it complaints to
> add atleast one
> --
>
> Key: AMBARI-17551
> URL: https://issues.apache.org/jira/browse/AMBARI-17551
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: Screen Shot 2016-06-30 at 2.53.48 PM.png, pic1.png
>
>
> - Had a single node cluster with HDFS,YARN,MR and Zookeeper
> - Try to add service Ambari Metrics
> - Right after clicking Next on AssignMasters Page there comes a popup in
> AssignSlaves page that there is an issue with slaves assignment (pic1.png)
> - Click Cancel on warning and check the details. Issue was:
> {code}
> At least 1 NodeManager components should be installed in cluster.
> {code}
> Try to choose NodeManager checkbox. But its disabled. User can still proceed
> by clicking Next and Continue Anyway. But the issue showed in popup and
> NodeManager checkbox being disabled doesnt look right
> Could you please take a look at this scenario
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17551) AssignSlaves page doesnt let choose NodeManager evethough it complaints to add atleast one
Andrii Tkach created AMBARI-17551:
-
Summary: AssignSlaves page doesnt let choose NodeManager evethough
it complaints to add atleast one
Key: AMBARI-17551
URL: https://issues.apache.org/jira/browse/AMBARI-17551
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.4.0
Reporter: Andrii Tkach
Priority: Critical
Fix For: 2.4.0
- Had a single node cluster with HDFS,YARN,MR and Zookeeper
- Try to add service Ambari Metrics
- Right after clicking Next on AssignMasters Page there comes a popup in
AssignSlaves page that there is an issue with slaves assignment (pic1.png)
- Click Cancel on warning and check the details. Issue was:
{code}
At least 1 NodeManager components should be installed in cluster.
{code}
Try to choose NodeManager checkbox. But its disabled. User can still proceed by
clicking Next and Continue Anyway. But the issue showed in popup and
NodeManager checkbox being disabled doesnt look right
Could you please take a look at this scenario
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17550) While changing NN, DN directories from UI, proper warning should be present for invalid values
[ https://issues.apache.org/jira/browse/AMBARI-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-17550: - Attachment: AMBARI-17550.patch > While changing NN, DN directories from UI, proper warning should be present > for invalid values > -- > > Key: AMBARI-17550 > URL: https://issues.apache.org/jira/browse/AMBARI-17550 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-17550.patch > > > While changing NN and DN directories from ambari, for example: > changing dn directories from **/grid/0/hadoop/hdfs/data** to **/grid/0/hadoop/ > hdfs/data,/grid/0/hadoop/hdfs/data1,/grid/0/hadoop/hdfs/data2** > The values are changed without being validated > This leads to datanodes start failing > > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py", > line 174, in > DataNode().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 280, in execute > method(env) > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 709, in restart > self.start(env, upgrade_type=upgrade_type) > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py", > line 60, in start > self.configure(env) > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py", > line 55, in configure > datanode(action="configure") > File > "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, > in thunk > return fn(*args, **kwargs) > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_datanode.py", > line 53, in datanode > data_dir_to_mount_file_content = handle_mounted_dirs(create_dirs, > params.dfs_data_dirs, params.data_dir_mount_file, params) > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/mounted_dirs_helper.py", > line 158, in handle_mounted_dirs > raise Fail(message + " . Please turn off > cluster-env/one_dir_per_partition or handle the situation manually.") > resource_management.core.exceptions.Fail: Trying to create another > directory on the following mount: /grid/0 . Please turn off > cluster-env/one_dir_per_partition or handle the situation manually. > > The test fails because it set invalid value, and the directory was not > created > A warning message informing why the new directory name is invalid could be > useful -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17550) While changing NN, DN directories from UI, proper warning should be present for invalid values
Andrew Onischuk created AMBARI-17550: Summary: While changing NN, DN directories from UI, proper warning should be present for invalid values Key: AMBARI-17550 URL: https://issues.apache.org/jira/browse/AMBARI-17550 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.0 Attachments: AMBARI-17550.patch While changing NN and DN directories from ambari, for example: changing dn directories from **/grid/0/hadoop/hdfs/data** to **/grid/0/hadoop/ hdfs/data,/grid/0/hadoop/hdfs/data1,/grid/0/hadoop/hdfs/data2** The values are changed without being validated This leads to datanodes start failing Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py", line 174, in DataNode().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 280, in execute method(env) File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 709, in restart self.start(env, upgrade_type=upgrade_type) File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py", line 60, in start self.configure(env) File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py", line 55, in configure datanode(action="configure") File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, in thunk return fn(*args, **kwargs) File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_datanode.py", line 53, in datanode data_dir_to_mount_file_content = handle_mounted_dirs(create_dirs, params.dfs_data_dirs, params.data_dir_mount_file, params) File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/mounted_dirs_helper.py", line 158, in handle_mounted_dirs raise Fail(message + " . Please turn off cluster-env/one_dir_per_partition or handle the situation manually.") resource_management.core.exceptions.Fail: Trying to create another directory on the following mount: /grid/0 . Please turn off cluster-env/one_dir_per_partition or handle the situation manually. The test fails because it set invalid value, and the directory was not created A warning message informing why the new directory name is invalid could be useful -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17550) While changing NN, DN directories from UI, proper warning should be present for invalid values
[ https://issues.apache.org/jira/browse/AMBARI-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-17550: - Status: Patch Available (was: Open) > While changing NN, DN directories from UI, proper warning should be present > for invalid values > -- > > Key: AMBARI-17550 > URL: https://issues.apache.org/jira/browse/AMBARI-17550 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-17550.patch > > > While changing NN and DN directories from ambari, for example: > changing dn directories from **/grid/0/hadoop/hdfs/data** to **/grid/0/hadoop/ > hdfs/data,/grid/0/hadoop/hdfs/data1,/grid/0/hadoop/hdfs/data2** > The values are changed without being validated > This leads to datanodes start failing > > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py", > line 174, in > DataNode().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 280, in execute > method(env) > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 709, in restart > self.start(env, upgrade_type=upgrade_type) > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py", > line 60, in start > self.configure(env) > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py", > line 55, in configure > datanode(action="configure") > File > "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, > in thunk > return fn(*args, **kwargs) > File > "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_datanode.py", > line 53, in datanode > data_dir_to_mount_file_content = handle_mounted_dirs(create_dirs, > params.dfs_data_dirs, params.data_dir_mount_file, params) > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/mounted_dirs_helper.py", > line 158, in handle_mounted_dirs > raise Fail(message + " . Please turn off > cluster-env/one_dir_per_partition or handle the situation manually.") > resource_management.core.exceptions.Fail: Trying to create another > directory on the following mount: /grid/0 . Please turn off > cluster-env/one_dir_per_partition or handle the situation manually. > > The test fails because it set invalid value, and the directory was not > created > A warning message informing why the new directory name is invalid could be > useful -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17549) Client Install Failed icon appears even after reinstall
[ https://issues.apache.org/jira/browse/AMBARI-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361267#comment-15361267 ] Andrii Tkach commented on AMBARI-17549: --- +1 for the patch > Client Install Failed icon appears even after reinstall > --- > > Key: AMBARI-17549 > URL: https://issues.apache.org/jira/browse/AMBARI-17549 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-17549.patch > > > When client has status install failed, special icon is appeared beside it's > name. And this icon doesn't disappear even after successful reinstall. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17548) Quicklinks combobox is not present for Oozie
[ https://issues.apache.org/jira/browse/AMBARI-17548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17548: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > Quicklinks combobox is not present for Oozie > > > Key: AMBARI-17548 > URL: https://issues.apache.org/jira/browse/AMBARI-17548 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17548.patch > > > Quicklinks combobox is not present for Oozie -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17549) Client Install Failed icon appears even after reinstall
[ https://issues.apache.org/jira/browse/AMBARI-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17549: - Attachment: AMBARI-17549.patch > Client Install Failed icon appears even after reinstall > --- > > Key: AMBARI-17549 > URL: https://issues.apache.org/jira/browse/AMBARI-17549 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-17549.patch > > > When client has status install failed, special icon is appeared beside it's > name. And this icon doesn't disappear even after successful reinstall. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17549) Client Install Failed icon appears even after reinstall
[ https://issues.apache.org/jira/browse/AMBARI-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17549: - Status: Patch Available (was: Open) > Client Install Failed icon appears even after reinstall > --- > > Key: AMBARI-17549 > URL: https://issues.apache.org/jira/browse/AMBARI-17549 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-17549.patch > > > When client has status install failed, special icon is appeared beside it's > name. And this icon doesn't disappear even after successful reinstall. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17549) Client Install Failed icon appears even after reinstall
Aleksandr Kovalenko created AMBARI-17549: Summary: Client Install Failed icon appears even after reinstall Key: AMBARI-17549 URL: https://issues.apache.org/jira/browse/AMBARI-17549 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.4.0 When client has status install failed, special icon is appeared beside it's name. And this icon doesn't disappear even after successful reinstall. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17548) Quicklinks combobox is not present for Oozie
[
https://issues.apache.org/jira/browse/AMBARI-17548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361246#comment-15361246
]
Hadoop QA commented on AMBARI-17548:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816030/AMBARI-17548.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7674//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7674//console
This message is automatically generated.
> Quicklinks combobox is not present for Oozie
>
>
> Key: AMBARI-17548
> URL: https://issues.apache.org/jira/browse/AMBARI-17548
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17548.patch
>
>
> Quicklinks combobox is not present for Oozie
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17445) Storm metrics sink: expand metrics name to contain additional informations
[ https://issues.apache.org/jira/browse/AMBARI-17445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17445: -- Attachment: AMBARI-17445-v4.patch Updating patch which rebases to current trunk, and apply changeset to legacy sink, too. > Storm metrics sink: expand metrics name to contain additional informations > -- > > Key: AMBARI-17445 > URL: https://issues.apache.org/jira/browse/AMBARI-17445 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: AMBARI-17445-changes.png, AMBARI-17445-v1.patch, > AMBARI-17445-v2.patch, AMBARI-17445-v3.patch, AMBARI-17445-v4.patch > > > With AMBARI-16946 we expanded metric name to have component name, task id, > and key when type of metric value is Map. Topology name was placed to appId. > While talking with [~prajwal] and [~harsha_ch], we found that we should move > out all necessary informations like topology name, worker host, worker port > to metric name so that they can be templatized. > This also supercedes AMBARI-17249 since all metrics will include worker host > and worker port to metric name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17539) Ambari Agent memory Leak fix.
[ https://issues.apache.org/jira/browse/AMBARI-17539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-17539: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > Ambari Agent memory Leak fix. > - > > Key: AMBARI-17539 > URL: https://issues.apache.org/jira/browse/AMBARI-17539 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-17539.patch > > > *Reason of memory leak:* > Race condition in subprocess python module. > Due to this race condition at some unlucky cases python garbage collection > was disabled. > This usually happened when running alerts, as a bunch of our alerts run shell > commands and they do it in different threads. > *Fix for the issue:* > Synchronizing subprocess is not the best option. Since some people can still > use it without synchronization not knowing about the issue. > Also synchronizing will provide some unnecessary slowdown. So for this issue > the proposed fix is to monkey patch subprocess.gc.isenabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17548) Quicklinks combobox is not present for Oozie
[ https://issues.apache.org/jira/browse/AMBARI-17548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17548: Attachment: AMBARI-17548.patch > Quicklinks combobox is not present for Oozie > > > Key: AMBARI-17548 > URL: https://issues.apache.org/jira/browse/AMBARI-17548 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17548.patch > > > Quicklinks combobox is not present for Oozie -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17548) Quicklinks combobox is not present for Oozie
[ https://issues.apache.org/jira/browse/AMBARI-17548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17548: Status: Patch Available (was: Open) > Quicklinks combobox is not present for Oozie > > > Key: AMBARI-17548 > URL: https://issues.apache.org/jira/browse/AMBARI-17548 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17548.patch > > > Quicklinks combobox is not present for Oozie -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17548) Quicklinks combobox is not present for Oozie
Dmytro Sen created AMBARI-17548: --- Summary: Quicklinks combobox is not present for Oozie Key: AMBARI-17548 URL: https://issues.apache.org/jira/browse/AMBARI-17548 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.4.0 Quicklinks combobox is not present for Oozie -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17505) Optimize class path scanning
[ https://issues.apache.org/jira/browse/AMBARI-17505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17505: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Optimize class path scanning > - > > Key: AMBARI-17505 > URL: https://issues.apache.org/jira/browse/AMBARI-17505 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 2.5.0 > > Attachments: AMBARI-17505.2.2-next.patch, AMBARI-17505.v2.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > Problem: > When looking up upgrade checks the whole ambari server package is scanned > that considerably increases the server start time. > Solution: > Scan only the specific package that contains upgradecheck implementations -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17505) Optimize class path scanning
[
https://issues.apache.org/jira/browse/AMBARI-17505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361220#comment-15361220
]
Sebastian Toader commented on AMBARI-17505:
---
Committed to trunk:
{code}
commit d6abf7377b2c95bf8502e953c4935a3edc55b5a3
Author: Laszlo Puskas
Date: Mon Jul 4 09:59:40 2016 +0200
AMBARI-17505. Optimize class path scanning. (Laszlo Puskas via stoader)
{code}
Committed to branch-2.4:
{code}
commit d746048f0b3d64ed66f832bb6435af4a0b32cdb3
Author: Laszlo Puskas
Date: Mon Jul 4 09:59:40 2016 +0200
AMBARI-17505. Optimize class path scanning. (Laszlo Puskas via steadier)
{code}
> Optimize class path scanning
> -
>
> Key: AMBARI-17505
> URL: https://issues.apache.org/jira/browse/AMBARI-17505
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
> Fix For: 2.5.0
>
> Attachments: AMBARI-17505.2.2-next.patch, AMBARI-17505.v2.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Problem:
> When looking up upgrade checks the whole ambari server package is scanned
> that considerably increases the server start time.
> Solution:
> Scan only the specific package that contains upgradecheck implementations
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17547) Provide support for ViprFS filesystem in Ambari views
DIPAYAN BHOWMICK created AMBARI-17547: - Summary: Provide support for ViprFS filesystem in Ambari views Key: AMBARI-17547 URL: https://issues.apache.org/jira/browse/AMBARI-17547 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.2.0 Reporter: DIPAYAN BHOWMICK Assignee: DIPAYAN BHOWMICK Fix For: 2.4.0 Ambari Views do not work with the VIPR filesystem from EMC. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17546) Host Namenode Rebalance HDFS failed
[ https://issues.apache.org/jira/browse/AMBARI-17546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17546: Attachment: AMBARI-17546.patch > Host Namenode Rebalance HDFS failed > --- > > Key: AMBARI-17546 > URL: https://issues.apache.org/jira/browse/AMBARI-17546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: wangyaoxin > Fix For: trunk > > Attachments: 27c1ae6cdac7fd2fc6906689d50cb4da.png, > 594db9768b707ec62cd336f4d2aa445c.png, AMBARI-17546.patch > > > the host view ,excute namenode rebalance HDFS, json none lead fail . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17546) Host Namenode Rebalance HDFS failed
[ https://issues.apache.org/jira/browse/AMBARI-17546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17546: Status: Patch Available (was: Open) > Host Namenode Rebalance HDFS failed > --- > > Key: AMBARI-17546 > URL: https://issues.apache.org/jira/browse/AMBARI-17546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: wangyaoxin > Fix For: trunk > > Attachments: 27c1ae6cdac7fd2fc6906689d50cb4da.png, > 594db9768b707ec62cd336f4d2aa445c.png, AMBARI-17546.patch > > > the host view ,excute namenode rebalance HDFS, json none lead fail . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17546) Host Namenode Rebalance HDFS failed
[ https://issues.apache.org/jira/browse/AMBARI-17546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17546: Status: Open (was: Patch Available) > Host Namenode Rebalance HDFS failed > --- > > Key: AMBARI-17546 > URL: https://issues.apache.org/jira/browse/AMBARI-17546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: wangyaoxin > Fix For: trunk > > Attachments: 27c1ae6cdac7fd2fc6906689d50cb4da.png, > 594db9768b707ec62cd336f4d2aa445c.png, AMBARI-17546.patch > > > the host view ,excute namenode rebalance HDFS, json none lead fail . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17546) Host Namenode Rebalance HDFS failed
[ https://issues.apache.org/jira/browse/AMBARI-17546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17546: Attachment: (was: AMBARI-17546.patch) > Host Namenode Rebalance HDFS failed > --- > > Key: AMBARI-17546 > URL: https://issues.apache.org/jira/browse/AMBARI-17546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: wangyaoxin > Fix For: trunk > > Attachments: 27c1ae6cdac7fd2fc6906689d50cb4da.png, > 594db9768b707ec62cd336f4d2aa445c.png > > > the host view ,excute namenode rebalance HDFS, json none lead fail . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17546) Host Namenode Rebalance HDFS failed
[
https://issues.apache.org/jira/browse/AMBARI-17546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361188#comment-15361188
]
Hadoop QA commented on AMBARI-17546:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816019/AMBARI-17546.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7673//console
This message is automatically generated.
> Host Namenode Rebalance HDFS failed
> ---
>
> Key: AMBARI-17546
> URL: https://issues.apache.org/jira/browse/AMBARI-17546
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: wangyaoxin
> Fix For: trunk
>
> Attachments: 27c1ae6cdac7fd2fc6906689d50cb4da.png,
> 594db9768b707ec62cd336f4d2aa445c.png, AMBARI-17546.patch
>
>
> the host view ,excute namenode rebalance HDFS, json none lead fail .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16220) No INSTALL commands
[ https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-16220: Fix Version/s: (was: 2.5.0) 2.4.0 > No INSTALL commands > --- > > Key: AMBARI-16220 > URL: https://issues.apache.org/jira/browse/AMBARI-16220 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sandor Magyari > Fix For: 2.4.0 > > Attachments: AMBARI-16220.patch > > > In case packages.pre.installed=true is set in ambari.properties, Blueprint > based deployments will not create INSTALL commands for service components. > Normally START command should call configure, but we must ensure this is true > for all used components. For client components INSTALL will be still > generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm
[ https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17080: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > Support Storm 1.0 in Ambari Metrics for Storm > - > > Key: AMBARI-17080 > URL: https://issues.apache.org/jira/browse/AMBARI-17080 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-17080-trunk_6.patch, AMBARI-17080-v1.patch, > AMBARI-17080-v2.patch, AMBARI-17080-v3.patch > > > Since there was package name change on Apache Storm 1.0.0, Ambari Metrics > Reporter / Sink for Storm will not work when Ambari supports Apache Storm > 1.0.0 or upper. > This issue is for addressing this. > Please note that it will incur compile failure unless Ambari Metrics pom file > depends on Storm 1.x version, so decision for version of Storm should be made > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm
[ https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17080: Fix Version/s: 2.4.0 > Support Storm 1.0 in Ambari Metrics for Storm > - > > Key: AMBARI-17080 > URL: https://issues.apache.org/jira/browse/AMBARI-17080 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-17080-trunk_6.patch, AMBARI-17080-v1.patch, > AMBARI-17080-v2.patch, AMBARI-17080-v3.patch > > > Since there was package name change on Apache Storm 1.0.0, Ambari Metrics > Reporter / Sink for Storm will not work when Ambari supports Apache Storm > 1.0.0 or upper. > This issue is for addressing this. > Please note that it will incur compile failure unless Ambari Metrics pom file > depends on Storm 1.x version, so decision for version of Storm should be made > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17528) Fix Logfeeder visibilities
[
https://issues.apache.org/jira/browse/AMBARI-17528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-17528:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
{code:java}
commit 57b795dbc0657d49237433d2c2c7cc9369bfa958
Author: Miklos Gergely
Date: Mon Jul 4 12:59:42 2016 +0200
AMBARI-17528. Fix Logfeeder visibilities (Miklos Gergely via oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit 9cbb2c974cb17a73063d2326e9e0656144e05340
Author: Miklos Gergely
Date: Mon Jul 4 12:59:42 2016 +0200
AMBARI-17528. Fix Logfeeder visibilities (Miklos Gergely via oleewere)
{code}
> Fix Logfeeder visibilities
> --
>
> Key: AMBARI-17528
> URL: https://issues.apache.org/jira/browse/AMBARI-17528
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17528.patch
>
>
> Many variables/functions have a broader visibility than needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16214) Ensure Blueprint deployment can start immediately - after Server start
[ https://issues.apache.org/jira/browse/AMBARI-16214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-16214: Fix Version/s: (was: 2.4.1) 2.5.0 > Ensure Blueprint deployment can start immediately - after Server start > -- > > Key: AMBARI-16214 > URL: https://issues.apache.org/jira/browse/AMBARI-16214 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sandor Magyari > Fix For: 2.5.0 > > > * Blueprint may be provided during cluster start up (no need for a REST API > call). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17546) Host Namenode Rebalance HDFS failed
[ https://issues.apache.org/jira/browse/AMBARI-17546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17546: Status: Patch Available (was: Open) > Host Namenode Rebalance HDFS failed > --- > > Key: AMBARI-17546 > URL: https://issues.apache.org/jira/browse/AMBARI-17546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: wangyaoxin > Fix For: trunk > > Attachments: 27c1ae6cdac7fd2fc6906689d50cb4da.png, > 594db9768b707ec62cd336f4d2aa445c.png, AMBARI-17546.patch > > > the host view ,excute namenode rebalance HDFS, json none lead fail . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17546) Host Namenode Rebalance HDFS failed
[ https://issues.apache.org/jira/browse/AMBARI-17546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17546: Attachment: AMBARI-17546.patch > Host Namenode Rebalance HDFS failed > --- > > Key: AMBARI-17546 > URL: https://issues.apache.org/jira/browse/AMBARI-17546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: wangyaoxin > Fix For: trunk > > Attachments: 27c1ae6cdac7fd2fc6906689d50cb4da.png, > 594db9768b707ec62cd336f4d2aa445c.png, AMBARI-17546.patch > > > the host view ,excute namenode rebalance HDFS, json none lead fail . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17546) Host Namenode Rebalance HDFS failed
[ https://issues.apache.org/jira/browse/AMBARI-17546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17546: Attachment: (was: AMBARI-17546.patch) > Host Namenode Rebalance HDFS failed > --- > > Key: AMBARI-17546 > URL: https://issues.apache.org/jira/browse/AMBARI-17546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: wangyaoxin > Fix For: trunk > > Attachments: 27c1ae6cdac7fd2fc6906689d50cb4da.png, > 594db9768b707ec62cd336f4d2aa445c.png > > > the host view ,excute namenode rebalance HDFS, json none lead fail . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17505) Optimize class path scanning
[ https://issues.apache.org/jira/browse/AMBARI-17505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361155#comment-15361155 ] Hudson commented on AMBARI-17505: - SUCCESS: Integrated in Ambari-trunk-Commit #5219 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5219/]) AMBARI-17505. Optimize class path scanning. (Laszlo Puskas via stoader) (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d6abf7377b2c95bf8502e953c4935a3edc55b5a3]) * ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java > Optimize class path scanning > - > > Key: AMBARI-17505 > URL: https://issues.apache.org/jira/browse/AMBARI-17505 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 2.5.0 > > Attachments: AMBARI-17505.2.2-next.patch, AMBARI-17505.v2.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > Problem: > When looking up upgrade checks the whole ambari server package is scanned > that considerably increases the server start time. > Solution: > Scan only the specific package that contains upgradecheck implementations -- This message was sent by Atlassian JIRA (v6.3.4#6332)
