[
https://issues.apache.org/jira/browse/IMPALA-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503800#comment-16503800
]
Tim Armstrong commented on IMPALA-7101:
---------------------------------------
The fix didn't propagate to 2.x because we were seeing a "Default TException"
error with no message instead of "Query Id ... Not Found" and the test was
failing occasionally. Dan and I tracked the bug down to an issue in our Beeswax
implementation:
* get_results_metadata() does not declare that it throws BeeswaxException
* But our implementation actually throws that in the "Query Id ... Not Found"
case
* The Thrift C++ server has some logic that calls .what() on unknown exceptions
and wraps them into a TException
* On 3.x, we have the THRIFT-727 fix in Thrift 0.9.3, which implements .what(),
so the original error message is present albeit wrapped in some garbage. But on
2.x .what() does not return any useful information, so we just get a weird
TException()
We'll unblock this fix by loosening the test, but I'll file a bug for the
underlying issue.
> Builds are timing out/hanging
> -----------------------------
>
> Key: IMPALA-7101
> URL: https://issues.apache.org/jira/browse/IMPALA-7101
> Project: IMPALA
> Issue Type: Bug
> Reporter: Thomas Tauber-Marshall
> Assignee: Dan Hecht
> Priority: Blocker
> Labels: broken-build
>
> We've seen a large number of builds in the last week or two that appear to
> have hung and gotten killed after a 24-hour timeout.
> Exactly where the hang is occurring is different in each build, but II
> suspect it has something to do with cancellation no working correctly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
