[jira] [Updated] (AMBARI-25604) During blueprint deploy tasks sometimes fail due to KeyError on large clusters
[
https://issues.apache.org/jira/browse/AMBARI-25604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-25604:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.7
> During blueprint deploy tasks sometimes fail due to KeyError on large clusters
> --
>
> Key: AMBARI-25604
> URL: https://issues.apache.org/jira/browse/AMBARI-25604
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.6
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> During blueprint deploy we don't rely on topology cache since
> [https://issues.apache.org/jira/browse/AMBARI-23660] So topology is send with
> command. BUT the problem occurs when we still try to generate it on agent and
> fail. {code:java} ERROR 2020-12-10 06:30:09,350
> CustomServiceOrchestrator.py:459 - Caught an exception while executing custom
> service command: : 10; 10 Traceback (most recent call last): File "/usr/lib
> /ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line 324, in
> runCommand command = self.generate_command(command_header) File "/usr/lib
> /ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line 507, in
> generate_command command_dict =
> self.configuration_builder.get_configuration(cluster_id, service_name,
> component_name, required_config_timestamp) File "/usr/lib/ambari-
> agent/lib/ambari_agent/ConfigurationBuilder.py", line 43, in get_configuration
> 'clusterHostInfo': self.topology_cache.get_cluster_host_info(cluster_id), File
> "/usr/lib/ambari-agent/lib/ambari_agent/Utils.py", line 230, in newFunction
> return f(*args, **kw) File "/usr/lib/ambari-
> agent/lib/ambari_agent/ClusterTopologyCache.py", line 112, in
> get_cluster_host_info hostnames =
> [self.hosts_to_id[cluster_id][host_id].hostName for host_id in
> component_dict.hostIds] KeyError: 10{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25602) Bump up org.apache.hadoop in fast-hdfs
[ https://issues.apache.org/jira/browse/AMBARI-25602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-25602: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.7 > Bump up org.apache.hadoop in fast-hdfs > -- > > Key: AMBARI-25602 > URL: https://issues.apache.org/jira/browse/AMBARI-25602 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.6 > > Attachments: AMBARI-25602.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Please check if possible to bump up hadoop version in fast-hdfs-resource from > 1.2.1 to 2.7.7.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25602) Bump up org.apache.hadoop in fast-hdfs
[ https://issues.apache.org/jira/browse/AMBARI-25602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-25602: - Summary: Bump up org.apache.hadoop in fast-hdfs (was: Bump org.apache.hadoop in fast-hdfs) > Bump up org.apache.hadoop in fast-hdfs > -- > > Key: AMBARI-25602 > URL: https://issues.apache.org/jira/browse/AMBARI-25602 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.6 > > Attachments: AMBARI-25602.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Please check if possible to bump up hadoop version in fast-hdfs-resource from > 1.2.1 to 2.7.7.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25602) Bump org.apache.hadoop in fast-hdfs
[ https://issues.apache.org/jira/browse/AMBARI-25602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-25602: - Summary: Bump org.apache.hadoop in fast-hdfs (was: BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs) > Bump org.apache.hadoop in fast-hdfs > --- > > Key: AMBARI-25602 > URL: https://issues.apache.org/jira/browse/AMBARI-25602 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.6 > > Attachments: AMBARI-25602.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Please check if possible to bump up hadoop version in fast-hdfs-resource from > 1.2.1 to 2.7.7.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25603) Bump up org.apache.hadoop in fast-hdfs
[ https://issues.apache.org/jira/browse/AMBARI-25603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-25603: - Summary: Bump up org.apache.hadoop in fast-hdfs (was: BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs) > Bump up org.apache.hadoop in fast-hdfs > -- > > Key: AMBARI-25603 > URL: https://issues.apache.org/jira/browse/AMBARI-25603 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.6 > > > Please check if possible to bump up hadoop version in fast-hdfs-resource from > 1.2.1 to 2.7.7.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25604) During blueprint deploy tasks sometimes fail due to KeyError on large clusters
Andrew Onischuk created AMBARI-25604:
Summary: During blueprint deploy tasks sometimes fail due to
KeyError on large clusters
Key: AMBARI-25604
URL: https://issues.apache.org/jira/browse/AMBARI-25604
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.7.6
During blueprint deploy we don't rely on topology cache since
[https://issues.apache.org/jira/browse/AMBARI-23660] So topology is send with
command. BUT the problem occurs when we still try to generate it on agent and
fail. {code:java} ERROR 2020-12-10 06:30:09,350
CustomServiceOrchestrator.py:459 - Caught an exception while executing custom
service command: : 10; 10 Traceback (most recent call last): File "/usr/lib
/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line 324, in
runCommand command = self.generate_command(command_header) File "/usr/lib
/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line 507, in
generate_command command_dict =
self.configuration_builder.get_configuration(cluster_id, service_name,
component_name, required_config_timestamp) File "/usr/lib/ambari-
agent/lib/ambari_agent/ConfigurationBuilder.py", line 43, in get_configuration
'clusterHostInfo': self.topology_cache.get_cluster_host_info(cluster_id), File
"/usr/lib/ambari-agent/lib/ambari_agent/Utils.py", line 230, in newFunction
return f(*args, **kw) File "/usr/lib/ambari-
agent/lib/ambari_agent/ClusterTopologyCache.py", line 112, in
get_cluster_host_info hostnames =
[self.hosts_to_id[cluster_id][host_id].hostName for host_id in
component_dict.hostIds] KeyError: 10{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25604) During blueprint deploy tasks sometimes fail due to KeyError on large clusters
[
https://issues.apache.org/jira/browse/AMBARI-25604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-25604:
-
Status: Patch Available (was: Open)
> During blueprint deploy tasks sometimes fail due to KeyError on large clusters
> --
>
> Key: AMBARI-25604
> URL: https://issues.apache.org/jira/browse/AMBARI-25604
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.6
>
>
> During blueprint deploy we don't rely on topology cache since
> [https://issues.apache.org/jira/browse/AMBARI-23660] So topology is send with
> command. BUT the problem occurs when we still try to generate it on agent and
> fail. {code:java} ERROR 2020-12-10 06:30:09,350
> CustomServiceOrchestrator.py:459 - Caught an exception while executing custom
> service command: : 10; 10 Traceback (most recent call last): File "/usr/lib
> /ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line 324, in
> runCommand command = self.generate_command(command_header) File "/usr/lib
> /ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line 507, in
> generate_command command_dict =
> self.configuration_builder.get_configuration(cluster_id, service_name,
> component_name, required_config_timestamp) File "/usr/lib/ambari-
> agent/lib/ambari_agent/ConfigurationBuilder.py", line 43, in get_configuration
> 'clusterHostInfo': self.topology_cache.get_cluster_host_info(cluster_id), File
> "/usr/lib/ambari-agent/lib/ambari_agent/Utils.py", line 230, in newFunction
> return f(*args, **kw) File "/usr/lib/ambari-
> agent/lib/ambari_agent/ClusterTopologyCache.py", line 112, in
> get_cluster_host_info hostnames =
> [self.hosts_to_id[cluster_id][host_id].hostName for host_id in
> component_dict.hostIds] KeyError: 10{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (AMBARI-25603) BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs
[ https://issues.apache.org/jira/browse/AMBARI-25603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk resolved AMBARI-25603. -- Resolution: Duplicate Duplicate > BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs > --- > > Key: AMBARI-25603 > URL: https://issues.apache.org/jira/browse/AMBARI-25603 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.6 > > > Please check if possible to bump up hadoop version in fast-hdfs-resource from > 1.2.1 to 2.7.7.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-12556) Provide ability to apply single patches on top of RU release
[ https://issues.apache.org/jira/browse/AMBARI-12556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247400#comment-17247400 ] Dong Qiu commented on AMBARI-12556: --- Sorry for digging into this old post. Is there any updates on this issue? has the new code committed to a branch ? I am very interested on this feature and would be happy to help for testing. > Provide ability to apply single patches on top of RU release > > > Key: AMBARI-12556 > URL: https://issues.apache.org/jira/browse/AMBARI-12556 > Project: Ambari > Issue Type: Epic >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.0 > > Attachments: Patch Upgrade Requirements.pdf, Patch Upgrade Tech > Design v2.pdf, Patch Upgrade Tech Design.pdf > > Time Spent: 0.5h > Remaining Estimate: 0h > > Documentation and updates to follow -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25602) BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs
[ https://issues.apache.org/jira/browse/AMBARI-25602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-25602: - Status: Patch Available (was: Open) > BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs > --- > > Key: AMBARI-25602 > URL: https://issues.apache.org/jira/browse/AMBARI-25602 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.6 > > Attachments: AMBARI-25602.patch > > > Please check if possible to bump up hadoop version in fast-hdfs-resource from > 1.2.1 to 2.7.7.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25603) BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs
Andrew Onischuk created AMBARI-25603: Summary: BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs Key: AMBARI-25603 URL: https://issues.apache.org/jira/browse/AMBARI-25603 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.6 Please check if possible to bump up hadoop version in fast-hdfs-resource from 1.2.1 to 2.7.7.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25602) BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs
Andrew Onischuk created AMBARI-25602: Summary: BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs Key: AMBARI-25602 URL: https://issues.apache.org/jira/browse/AMBARI-25602 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.6 Attachments: AMBARI-25602.patch Please check if possible to bump up hadoop version in fast-hdfs-resource from 1.2.1 to 2.7.7.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25602) BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs
[ https://issues.apache.org/jira/browse/AMBARI-25602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-25602: - Attachment: AMBARI-25602.patch > BlackDuck scan: vulnerable org.apache.hadoop 1.2.1 in fast-hdfs > --- > > Key: AMBARI-25602 > URL: https://issues.apache.org/jira/browse/AMBARI-25602 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.6 > > Attachments: AMBARI-25602.patch > > > Please check if possible to bump up hadoop version in fast-hdfs-resource from > 1.2.1 to 2.7.7.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25601) Ambari with AMS HA unable to change metrics collector for metrics providing on collector fail
Dmytro Vitiuk created AMBARI-25601:
--
Summary: Ambari with AMS HA unable to change metrics collector for
metrics providing on collector fail
Key: AMBARI-25601
URL: https://issues.apache.org/jira/browse/AMBARI-25601
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.5
Reporter: Dmytro Vitiuk
Fix For: 2.7.6
It is expected that ambari server should select another available metrics
collector for metrics retrieval on current collector fail. But actually we have
the next numerous exceptions. Of course in this case metrics are unavailable
via ambari API.
{code}
2020-12-10 08:41:44,402 ERROR [pool-3-thread-1] ambari-event-bus:232 -
Exception thrown by subscriber method
onMetricsCollectorHostDownEvent(org.apache.ambari.server.events.MetricsCollectorHostDownEvent)
on subscriber
org.apache.ambari.server.controller.metrics.MetricsCollectorHAManager@470dea54
when dispatching event:
MetricsCollectorHostDownEvent{eventType=METRICS_COLLECTOR_HOST_DOWN}
java.lang.NullPointerException
at
org.apache.ambari.server.controller.metrics.CollectorHostDownRefreshCounter.testRefreshCounter(CollectorHostDownRefreshCounter.java:33)
at
org.apache.ambari.server.controller.metrics.MetricsCollectorHAClusterState.onCollectorHostDown(MetricsCollectorHAClusterState.java:117)
at
org.apache.ambari.server.controller.metrics.MetricsCollectorHAManager.onMetricsCollectorHostDownEvent(MetricsCollectorHAManager.java:126)
at sun.reflect.GeneratedMethodAccessor569.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:87)
at
com.google.common.eventbus.Subscriber$SynchronizedSubscriber.invokeSubscriberMethod(Subscriber.java:144)
at com.google.common.eventbus.Subscriber$1.run(Subscriber.java:72)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
