wise to change the default behavior for released versions
> of Hadoop? Should this be limited to
> trunk?
>
> Thanks,
> -Eric Payne
>
>
> On Wednesday, September 23, 2020, 2:16:14 PM CDT, Jim Brennan
> wrote:
>
> I replied in the Jira. The speed up provided b
?
Thanks,
-Eric Payne
On Wednesday, September 23, 2020, 2:16:14 PM CDT, Jim Brennan
wrote:
I replied in the Jira. The speed up provided by the v2 commit algorithm
is very important to us at Verizon Media (Yahoo). Please do not remove it.
I referred to this comment from Jason Lowe on the original
On Wed, 23 Sep 2020 at 20:16, Jim Brennan
wrote:
> I replied in the Jira. The speed up provided by the v2 commit algorithm
> is very important to us at Verizon Media (Yahoo). Please do not remove it.
> I referred to this comment from Jason Lowe on the original Jira:
e got a PR up to completely remove the v2 commit algorithm
>>
>> https://github.com/apache/hadoop/pull/2320
>>
>> That may seem overkill, but while *we* know there's a small window of risk
>> (task attempt 1 failing partway through a nonatomic commit), that's n
I replied in the Jira. The speed up provided by the v2 commit algorithm
is very important to us at Verizon Media (Yahoo). Please do not remove it.
I referred to this comment from Jason Lowe on the original Jira:
https://issues.apache.org/jira/browse/MAPREDUCE-4815?focusedCommentId=14271115&
What will be the solution for object stores to have fast and correct commit
algorithms?
On Wed, Sep 23, 2020 at 11:42 AM Steve Loughran
wrote:
> I've got a PR up to completely remove the v2 commit algorithm
>
> https://github.com/apache/hadoop/pull/2320
>
> That may seem ove
I've got a PR up to completely remove the v2 commit algorithm
https://github.com/apache/hadoop/pull/2320
That may seem overkill, but while *we* know there's a small window of risk
(task attempt 1 failing partway through a nonatomic commit), that's not
known/appreciated by oth
