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

Hadoop QA commented on OOZIE-1783:
----------------------------------

Testing JIRA OOZIE-1783

Cleaning local git 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 2 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:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:red}-1{color} the patch seems to introduce 1 new javac warning(s)
{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}
.    Tests run: 1447
.    Tests failed: 2
.    Tests errors: 2

.    The patch failed the following testcases:

.      testSingleRecord(org.apache.oozie.servlet.TestBulkMonitorWebServiceAPI)
.      
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)

{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds 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/1248/

> Sharelib purging only occurs at Oozie startup
> ---------------------------------------------
>
>                 Key: OOZIE-1783
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1783
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>            Priority: Critical
>         Attachments: OOZIE-1783.patch, OOZIE-1783.patch
>
>
> The purgeLibs method only gets called on startup of the first Oozie server.  
> This means that if you update the sharelib without restarting Oozie, then 
> Oozie will never clean up the old sharelibs and launcherlibs until you 
> restart the server.  In fact, with Oozie HA, it will never clean up unless 
> you restart all of the servers at the same time (in other words, a rolling 
> restart or just restarting one Oozie will never cause purgeLibs to get 
> called).  
> This should be moved into a background thread (i.e. scheduled with 
> SchedulerService) to run periodically.  Once a day is probably good enough, 
> but we could make it configurable if needed.  



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

Reply via email to