[
https://issues.apache.org/jira/browse/AMBARI-25235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813726#comment-16813726
]
Hudson commented on AMBARI-25235:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #476 (See
[https://builds.apache.org/job/Ambari-branch-2.7/476/])
AMBARI-25235. Add a sysprep configurations to run conf-selects only a (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=a112364df203008048448759341e1e4ef9f97563])
* (edit)
ambari-server/src/main/resources/stack-hooks/after-INSTALL/scripts/shared_initialization.py
* (edit)
ambari-server/src/main/resources/stack-hooks/after-INSTALL/scripts/params.py
> Add a sysprep configurations to run conf-selects only a single time
> --------------------------------------------------------------------
>
> Key: AMBARI-25235
> URL: https://issues.apache.org/jira/browse/AMBARI-25235
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.2, 2.7.3
> Reporter: Myroslav Papirkovskyi
> Assignee: Myroslav Papirkovskyi
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.6.2, 2.7.4
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Background:
> On the cluster with 5-6 nodes conf-select cycles takes 3 seconds. Trying to
> create conf-dir for every single components. Which makes install stages like
> ~25-30seconds for hosts with a lot of clients.
> Usually we run conf-select during every task. Since with every single install
> new packages might appear and new conf-select links will be required.
> Solution:
> If host_sysprep is true, run conf-select cycle only during first task and
> than create a file indicating this was done, so other tasks skip.
> Since all packages are preinstalled this should work fine as during first
> single run it will be possible to create all links.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
