Tim Armstrong has posted comments on this change.
Change subject: IMPALA-5715: (potential mitigation) don't destroy MemTracker
during Close()
..
Patch Set 1:
Talked with Michael offline. We agreed that it would be good to
Henry Robinson has posted comments on this change.
Change subject: IMPALA-5715: (potential mitigation) don't destroy MemTracker
during Close()
..
Patch Set 1:
Thanks!
--
To view, visit http://gerrit.cloudera.org:8080/7492
Tim Armstrong has posted comments on this change.
Change subject: IMPALA-5715: (potential mitigation) don't destroy MemTracker
during Close()
..
Patch Set 1:
I wrote up a short page on the wiki per Henry's suggestion:
Tim Armstrong has posted comments on this change.
Change subject: IMPALA-5715: (potential mitigation) don't destroy MemTracker
during Close()
..
Patch Set 1:
Any more comments?
--
To view, visit
Michael Ho has posted comments on this change.
Change subject: IMPALA-5715: (potential mitigation) don't destroy MemTracker
during Close()
..
Patch Set 1:
OK. Thanks for the clarification. This kind of implicit rule is always
Henry Robinson has posted comments on this change.
Change subject: IMPALA-5715: (potential mitigation) don't destroy MemTracker
during Close()
..
Patch Set 1:
It would be great if someone could write the best-practice
Tim Armstrong has posted comments on this change.
Change subject: IMPALA-5715: (potential mitigation) don't destroy MemTracker
during Close()
..
Patch Set 1:
Matt's understanding matches mine - releasing resources in
Matthew Jacobs has posted comments on this change.
Change subject: IMPALA-5715: (potential mitigation) don't destroy MemTracker
during Close()
..
Patch Set 1:
> Isn't the general direction we are moving towards to not rely on
Michael Ho has posted comments on this change.
Change subject: IMPALA-5715: (potential mitigation) don't destroy MemTracker
during Close()
..
Patch Set 1:
Isn't the general direction we are moving towards to not rely on
Matthew Jacobs has posted comments on this change.
Change subject: IMPALA-5715: (potential mitigation) don't destroy MemTracker
during Close()
..
Patch Set 1: Code-Review+1
Seems like the right thing to do (i.e. control state
Tim Armstrong has uploaded a new change for review.
http://gerrit.cloudera.org:8080/7492
Change subject: IMPALA-5715: (potential mitigation) don't destroy MemTracker
during Close()
..
IMPALA-5715: (potential mitigation)
11 matches
Mail list logo