ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AMBARI-21945) Refresh Include/Exclude breaks parallel operations and can't be turned off
Date Fri, 15 Sep 2017 12:22:00 GMT


Hudson commented on AMBARI-21945:

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #219 (See [])
AMBARI-21945. Refresh Include/Exclude breaks parallel operations and (vbrodetskyi: [])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/
* (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/

> Refresh Include/Exclude breaks parallel operations and can't be turned off
> --------------------------------------------------------------------------
>                 Key: AMBARI-21945
>                 URL:
>             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_2.patch, 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

View raw message