You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by bowen zhang <bo...@yahoo.com.INVALID> on 2014/10/15 20:32:14 UTC
4.1 release and remaining issues
Hi folks,
Does anyone still have outstanding issue that is waiting to be checked in? I have one remaining puzzle to ask about a potential statusTransitService.java. Suppose one bundle job submits two coord jobs, one of which fails at submission due to syntax error. In StatusTransitService, we will issue a kill command on that bundle job. But when we check the terminal status of the bundle job, it will transition to "DONEWITHERROR". rather than "KILLED" since it has one action being "KILLED" and one being "FAILED". I don't know which patch caused this issue. Can someone clarify the issue?
Thanks
Bowen
Re: 4.1 release and remaining issues
Posted by Robert Kanter <rk...@cloudera.com>.
We may want to also fix the POODLEbleed vulnerability that was recently
announced. I'm about to send out a separate email to discuss that.
On Thu, Oct 16, 2014 at 3:39 PM, Robert Kanter <rk...@cloudera.com> wrote:
> I recently created 2 simple JIRAs that I'd like to get in to 4.1:
> 1) OOZIE-2033 <https://issues.apache.org/jira/browse/OOZIE-2033> is just
> a doc fix, but it clarifies how to do SSL + HA
> 2) OOZIE-2032 <https://issues.apache.org/jira/browse/OOZIE-2032> is a
> very very simple fix, also for SSL + HA where the URLs in the service
> discovery have the work port number.
> Both of these are important for HA
>
> On Wed, Oct 15, 2014 at 11:32 AM, bowen zhang <
> bowenzhangusa@yahoo.com.invalid> wrote:
>
>> Hi folks,
>> Does anyone still have outstanding issue that is waiting to be checked
>> in? I have one remaining puzzle to ask about a potential
>> statusTransitService.java. Suppose one bundle job submits two coord jobs,
>> one of which fails at submission due to syntax error. In
>> StatusTransitService, we will issue a kill command on that bundle job. But
>> when we check the terminal status of the bundle job, it will transition to
>> "DONEWITHERROR". rather than "KILLED" since it has one action being
>> "KILLED" and one being "FAILED". I don't know which patch caused this
>> issue. Can someone clarify the issue?
>> Thanks
>> Bowen
>>
>
>
Re: 4.1 release and remaining issues
Posted by Robert Kanter <rk...@cloudera.com>.
I recently created 2 simple JIRAs that I'd like to get in to 4.1:
1) OOZIE-2033 <https://issues.apache.org/jira/browse/OOZIE-2033> is just a
doc fix, but it clarifies how to do SSL + HA
2) OOZIE-2032 <https://issues.apache.org/jira/browse/OOZIE-2032> is a very
very simple fix, also for SSL + HA where the URLs in the service discovery
have the work port number.
Both of these are important for HA
On Wed, Oct 15, 2014 at 11:32 AM, bowen zhang <
bowenzhangusa@yahoo.com.invalid> wrote:
> Hi folks,
> Does anyone still have outstanding issue that is waiting to be checked in?
> I have one remaining puzzle to ask about a potential
> statusTransitService.java. Suppose one bundle job submits two coord jobs,
> one of which fails at submission due to syntax error. In
> StatusTransitService, we will issue a kill command on that bundle job. But
> when we check the terminal status of the bundle job, it will transition to
> "DONEWITHERROR". rather than "KILLED" since it has one action being
> "KILLED" and one being "FAILED". I don't know which patch caused this
> issue. Can someone clarify the issue?
> Thanks
> Bowen
>