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

Hadoop QA commented on OOZIE-615:
---------------------------------

Testing JIRA OOZIE-615

Cleaning local svn workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 
132
.    {color:green}+1{color} the patch does adds/modifies 19 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.    {color:red}-1{color} HEAD does not compile
.    {color:red}-1{color} patch does not compile
.    {color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
.    {color:red}-1{color} distro tarball fails with the patch

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/707/
                
> Support high availability for the Oozie service
> -----------------------------------------------
>
>                 Key: OOZIE-615
>                 URL: https://issues.apache.org/jira/browse/OOZIE-615
>             Project: Oozie
>          Issue Type: New Feature
>    Affects Versions: trunk
>            Reporter: Craig Peters
>            Assignee: Robert Kanter
>             Fix For: trunk
>
>         Attachments: OOZIE-615.patch, OOZIE-615.patch, OOZIE-615.patch, 
> OOZIE-615.patch, OOZIE-615.patch, OOZIE-615.patch, OOZIE-615.patch, 
> OOZIE-615.patch, OOZIE-615.patch, OozieHADesign.pdf, Oozie HA Overview.pdf, 
> zookeeper_yahoo_code.zip
>
>
> As Oozie becomes a critical component in the Hadoop ecosystem users needs 
> assured availability of the services provided by Oozie.  To support this need 
> Oozie should include a new feature to support high availability.  This 
> feature needs to take into consideration that Oozie provides RESTful APIs, 
> Java APIs, and a command line API that should all be insensitive to the 
> availability of any specific server or components.  At Yahoo! it is not 
> required that there be session fail-over from the client.  It is acceptable 
> for the client to reconnect if a session is lost as long as the state data 
> managed by the Oozie service is not lost.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to