impala-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Armstrong (Code Review)" <>
Subject [Impala-ASF-CR] IMPALA-4957: Don't crash Impalad on LLVM fatal error
Date Wed, 08 Mar 2017 22:28:34 GMT
Tim Armstrong has posted comments on this change.

Change subject: IMPALA-4957: Don't crash Impalad on LLVM fatal error

Patch Set 4:

(1 comment)
File be/src/codegen/

Line 148:   llvm::install_fatal_error_handler(LlvmCodegenHandleError);
> And even if LLVM is not in a sane state, I believe it would still allow a u
I think you're right in many cases, but they could possible have cleanup logic that we'd bypass
by throwing an exception.

One example I found is WriteBitcodeToFile(), which stack-allocates a BitstreamWriter object,
which has some assertions in the destructor that would be violated if it did an early exit.
One of it's callees calls       report_fatal_error("Unexpected anonymous function when writing

I agree in some situations that attempting recovery is better than crashing Impala. In some
situations though it may be better to fail hard and restart Impala to get to a known-good

One compromise would be to have a white list of errors where we feel reasonably confident
it's safe to attempt recovery from.

To view, visit
To unsubscribe, visit

Gerrit-MessageType: comment
Gerrit-Change-Id: I54706e261ed223eadde347b1184fb0102e03a3d6
Gerrit-PatchSet: 4
Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-Owner: Michael Ho <>
Gerrit-Reviewer: Dan Hecht <>
Gerrit-Reviewer: Jim Apple <>
Gerrit-Reviewer: Michael Ho <>
Gerrit-Reviewer: Tim Armstrong <>
Gerrit-HasComments: Yes

View raw message