You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/09/21 15:20:00 UTC

[jira] [Commented] (AMBARI-24671) Workaround for non-atomic directory creation

    [ https://issues.apache.org/jira/browse/AMBARI-24671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623764#comment-16623764 ] 

Hudson commented on AMBARI-24671:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #706 (See [https://builds.apache.org/job/Ambari-branch-2.6/706/])
AMBARI-24671. Workaround for non-atomic directory creation (#2357) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=f91518cbe132256dcfb1cab90277c1d425e1c7e1])
* (edit) ambari-server/src/main/resources/scripts/Ambaripreupload.py


> Workaround for non-atomic directory creation
> --------------------------------------------
>
>                 Key: AMBARI-24671
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24671
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Doroszlai, Attila
>            Assignee: Doroszlai, Attila
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> {{before-*}} hooks create a few directories.  If parallel agent execution is enabled tasks may need to be retried, because directory creation is not atomic (see AMBARI-24670).  This causes delays during cluster deployment.  While the underlying problem is being fixed, the goal of this task is to provide a workaround by creating the directory during sysprep phase.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)