[jira] [Commented] (AMBARI-21649) Update Atlas log4j to reflect latest configurations
[ https://issues.apache.org/jira/browse/AMBARI-21649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122881#comment-16122881 ] Hudson commented on AMBARI-21649: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7880 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7880/]) AMBARI-21649 : Update Atlas log4j to reflect latest configurations (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=faf5d90799deee6509b1398f762616219e241f68]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/atlas-log4j.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.7.0.3.0/configuration/atlas-log4j.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml > Update Atlas log4j to reflect latest configurations > --- > > Key: AMBARI-21649 > URL: https://issues.apache.org/jira/browse/AMBARI-21649 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.3 > > Attachments: AMBARI-21649-branch-2.6.patch, > AMBARI-21649-trunk.1.patch, AMBARI-21649-trunk.patch > > > Need to update Atlas log4j configurations to reflect latest configurations as > per update in ATLAS-1996 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21649) Update Atlas log4j to reflect latest configurations
[ https://issues.apache.org/jira/browse/AMBARI-21649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-21649: Resolution: Fixed Status: Resolved (was: Patch Available) committed to [trunk|https://github.com/apache/ambari/commit/faf5d90799deee6509b1398f762616219e241f68] and [branch-2.6|https://github.com/apache/ambari/commit/6ddd4ac76f426e31386822b37b20ec3fa7b133e5] > Update Atlas log4j to reflect latest configurations > --- > > Key: AMBARI-21649 > URL: https://issues.apache.org/jira/browse/AMBARI-21649 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.3 > > Attachments: AMBARI-21649-branch-2.6.patch, > AMBARI-21649-trunk.1.patch, AMBARI-21649-trunk.patch > > > Need to update Atlas log4j configurations to reflect latest configurations as > per update in ATLAS-1996 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21690) Updating get_stack_version pattern match
[
https://issues.apache.org/jira/browse/AMBARI-21690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122854#comment-16122854
]
Hudson commented on AMBARI-21690:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1805 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1805/])
AMBARI-21690 Updating get_stack_version pattern match (mugdha) (mugdha:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ee87b6ab60edc43ef94a404ae2ab72da42f3549f])
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/get_stack_version.py
> Updating get_stack_version pattern match
>
>
> Key: AMBARI-21690
> URL: https://issues.apache.org/jira/browse/AMBARI-21690
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.2, 2.6.0
>
> Attachments: AMBARI-21690.1.patch, AMBARI-21690.patch
>
>
> Currently {{get_stack_version}} only accepts stack version with
> {{-buildnumber}} at the end. Need to change stack version pattern match for
> stack version without {{-buildnumber}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21690) Updating get_stack_version pattern match
[
https://issues.apache.org/jira/browse/AMBARI-21690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-21690:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.5:
[ee87b6ab60edc43ef94a404ae2ab72da42f3549f|https://github.com/apache/ambari/commit/ee87b6ab60edc43ef94a404ae2ab72da42f3549f]
and branch-2.6:
[abcf1ce8619bb0459c633f63fc2e2edaa7f04f64|https://github.com/apache/ambari/commit/abcf1ce8619bb0459c633f63fc2e2edaa7f04f64]
> Updating get_stack_version pattern match
>
>
> Key: AMBARI-21690
> URL: https://issues.apache.org/jira/browse/AMBARI-21690
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.2, 2.6.0
>
> Attachments: AMBARI-21690.1.patch, AMBARI-21690.patch
>
>
> Currently {{get_stack_version}} only accepts stack version with
> {{-buildnumber}} at the end. Need to change stack version pattern match for
> stack version without {{-buildnumber}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21690) Updating get_stack_version pattern match
[
https://issues.apache.org/jira/browse/AMBARI-21690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-21690:
-
Fix Version/s: (was: trunk)
> Updating get_stack_version pattern match
>
>
> Key: AMBARI-21690
> URL: https://issues.apache.org/jira/browse/AMBARI-21690
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.2, 2.6.0
>
> Attachments: AMBARI-21690.1.patch, AMBARI-21690.patch
>
>
> Currently {{get_stack_version}} only accepts stack version with
> {{-buildnumber}} at the end. Need to change stack version pattern match for
> stack version without {{-buildnumber}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes
[ https://issues.apache.org/jira/browse/AMBARI-21707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-21707: --- Attachment: (was: AMBARI-21707.patch) > Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 > changes > -- > > Key: AMBARI-21707 > URL: https://issues.apache.org/jira/browse/AMBARI-21707 > Project: Ambari > Issue Type: Bug >Reporter: Arpit Gupta >Assignee: Madhuvanthi Radhakrishnan >Priority: Critical > Fix For: 2.5.2 > > > Refer : https://issues.apache.org/jira/browse/AMBARI-21430 > Changes are required in the HDF stack definition so that Ambari is able to > parse the stack_features and tools correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes
[ https://issues.apache.org/jira/browse/AMBARI-21707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-21707: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 > changes > -- > > Key: AMBARI-21707 > URL: https://issues.apache.org/jira/browse/AMBARI-21707 > Project: Ambari > Issue Type: Bug >Reporter: Arpit Gupta >Assignee: Madhuvanthi Radhakrishnan >Priority: Critical > Fix For: 2.5.2 > > > Refer : https://issues.apache.org/jira/browse/AMBARI-21430 > Changes are required in the HDF stack definition so that Ambari is able to > parse the stack_features and tools correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21173) Not able to start Yarn services after restoring the configs to initial value
[
https://issues.apache.org/jira/browse/AMBARI-21173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122648#comment-16122648
]
Hudson commented on AMBARI-21173:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7879 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7879/])
AMBARI-21173. Not able to start Yarn services after restoring the (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=86c7f92c31fda6b89eb7c9389072a94abe35d917])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
> Not able to start Yarn services after restoring the configs to initial value
>
>
> Key: AMBARI-21173
> URL: https://issues.apache.org/jira/browse/AMBARI-21173
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Sumana Sathish
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21173.patch
>
>
> Change Yarn-site.xml to some custom configs and restart Yarn
> Restore it back to the origin config; Restart fails
> {Code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 106, in
> Nodemanager().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 330, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 835, in restart
> self.stop(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 45, in stop
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params.py",
> line 29, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params_linux.py",
> line 39, in
> import status_params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/status_params.py",
> line 46, in
> yarn_pid_dir = format("{yarn_pid_dir_prefix}/{yarn_user}")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'yarn-env'
> was not found in configurations dictionary!
> {Code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21706) Fix exception messages whenever empty host list is passed in predicate.
[
https://issues.apache.org/jira/browse/AMBARI-21706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122630#comment-16122630
]
Hadoop QA commented on AMBARI-21706:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881352/AMBARI-21706.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/11981//console
This message is automatically generated.
> Fix exception messages whenever empty host list is passed in predicate.
> ---
>
> Key: AMBARI-21706
> URL: https://issues.apache.org/jira/browse/AMBARI-21706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21706.patch
>
>
> Cluster installation stuck on Customize Services Page and wasn't loaded even
> after 4000 seconds waiting
> ambari-server.log shows:
> {code}
> 10 Aug 2017 09:48:08,356 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 -
> No clusters configured.
> 10 Aug 2017 09:49:17,123 ERROR [ambari-client-thread-593] QueryParser:115 -
> Lowercase host_name value in expression failed with
> error:java.lang.NullPointerException
> 10 Aug 2017 09:49:17,125 ERROR [ambari-client-thread-593] Request:147 -
> Unable to compile query predicate: IN operator is missing a required right
> oper
> and.
> org.apache.ambari.server.api.predicate.InvalidQueryException: IN operator is
> missing a required right operand.
> at
> org.apache.ambari.server.api.predicate.operators.InOperator.toPredicate(InOperator.java:50)
> at
> org.apache.ambari.server.api.predicate.expressions.RelationalExpression.toPredicate(RelationalExpression.java:43)
> at
> org.apache.ambari.server.api.predicate.QueryParser.parse(QueryParser.java:99)
> at
> org.apache.ambari.server.api.predicate.PredicateCompiler.compile(PredicateCompiler.java:62)
> at
> org.apache.ambari.server.api.services.BaseRequest.parseQueryPredicate(BaseRequest.java:344)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:143)
> {code}
> {code}
> 10 Aug 2017 09:49:17,126 WARN [ambari-client-thread-597]
> AbstractResourceProvider:134 - Error occurred during preparation of stack
> advisor request
> java.lang.ClassCastException: java.util.LinkedHashSet cannot be cast to
> java.util.List
> at
> org.apache.ambari.server.controller.internal.StackAdvisorResourceProvider.prepareStackAdvisorRequest(StackAdvisorResourceProvider.java:110)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:88)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes
[
https://issues.apache.org/jira/browse/AMBARI-21707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122611#comment-16122611
]
Hadoop QA commented on AMBARI-21707:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881360/AMBARI-21707.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/11980//console
This message is automatically generated.
> Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2
> changes
> --
>
> Key: AMBARI-21707
> URL: https://issues.apache.org/jira/browse/AMBARI-21707
> Project: Ambari
> Issue Type: Bug
>Reporter: Arpit Gupta
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21707.patch
>
>
> Refer : https://issues.apache.org/jira/browse/AMBARI-21430
> Changes are required in the HDF stack definition so that Ambari is able to
> parse the stack_features and tools correctly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21705) Metrics Collector start failed due to "Unable to initialize HA controller"
[
https://issues.apache.org/jira/browse/AMBARI-21705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122608#comment-16122608
]
Hudson commented on AMBARI-21705:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7878 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7878/])
AMBARI-21705 : Metrics Collector start failed due to 'Unable to (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d0168787ed617b381b0a41c0e72abfbcc7f4c859])
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/MetricCollectorHAController.java
> Metrics Collector start failed due to "Unable to initialize HA controller"
> --
>
> Key: AMBARI-21705
> URL: https://issues.apache.org/jira/browse/AMBARI-21705
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21705.patch
>
>
> AMS start failed due to "Unable to initialize HA controller"
> STR:
> 1)Enable HA
> 2)Delete all services except HDFS, Yarn, MapReduce, Zookeeper
> 3)Add all services
> Metrics collector start, but after few minutes fail
> {code}
> Error starting ApplicationHistoryServer
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.MetricsSystemInitializationException:
> Unable to initialize HA controller at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:118)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.serviceInit(HBaseTimelineMetricStore.java:96)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:84)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:137)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: org.I0Itec.zkclient.exception.ZkException:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.I0Itec.zkclient.exception.ZkException.create(ZkException.java:68) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:1000) at
> org.apache.helix.manager.zk.ZkClient.delete(ZkClient.java:347) at
> org.I0Itec.zkclient.ZkClient.deleteRecursive(ZkClient.java:791) at
> org.apache.helix.manager.zk.ZKHelixAdmin.addCluster(ZKHelixAdmin.java:497) at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAController.initializeHAController(MetricCollectorHAController.java:156)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:115)
> ... 7 more Caused by:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:125) at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at
> org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873) at
> org.I0Itec.zkclient.ZkConnection.delete(ZkConnection.java:104) at
> org.apache.helix.manager.zk.ZkClient$8.call(ZkClient.java:351) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:990) ... 12
> more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21705) Metrics Collector start failed due to "Unable to initialize HA controller"
[
https://issues.apache.org/jira/browse/AMBARI-21705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122578#comment-16122578
]
Hudson commented on AMBARI-21705:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1804 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1804/])
AMBARI-21705 : Metrics Collector start failed due to 'Unable to (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bf51a82c9cf82d0cdda2a748d8102cffd73a8246])
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/MetricCollectorHAController.java
> Metrics Collector start failed due to "Unable to initialize HA controller"
> --
>
> Key: AMBARI-21705
> URL: https://issues.apache.org/jira/browse/AMBARI-21705
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21705.patch
>
>
> AMS start failed due to "Unable to initialize HA controller"
> STR:
> 1)Enable HA
> 2)Delete all services except HDFS, Yarn, MapReduce, Zookeeper
> 3)Add all services
> Metrics collector start, but after few minutes fail
> {code}
> Error starting ApplicationHistoryServer
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.MetricsSystemInitializationException:
> Unable to initialize HA controller at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:118)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.serviceInit(HBaseTimelineMetricStore.java:96)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:84)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:137)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: org.I0Itec.zkclient.exception.ZkException:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.I0Itec.zkclient.exception.ZkException.create(ZkException.java:68) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:1000) at
> org.apache.helix.manager.zk.ZkClient.delete(ZkClient.java:347) at
> org.I0Itec.zkclient.ZkClient.deleteRecursive(ZkClient.java:791) at
> org.apache.helix.manager.zk.ZKHelixAdmin.addCluster(ZKHelixAdmin.java:497) at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAController.initializeHAController(MetricCollectorHAController.java:156)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:115)
> ... 7 more Caused by:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:125) at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at
> org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873) at
> org.I0Itec.zkclient.ZkConnection.delete(ZkConnection.java:104) at
> org.apache.helix.manager.zk.ZkClient$8.call(ZkClient.java:351) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:990) ... 12
> more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21173) Not able to start Yarn services after restoring the configs to initial value
[
https://issues.apache.org/jira/browse/AMBARI-21173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-21173:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
> Not able to start Yarn services after restoring the configs to initial value
>
>
> Key: AMBARI-21173
> URL: https://issues.apache.org/jira/browse/AMBARI-21173
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Sumana Sathish
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21173.patch
>
>
> Change Yarn-site.xml to some custom configs and restart Yarn
> Restore it back to the origin config; Restart fails
> {Code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 106, in
> Nodemanager().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 330, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 835, in restart
> self.stop(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 45, in stop
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params.py",
> line 29, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params_linux.py",
> line 39, in
> import status_params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/status_params.py",
> line 46, in
> yarn_pid_dir = format("{yarn_pid_dir_prefix}/{yarn_user}")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'yarn-env'
> was not found in configurations dictionary!
> {Code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21364) DB consistency checker throws errors for missing 'parquet-logging' and 'product-info' configs after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122563#comment-16122563
]
Matt commented on AMBARI-21364:
---
I had a similar issue with a service I'm working on. When I upgrade to a new
version(of the service) that has a new dictionaryName, the database startup
checks fail because it doesn't find the new property in the current config
version. I found this ticket, built Ambari branch-2.5, and added optional set
to true for my new configFile. This got me passed the startup check but the
service failed to start with the an error stating that it was unable to find my
new parameter in the configurations dictionary!
I took a look at the PR and it appears like it appends optional properties to
the configuration but I'm not sure what this is appending to. Does this append
to the configuration dictionary? If not, how can one add to the configuration
dictionary?
https://github.com/apache/ambari/blob/19d4200e719854b0d304e0d7be5e20f33cda46ff/ambari-server/src/main/java/org/apache/ambari/server/state/ClientConfigFileDefinition.java#L86
https://github.com/apache/ambari/commit/19d4200e719854b0d304e0d7be5e20f33cda46ff
> DB consistency checker throws errors for missing 'parquet-logging' and
> 'product-info' configs after Ambari upgrade
> --
>
> Key: AMBARI-21364
> URL: https://issues.apache.org/jira/browse/AMBARI-21364
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: upgrade
> Fix For: 2.5.2
>
> Attachments: AMBARI-21364.patch, AMBARI-21364.trunk.patch,
> AMBARI-21364.trunk.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version:
> 2.6.1.0-129
> # Upgrade Ambari to 2.5.2.0-74 (hash:
> fd30644590991deb41241454d6e9091ed7a38e92)
> # Run "ambari-server start"
> {code}
> root@ctr-e133-1493418528701-156570-01-05:/hwqe/hadoopqe# ambari-server
> restart
> Using python /usr/bin/python
> Restarting ambari-server
> Waiting for server stop...
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start..
> DB configs consistency check failed. Run "ambari-server start
> --skip-database-check" to skip. You may try --auto-fix-database flag to
> attempt to fix issues automatically. If you use this "--skip-database-check"
> option, do not make any changes to your cluster topology or perform a cluster
> upgrade until you correct the database consistency issues. See
> /var/log/ambari-server/ambari-server-check-database.log for more details on
> the consistency issues.
> ERROR: Exiting with exit code -1.
> REASON: Ambari Server java process has stopped. Please check the logs for
> more information.
> {code}
> DB log: ambari-server-check-database.log
> {code}
> 2017-06-27 13:51:38,743 INFO - Executing query 'GET_SERVICES_WITH_CONFIGS'
> 2017-06-27 13:51:38,748 INFO - Comparing service configs from stack with
> configs that we got from db
> 2017-06-27 13:51:38,748 INFO - Getting services from metainfo
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / KAFKA
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / PIG
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / ZEPPELIN
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / LOGSEARCH
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / MAPREDUCE2
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / SLIDER
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / HIVE
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / TEZ
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / HBASE
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / OOZIE
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / FLUME
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / MAHOUT
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / HDFS
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / DRUID
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / AMBARI_METRICS
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / SPARK
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / SMARTSENSE
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / AMBARI_INFRA
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / YARN
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / FALCON
> 2017-06-27 13:51:38,749 INFO
[jira] [Comment Edited] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes
[ https://issues.apache.org/jira/browse/AMBARI-21707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122559#comment-16122559 ] Madhuvanthi Radhakrishnan edited comment on AMBARI-21707 at 8/10/17 11:55 PM: -- Hi [~jluniya], Kindly review this patch. Thanks was (Author: mradhakrishnan): [~jluniya], Kindly review this patch. Thanks > Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 > changes > -- > > Key: AMBARI-21707 > URL: https://issues.apache.org/jira/browse/AMBARI-21707 > Project: Ambari > Issue Type: Bug >Reporter: Arpit Gupta >Assignee: Madhuvanthi Radhakrishnan >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21707.patch > > > Refer : https://issues.apache.org/jira/browse/AMBARI-21430 > Changes are required in the HDF stack definition so that Ambari is able to > parse the stack_features and tools correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes
[ https://issues.apache.org/jira/browse/AMBARI-21707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122559#comment-16122559 ] Madhuvanthi Radhakrishnan commented on AMBARI-21707: [~jluniya], Kindly review this patch. Thanks > Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 > changes > -- > > Key: AMBARI-21707 > URL: https://issues.apache.org/jira/browse/AMBARI-21707 > Project: Ambari > Issue Type: Bug >Reporter: Arpit Gupta >Assignee: Madhuvanthi Radhakrishnan >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21707.patch > > > Refer : https://issues.apache.org/jira/browse/AMBARI-21430 > Changes are required in the HDF stack definition so that Ambari is able to > parse the stack_features and tools correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes
[ https://issues.apache.org/jira/browse/AMBARI-21707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-21707: --- Status: Patch Available (was: Open) > Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 > changes > -- > > Key: AMBARI-21707 > URL: https://issues.apache.org/jira/browse/AMBARI-21707 > Project: Ambari > Issue Type: Bug >Reporter: Arpit Gupta >Assignee: Madhuvanthi Radhakrishnan >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21707.patch > > > Refer : https://issues.apache.org/jira/browse/AMBARI-21430 > Changes are required in the HDF stack definition so that Ambari is able to > parse the stack_features and tools correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes
[ https://issues.apache.org/jira/browse/AMBARI-21707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-21707: --- Attachment: AMBARI-21707.patch > Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 > changes > -- > > Key: AMBARI-21707 > URL: https://issues.apache.org/jira/browse/AMBARI-21707 > Project: Ambari > Issue Type: Bug >Reporter: Arpit Gupta >Assignee: Madhuvanthi Radhakrishnan >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21707.patch > > > Refer : https://issues.apache.org/jira/browse/AMBARI-21430 > Changes are required in the HDF stack definition so that Ambari is able to > parse the stack_features and tools correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes
[ https://issues.apache.org/jira/browse/AMBARI-21707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-21707: --- Reporter: Arpit Gupta (was: Madhuvanthi Radhakrishnan) > Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 > changes > -- > > Key: AMBARI-21707 > URL: https://issues.apache.org/jira/browse/AMBARI-21707 > Project: Ambari > Issue Type: Bug >Reporter: Arpit Gupta >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.2 > > > Refer : https://issues.apache.org/jira/browse/AMBARI-21430 > Changes are required in the HDF stack definition so that Ambari is able to > parse the stack_features and tools correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes
[ https://issues.apache.org/jira/browse/AMBARI-21707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-21707: --- Fix Version/s: 2.5.2 > Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 > changes > -- > > Key: AMBARI-21707 > URL: https://issues.apache.org/jira/browse/AMBARI-21707 > Project: Ambari > Issue Type: Bug >Reporter: Arpit Gupta >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.2 > > > Refer : https://issues.apache.org/jira/browse/AMBARI-21430 > Changes are required in the HDF stack definition so that Ambari is able to > parse the stack_features and tools correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes
[ https://issues.apache.org/jira/browse/AMBARI-21707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-21707: --- Priority: Critical (was: Major) > Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 > changes > -- > > Key: AMBARI-21707 > URL: https://issues.apache.org/jira/browse/AMBARI-21707 > Project: Ambari > Issue Type: Bug >Reporter: Arpit Gupta >Assignee: Madhuvanthi Radhakrishnan >Priority: Critical > Fix For: 2.5.2 > > > Refer : https://issues.apache.org/jira/browse/AMBARI-21430 > Changes are required in the HDF stack definition so that Ambari is able to > parse the stack_features and tools correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21657) Ambari does not display metric data on widgets when the JMX path contains the '-' character.
[
https://issues.apache.org/jira/browse/AMBARI-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21657:
---
Description:
{code}
"name" : "Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4",
"modelerType" : "AzureFileSystemMetrics4",
"tag.Context" : "azureFileSystem",
"tag.wasbFileSystemId" : "24f05882-a63a-43d4-9dec-eff23f9fcfa0",
"tag.accountName" : "<>",
"tag.containerName" : "xhdinsight-2017-07-24t21-26-36-619z",
"tag.Hostname" : "zk2-xhdins",
"wasb_web_responses" : 87824,
"wasb_files_created" : 8
{code}
For example, the above metrics cannot be displayed on widgets due to the '-' in
*Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4*.
> Ambari does not display metric data on widgets when the JMX path contains the
> '-' character.
>
>
> Key: AMBARI-21657
> URL: https://issues.apache.org/jira/browse/AMBARI-21657
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.6.0
>
> Attachments: AMBARI-21657.patch
>
>
> {code}
> "name" : "Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4",
> "modelerType" : "AzureFileSystemMetrics4",
> "tag.Context" : "azureFileSystem",
> "tag.wasbFileSystemId" : "24f05882-a63a-43d4-9dec-eff23f9fcfa0",
> "tag.accountName" : "<>",
> "tag.containerName" : "xhdinsight-2017-07-24t21-26-36-619z",
> "tag.Hostname" : "zk2-xhdins",
> "wasb_web_responses" : 87824,
> "wasb_files_created" : 8
> {code}
> For example, the above metrics cannot be displayed on widgets due to the '-'
> in *Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4*.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-21705) Metrics Collector start failed due to "Unable to initialize HA controller"
[
https://issues.apache.org/jira/browse/AMBARI-21705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122540#comment-16122540
]
Aravindan Vijayan edited comment on AMBARI-21705 at 8/10/17 11:49 PM:
--
Pushed to branch-2.5, branch-2.6 and trunk.
was (Author: avijayan):
Pushed to branch-2.5 and trunk.
> Metrics Collector start failed due to "Unable to initialize HA controller"
> --
>
> Key: AMBARI-21705
> URL: https://issues.apache.org/jira/browse/AMBARI-21705
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21705.patch
>
>
> AMS start failed due to "Unable to initialize HA controller"
> STR:
> 1)Enable HA
> 2)Delete all services except HDFS, Yarn, MapReduce, Zookeeper
> 3)Add all services
> Metrics collector start, but after few minutes fail
> {code}
> Error starting ApplicationHistoryServer
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.MetricsSystemInitializationException:
> Unable to initialize HA controller at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:118)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.serviceInit(HBaseTimelineMetricStore.java:96)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:84)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:137)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: org.I0Itec.zkclient.exception.ZkException:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.I0Itec.zkclient.exception.ZkException.create(ZkException.java:68) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:1000) at
> org.apache.helix.manager.zk.ZkClient.delete(ZkClient.java:347) at
> org.I0Itec.zkclient.ZkClient.deleteRecursive(ZkClient.java:791) at
> org.apache.helix.manager.zk.ZKHelixAdmin.addCluster(ZKHelixAdmin.java:497) at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAController.initializeHAController(MetricCollectorHAController.java:156)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:115)
> ... 7 more Caused by:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:125) at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at
> org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873) at
> org.I0Itec.zkclient.ZkConnection.delete(ZkConnection.java:104) at
> org.apache.helix.manager.zk.ZkClient$8.call(ZkClient.java:351) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:990) ... 12
> more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21657) Ambari does not display metric data on widgets when the JMX path contains the '-' character.
[ https://issues.apache.org/jira/browse/AMBARI-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122550#comment-16122550 ] Aravindan Vijayan commented on AMBARI-21657: Manually tested on cluster. mvn clean test on ambari-web [~u39kun] / [~jaimin] Can you review this simple patch ? > Ambari does not display metric data on widgets when the JMX path contains the > '-' character. > > > Key: AMBARI-21657 > URL: https://issues.apache.org/jira/browse/AMBARI-21657 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.6.0 > > Attachments: AMBARI-21657.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21657) Ambari does not display metric data on widgets when the JMX path contains the '-' character.
[ https://issues.apache.org/jira/browse/AMBARI-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21657: --- Attachment: AMBARI-21657.patch > Ambari does not display metric data on widgets when the JMX path contains the > '-' character. > > > Key: AMBARI-21657 > URL: https://issues.apache.org/jira/browse/AMBARI-21657 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.6.0 > > Attachments: AMBARI-21657.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21657) Ambari does not display metric data on widgets when the JMX path contains the '-' character.
[ https://issues.apache.org/jira/browse/AMBARI-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21657: --- Fix Version/s: 2.6.0 > Ambari does not display metric data on widgets when the JMX path contains the > '-' character. > > > Key: AMBARI-21657 > URL: https://issues.apache.org/jira/browse/AMBARI-21657 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes
Madhuvanthi Radhakrishnan created AMBARI-21707: -- Summary: Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes Key: AMBARI-21707 URL: https://issues.apache.org/jira/browse/AMBARI-21707 Project: Ambari Issue Type: Bug Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Refer : https://issues.apache.org/jira/browse/AMBARI-21430 Changes are required in the HDF stack definition so that Ambari is able to parse the stack_features and tools correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21706) Fix exception messages whenever empty host list is passed in predicate.
[
https://issues.apache.org/jira/browse/AMBARI-21706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21706:
---
Status: Patch Available (was: Open)
> Fix exception messages whenever empty host list is passed in predicate.
> ---
>
> Key: AMBARI-21706
> URL: https://issues.apache.org/jira/browse/AMBARI-21706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21706.patch
>
>
> Cluster installation stuck on Customize Services Page and wasn't loaded even
> after 4000 seconds waiting
> ambari-server.log shows:
> {code}
> 10 Aug 2017 09:48:08,356 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 -
> No clusters configured.
> 10 Aug 2017 09:49:17,123 ERROR [ambari-client-thread-593] QueryParser:115 -
> Lowercase host_name value in expression failed with
> error:java.lang.NullPointerException
> 10 Aug 2017 09:49:17,125 ERROR [ambari-client-thread-593] Request:147 -
> Unable to compile query predicate: IN operator is missing a required right
> oper
> and.
> org.apache.ambari.server.api.predicate.InvalidQueryException: IN operator is
> missing a required right operand.
> at
> org.apache.ambari.server.api.predicate.operators.InOperator.toPredicate(InOperator.java:50)
> at
> org.apache.ambari.server.api.predicate.expressions.RelationalExpression.toPredicate(RelationalExpression.java:43)
> at
> org.apache.ambari.server.api.predicate.QueryParser.parse(QueryParser.java:99)
> at
> org.apache.ambari.server.api.predicate.PredicateCompiler.compile(PredicateCompiler.java:62)
> at
> org.apache.ambari.server.api.services.BaseRequest.parseQueryPredicate(BaseRequest.java:344)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:143)
> {code}
> {code}
> 10 Aug 2017 09:49:17,126 WARN [ambari-client-thread-597]
> AbstractResourceProvider:134 - Error occurred during preparation of stack
> advisor request
> java.lang.ClassCastException: java.util.LinkedHashSet cannot be cast to
> java.util.List
> at
> org.apache.ambari.server.controller.internal.StackAdvisorResourceProvider.prepareStackAdvisorRequest(StackAdvisorResourceProvider.java:110)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:88)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21676) Support upgrading custom services with new dicts
[ https://issues.apache.org/jira/browse/AMBARI-21676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt resolved AMBARI-21676. --- Resolution: Duplicate This is a duplicate of https://issues.apache.org/jira/browse/AMBARI-21364 > Support upgrading custom services with new dicts > > > Key: AMBARI-21676 > URL: https://issues.apache.org/jira/browse/AMBARI-21676 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Matt > > When upgrading a custom service that has new dictionaryName, the database > startup checks fail because it doesn't find the new properties in the current > config version. > Two options for a workaround include, uninstalling/reinstalling the service > or manually creating the missing properties in Ambari before upgrading. > It would be helpful if there was a way to update the existing configuration > on startup. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21705) Metrics Collector start failed due to "Unable to initialize HA controller"
[
https://issues.apache.org/jira/browse/AMBARI-21705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21705:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5 and trunk.
> Metrics Collector start failed due to "Unable to initialize HA controller"
> --
>
> Key: AMBARI-21705
> URL: https://issues.apache.org/jira/browse/AMBARI-21705
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21705.patch
>
>
> AMS start failed due to "Unable to initialize HA controller"
> STR:
> 1)Enable HA
> 2)Delete all services except HDFS, Yarn, MapReduce, Zookeeper
> 3)Add all services
> Metrics collector start, but after few minutes fail
> {code}
> Error starting ApplicationHistoryServer
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.MetricsSystemInitializationException:
> Unable to initialize HA controller at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:118)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.serviceInit(HBaseTimelineMetricStore.java:96)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:84)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:137)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: org.I0Itec.zkclient.exception.ZkException:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.I0Itec.zkclient.exception.ZkException.create(ZkException.java:68) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:1000) at
> org.apache.helix.manager.zk.ZkClient.delete(ZkClient.java:347) at
> org.I0Itec.zkclient.ZkClient.deleteRecursive(ZkClient.java:791) at
> org.apache.helix.manager.zk.ZKHelixAdmin.addCluster(ZKHelixAdmin.java:497) at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAController.initializeHAController(MetricCollectorHAController.java:156)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:115)
> ... 7 more Caused by:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:125) at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at
> org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873) at
> org.I0Itec.zkclient.ZkConnection.delete(ZkConnection.java:104) at
> org.apache.helix.manager.zk.ZkClient$8.call(ZkClient.java:351) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:990) ... 12
> more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21706) Fix exception messages whenever empty host list is passed in predicate.
[
https://issues.apache.org/jira/browse/AMBARI-21706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21706:
---
Summary: Fix exception messages whenever empty host list is passed in
predicate. (was: Cluster installation stuck on Customize Services Page)
> Fix exception messages whenever empty host list is passed in predicate.
> ---
>
> Key: AMBARI-21706
> URL: https://issues.apache.org/jira/browse/AMBARI-21706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21706.patch
>
>
> Cluster installation stuck on Customize Services Page and wasn't loaded even
> after 4000 seconds waiting
> ambari-server.log shows:
> {code}
> 10 Aug 2017 09:48:08,356 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 -
> No clusters configured.
> 10 Aug 2017 09:49:17,123 ERROR [ambari-client-thread-593] QueryParser:115 -
> Lowercase host_name value in expression failed with
> error:java.lang.NullPointerException
> 10 Aug 2017 09:49:17,125 ERROR [ambari-client-thread-593] Request:147 -
> Unable to compile query predicate: IN operator is missing a required right
> oper
> and.
> org.apache.ambari.server.api.predicate.InvalidQueryException: IN operator is
> missing a required right operand.
> at
> org.apache.ambari.server.api.predicate.operators.InOperator.toPredicate(InOperator.java:50)
> at
> org.apache.ambari.server.api.predicate.expressions.RelationalExpression.toPredicate(RelationalExpression.java:43)
> at
> org.apache.ambari.server.api.predicate.QueryParser.parse(QueryParser.java:99)
> at
> org.apache.ambari.server.api.predicate.PredicateCompiler.compile(PredicateCompiler.java:62)
> at
> org.apache.ambari.server.api.services.BaseRequest.parseQueryPredicate(BaseRequest.java:344)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:143)
> {code}
> {code}
> 10 Aug 2017 09:49:17,126 WARN [ambari-client-thread-597]
> AbstractResourceProvider:134 - Error occurred during preparation of stack
> advisor request
> java.lang.ClassCastException: java.util.LinkedHashSet cannot be cast to
> java.util.List
> at
> org.apache.ambari.server.controller.internal.StackAdvisorResourceProvider.prepareStackAdvisorRequest(StackAdvisorResourceProvider.java:110)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:88)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21706) Cluster installation stuck on Customize Services Page
[
https://issues.apache.org/jira/browse/AMBARI-21706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21706:
---
Attachment: AMBARI-21706.patch
> Cluster installation stuck on Customize Services Page
> -
>
> Key: AMBARI-21706
> URL: https://issues.apache.org/jira/browse/AMBARI-21706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21706.patch
>
>
> Cluster installation stuck on Customize Services Page and wasn't loaded even
> after 4000 seconds waiting
> ambari-server.log shows:
> {code}
> 10 Aug 2017 09:48:08,356 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 -
> No clusters configured.
> 10 Aug 2017 09:49:17,123 ERROR [ambari-client-thread-593] QueryParser:115 -
> Lowercase host_name value in expression failed with
> error:java.lang.NullPointerException
> 10 Aug 2017 09:49:17,125 ERROR [ambari-client-thread-593] Request:147 -
> Unable to compile query predicate: IN operator is missing a required right
> oper
> and.
> org.apache.ambari.server.api.predicate.InvalidQueryException: IN operator is
> missing a required right operand.
> at
> org.apache.ambari.server.api.predicate.operators.InOperator.toPredicate(InOperator.java:50)
> at
> org.apache.ambari.server.api.predicate.expressions.RelationalExpression.toPredicate(RelationalExpression.java:43)
> at
> org.apache.ambari.server.api.predicate.QueryParser.parse(QueryParser.java:99)
> at
> org.apache.ambari.server.api.predicate.PredicateCompiler.compile(PredicateCompiler.java:62)
> at
> org.apache.ambari.server.api.services.BaseRequest.parseQueryPredicate(BaseRequest.java:344)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:143)
> {code}
> {code}
> 10 Aug 2017 09:49:17,126 WARN [ambari-client-thread-597]
> AbstractResourceProvider:134 - Error occurred during preparation of stack
> advisor request
> java.lang.ClassCastException: java.util.LinkedHashSet cannot be cast to
> java.util.List
> at
> org.apache.ambari.server.controller.internal.StackAdvisorResourceProvider.prepareStackAdvisorRequest(StackAdvisorResourceProvider.java:110)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:88)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-21706) Cluster installation stuck on Customize Services Page
[
https://issues.apache.org/jira/browse/AMBARI-21706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122519#comment-16122519
]
Aravindan Vijayan edited comment on AMBARI-21706 at 8/10/17 11:20 PM:
--
This patch will refine the backend code to capture and throw an appropriate
exception message.
If the issue repros, the UI fix will be handled on a separate future jira.
was (Author: avijayan):
This patch will refine the backend code to capture and throw an appropriate
exception message.
> Cluster installation stuck on Customize Services Page
> -
>
> Key: AMBARI-21706
> URL: https://issues.apache.org/jira/browse/AMBARI-21706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.6.0
>
>
> Cluster installation stuck on Customize Services Page and wasn't loaded even
> after 4000 seconds waiting
> ambari-server.log shows:
> {code}
> 10 Aug 2017 09:48:08,356 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 -
> No clusters configured.
> 10 Aug 2017 09:49:17,123 ERROR [ambari-client-thread-593] QueryParser:115 -
> Lowercase host_name value in expression failed with
> error:java.lang.NullPointerException
> 10 Aug 2017 09:49:17,125 ERROR [ambari-client-thread-593] Request:147 -
> Unable to compile query predicate: IN operator is missing a required right
> oper
> and.
> org.apache.ambari.server.api.predicate.InvalidQueryException: IN operator is
> missing a required right operand.
> at
> org.apache.ambari.server.api.predicate.operators.InOperator.toPredicate(InOperator.java:50)
> at
> org.apache.ambari.server.api.predicate.expressions.RelationalExpression.toPredicate(RelationalExpression.java:43)
> at
> org.apache.ambari.server.api.predicate.QueryParser.parse(QueryParser.java:99)
> at
> org.apache.ambari.server.api.predicate.PredicateCompiler.compile(PredicateCompiler.java:62)
> at
> org.apache.ambari.server.api.services.BaseRequest.parseQueryPredicate(BaseRequest.java:344)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:143)
> {code}
> {code}
> 10 Aug 2017 09:49:17,126 WARN [ambari-client-thread-597]
> AbstractResourceProvider:134 - Error occurred during preparation of stack
> advisor request
> java.lang.ClassCastException: java.util.LinkedHashSet cannot be cast to
> java.util.List
> at
> org.apache.ambari.server.controller.internal.StackAdvisorResourceProvider.prepareStackAdvisorRequest(StackAdvisorResourceProvider.java:110)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:88)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21706) Cluster installation stuck on Customize Services Page
[
https://issues.apache.org/jira/browse/AMBARI-21706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122519#comment-16122519
]
Aravindan Vijayan commented on AMBARI-21706:
This patch will refine the backend code to capture and throw an appropriate
exception message.
> Cluster installation stuck on Customize Services Page
> -
>
> Key: AMBARI-21706
> URL: https://issues.apache.org/jira/browse/AMBARI-21706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.6.0
>
>
> Cluster installation stuck on Customize Services Page and wasn't loaded even
> after 4000 seconds waiting
> ambari-server.log shows:
> {code}
> 10 Aug 2017 09:48:08,356 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 -
> No clusters configured.
> 10 Aug 2017 09:49:17,123 ERROR [ambari-client-thread-593] QueryParser:115 -
> Lowercase host_name value in expression failed with
> error:java.lang.NullPointerException
> 10 Aug 2017 09:49:17,125 ERROR [ambari-client-thread-593] Request:147 -
> Unable to compile query predicate: IN operator is missing a required right
> oper
> and.
> org.apache.ambari.server.api.predicate.InvalidQueryException: IN operator is
> missing a required right operand.
> at
> org.apache.ambari.server.api.predicate.operators.InOperator.toPredicate(InOperator.java:50)
> at
> org.apache.ambari.server.api.predicate.expressions.RelationalExpression.toPredicate(RelationalExpression.java:43)
> at
> org.apache.ambari.server.api.predicate.QueryParser.parse(QueryParser.java:99)
> at
> org.apache.ambari.server.api.predicate.PredicateCompiler.compile(PredicateCompiler.java:62)
> at
> org.apache.ambari.server.api.services.BaseRequest.parseQueryPredicate(BaseRequest.java:344)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:143)
> {code}
> {code}
> 10 Aug 2017 09:49:17,126 WARN [ambari-client-thread-597]
> AbstractResourceProvider:134 - Error occurred during preparation of stack
> advisor request
> java.lang.ClassCastException: java.util.LinkedHashSet cannot be cast to
> java.util.List
> at
> org.apache.ambari.server.controller.internal.StackAdvisorResourceProvider.prepareStackAdvisorRequest(StackAdvisorResourceProvider.java:110)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:88)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21706) Cluster installation stuck on Customize Services Page
[
https://issues.apache.org/jira/browse/AMBARI-21706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122515#comment-16122515
]
Aravindan Vijayan commented on AMBARI-21706:
Both the exception traces are seen because the server is getting a request from
the UI with an unexpectedly empty host list.
In the Assign Masters page if the following call is made
{code}
http://:8080/api/v1/hosts?Hosts/host_name.in()=Hosts/cpu_count,Hosts/disk_info,Hosts/total_mem,Hosts/ip,Hosts/os_type,Hosts/os_arch,Hosts/public_host_name_response=true&_=1502392278264
{code}
it leads to the exception
{code}
10 Aug 2017 09:49:17,123 ERROR [ambari-client-thread-593] QueryParser:115 -
Lowercase host_name value in expression failed with error:java.lang.NullPoi
nterException
10 Aug 2017 09:49:17,125 ERROR [ambari-client-thread-593] Request:147 - Unable
to compile query predicate: IN operator is missing a required right operand.
{code}
and the if next /recommendations call has a request body with empty host list,
it causes the second exception
{code}
java.lang.ClassCastException: java.util.LinkedHashSet cannot be cast to
java.util.List
at
org.apache.ambari.server.controller.internal.StackAdvisorResourceProvider.prepareStackAdvisorRequest(StackAdvisorResourceProvider.java:110)
{code}
The UI call to get current 'hosts' in context is returning an empty list
(ambari/ambari-web/app/mixins/wizard/assign_master_components.js:getHosts). Not
able to reproduce this issue on 2 clusters.
> Cluster installation stuck on Customize Services Page
> -
>
> Key: AMBARI-21706
> URL: https://issues.apache.org/jira/browse/AMBARI-21706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.6.0
>
>
> Cluster installation stuck on Customize Services Page and wasn't loaded even
> after 4000 seconds waiting
> ambari-server.log shows:
> {code}
> 10 Aug 2017 09:48:08,356 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 -
> No clusters configured.
> 10 Aug 2017 09:49:17,123 ERROR [ambari-client-thread-593] QueryParser:115 -
> Lowercase host_name value in expression failed with
> error:java.lang.NullPointerException
> 10 Aug 2017 09:49:17,125 ERROR [ambari-client-thread-593] Request:147 -
> Unable to compile query predicate: IN operator is missing a required right
> oper
> and.
> org.apache.ambari.server.api.predicate.InvalidQueryException: IN operator is
> missing a required right operand.
> at
> org.apache.ambari.server.api.predicate.operators.InOperator.toPredicate(InOperator.java:50)
> at
> org.apache.ambari.server.api.predicate.expressions.RelationalExpression.toPredicate(RelationalExpression.java:43)
> at
> org.apache.ambari.server.api.predicate.QueryParser.parse(QueryParser.java:99)
> at
> org.apache.ambari.server.api.predicate.PredicateCompiler.compile(PredicateCompiler.java:62)
> at
> org.apache.ambari.server.api.services.BaseRequest.parseQueryPredicate(BaseRequest.java:344)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:143)
> {code}
> {code}
> 10 Aug 2017 09:49:17,126 WARN [ambari-client-thread-597]
> AbstractResourceProvider:134 - Error occurred during preparation of stack
> advisor request
> java.lang.ClassCastException: java.util.LinkedHashSet cannot be cast to
> java.util.List
> at
> org.apache.ambari.server.controller.internal.StackAdvisorResourceProvider.prepareStackAdvisorRequest(StackAdvisorResourceProvider.java:110)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:88)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21706) Cluster installation stuck on Customize Services Page
[
https://issues.apache.org/jira/browse/AMBARI-21706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21706:
---
Description:
Cluster installation stuck on Customize Services Page and wasn't loaded even
after 4000 seconds waiting
ambari-server.log shows:
{code}
10 Aug 2017 09:48:08,356 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 - No
clusters configured.
10 Aug 2017 09:49:17,123 ERROR [ambari-client-thread-593] QueryParser:115 -
Lowercase host_name value in expression failed with
error:java.lang.NullPointerException
10 Aug 2017 09:49:17,125 ERROR [ambari-client-thread-593] Request:147 - Unable
to compile query predicate: IN operator is missing a required right oper
and.
org.apache.ambari.server.api.predicate.InvalidQueryException: IN operator is
missing a required right operand.
at
org.apache.ambari.server.api.predicate.operators.InOperator.toPredicate(InOperator.java:50)
at
org.apache.ambari.server.api.predicate.expressions.RelationalExpression.toPredicate(RelationalExpression.java:43)
at
org.apache.ambari.server.api.predicate.QueryParser.parse(QueryParser.java:99)
at
org.apache.ambari.server.api.predicate.PredicateCompiler.compile(PredicateCompiler.java:62)
at
org.apache.ambari.server.api.services.BaseRequest.parseQueryPredicate(BaseRequest.java:344)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:143)
{code}
{code}
10 Aug 2017 09:49:17,126 WARN [ambari-client-thread-597]
AbstractResourceProvider:134 - Error occurred during preparation of stack
advisor request
java.lang.ClassCastException: java.util.LinkedHashSet cannot be cast to
java.util.List
at
org.apache.ambari.server.controller.internal.StackAdvisorResourceProvider.prepareStackAdvisorRequest(StackAdvisorResourceProvider.java:110)
at
org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:88)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
at
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
at
org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
at
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
{code}
was:Cluster installation stuck on Customize Services Page and wasn't loaded
even after 4000 seconds waiting
> Cluster installation stuck on Customize Services Page
> -
>
> Key: AMBARI-21706
> URL: https://issues.apache.org/jira/browse/AMBARI-21706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.6.0
>
>
> Cluster installation stuck on Customize Services Page and wasn't loaded even
> after 4000 seconds waiting
> ambari-server.log shows:
> {code}
> 10 Aug 2017 09:48:08,356 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 -
> No clusters configured.
> 10 Aug 2017 09:49:17,123 ERROR [ambari-client-thread-593] QueryParser:115 -
> Lowercase host_name value in expression failed with
> error:java.lang.NullPointerException
> 10 Aug 2017 09:49:17,125 ERROR [ambari-client-thread-593] Request:147 -
> Unable to compile query predicate: IN operator is missing a required right
> oper
> and.
> org.apache.ambari.server.api.predicate.InvalidQueryException: IN operator is
> missing a required right operand.
> at
> org.apache.ambari.server.api.predicate.operators.InOperator.toPredicate(InOperator.java:50)
> at
> org.apache.ambari.server.api.predicate.expressions.RelationalExpression.toPredicate(RelationalExpression.java:43)
> at
> org.apache.ambari.server.api.predicate.QueryParser.parse(QueryParser.java:99)
> at
> org.apache.ambari.server.api.predicate.PredicateCompiler.compile(PredicateCompiler.java:62)
> at
> org.apache.ambari.server.api.services.BaseRequest.parseQueryPredicate(BaseRequest.java:344)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:143)
> {code}
> {code}
> 10 Aug 2017 09:49:17,126 WARN [ambari-client-thread-597]
> AbstractResourceProvider:134 - Error occurred during preparation of stack
> advisor request
> java.lang.ClassCastException: java.util.LinkedHashSet cannot be cast to
> java.util.List
> at
>
[jira] [Created] (AMBARI-21706) Cluster installation stuck on Customize Services Page
Aravindan Vijayan created AMBARI-21706: -- Summary: Cluster installation stuck on Customize Services Page Key: AMBARI-21706 URL: https://issues.apache.org/jira/browse/AMBARI-21706 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.2 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Priority: Critical Fix For: 2.6.0 Cluster installation stuck on Customize Services Page and wasn't loaded even after 4000 seconds waiting -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21664) HDFS namenode rpc and connection load metrics are not showing
[ https://issues.apache.org/jira/browse/AMBARI-21664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122414#comment-16122414 ] Hudson commented on AMBARI-21664: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1802 (See [https://builds.apache.org/job/Ambari-branch-2.5/1802/]) AMBARI-21664. HDFS namenode rpc and connection load metrics are not (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f153268797c3d448a741ceef5dd92dd8e3d7cb48]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py > HDFS namenode rpc and connection load metrics are not showing > - > > Key: AMBARI-21664 > URL: https://issues.apache.org/jira/browse/AMBARI-21664 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.2 > Environment: CentOS 7, IOP 4.2 upgrade to Ambari 2.5.2 >Reporter: Eric Yang >Assignee: Siddharth Wagle > Fix For: 2.5.2 > > Attachments: AMBARI-21664-1.patch, AMBARI-21664.patch, > AMBARI-21664_trunk.patch > > > After upgrading from IOP 4.2 to HDP 2.6 with Ambari 2.5.2, there are two > metrics widget don't show the right results. > Namenode RPC and Namenode Connection Load graph don't show any data. This > might be caused by different implementation to fetch metrics data for those > two graphs in IOP. Check if there is a way to bridge the gap by updating > widget information or document this and ask user to remove the widget. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21705) Metrics Collector start failed due to "Unable to initialize HA controller"
[
https://issues.apache.org/jira/browse/AMBARI-21705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122391#comment-16122391
]
Siddharth Wagle commented on AMBARI-21705:
--
+1 LGTM
> Metrics Collector start failed due to "Unable to initialize HA controller"
> --
>
> Key: AMBARI-21705
> URL: https://issues.apache.org/jira/browse/AMBARI-21705
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21705.patch
>
>
> AMS start failed due to "Unable to initialize HA controller"
> STR:
> 1)Enable HA
> 2)Delete all services except HDFS, Yarn, MapReduce, Zookeeper
> 3)Add all services
> Metrics collector start, but after few minutes fail
> {code}
> Error starting ApplicationHistoryServer
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.MetricsSystemInitializationException:
> Unable to initialize HA controller at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:118)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.serviceInit(HBaseTimelineMetricStore.java:96)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:84)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:137)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: org.I0Itec.zkclient.exception.ZkException:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.I0Itec.zkclient.exception.ZkException.create(ZkException.java:68) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:1000) at
> org.apache.helix.manager.zk.ZkClient.delete(ZkClient.java:347) at
> org.I0Itec.zkclient.ZkClient.deleteRecursive(ZkClient.java:791) at
> org.apache.helix.manager.zk.ZKHelixAdmin.addCluster(ZKHelixAdmin.java:497) at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAController.initializeHAController(MetricCollectorHAController.java:156)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:115)
> ... 7 more Caused by:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:125) at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at
> org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873) at
> org.I0Itec.zkclient.ZkConnection.delete(ZkConnection.java:104) at
> org.apache.helix.manager.zk.ZkClient$8.call(ZkClient.java:351) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:990) ... 12
> more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21173) Not able to start Yarn services after restoring the configs to initial value
[
https://issues.apache.org/jira/browse/AMBARI-21173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-21173:
---
Component/s: ambari-server
> Not able to start Yarn services after restoring the configs to initial value
>
>
> Key: AMBARI-21173
> URL: https://issues.apache.org/jira/browse/AMBARI-21173
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Sumana Sathish
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21173.patch
>
>
> Change Yarn-site.xml to some custom configs and restart Yarn
> Restore it back to the origin config; Restart fails
> {Code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 106, in
> Nodemanager().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 330, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 835, in restart
> self.stop(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 45, in stop
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params.py",
> line 29, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params_linux.py",
> line 39, in
> import status_params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/status_params.py",
> line 46, in
> yarn_pid_dir = format("{yarn_pid_dir_prefix}/{yarn_user}")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'yarn-env'
> was not found in configurations dictionary!
> {Code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21173) Not able to start Yarn services after restoring the configs to initial value
[
https://issues.apache.org/jira/browse/AMBARI-21173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-21173:
---
Status: Patch Available (was: Open)
> Not able to start Yarn services after restoring the configs to initial value
>
>
> Key: AMBARI-21173
> URL: https://issues.apache.org/jira/browse/AMBARI-21173
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Sumana Sathish
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21173.patch
>
>
> Change Yarn-site.xml to some custom configs and restart Yarn
> Restore it back to the origin config; Restart fails
> {Code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 106, in
> Nodemanager().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 330, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 835, in restart
> self.stop(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 45, in stop
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params.py",
> line 29, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params_linux.py",
> line 39, in
> import status_params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/status_params.py",
> line 46, in
> yarn_pid_dir = format("{yarn_pid_dir_prefix}/{yarn_user}")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'yarn-env'
> was not found in configurations dictionary!
> {Code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21173) Not able to start Yarn services after restoring the configs to initial value
[
https://issues.apache.org/jira/browse/AMBARI-21173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-21173:
---
Attachment: AMBARI-21173.patch
> Not able to start Yarn services after restoring the configs to initial value
>
>
> Key: AMBARI-21173
> URL: https://issues.apache.org/jira/browse/AMBARI-21173
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Sumana Sathish
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21173.patch
>
>
> Change Yarn-site.xml to some custom configs and restart Yarn
> Restore it back to the origin config; Restart fails
> {Code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 106, in
> Nodemanager().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 330, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 835, in restart
> self.stop(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 45, in stop
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params.py",
> line 29, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params_linux.py",
> line 39, in
> import status_params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/status_params.py",
> line 46, in
> yarn_pid_dir = format("{yarn_pid_dir_prefix}/{yarn_user}")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'yarn-env'
> was not found in configurations dictionary!
> {Code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21173) Not able to start Yarn services after restoring the configs to initial value
[
https://issues.apache.org/jira/browse/AMBARI-21173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi reassigned AMBARI-21173:
--
Assignee: Vitaly Brodetskyi
> Not able to start Yarn services after restoring the configs to initial value
>
>
> Key: AMBARI-21173
> URL: https://issues.apache.org/jira/browse/AMBARI-21173
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Sumana Sathish
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21173.patch
>
>
> Change Yarn-site.xml to some custom configs and restart Yarn
> Restore it back to the origin config; Restart fails
> {Code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 106, in
> Nodemanager().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 330, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 835, in restart
> self.stop(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py",
> line 45, in stop
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params.py",
> line 29, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/params_linux.py",
> line 39, in
> import status_params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/status_params.py",
> line 46, in
> yarn_pid_dir = format("{yarn_pid_dir_prefix}/{yarn_user}")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'yarn-env'
> was not found in configurations dictionary!
> {Code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21705) Metrics Collector start failed due to "Unable to initialize HA controller"
[
https://issues.apache.org/jira/browse/AMBARI-21705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122322#comment-16122322
]
Hadoop QA commented on AMBARI-21705:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881279/AMBARI-21705.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-metrics/ambari-metrics-timelineservice.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11979//console
This message is automatically generated.
> Metrics Collector start failed due to "Unable to initialize HA controller"
> --
>
> Key: AMBARI-21705
> URL: https://issues.apache.org/jira/browse/AMBARI-21705
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21705.patch
>
>
> AMS start failed due to "Unable to initialize HA controller"
> STR:
> 1)Enable HA
> 2)Delete all services except HDFS, Yarn, MapReduce, Zookeeper
> 3)Add all services
> Metrics collector start, but after few minutes fail
> {code}
> Error starting ApplicationHistoryServer
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.MetricsSystemInitializationException:
> Unable to initialize HA controller at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:118)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.serviceInit(HBaseTimelineMetricStore.java:96)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:84)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:137)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: org.I0Itec.zkclient.exception.ZkException:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.I0Itec.zkclient.exception.ZkException.create(ZkException.java:68) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:1000) at
> org.apache.helix.manager.zk.ZkClient.delete(ZkClient.java:347) at
> org.I0Itec.zkclient.ZkClient.deleteRecursive(ZkClient.java:791) at
> org.apache.helix.manager.zk.ZKHelixAdmin.addCluster(ZKHelixAdmin.java:497) at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAController.initializeHAController(MetricCollectorHAController.java:156)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:115)
> ... 7 more Caused by:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:125) at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at
> org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873) at
> org.I0Itec.zkclient.ZkConnection.delete(ZkConnection.java:104) at
> org.apache.helix.manager.zk.ZkClient$8.call(ZkClient.java:351) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:990) ... 12
> more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21664) HDFS namenode rpc and connection load metrics are not showing
[ https://issues.apache.org/jira/browse/AMBARI-21664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21664: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to 2.5 2.6 and trunk were already patched. > HDFS namenode rpc and connection load metrics are not showing > - > > Key: AMBARI-21664 > URL: https://issues.apache.org/jira/browse/AMBARI-21664 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.2 > Environment: CentOS 7, IOP 4.2 upgrade to Ambari 2.5.2 >Reporter: Eric Yang >Assignee: Siddharth Wagle > Fix For: 2.5.2 > > Attachments: AMBARI-21664-1.patch, AMBARI-21664.patch, > AMBARI-21664_trunk.patch > > > After upgrading from IOP 4.2 to HDP 2.6 with Ambari 2.5.2, there are two > metrics widget don't show the right results. > Namenode RPC and Namenode Connection Load graph don't show any data. This > might be caused by different implementation to fetch metrics data for those > two graphs in IOP. Check if there is a way to bridge the gap by updating > widget information or document this and ask user to remove the widget. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21664) HDFS namenode rpc and connection load metrics are not showing
[ https://issues.apache.org/jira/browse/AMBARI-21664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122313#comment-16122313 ] Aravindan Vijayan commented on AMBARI-21664: LGTM +1 > HDFS namenode rpc and connection load metrics are not showing > - > > Key: AMBARI-21664 > URL: https://issues.apache.org/jira/browse/AMBARI-21664 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.2 > Environment: CentOS 7, IOP 4.2 upgrade to Ambari 2.5.2 >Reporter: Eric Yang >Assignee: Siddharth Wagle > Fix For: 2.5.2 > > Attachments: AMBARI-21664-1.patch, AMBARI-21664.patch, > AMBARI-21664_trunk.patch > > > After upgrading from IOP 4.2 to HDP 2.6 with Ambari 2.5.2, there are two > metrics widget don't show the right results. > Namenode RPC and Namenode Connection Load graph don't show any data. This > might be caused by different implementation to fetch metrics data for those > two graphs in IOP. Check if there is a way to bridge the gap by updating > widget information or document this and ask user to remove the widget. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21664) HDFS namenode rpc and connection load metrics are not showing
[ https://issues.apache.org/jira/browse/AMBARI-21664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122303#comment-16122303 ] Sumit Mohanty commented on AMBARI-21664: LGTM, +1 for https://issues.apache.org/jira/secure/attachment/12881320/AMBARI-21664-1.patch > HDFS namenode rpc and connection load metrics are not showing > - > > Key: AMBARI-21664 > URL: https://issues.apache.org/jira/browse/AMBARI-21664 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.2 > Environment: CentOS 7, IOP 4.2 upgrade to Ambari 2.5.2 >Reporter: Eric Yang >Assignee: Siddharth Wagle > Fix For: 2.5.2 > > Attachments: AMBARI-21664-1.patch, AMBARI-21664.patch, > AMBARI-21664_trunk.patch > > > After upgrading from IOP 4.2 to HDP 2.6 with Ambari 2.5.2, there are two > metrics widget don't show the right results. > Namenode RPC and Namenode Connection Load graph don't show any data. This > might be caused by different implementation to fetch metrics data for those > two graphs in IOP. Check if there is a way to bridge the gap by updating > widget information or document this and ask user to remove the widget. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21696) Spark thrift service was alerting for connectivity for all newly created clusters
[ https://issues.apache.org/jira/browse/AMBARI-21696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122296#comment-16122296 ] Hudson commented on AMBARI-21696: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1801 (See [https://builds.apache.org/job/Ambari-branch-2.5/1801/]) AMBARI-21696. Spark thrift service was alerting for connectivity for all (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=43c0e4946709d73bf3009dcfed68eb9820184382]) * (edit) ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/alerts/alert_spark_thrift_port.py * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/alerts/alert_spark2_thrift_port.py > Spark thrift service was alerting for connectivity for all newly created > clusters > - > > Key: AMBARI-21696 > URL: https://issues.apache.org/jira/browse/AMBARI-21696 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Fix For: 2.5.2 > > Attachments: AMBARI-21696.patch > > > Error: Could not open client transport with JDBC Uri: > jdbc:hive2://hn0-salqa0.lv5aupozrfhezhozcxr3xjcwqe.dx.internal.cloudapp.net:10016/default: > java.net.ConnectException: Connection refused (Connection refused) > (state=08S01,code=0) > This is belong to the alert service does not change the port number based on > model. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21664) HDFS namenode rpc and connection load metrics are not showing
[ https://issues.apache.org/jira/browse/AMBARI-21664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21664: - Status: Patch Available (was: Reopened) > HDFS namenode rpc and connection load metrics are not showing > - > > Key: AMBARI-21664 > URL: https://issues.apache.org/jira/browse/AMBARI-21664 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.2 > Environment: CentOS 7, IOP 4.2 upgrade to Ambari 2.5.2 >Reporter: Eric Yang >Assignee: Siddharth Wagle > Fix For: 2.5.2 > > Attachments: AMBARI-21664-1.patch, AMBARI-21664.patch, > AMBARI-21664_trunk.patch > > > After upgrading from IOP 4.2 to HDP 2.6 with Ambari 2.5.2, there are two > metrics widget don't show the right results. > Namenode RPC and Namenode Connection Load graph don't show any data. This > might be caused by different implementation to fetch metrics data for those > two graphs in IOP. Check if there is a way to bridge the gap by updating > widget information or document this and ask user to remove the widget. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21664) HDFS namenode rpc and connection load metrics are not showing
[ https://issues.apache.org/jira/browse/AMBARI-21664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21664: - Attachment: AMBARI-21664-1.patch > HDFS namenode rpc and connection load metrics are not showing > - > > Key: AMBARI-21664 > URL: https://issues.apache.org/jira/browse/AMBARI-21664 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.2 > Environment: CentOS 7, IOP 4.2 upgrade to Ambari 2.5.2 >Reporter: Eric Yang >Assignee: Siddharth Wagle > Fix For: 2.5.2 > > Attachments: AMBARI-21664-1.patch, AMBARI-21664.patch, > AMBARI-21664_trunk.patch > > > After upgrading from IOP 4.2 to HDP 2.6 with Ambari 2.5.2, there are two > metrics widget don't show the right results. > Namenode RPC and Namenode Connection Load graph don't show any data. This > might be caused by different implementation to fetch metrics data for those > two graphs in IOP. Check if there is a way to bridge the gap by updating > widget information or document this and ask user to remove the widget. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-21664) HDFS namenode rpc and connection load metrics are not showing
[
https://issues.apache.org/jira/browse/AMBARI-21664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle reopened AMBARI-21664:
--
Installing Flume without HDFS Fails as ZK, AMS and SmartSense cannot start:
Configuration parameter 'hdfs-site' was not found in configurations dictionary
HST Server, ZK server, metrics monitor fail to start
{code}
resource_management.core.exceptions.Fail: Configuration parameter 'hdfs-site'
was not found in configurations dictionary!
{code}
> HDFS namenode rpc and connection load metrics are not showing
> -
>
> Key: AMBARI-21664
> URL: https://issues.apache.org/jira/browse/AMBARI-21664
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.2
> Environment: CentOS 7, IOP 4.2 upgrade to Ambari 2.5.2
>Reporter: Eric Yang
>Assignee: Siddharth Wagle
> Fix For: 2.5.2
>
> Attachments: AMBARI-21664.patch, AMBARI-21664_trunk.patch
>
>
> After upgrading from IOP 4.2 to HDP 2.6 with Ambari 2.5.2, there are two
> metrics widget don't show the right results.
> Namenode RPC and Namenode Connection Load graph don't show any data. This
> might be caused by different implementation to fetch metrics data for those
> two graphs in IOP. Check if there is a way to bridge the gap by updating
> widget information or document this and ask user to remove the widget.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21696) Spark thrift service was alerting for connectivity for all newly created clusters
[ https://issues.apache.org/jira/browse/AMBARI-21696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122271#comment-16122271 ] Hudson commented on AMBARI-21696: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7877 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7877/]) AMBARI-21696. Spark thrift service was alerting for connectivity for all (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=24d8802d6369244a666044397ff29c3775a44dcd]) * (edit) ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/alerts/alert_spark_thrift_port.py * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/alerts/alert_spark2_thrift_port.py > Spark thrift service was alerting for connectivity for all newly created > clusters > - > > Key: AMBARI-21696 > URL: https://issues.apache.org/jira/browse/AMBARI-21696 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Fix For: 2.5.2 > > Attachments: AMBARI-21696.patch > > > Error: Could not open client transport with JDBC Uri: > jdbc:hive2://hn0-salqa0.lv5aupozrfhezhozcxr3xjcwqe.dx.internal.cloudapp.net:10016/default: > java.net.ConnectException: Connection refused (Connection refused) > (state=08S01,code=0) > This is belong to the alert service does not change the port number based on > model. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21696) Spark thrift service was alerting for connectivity for all newly created clusters
[ https://issues.apache.org/jira/browse/AMBARI-21696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-21696: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Spark thrift service was alerting for connectivity for all newly created > clusters > - > > Key: AMBARI-21696 > URL: https://issues.apache.org/jira/browse/AMBARI-21696 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Fix For: 2.5.2 > > Attachments: AMBARI-21696.patch > > > Error: Could not open client transport with JDBC Uri: > jdbc:hive2://hn0-salqa0.lv5aupozrfhezhozcxr3xjcwqe.dx.internal.cloudapp.net:10016/default: > java.net.ConnectException: Connection refused (Connection refused) > (state=08S01,code=0) > This is belong to the alert service does not change the port number based on > model. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21702) ambari-agent registration fails due to invalid public hostname
[
https://issues.apache.org/jira/browse/AMBARI-21702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Davie updated AMBARI-21702:
---
Description:
* The script {{hostname.py}}
(https://github.com/apache/ambari/blob/79cca1c7184f1661236971dac70d85a83fab6c11/ambari-agent/src/main/python/ambari_agent/hostname.py)
attempts to retrieve a host's public hostname from AWS from the location
http://169.254.169.254/latest/meta-data/public-hostname.
* In a non-AWS network with a network proxy present, this request can return an
HTML login or redirect page, rather than the expected hostname value.
* The script does not validate the length or format of the returned value, and
submits the returned HTML code to ambari-server as the public hostname.
* Registration of the host fails, as the submitted HTML code exceeds the size
of the hostname field in the server's database (255 characters).
A functioning manual workaround has been published at
https://community.hortonworks.com/articles/42872/why-ambari-host-might-have-different-public-host-n.html.
was:
* The script hostname.py
(https://github.com/apache/ambari/blob/79cca1c7184f1661236971dac70d85a83fab6c11/ambari-agent/src/main/python/ambari_agent/hostname.py)
attempts to retrieve a host's public hostname from AWS at the address
http://169.254.169.254/latest/meta-data/public-hostname.
* In a non-AWS network with a network proxy present, this request can return an
HTML login or redirect page, rather than the expected hostname value.
* The script does not validate the length or format of the returned value, and
submits the returned HTML code to ambari-server as the public hostname.
* Registration fails, as the HTML page exceeds the size (255 characters) of the
hostname field.
A functioning workaround has been published at
https://community.hortonworks.com/articles/42872/why-ambari-host-might-have-different-public-host-n.html.
> ambari-agent registration fails due to invalid public hostname
> --
>
> Key: AMBARI-21702
> URL: https://issues.apache.org/jira/browse/AMBARI-21702
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.6.0
> Environment: Networks with an active web proxy
>Reporter: Michael Davie
>
> * The script {{hostname.py}}
> (https://github.com/apache/ambari/blob/79cca1c7184f1661236971dac70d85a83fab6c11/ambari-agent/src/main/python/ambari_agent/hostname.py)
> attempts to retrieve a host's public hostname from AWS from the location
> http://169.254.169.254/latest/meta-data/public-hostname.
> * In a non-AWS network with a network proxy present, this request can return
> an HTML login or redirect page, rather than the expected hostname value.
> * The script does not validate the length or format of the returned value,
> and submits the returned HTML code to ambari-server as the public hostname.
> * Registration of the host fails, as the submitted HTML code exceeds the size
> of the hostname field in the server's database (255 characters).
> A functioning manual workaround has been published at
> https://community.hortonworks.com/articles/42872/why-ambari-host-might-have-different-public-host-n.html.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21642) Add hadoop LZO jars if installed in the cluster
[ https://issues.apache.org/jira/browse/AMBARI-21642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122151#comment-16122151 ] slim bouguerra commented on AMBARI-21642: - [~aonishuk] thanks! > Add hadoop LZO jars if installed in the cluster > --- > > Key: AMBARI-21642 > URL: https://issues.apache.org/jira/browse/AMBARI-21642 > Project: Ambari > Issue Type: Improvement >Reporter: slim bouguerra >Assignee: slim bouguerra > Fix For: 2.6.0 > > > Check the existence of hadoop lzo packages and added to the > druid-hadoop-clients directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-21325: --- Affects Version/s: 2.5.3 2.5.2 > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.5.2, 2.5.3 >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: AMBARI-21325.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether > SSL is enabled for the services listed above, the port and protocol in > params_linux.py will be updated. > 5. Update quick_view_link_view.js so that when Knox is installed and > support_knox is true, quicklink url follows knox url template specified in > the quicklinks.json for the service/component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21695) Problem in starting accumulo in upgraded cluster (IOP-HDP)
[ https://issues.apache.org/jira/browse/AMBARI-21695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121961#comment-16121961 ] Hudson commented on AMBARI-21695: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1800 (See [https://builds.apache.org/job/Ambari-branch-2.5/1800/]) AMBARI-21695. Problem in starting accumulo in upgraded cluster (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b02146cd5b3172de9081cbb43b46e54c715d0876]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/events/listeners/upgrade/StackUpgradeFinishListenerTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/StackUpgradeFinishListener.java > Problem in starting accumulo in upgraded cluster (IOP-HDP) > -- > > Key: AMBARI-21695 > URL: https://issues.apache.org/jira/browse/AMBARI-21695 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21695.patch > > > org.apache.ambari.server.metadata.CachedRoleCommandOrderProvider#getRoleCommandOrder(org.apache.ambari.server.state.Cluster) > This method caches the RCO for the stack which is never cleared. Since the BI > stack does not have Accumulo service the RCO is not honored resulting in > ACCUMULO service not starting after the express upgrade when ACCUMULO is > added. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21695) Problem in starting accumulo in upgraded cluster (IOP-HDP)
[ https://issues.apache.org/jira/browse/AMBARI-21695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121956#comment-16121956 ] Hudson commented on AMBARI-21695: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7876 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7876/]) AMBARI-21695. Problem in starting accumulo in upgraded cluster (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d2ac184c3de509d2fb6f6b46f6f0119b4f1a121d]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/StackUpgradeFinishListener.java > Problem in starting accumulo in upgraded cluster (IOP-HDP) > -- > > Key: AMBARI-21695 > URL: https://issues.apache.org/jira/browse/AMBARI-21695 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21695.patch > > > org.apache.ambari.server.metadata.CachedRoleCommandOrderProvider#getRoleCommandOrder(org.apache.ambari.server.state.Cluster) > This method caches the RCO for the stack which is never cleared. Since the BI > stack does not have Accumulo service the RCO is not honored resulting in > ACCUMULO service not starting after the express upgrade when ACCUMULO is > added. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21705) Metrics Collector start failed due to "Unable to initialize HA controller"
[
https://issues.apache.org/jira/browse/AMBARI-21705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21705:
---
Status: Patch Available (was: Open)
> Metrics Collector start failed due to "Unable to initialize HA controller"
> --
>
> Key: AMBARI-21705
> URL: https://issues.apache.org/jira/browse/AMBARI-21705
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21705.patch
>
>
> AMS start failed due to "Unable to initialize HA controller"
> STR:
> 1)Enable HA
> 2)Delete all services except HDFS, Yarn, MapReduce, Zookeeper
> 3)Add all services
> Metrics collector start, but after few minutes fail
> {code}
> Error starting ApplicationHistoryServer
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.MetricsSystemInitializationException:
> Unable to initialize HA controller at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:118)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.serviceInit(HBaseTimelineMetricStore.java:96)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:84)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:137)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: org.I0Itec.zkclient.exception.ZkException:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.I0Itec.zkclient.exception.ZkException.create(ZkException.java:68) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:1000) at
> org.apache.helix.manager.zk.ZkClient.delete(ZkClient.java:347) at
> org.I0Itec.zkclient.ZkClient.deleteRecursive(ZkClient.java:791) at
> org.apache.helix.manager.zk.ZKHelixAdmin.addCluster(ZKHelixAdmin.java:497) at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAController.initializeHAController(MetricCollectorHAController.java:156)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:115)
> ... 7 more Caused by:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:125) at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at
> org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873) at
> org.I0Itec.zkclient.ZkConnection.delete(ZkConnection.java:104) at
> org.apache.helix.manager.zk.ZkClient$8.call(ZkClient.java:351) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:990) ... 12
> more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21705) Metrics Collector start failed due to "Unable to initialize HA controller"
[
https://issues.apache.org/jira/browse/AMBARI-21705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21705:
---
Attachment: AMBARI-21705.patch
The bug is that when the collector instance is already present in the znode,
the instance treats this as a 'failure' rather than a 'success'.
Manually tested patch.
[~swagle] / [~dsen] / [~sumitmohanty] Can you review this simple patch ?
> Metrics Collector start failed due to "Unable to initialize HA controller"
> --
>
> Key: AMBARI-21705
> URL: https://issues.apache.org/jira/browse/AMBARI-21705
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21705.patch
>
>
> AMS start failed due to "Unable to initialize HA controller"
> STR:
> 1)Enable HA
> 2)Delete all services except HDFS, Yarn, MapReduce, Zookeeper
> 3)Add all services
> Metrics collector start, but after few minutes fail
> {code}
> Error starting ApplicationHistoryServer
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.MetricsSystemInitializationException:
> Unable to initialize HA controller at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:118)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.serviceInit(HBaseTimelineMetricStore.java:96)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:84)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:137)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: org.I0Itec.zkclient.exception.ZkException:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.I0Itec.zkclient.exception.ZkException.create(ZkException.java:68) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:1000) at
> org.apache.helix.manager.zk.ZkClient.delete(ZkClient.java:347) at
> org.I0Itec.zkclient.ZkClient.deleteRecursive(ZkClient.java:791) at
> org.apache.helix.manager.zk.ZKHelixAdmin.addCluster(ZKHelixAdmin.java:497) at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAController.initializeHAController(MetricCollectorHAController.java:156)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:115)
> ... 7 more Caused by:
> org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
> Directory not empty for /ambari-metrics-cluster at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:125) at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at
> org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873) at
> org.I0Itec.zkclient.ZkConnection.delete(ZkConnection.java:104) at
> org.apache.helix.manager.zk.ZkClient$8.call(ZkClient.java:351) at
> org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:990) ... 12
> more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21705) Metrics Collector start failed due to "Unable to initialize HA controller"
Aravindan Vijayan created AMBARI-21705:
--
Summary: Metrics Collector start failed due to "Unable to
initialize HA controller"
Key: AMBARI-21705
URL: https://issues.apache.org/jira/browse/AMBARI-21705
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.5.2
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Blocker
Fix For: 2.5.2
AMS start failed due to "Unable to initialize HA controller"
STR:
1)Enable HA
2)Delete all services except HDFS, Yarn, MapReduce, Zookeeper
3)Add all services
Metrics collector start, but after few minutes fail
{code}
Error starting ApplicationHistoryServer
org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.MetricsSystemInitializationException:
Unable to initialize HA controller at
org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:118)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.serviceInit(HBaseTimelineMetricStore.java:96)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) at
org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:84)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) at
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:137)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
Caused by: org.I0Itec.zkclient.exception.ZkException:
org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode =
Directory not empty for /ambari-metrics-cluster at
org.I0Itec.zkclient.exception.ZkException.create(ZkException.java:68) at
org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:1000) at
org.apache.helix.manager.zk.ZkClient.delete(ZkClient.java:347) at
org.I0Itec.zkclient.ZkClient.deleteRecursive(ZkClient.java:791) at
org.apache.helix.manager.zk.ZKHelixAdmin.addCluster(ZKHelixAdmin.java:497) at
org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAController.initializeHAController(MetricCollectorHAController.java:156)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricStore.java:115)
... 7 more Caused by: org.apache.zookeeper.KeeperException$NotEmptyException:
KeeperErrorCode = Directory not empty for /ambari-metrics-cluster at
org.apache.zookeeper.KeeperException.create(KeeperException.java:125) at
org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at
org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873) at
org.I0Itec.zkclient.ZkConnection.delete(ZkConnection.java:104) at
org.apache.helix.manager.zk.ZkClient$8.call(ZkClient.java:351) at
org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:990) ... 12 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21704) Upgrade Wizard Has Incorrect Title
[
https://issues.apache.org/jira/browse/AMBARI-21704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121912#comment-16121912
]
Hadoop QA commented on AMBARI-21704:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881267/AMBARI-21704.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/11978//console
This message is automatically generated.
> Upgrade Wizard Has Incorrect Title
> --
>
> Key: AMBARI-21704
> URL: https://issues.apache.org/jira/browse/AMBARI-21704
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.3
>
> Attachments: AMBARI-21704.patch, Screen Shot 2017-08-03 at 1.53.31
> PM.png
>
>
> Perform an Express {{PATCH}} upgrade. The upgrade wizard dialog will have an
> incorrect title of "Upgrade to Express Upgrade". I would have expected
> something like:
> - Express Upgrade to HDP-2.5.4.0-1234
> - Express Patch Upgrade to HDP-2.5.4.0-1234
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21625) Failed to update custom repos defined via service extension after such a service is installed to cluster
[
https://issues.apache.org/jira/browse/AMBARI-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle resolved AMBARI-21625.
--
Resolution: Cannot Reproduce
> Failed to update custom repos defined via service extension after such a
> service is installed to cluster
>
>
> Key: AMBARI-21625
> URL: https://issues.apache.org/jira/browse/AMBARI-21625
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Di Li
>Assignee: Balázs Bence Sári
> Fix For: 2.5.2
>
>
> This should be a general issue that can be reproduced by having a service as
> an extension. add it to an HDP 2.6.2/Ambari 2.5.2 cluster, then try to update
> repos for the HDP 2.6.2 stack.
> Our QA hit on BigSQL, but it doesn't have to be BigSQL to reproduce.
> Our QA hit the following error on HDP/HDP upgrade ( will most likely to hit
> it also on the migration):
> *Case* HDP 2.4/BigSQL 4.2.5 upgrade to HDP 2.5.1/BigSQL 5.0.1
> *Error* Updating BigSQL URL via UI and via REST API throws errors, after
> adding BigSQL back to the cluster post HDP 2.5.1 EU.
> ```Via UI: The validation will fail with ambari server side error:
> An internal syste
> m exception occurred: Stack data, stackName=HDP, stackVersion= 2.5,
> osType=redhat7,
> repoId= IBM-Big_SQL
> Via REST API:
> {
> "status" : 404,
> "message" :
> "org.apache.ambari.server.controller.spi.NoSuchResourceException: The
> specified resource doesn't exist: Stack data, stackName=HDP, stackVersion=
> 2.5, osType=redhat7, repoId= IBM-Big_SQL"
> }```
> *Investigation*: Ambari server failed to reads BigSQL's repoinfo.xml
> (defined as part of the extension
> /var/lib/ambari-server/resources/extensions/IBM-Big_SQL/5.0.1.0/services/BIGSQL/repos/repoinfo.xml
> ) for the repo id. It only reads repo ids defined in
> /var/lib/ambari-server/resources/stacks/HDP/2.6/repos/repoinfo.xml
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21704) Upgrade Wizard Has Incorrect Title
[
https://issues.apache.org/jira/browse/AMBARI-21704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121883#comment-16121883
]
Andrii Babiichuk commented on AMBARI-21704:
---
+1 for the patch
> Upgrade Wizard Has Incorrect Title
> --
>
> Key: AMBARI-21704
> URL: https://issues.apache.org/jira/browse/AMBARI-21704
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.3
>
> Attachments: AMBARI-21704.patch, Screen Shot 2017-08-03 at 1.53.31
> PM.png
>
>
> Perform an Express {{PATCH}} upgrade. The upgrade wizard dialog will have an
> incorrect title of "Upgrade to Express Upgrade". I would have expected
> something like:
> - Express Upgrade to HDP-2.5.4.0-1234
> - Express Patch Upgrade to HDP-2.5.4.0-1234
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21704) Upgrade Wizard Has Incorrect Title
[
https://issues.apache.org/jira/browse/AMBARI-21704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-21704:
--
Description:
Perform an Express {{PATCH}} upgrade. The upgrade wizard dialog will have an
incorrect title of "Upgrade to Express Upgrade". I would have expected
something like:
- Express Upgrade to HDP-2.5.4.0-1234
- Express Patch Upgrade to HDP-2.5.4.0-1234
was:
Perform an Express PATCH upgrade. The upgrade wizard dialog will have an
incorrect title of "Upgrade to Express Upgrade". I would have expected
something like:
Express Upgrade to HDP-2.5.4.0-1234
Express Patch Upgrade to HDP-2.5.4.0-1234
> Upgrade Wizard Has Incorrect Title
> --
>
> Key: AMBARI-21704
> URL: https://issues.apache.org/jira/browse/AMBARI-21704
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.3
>
> Attachments: AMBARI-21704.patch, Screen Shot 2017-08-03 at 1.53.31
> PM.png
>
>
> Perform an Express {{PATCH}} upgrade. The upgrade wizard dialog will have an
> incorrect title of "Upgrade to Express Upgrade". I would have expected
> something like:
> - Express Upgrade to HDP-2.5.4.0-1234
> - Express Patch Upgrade to HDP-2.5.4.0-1234
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21704) Upgrade Wizard Has Incorrect Title
[ https://issues.apache.org/jira/browse/AMBARI-21704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121877#comment-16121877 ] Andrii Tkach commented on AMBARI-21704: --- 30463 passing (27s) 157 pending > Upgrade Wizard Has Incorrect Title > -- > > Key: AMBARI-21704 > URL: https://issues.apache.org/jira/browse/AMBARI-21704 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21704.patch, Screen Shot 2017-08-03 at 1.53.31 > PM.png > > > Perform an Express PATCH upgrade. The upgrade wizard dialog will have an > incorrect title of "Upgrade to Express Upgrade". I would have expected > something like: > Express Upgrade to HDP-2.5.4.0-1234 > Express Patch Upgrade to HDP-2.5.4.0-1234 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21704) Upgrade Wizard Has Incorrect Title
[ https://issues.apache.org/jira/browse/AMBARI-21704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21704: -- Status: Patch Available (was: In Progress) > Upgrade Wizard Has Incorrect Title > -- > > Key: AMBARI-21704 > URL: https://issues.apache.org/jira/browse/AMBARI-21704 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21704.patch, Screen Shot 2017-08-03 at 1.53.31 > PM.png > > > Perform an Express PATCH upgrade. The upgrade wizard dialog will have an > incorrect title of "Upgrade to Express Upgrade". I would have expected > something like: > Express Upgrade to HDP-2.5.4.0-1234 > Express Patch Upgrade to HDP-2.5.4.0-1234 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21695) Problem in starting accumulo in upgraded cluster (IOP-HDP)
[ https://issues.apache.org/jira/browse/AMBARI-21695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121878#comment-16121878 ] Hudson commented on AMBARI-21695: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7875 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7875/]) AMBARI-21695. Problem in starting accumulo in upgraded cluster (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=64a3926fb430a128fbda63a3477f8330e2562c58]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/events/listeners/upgrade/StackUpgradeFinishListenerTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/StackUpgradeFinishListener.java > Problem in starting accumulo in upgraded cluster (IOP-HDP) > -- > > Key: AMBARI-21695 > URL: https://issues.apache.org/jira/browse/AMBARI-21695 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21695.patch > > > org.apache.ambari.server.metadata.CachedRoleCommandOrderProvider#getRoleCommandOrder(org.apache.ambari.server.state.Cluster) > This method caches the RCO for the stack which is never cleared. Since the BI > stack does not have Accumulo service the RCO is not honored resulting in > ACCUMULO service not starting after the express upgrade when ACCUMULO is > added. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21704) Upgrade Wizard Has Incorrect Title
[ https://issues.apache.org/jira/browse/AMBARI-21704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21704: -- Attachment: AMBARI-21704.patch > Upgrade Wizard Has Incorrect Title > -- > > Key: AMBARI-21704 > URL: https://issues.apache.org/jira/browse/AMBARI-21704 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21704.patch, Screen Shot 2017-08-03 at 1.53.31 > PM.png > > > Perform an Express PATCH upgrade. The upgrade wizard dialog will have an > incorrect title of "Upgrade to Express Upgrade". I would have expected > something like: > Express Upgrade to HDP-2.5.4.0-1234 > Express Patch Upgrade to HDP-2.5.4.0-1234 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21704) Upgrade Wizard Has Incorrect Title
[ https://issues.apache.org/jira/browse/AMBARI-21704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21704: -- Attachment: Screen Shot 2017-08-03 at 1.53.31 PM.png > Upgrade Wizard Has Incorrect Title > -- > > Key: AMBARI-21704 > URL: https://issues.apache.org/jira/browse/AMBARI-21704 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: Screen Shot 2017-08-03 at 1.53.31 PM.png > > > Perform an Express PATCH upgrade. The upgrade wizard dialog will have an > incorrect title of "Upgrade to Express Upgrade". I would have expected > something like: > Express Upgrade to HDP-2.5.4.0-1234 > Express Patch Upgrade to HDP-2.5.4.0-1234 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21704) Upgrade Wizard Has Incorrect Title
Andrii Tkach created AMBARI-21704: - Summary: Upgrade Wizard Has Incorrect Title Key: AMBARI-21704 URL: https://issues.apache.org/jira/browse/AMBARI-21704 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.3 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.5.3 Perform an Express PATCH upgrade. The upgrade wizard dialog will have an incorrect title of "Upgrade to Express Upgrade". I would have expected something like: Express Upgrade to HDP-2.5.4.0-1234 Express Patch Upgrade to HDP-2.5.4.0-1234 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21169) Service and Patch Upgrade Catalog Changes for 2.6.0
[
https://issues.apache.org/jira/browse/AMBARI-21169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21169:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
6c5faee5c0..2307c9d499 branch-feature-AMBARI-21450 ->
branch-feature-AMBARI-21450
> Service and Patch Upgrade Catalog Changes for 2.6.0
> ---
>
> Key: AMBARI-21169
> URL: https://issues.apache.org/jira/browse/AMBARI-21169
> Project: Ambari
> Issue Type: Task
> Components: ambari-upgrade
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21169.patch
>
>
> Implement the following upgrade catalog changes related to service/patch
> upgrades:
> h5. {{servicecomponentdesiredstate}}
> - Remove: desired_stack_id BIGINT NOT NULL
> - Remove: desired_version VARCHAR(255) NOT NULL DEFAULT 'UNKNOWN'
> - Remove: FK on desired_stack_id (FK_scds_desired_stack_id)
> - Add: desired_repo_version_id BIGINT NOT NULL
> - Add: FK to repo_version_id (FK_scds_desired_repo_id)
> h5. {{hostcomponentdesiredstate}}
> - Remove: desired_stack_id BIGINT NOT NULL
> - Remove: FK on desired_stack_id (FK_hcds_desired_stack_id)
> h5. {{hostcomponentstate}}
> - Remove: current_stack_id BIGINT NOT NULL
> - Remove: FK on desired_stack_id (FK_hcs_current_stack_id)
> h5. {{servicedesiredstate}}
> - Remove: desired_stack_id BIGINT NOT NULL
> - Add: desired_repo_version_id BIGINT NOT NULL
> - Add: FK to repo_version_id (FK_repo_version_id)
> h5. {{host_version}}
> - Change the {{UNIQUE}} constraint to allow for multiple {{CURRENT}}
> repositories per host. Restriction should also include the
> {{repo_version_id}} for uniqueness now.
> h5. {{cluster_version}}
> - This table was removed.
> h5. {{servicecomponent_version}}
> - Create this table and populate with data
> h5. {{upgrade}}
> - Add orchestration VARCHAR(255) NOT NULL DEFAULT 'STANDARD'
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster
[
https://issues.apache.org/jira/browse/AMBARI-21125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-21125:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
> Labels: spark
> Fix For: 2.5.2
>
> Attachments: BUG-81619.diff
>
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException:
> Unsupported mechanism type PLAIN
>
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException:
> Unsupported mechanism type PLAIN
>
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException:
> Unsupported mechanism type PLAIN
>
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException:
> Unsupported mechanism type PLAIN
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21625) Failed to update custom repos defined via service extension after such a service is installed to cluster
[
https://issues.apache.org/jira/browse/AMBARI-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121800#comment-16121800
]
Di Li commented on AMBARI-21625:
Hello Balázs Bence Sári,
Tim and I gave our QA new steps and that appeared to have resolved the issue I
reported here. I have talked to my QA and we decided it's ok to close this JIRA
for now. I will reopen if he hit it in any way later on.
Please close it for now.
Thanks.
> Failed to update custom repos defined via service extension after such a
> service is installed to cluster
>
>
> Key: AMBARI-21625
> URL: https://issues.apache.org/jira/browse/AMBARI-21625
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Di Li
>Assignee: Balázs Bence Sári
> Fix For: 2.5.2
>
>
> This should be a general issue that can be reproduced by having a service as
> an extension. add it to an HDP 2.6.2/Ambari 2.5.2 cluster, then try to update
> repos for the HDP 2.6.2 stack.
> Our QA hit on BigSQL, but it doesn't have to be BigSQL to reproduce.
> Our QA hit the following error on HDP/HDP upgrade ( will most likely to hit
> it also on the migration):
> *Case* HDP 2.4/BigSQL 4.2.5 upgrade to HDP 2.5.1/BigSQL 5.0.1
> *Error* Updating BigSQL URL via UI and via REST API throws errors, after
> adding BigSQL back to the cluster post HDP 2.5.1 EU.
> ```Via UI: The validation will fail with ambari server side error:
> An internal syste
> m exception occurred: Stack data, stackName=HDP, stackVersion= 2.5,
> osType=redhat7,
> repoId= IBM-Big_SQL
> Via REST API:
> {
> "status" : 404,
> "message" :
> "org.apache.ambari.server.controller.spi.NoSuchResourceException: The
> specified resource doesn't exist: Stack data, stackName=HDP, stackVersion=
> 2.5, osType=redhat7, repoId= IBM-Big_SQL"
> }```
> *Investigation*: Ambari server failed to reads BigSQL's repoinfo.xml
> (defined as part of the extension
> /var/lib/ambari-server/resources/extensions/IBM-Big_SQL/5.0.1.0/services/BIGSQL/repos/repoinfo.xml
> ) for the repo id. It only reads repo ids defined in
> /var/lib/ambari-server/resources/stacks/HDP/2.6/repos/repoinfo.xml
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121798#comment-16121798 ] Jeffrey E Rodriguez commented on AMBARI-21325: --- Hi Chandana, et all. What is the status of this AMBARI-21325 patch? Is the core test failure relevant?? > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: AMBARI-21325.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether > SSL is enabled for the services listed above, the port and protocol in > params_linux.py will be updated. > 5. Update quick_view_link_view.js so that when Knox is installed and > support_knox is true, quicklink url follows knox url template specified in > the quicklinks.json for the service/component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21698) Error starting client components on RedHat7 and BI 4.2.5 after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121795#comment-16121795
]
Hudson commented on AMBARI-21698:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1799 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1799/])
AMBARI-21698. Error starting client components on RedHat7 and BI 4.2.5
(adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3c5ec6a46dcc76f00dcc5278ed4e38ec2e8fed02])
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/repos/repoinfo.xml
> Error starting client components on RedHat7 and BI 4.2.5 after Ambari upgrade
> -
>
> Key: AMBARI-21698
> URL: https://issues.apache.org/jira/browse/AMBARI-21698
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Labels: system_test
> Fix For: 2.5.2
>
> Attachments: AMBARI-21698.patch
>
>
> *STR*
> # Deployed IOP-4.2.5 cluster with Ambari-2.4.2
> # Upgrade Ambari to 2.5.2
> # Stop Hbase service and delete HBASE_REST_SERVER component via API
> # Try to start HBase service
> Result
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/hook.py",
> line 33, in hook
> install_repos()
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/repo_initialization.py",
> line 68, in install_repos
> _alter_repo("create", params.repo_info, template)
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/repo_initialization.py",
> line 35, in _alter_repo
> repo_dicts = json.loads(repo_string)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21701) Add check for import from relocated packages
[
https://issues.apache.org/jira/browse/AMBARI-21701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121785#comment-16121785
]
Hudson commented on AMBARI-21701:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7874 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7874/])
AMBARI-21701. Add check for import from relocated packages (adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8895386bcc7b122788ae2af42031ff0e786c7733])
* (edit) ambari-server/checkstyle.xml
> Add check for import from relocated packages
>
>
> Key: AMBARI-21701
> URL: https://issues.apache.org/jira/browse/AMBARI-21701
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-21701.patch
>
>
> Occasionally an import from {{org.apache.hadoop.metrics2.sink.relocated}}
> creeps into {{ambari-server}} source code, causing compile errors:
> {noformat}
> $ mvn -am -pl ambari-server clean test
> ...
> [ERROR]
> ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[39,71]
> package org.apache.hadoop.metrics2.sink.relocated.google.common.collect does
> not exist
> [ERROR]
> ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[114,34]
> cannot find symbol
> [ERROR] symbol: variable Sets
> [ERROR] location: class
> org.apache.ambari.server.checks.AbstractCheckDescriptorTest
> {noformat}
> The problem is that the same code can be compiled if dependencies are already
> installed in one's local Maven repository.
> {noformat}
> $ mvn -am -pl
> ambari-metrics/ambari-metrics-common,ambari-serviceadvisor,ambari-views clean
> install
> ...
> $ mvn -pl ambari-server clean test
> ...
> [INFO] BUILD SUCCESS
> {noformat}
> This succeeds because {{ambari-metrics-common}} installs a shaded uber jar
> including the {{..relocated..}} packages, hence they are available when
> compiling {{ambari-server}}. On the other hand, when building from scratch
> (selectively with {{-am -pl ...}}, or the entire multimodule project)
> classpath contains {{ambari-metrics-common}} classes and individual
> dependencies without relocation.
> The goal of this change is to add a checkstyle check to catch such imports at
> build-time with both compilation methods.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21698) Error starting client components on RedHat7 and BI 4.2.5 after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21698:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
[branch-2.5|http://git-wip-us.apache.org/repos/asf/ambari/commit/3c5ec6a46d].
> Error starting client components on RedHat7 and BI 4.2.5 after Ambari upgrade
> -
>
> Key: AMBARI-21698
> URL: https://issues.apache.org/jira/browse/AMBARI-21698
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Labels: system_test
> Fix For: 2.5.2
>
> Attachments: AMBARI-21698.patch
>
>
> *STR*
> # Deployed IOP-4.2.5 cluster with Ambari-2.4.2
> # Upgrade Ambari to 2.5.2
> # Stop Hbase service and delete HBASE_REST_SERVER component via API
> # Try to start HBase service
> Result
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/hook.py",
> line 33, in hook
> install_repos()
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/repo_initialization.py",
> line 68, in install_repos
> _alter_repo("create", params.repo_info, template)
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/repo_initialization.py",
> line 35, in _alter_repo
> repo_dicts = json.loads(repo_string)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21701) Add check for import from relocated packages
[
https://issues.apache.org/jira/browse/AMBARI-21701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21701:
---
Resolution: Implemented
Status: Resolved (was: Patch Available)
Committed to
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/8895386bcc].
> Add check for import from relocated packages
>
>
> Key: AMBARI-21701
> URL: https://issues.apache.org/jira/browse/AMBARI-21701
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-21701.patch
>
>
> Occasionally an import from {{org.apache.hadoop.metrics2.sink.relocated}}
> creeps into {{ambari-server}} source code, causing compile errors:
> {noformat}
> $ mvn -am -pl ambari-server clean test
> ...
> [ERROR]
> ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[39,71]
> package org.apache.hadoop.metrics2.sink.relocated.google.common.collect does
> not exist
> [ERROR]
> ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[114,34]
> cannot find symbol
> [ERROR] symbol: variable Sets
> [ERROR] location: class
> org.apache.ambari.server.checks.AbstractCheckDescriptorTest
> {noformat}
> The problem is that the same code can be compiled if dependencies are already
> installed in one's local Maven repository.
> {noformat}
> $ mvn -am -pl
> ambari-metrics/ambari-metrics-common,ambari-serviceadvisor,ambari-views clean
> install
> ...
> $ mvn -pl ambari-server clean test
> ...
> [INFO] BUILD SUCCESS
> {noformat}
> This succeeds because {{ambari-metrics-common}} installs a shaded uber jar
> including the {{..relocated..}} packages, hence they are available when
> compiling {{ambari-server}}. On the other hand, when building from scratch
> (selectively with {{-am -pl ...}}, or the entire multimodule project)
> classpath contains {{ambari-metrics-common}} classes and individual
> dependencies without relocation.
> The goal of this change is to add a checkstyle check to catch such imports at
> build-time with both compilation methods.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files
[
https://issues.apache.org/jira/browse/AMBARI-21692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121758#comment-16121758
]
Hadoop QA commented on AMBARI-21692:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881203/AMBARI-21692.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11975//console
This message is automatically generated.
> dfs.include file is created on all datanode hosts when Ambari manages
> include/exclude files
> ---
>
> Key: AMBARI-21692
> URL: https://issues.apache.org/jira/browse/AMBARI-21692
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.5.2
>Reporter: Dhanya Balasundaran
>Assignee: Dmytro Sen
> Fix For: 2.5.2
>
> Attachments: AMBARI-21692.patch
>
>
> - deploy cluster with default configs
> - Update manage.include.files to true in hdfs-site.xml
> - Add property dfs.hosts=/etc/hadoop/conf/dfs.include in cstm-hdfs-site.xml
> - Create /etc/hadoop/conf/dfs.include on Namenode host
> - Restart all required services
> - dfs.include gets created on all datanode hosts.
> Tried the same with Yarn, yarn.include will be present only on
> Resourcemanager node and doesnt get created on any other nodes(eg: one with
> nodemanager)
> Ideally dfs.include should not be created on all datanode hosts
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21701) Add check for import from relocated packages
[
https://issues.apache.org/jira/browse/AMBARI-21701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121673#comment-16121673
]
Hadoop QA commented on AMBARI-21701:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881214/AMBARI-21701.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11974//console
This message is automatically generated.
> Add check for import from relocated packages
>
>
> Key: AMBARI-21701
> URL: https://issues.apache.org/jira/browse/AMBARI-21701
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-21701.patch
>
>
> Occasionally an import from {{org.apache.hadoop.metrics2.sink.relocated}}
> creeps into {{ambari-server}} source code, causing compile errors:
> {noformat}
> $ mvn -am -pl ambari-server clean test
> ...
> [ERROR]
> ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[39,71]
> package org.apache.hadoop.metrics2.sink.relocated.google.common.collect does
> not exist
> [ERROR]
> ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[114,34]
> cannot find symbol
> [ERROR] symbol: variable Sets
> [ERROR] location: class
> org.apache.ambari.server.checks.AbstractCheckDescriptorTest
> {noformat}
> The problem is that the same code can be compiled if dependencies are already
> installed in one's local Maven repository.
> {noformat}
> $ mvn -am -pl
> ambari-metrics/ambari-metrics-common,ambari-serviceadvisor,ambari-views clean
> install
> ...
> $ mvn -pl ambari-server clean test
> ...
> [INFO] BUILD SUCCESS
> {noformat}
> This succeeds because {{ambari-metrics-common}} installs a shaded uber jar
> including the {{..relocated..}} packages, hence they are available when
> compiling {{ambari-server}}. On the other hand, when building from scratch
> (selectively with {{-am -pl ...}}, or the entire multimodule project)
> classpath contains {{ambari-metrics-common}} classes and individual
> dependencies without relocation.
> The goal of this change is to add a checkstyle check to catch such imports at
> build-time with both compilation methods.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21693) Can't register multiple PATCH versions
[
https://issues.apache.org/jira/browse/AMBARI-21693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121671#comment-16121671
]
Hudson commented on AMBARI-21693:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7873 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7873/])
AMBARI-21693. Can't register multiple PATCH versions (ncole) (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7a3ffea9e4236c2ad58b05ff7af8a31691c96ce6])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepositoryVersionEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/RepositoryVersionDAO.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProviderTest.java
> Can't register multiple PATCH versions
> --
>
> Key: AMBARI-21693
> URL: https://issues.apache.org/jira/browse/AMBARI-21693
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21693.patch
>
>
> Deploy cluster with HDP-2.5.3.0-37, then register PATCH vdf with
> HDP-2.5.3.0-38.
> When you try to register PATCH vdf with HDP-2.5.3.0-39, server returns an
> error:
> {noformat}
> {
> "status" : 400,
> "message" : "More than one repository matches patch 2.5.3.0-36: 2.5.3.0-38,
> 2.5.3.0-39"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21625) Failed to update custom repos defined via service extension after such a service is installed to cluster
[
https://issues.apache.org/jira/browse/AMBARI-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121657#comment-16121657
]
Balázs Bence Sári commented on AMBARI-21625:
cc [~Tim Thorpe]
> Failed to update custom repos defined via service extension after such a
> service is installed to cluster
>
>
> Key: AMBARI-21625
> URL: https://issues.apache.org/jira/browse/AMBARI-21625
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Di Li
>Assignee: Balázs Bence Sári
> Fix For: 2.5.2
>
>
> This should be a general issue that can be reproduced by having a service as
> an extension. add it to an HDP 2.6.2/Ambari 2.5.2 cluster, then try to update
> repos for the HDP 2.6.2 stack.
> Our QA hit on BigSQL, but it doesn't have to be BigSQL to reproduce.
> Our QA hit the following error on HDP/HDP upgrade ( will most likely to hit
> it also on the migration):
> *Case* HDP 2.4/BigSQL 4.2.5 upgrade to HDP 2.5.1/BigSQL 5.0.1
> *Error* Updating BigSQL URL via UI and via REST API throws errors, after
> adding BigSQL back to the cluster post HDP 2.5.1 EU.
> ```Via UI: The validation will fail with ambari server side error:
> An internal syste
> m exception occurred: Stack data, stackName=HDP, stackVersion= 2.5,
> osType=redhat7,
> repoId= IBM-Big_SQL
> Via REST API:
> {
> "status" : 404,
> "message" :
> "org.apache.ambari.server.controller.spi.NoSuchResourceException: The
> specified resource doesn't exist: Stack data, stackName=HDP, stackVersion=
> 2.5, osType=redhat7, repoId= IBM-Big_SQL"
> }```
> *Investigation*: Ambari server failed to reads BigSQL's repoinfo.xml
> (defined as part of the extension
> /var/lib/ambari-server/resources/extensions/IBM-Big_SQL/5.0.1.0/services/BIGSQL/repos/repoinfo.xml
> ) for the repo id. It only reads repo ids defined in
> /var/lib/ambari-server/resources/stacks/HDP/2.6/repos/repoinfo.xml
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21703) UI must consume API to show whether a service will be upgraded
[ https://issues.apache.org/jira/browse/AMBARI-21703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121655#comment-16121655 ] Andrii Tkach commented on AMBARI-21703: --- +1 for the patch > UI must consume API to show whether a service will be upgraded > -- > > Key: AMBARI-21703 > URL: https://issues.apache.org/jira/browse/AMBARI-21703 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.3 > > Attachments: AMBARI-21703.patch > > > use the API to indicate if a service is going to be upgraded based on its > version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21703) UI must consume API to show whether a service will be upgraded
[ https://issues.apache.org/jira/browse/AMBARI-21703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21703: - Status: Patch Available (was: Open) > UI must consume API to show whether a service will be upgraded > -- > > Key: AMBARI-21703 > URL: https://issues.apache.org/jira/browse/AMBARI-21703 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.3 > > Attachments: AMBARI-21703.patch > > > use the API to indicate if a service is going to be upgraded based on its > version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21703) UI must consume API to show whether a service will be upgraded
[ https://issues.apache.org/jira/browse/AMBARI-21703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21703: Assignee: Antonenko Alexander > UI must consume API to show whether a service will be upgraded > -- > > Key: AMBARI-21703 > URL: https://issues.apache.org/jira/browse/AMBARI-21703 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.3 > > Attachments: AMBARI-21703.patch > > > use the API to indicate if a service is going to be upgraded based on its > version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21703) UI must consume API to show whether a service will be upgraded
[ https://issues.apache.org/jira/browse/AMBARI-21703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21703: - Attachment: AMBARI-21703.patch > UI must consume API to show whether a service will be upgraded > -- > > Key: AMBARI-21703 > URL: https://issues.apache.org/jira/browse/AMBARI-21703 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Antonenko Alexander > Fix For: 2.5.3 > > Attachments: AMBARI-21703.patch > > > use the API to indicate if a service is going to be upgraded based on its > version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21703) UI must consume API to show whether a service will be upgraded
Antonenko Alexander created AMBARI-21703: Summary: UI must consume API to show whether a service will be upgraded Key: AMBARI-21703 URL: https://issues.apache.org/jira/browse/AMBARI-21703 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.3 Reporter: Antonenko Alexander Fix For: 2.5.3 use the API to indicate if a service is going to be upgraded based on its version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21702) ambari-agent registration fails due to invalid public hostname
Michael Davie created AMBARI-21702: -- Summary: ambari-agent registration fails due to invalid public hostname Key: AMBARI-21702 URL: https://issues.apache.org/jira/browse/AMBARI-21702 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.6.0 Environment: Networks with an active web proxy Reporter: Michael Davie * The script hostname.py (https://github.com/apache/ambari/blob/79cca1c7184f1661236971dac70d85a83fab6c11/ambari-agent/src/main/python/ambari_agent/hostname.py) attempts to retrieve a host's public hostname from AWS at the address http://169.254.169.254/latest/meta-data/public-hostname. * In a non-AWS network with a network proxy present, this request can return an HTML login or redirect page, rather than the expected hostname value. * The script does not validate the length or format of the returned value, and submits the returned HTML code to ambari-server as the public hostname. * Registration fails, as the HTML page exceeds the size (255 characters) of the hostname field. A functioning workaround has been published at https://community.hortonworks.com/articles/42872/why-ambari-host-might-have-different-public-host-n.html. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21701) Add check for import from relocated packages
[
https://issues.apache.org/jira/browse/AMBARI-21701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21701:
---
Status: Patch Available (was: In Progress)
> Add check for import from relocated packages
>
>
> Key: AMBARI-21701
> URL: https://issues.apache.org/jira/browse/AMBARI-21701
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-21701.patch
>
>
> Occasionally an import from {{org.apache.hadoop.metrics2.sink.relocated}}
> creeps into {{ambari-server}} source code, causing compile errors:
> {noformat}
> $ mvn -am -pl ambari-server clean test
> ...
> [ERROR]
> ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[39,71]
> package org.apache.hadoop.metrics2.sink.relocated.google.common.collect does
> not exist
> [ERROR]
> ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[114,34]
> cannot find symbol
> [ERROR] symbol: variable Sets
> [ERROR] location: class
> org.apache.ambari.server.checks.AbstractCheckDescriptorTest
> {noformat}
> The problem is that the same code can be compiled if dependencies are already
> installed in one's local Maven repository.
> {noformat}
> $ mvn -am -pl
> ambari-metrics/ambari-metrics-common,ambari-serviceadvisor,ambari-views clean
> install
> ...
> $ mvn -pl ambari-server clean test
> ...
> [INFO] BUILD SUCCESS
> {noformat}
> This succeeds because {{ambari-metrics-common}} installs a shaded uber jar
> including the {{..relocated..}} packages, hence they are available when
> compiling {{ambari-server}}. On the other hand, when building from scratch
> (selectively with {{-am -pl ...}}, or the entire multimodule project)
> classpath contains {{ambari-metrics-common}} classes and individual
> dependencies without relocation.
> The goal of this change is to add a checkstyle check to catch such imports at
> build-time with both compilation methods.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21701) Add check for import from relocated packages
[
https://issues.apache.org/jira/browse/AMBARI-21701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21701:
---
Attachment: AMBARI-21701.patch
> Add check for import from relocated packages
>
>
> Key: AMBARI-21701
> URL: https://issues.apache.org/jira/browse/AMBARI-21701
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-21701.patch
>
>
> Occasionally an import from {{org.apache.hadoop.metrics2.sink.relocated}}
> creeps into {{ambari-server}} source code, causing compile errors:
> {noformat}
> $ mvn -am -pl ambari-server clean test
> ...
> [ERROR]
> ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[39,71]
> package org.apache.hadoop.metrics2.sink.relocated.google.common.collect does
> not exist
> [ERROR]
> ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[114,34]
> cannot find symbol
> [ERROR] symbol: variable Sets
> [ERROR] location: class
> org.apache.ambari.server.checks.AbstractCheckDescriptorTest
> {noformat}
> The problem is that the same code can be compiled if dependencies are already
> installed in one's local Maven repository.
> {noformat}
> $ mvn -am -pl
> ambari-metrics/ambari-metrics-common,ambari-serviceadvisor,ambari-views clean
> install
> ...
> $ mvn -pl ambari-server clean test
> ...
> [INFO] BUILD SUCCESS
> {noformat}
> This succeeds because {{ambari-metrics-common}} installs a shaded uber jar
> including the {{..relocated..}} packages, hence they are available when
> compiling {{ambari-server}}. On the other hand, when building from scratch
> (selectively with {{-am -pl ...}}, or the entire multimodule project)
> classpath contains {{ambari-metrics-common}} classes and individual
> dependencies without relocation.
> The goal of this change is to add a checkstyle check to catch such imports at
> build-time with both compilation methods.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files
[
https://issues.apache.org/jira/browse/AMBARI-21692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121583#comment-16121583
]
Hadoop QA commented on AMBARI-21692:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881203/AMBARI-21692.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11973//console
This message is automatically generated.
> dfs.include file is created on all datanode hosts when Ambari manages
> include/exclude files
> ---
>
> Key: AMBARI-21692
> URL: https://issues.apache.org/jira/browse/AMBARI-21692
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.5.2
>Reporter: Dhanya Balasundaran
>Assignee: Dmytro Sen
> Fix For: 2.5.2
>
> Attachments: AMBARI-21692.patch
>
>
> - deploy cluster with default configs
> - Update manage.include.files to true in hdfs-site.xml
> - Add property dfs.hosts=/etc/hadoop/conf/dfs.include in cstm-hdfs-site.xml
> - Create /etc/hadoop/conf/dfs.include on Namenode host
> - Restart all required services
> - dfs.include gets created on all datanode hosts.
> Tried the same with Yarn, yarn.include will be present only on
> Resourcemanager node and doesnt get created on any other nodes(eg: one with
> nodemanager)
> Ideally dfs.include should not be created on all datanode hosts
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21701) Add check for import from relocated packages
Doroszlai, Attila created AMBARI-21701:
--
Summary: Add check for import from relocated packages
Key: AMBARI-21701
URL: https://issues.apache.org/jira/browse/AMBARI-21701
Project: Ambari
Issue Type: Improvement
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Priority: Minor
Fix For: 3.0.0
Occasionally an import from {{org.apache.hadoop.metrics2.sink.relocated}}
creeps into {{ambari-server}} source code, causing compile errors:
{noformat}
$ mvn -am -pl ambari-server clean test
...
[ERROR]
ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[39,71]
package org.apache.hadoop.metrics2.sink.relocated.google.common.collect does
not exist
[ERROR]
ambari-server/src/test/java/org/apache/ambari/server/checks/AbstractCheckDescriptorTest.java:[114,34]
cannot find symbol
[ERROR] symbol: variable Sets
[ERROR] location: class
org.apache.ambari.server.checks.AbstractCheckDescriptorTest
{noformat}
The problem is that the same code can be compiled if dependencies are already
installed in one's local Maven repository.
{noformat}
$ mvn -am -pl
ambari-metrics/ambari-metrics-common,ambari-serviceadvisor,ambari-views clean
install
...
$ mvn -pl ambari-server clean test
...
[INFO] BUILD SUCCESS
{noformat}
This succeeds because {{ambari-metrics-common}} installs a shaded uber jar
including the {{..relocated..}} packages, hence they are available when
compiling {{ambari-server}}. On the other hand, when building from scratch
(selectively with {{-am -pl ...}}, or the entire multimodule project) classpath
contains {{ambari-metrics-common}} classes and individual dependencies without
relocation.
The goal of this change is to add a checkstyle check to catch such imports at
build-time with both compilation methods.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files
[ https://issues.apache.org/jira/browse/AMBARI-21692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21692: Attachment: AMBARI-21692.patch > dfs.include file is created on all datanode hosts when Ambari manages > include/exclude files > --- > > Key: AMBARI-21692 > URL: https://issues.apache.org/jira/browse/AMBARI-21692 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Dmytro Sen > Fix For: 2.5.2 > > Attachments: AMBARI-21692.patch > > > - deploy cluster with default configs > - Update manage.include.files to true in hdfs-site.xml > - Add property dfs.hosts=/etc/hadoop/conf/dfs.include in cstm-hdfs-site.xml > - Create /etc/hadoop/conf/dfs.include on Namenode host > - Restart all required services > - dfs.include gets created on all datanode hosts. > Tried the same with Yarn, yarn.include will be present only on > Resourcemanager node and doesnt get created on any other nodes(eg: one with > nodemanager) > Ideally dfs.include should not be created on all datanode hosts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files
[ https://issues.apache.org/jira/browse/AMBARI-21692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21692: Status: Patch Available (was: In Progress) > dfs.include file is created on all datanode hosts when Ambari manages > include/exclude files > --- > > Key: AMBARI-21692 > URL: https://issues.apache.org/jira/browse/AMBARI-21692 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Dmytro Sen > Fix For: 2.5.2 > > Attachments: AMBARI-21692.patch > > > - deploy cluster with default configs > - Update manage.include.files to true in hdfs-site.xml > - Add property dfs.hosts=/etc/hadoop/conf/dfs.include in cstm-hdfs-site.xml > - Create /etc/hadoop/conf/dfs.include on Namenode host > - Restart all required services > - dfs.include gets created on all datanode hosts. > Tried the same with Yarn, yarn.include will be present only on > Resourcemanager node and doesnt get created on any other nodes(eg: one with > nodemanager) > Ideally dfs.include should not be created on all datanode hosts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files
[ https://issues.apache.org/jira/browse/AMBARI-21692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen reassigned AMBARI-21692: --- Assignee: Dmytro Sen > dfs.include file is created on all datanode hosts when Ambari manages > include/exclude files > --- > > Key: AMBARI-21692 > URL: https://issues.apache.org/jira/browse/AMBARI-21692 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Dmytro Sen > Fix For: 2.5.2 > > Attachments: AMBARI-21692.patch > > > - deploy cluster with default configs > - Update manage.include.files to true in hdfs-site.xml > - Add property dfs.hosts=/etc/hadoop/conf/dfs.include in cstm-hdfs-site.xml > - Create /etc/hadoop/conf/dfs.include on Namenode host > - Restart all required services > - dfs.include gets created on all datanode hosts. > Tried the same with Yarn, yarn.include will be present only on > Resourcemanager node and doesnt get created on any other nodes(eg: one with > nodemanager) > Ideally dfs.include should not be created on all datanode hosts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21698) Error starting client components on RedHat7 and BI 4.2.5 after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21698:
---
Status: Patch Available (was: In Progress)
> Error starting client components on RedHat7 and BI 4.2.5 after Ambari upgrade
> -
>
> Key: AMBARI-21698
> URL: https://issues.apache.org/jira/browse/AMBARI-21698
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Labels: system_test
> Fix For: 2.5.2
>
> Attachments: AMBARI-21698.patch
>
>
> *STR*
> # Deployed IOP-4.2.5 cluster with Ambari-2.4.2
> # Upgrade Ambari to 2.5.2
> # Stop Hbase service and delete HBASE_REST_SERVER component via API
> # Try to start HBase service
> Result
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/hook.py",
> line 33, in hook
> install_repos()
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/repo_initialization.py",
> line 68, in install_repos
> _alter_repo("create", params.repo_info, template)
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-INSTALL/scripts/repo_initialization.py",
> line 35, in _alter_repo
> repo_dicts = json.loads(repo_string)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21429) Log Search UI: implement dynamic loading of options for filters
[ https://issues.apache.org/jira/browse/AMBARI-21429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-21429: -- Issue Type: Task (was: Bug) > Log Search UI: implement dynamic loading of options for filters > --- > > Key: AMBARI-21429 > URL: https://issues.apache.org/jira/browse/AMBARI-21429 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21429.patch > > > Options for logs list filters should be loaded dynamically based on real > application data. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21700) Expose Patch Reversion in the Web Client
[ https://issues.apache.org/jira/browse/AMBARI-21700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21700: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Expose Patch Reversion in the Web Client > > > Key: AMBARI-21700 > URL: https://issues.apache.org/jira/browse/AMBARI-21700 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.3 > > Attachments: AMBARI-21700.patch, patch-revert.gif > > > The web client will need to expose the ability to revert a patch which was > successfully applied to one or more services. Patch upgrades allows one or > more services to effectively be "patched" to a new version. Some facts: > - Patching will only apply to the current stack. If the cluster was installed > with HDP 2.5, then all patches must be scoped to 2.5.x.y - you cannot patch > outside the stack. > - Each service/component now exposes the repository version they are on. > The following work should be scoped in this Jira. If the scope turns out to > be too great, then it can be broken up into several JIras: > - The stacks and versions page will change to show multiple "CURRENT" stacks. > - The most recent patch will be able to be reverted. The revert button will > only show for the newest applied patch. Once reverted, the prior patch can be > reverted now. > - If a full stack upgrade is performed, then the bar is reset, regardless the > version upgraded to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21700) Expose Patch Reversion in the Web Client
[ https://issues.apache.org/jira/browse/AMBARI-21700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121466#comment-16121466 ] Andrii Tkach commented on AMBARI-21700: --- committed to branch-feature-AMBARI-21450 > Expose Patch Reversion in the Web Client > > > Key: AMBARI-21700 > URL: https://issues.apache.org/jira/browse/AMBARI-21700 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.3 > > Attachments: AMBARI-21700.patch, patch-revert.gif > > > The web client will need to expose the ability to revert a patch which was > successfully applied to one or more services. Patch upgrades allows one or > more services to effectively be "patched" to a new version. Some facts: > - Patching will only apply to the current stack. If the cluster was installed > with HDP 2.5, then all patches must be scoped to 2.5.x.y - you cannot patch > outside the stack. > - Each service/component now exposes the repository version they are on. > The following work should be scoped in this Jira. If the scope turns out to > be too great, then it can be broken up into several JIras: > - The stacks and versions page will change to show multiple "CURRENT" stacks. > - The most recent patch will be able to be reverted. The revert button will > only show for the newest applied patch. Once reverted, the prior patch can be > reverted now. > - If a full stack upgrade is performed, then the bar is reset, regardless the > version upgraded to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
