Re: Prepping for 1.3.1 release

[Todd Lipcon]

Need these two patches committed before I can tag the RC:
https://gerrit.cloudera.org/6621/
https://gerrit.cloudera.org/6622/

If someone can take a look tonight I'll build the RC for a vote, otherwise
will do so tomorrow AM.

-Todd



On Wed, Apr 12, 2017 at 7:04 PM, Todd Lipcon  wrote:

> Putting together the release candidate now, will send out a vote soon.
>
> On Wed, Apr 12, 2017 at 2:58 PM, Alexey Serbin 
> wrote:
>
>> On 4/12/17 2:56 PM, Todd Lipcon wrote:
>>
>> On Wed, Apr 12, 2017 at 2:54 PM, Alexey Serbin 
>>> wrote:
>>>
>>> There is a patch to fix shortened TSK lifetime:
 795f5ee948e525941c575b231e2c1f9456c160ac

 However, that does not sound like a critical fix to me.  If you think it
 would be nice to pick it up anyway, please let me know -- I'll put up a
 patch for 1.3.x branch.

 Agreed it doesn't seem quite critical enough -- the outcome is just a
>>> 6-day
>>> expiration instead of 7-day, right?
>>>
>> Exactly.  It does not seem to be a big deal, IMO.
>>
>>
>>
>>
>>
>>>
>>> Thank you for finding and fixing KUDU-1968!


 Best regards,

 Alexey


 On 4/12/17 2:43 PM, Jean-Daniel Cryans wrote:

 +1
>
> Nothing else comes to mind. Kudos for finding the bug.
>
> J-D
>
> On Wed, Apr 12, 2017 at 2:42 PM, Todd Lipcon 
> wrote:
>
> This morning we found a serious issue (KUDU-1968) which can eat data
> at a
>
>> relatively high rate on clusters after a failure. We need to get 1.3.1
>> out
>> ASAP.  I'd like to build a release candidate tonight or tomorrow.
>>
>> Are there any other patches that we should be cherry-picking into
>> 1.3.1?
>> Reminder that point-releases like this should be critical fixes (data
>> loss,
>> incorrect results, crashes, etc) only.
>>
>> -Todd
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
>>
>>
>>
>>>
>>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>



-- 
Todd Lipcon
Software Engineer, Cloudera

Re: Prepping for 1.3.1 release

[Todd Lipcon]

Putting together the release candidate now, will send out a vote soon.

On Wed, Apr 12, 2017 at 2:58 PM, Alexey Serbin  wrote:

> On 4/12/17 2:56 PM, Todd Lipcon wrote:
>
> On Wed, Apr 12, 2017 at 2:54 PM, Alexey Serbin 
>> wrote:
>>
>> There is a patch to fix shortened TSK lifetime:
>>> 795f5ee948e525941c575b231e2c1f9456c160ac
>>>
>>> However, that does not sound like a critical fix to me.  If you think it
>>> would be nice to pick it up anyway, please let me know -- I'll put up a
>>> patch for 1.3.x branch.
>>>
>>> Agreed it doesn't seem quite critical enough -- the outcome is just a
>> 6-day
>> expiration instead of 7-day, right?
>>
> Exactly.  It does not seem to be a big deal, IMO.
>
>
>
>
>
>>
>> Thank you for finding and fixing KUDU-1968!
>>>
>>>
>>> Best regards,
>>>
>>> Alexey
>>>
>>>
>>> On 4/12/17 2:43 PM, Jean-Daniel Cryans wrote:
>>>
>>> +1

 Nothing else comes to mind. Kudos for finding the bug.

 J-D

 On Wed, Apr 12, 2017 at 2:42 PM, Todd Lipcon  wrote:

 This morning we found a serious issue (KUDU-1968) which can eat data at
 a

> relatively high rate on clusters after a failure. We need to get 1.3.1
> out
> ASAP.  I'd like to build a release candidate tonight or tomorrow.
>
> Are there any other patches that we should be cherry-picking into
> 1.3.1?
> Reminder that point-releases like this should be critical fixes (data
> loss,
> incorrect results, crashes, etc) only.
>
> -Todd
> --
> Todd Lipcon
> Software Engineer, Cloudera
>
>
>
>>
>


-- 
Todd Lipcon
Software Engineer, Cloudera

Re: Prepping for 1.3.1 release

[Alexey Serbin]

On 4/12/17 2:56 PM, Todd Lipcon wrote:


On Wed, Apr 12, 2017 at 2:54 PM, Alexey Serbin  wrote:


There is a patch to fix shortened TSK lifetime:
795f5ee948e525941c575b231e2c1f9456c160ac

However, that does not sound like a critical fix to me.  If you think it
would be nice to pick it up anyway, please let me know -- I'll put up a
patch for 1.3.x branch.


Agreed it doesn't seem quite critical enough -- the outcome is just a 6-day
expiration instead of 7-day, right?

Exactly.  It does not seem to be a big deal, IMO.







Thank you for finding and fixing KUDU-1968!


Best regards,

Alexey


On 4/12/17 2:43 PM, Jean-Daniel Cryans wrote:


+1

Nothing else comes to mind. Kudos for finding the bug.

J-D

On Wed, Apr 12, 2017 at 2:42 PM, Todd Lipcon  wrote:

This morning we found a serious issue (KUDU-1968) which can eat data at a

relatively high rate on clusters after a failure. We need to get 1.3.1
out
ASAP.  I'd like to build a release candidate tonight or tomorrow.

Are there any other patches that we should be cherry-picking into 1.3.1?
Reminder that point-releases like this should be critical fixes (data
loss,
incorrect results, crashes, etc) only.

-Todd
--
Todd Lipcon
Software Engineer, Cloudera

Re: Prepping for 1.3.1 release

[Todd Lipcon]

On Wed, Apr 12, 2017 at 2:54 PM, Alexey Serbin  wrote:

> There is a patch to fix shortened TSK lifetime:
> 795f5ee948e525941c575b231e2c1f9456c160ac
>
> However, that does not sound like a critical fix to me.  If you think it
> would be nice to pick it up anyway, please let me know -- I'll put up a
> patch for 1.3.x branch.
>

Agreed it doesn't seem quite critical enough -- the outcome is just a 6-day
expiration instead of 7-day, right?


>
> Thank you for finding and fixing KUDU-1968!
>
>
> Best regards,
>
> Alexey
>
>
> On 4/12/17 2:43 PM, Jean-Daniel Cryans wrote:
>
>> +1
>>
>> Nothing else comes to mind. Kudos for finding the bug.
>>
>> J-D
>>
>> On Wed, Apr 12, 2017 at 2:42 PM, Todd Lipcon  wrote:
>>
>> This morning we found a serious issue (KUDU-1968) which can eat data at a
>>> relatively high rate on clusters after a failure. We need to get 1.3.1
>>> out
>>> ASAP.  I'd like to build a release candidate tonight or tomorrow.
>>>
>>> Are there any other patches that we should be cherry-picking into 1.3.1?
>>> Reminder that point-releases like this should be critical fixes (data
>>> loss,
>>> incorrect results, crashes, etc) only.
>>>
>>> -Todd
>>> --
>>> Todd Lipcon
>>> Software Engineer, Cloudera
>>>
>>>
>


-- 
Todd Lipcon
Software Engineer, Cloudera

Re: Prepping for 1.3.1 release

[Alexey Serbin]

There is a patch to fix shortened TSK lifetime: 
795f5ee948e525941c575b231e2c1f9456c160ac


However, that does not sound like a critical fix to me.  If you think it 
would be nice to pick it up anyway, please let me know -- I'll put up a 
patch for 1.3.x branch.


Thank you for finding and fixing KUDU-1968!


Best regards,

Alexey

On 4/12/17 2:43 PM, Jean-Daniel Cryans wrote:

+1

Nothing else comes to mind. Kudos for finding the bug.

J-D

On Wed, Apr 12, 2017 at 2:42 PM, Todd Lipcon  wrote:


This morning we found a serious issue (KUDU-1968) which can eat data at a
relatively high rate on clusters after a failure. We need to get 1.3.1 out
ASAP.  I'd like to build a release candidate tonight or tomorrow.

Are there any other patches that we should be cherry-picking into 1.3.1?
Reminder that point-releases like this should be critical fixes (data loss,
incorrect results, crashes, etc) only.

-Todd
--
Todd Lipcon
Software Engineer, Cloudera

Prepping for 1.3.1 release

[Todd Lipcon]

This morning we found a serious issue (KUDU-1968) which can eat data at a
relatively high rate on clusters after a failure. We need to get 1.3.1 out
ASAP.  I'd like to build a release candidate tonight or tomorrow.

Are there any other patches that we should be cherry-picking into 1.3.1?
Reminder that point-releases like this should be critical fixes (data loss,
incorrect results, crashes, etc) only.

-Todd
-- 
Todd Lipcon
Software Engineer, Cloudera