ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Sposetti (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-5367) Oozie directory on HDFS with incorrect owner
Date Tue, 08 Apr 2014 11:28:14 GMT

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

Jeff Sposetti commented on AMBARI-5367:
---------------------------------------

[~Slaytanic] Hi, after attaching the patch, instead of "Resolving", you should mark the JIRA
as with "Patch Available" (by clicking "Submit Patch") for it to be reviewed. I have re-opened
this JIRA and set as "Patch Available".

> Oozie directory on HDFS with incorrect owner
> --------------------------------------------
>
>                 Key: AMBARI-5367
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5367
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.5.0, 1.5.1, 1.4.4
>         Environment: Centos 6 SuSE 11 CentOS 5
>            Reporter: Lei Xiang
>            Priority: Critical
>              Labels: ambari-agent
>             Fix For: 1.6.0
>
>         Attachments: AMBARI-5367.patch
>
>
> From ambari 1.4.4-1.5.1, there is a puppet missing for Oozie server start, may cause
oozie server startup error. Oozie server will not start.
> The problem is , when oozie installed, the owner of  oozie's directory on HDFS (/user/oozie)
is not oozie:hdfs, so puppet cannot copy any thing to /user/oozie and the the oozie server
start process hangs up.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message