[jira] [Updated] (OOZIE-2915) Fix race conditon in check() methods and rewrite check() logic

2017-08-10 Thread Andras Piros (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-2915:

Affects Version/s: 5.0.0

> Fix race conditon in check() methods and rewrite check() logic
> --
>
> Key: OOZIE-2915
> URL: https://issues.apache.org/jira/browse/OOZIE-2915
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Priority: Blocker
>
> There is a race condition inside {{MapReduceActionExecutor.check()}}.
> Comment from Rohini:
> bq. This code will have race condition issues. super.check() will check the 
> status of launcher AM if action data file is not found. While it starts the 
> check, if it completes then it will read the NEW_ID from action data and mark 
> the action as completed even though the mapreduce job is just launched and is 
> still running.
> Also the existing logic is convoluted and complex, hard to test. It should be 
> refactored so we can validate the correctness of different code paths.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OOZIE-2915) Fix race conditon in check() methods and rewrite check() logic

2017-08-10 Thread Andras Piros (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-2915:

Priority: Blocker  (was: Major)

> Fix race conditon in check() methods and rewrite check() logic
> --
>
> Key: OOZIE-2915
> URL: https://issues.apache.org/jira/browse/OOZIE-2915
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Priority: Blocker
>
> There is a race condition inside {{MapReduceActionExecutor.check()}}.
> Comment from Rohini:
> bq. This code will have race condition issues. super.check() will check the 
> status of launcher AM if action data file is not found. While it starts the 
> check, if it completes then it will read the NEW_ID from action data and mark 
> the action as completed even though the mapreduce job is just launched and is 
> still running.
> Also the existing logic is convoluted and complex, hard to test. It should be 
> refactored so we can validate the correctness of different code paths.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)