Files
impala/be/src/benchmarks
Dan Hecht f732fe2cdf Log backtrace on all MEM_LIMIT_EXCEEDED errors
Normally, error Status logs backtrace, but this doesn't happen for
MEM_LIMIT_EXCEEDED because these were copied from a global status.
Instead, construct them on the fly so that we get the normal Status
backtrace logging.  Also, remove some special case backtrace logging
that is now redundant from buffered-block-mgr.cc.

Primary motivation for this is to help debug IMPALA-2327, where it
appears a MEM_LIMIT_EXCEEDED status is dropped.  But I think this will
be generally useful for debugging problems that happen after
MEM_LIMIT_EXCEEDED.

Testing: Run test_mem_scaling.py and see all "Memory limit exceeded"
         now have backtraces.

Change-Id: I4cd04426e63397c24d3e16faa33caafc2a608c0c
Reviewed-on: http://gerrit.cloudera.org:8080/872
Reviewed-by: Dan Hecht <dhecht@cloudera.com>
Tested-by: Internal Jenkins
2015-09-22 10:58:33 -07:00
..