[
https://issues.apache.org/jira/browse/AMBARI-21945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-21945:
--------------------------------
Status: Patch Available (was: In Progress)
> Refresh Include/Exclude breaks parallel operations and can't be turned off
> --------------------------------------------------------------------------
>
> Key: AMBARI-21945
> URL: https://issues.apache.org/jira/browse/AMBARI-21945
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.2
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Fix For: 2.6.0
>
> Attachments: AMBARI-21945.patch
>
>
> Each time a new server is registered, there is an operation to refresh HDFS
> and YARN exclude file and now the operations (install components + start
> components) in Ambari can not be executed in parallel b/c refresh exclude
> file is an atomic process. Each server's operations of install and start
> components processes have to await previous one's refresh node to be
> finished. This means adding servers through blueprint is extremely slow now
> when many servers are being launched at the similar time.
> Also the refresh exclude file for each servers are still being executed even
> when 'manage.include.files' flags are turned off in yarn-site and hdfs-site.
> Previously in 2.5.1 we mange refresh files after adding / removing each batch
> of the servers, now seems this is impossible in 2.5.2.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
