[
https://issues.apache.org/jira/browse/HIVE-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772182#comment-13772182
]
Hudson commented on HIVE-5198:
------------------------------
FAILURE: Integrated in Hive-trunk-hadoop1-ptest #173 (See
[https://builds.apache.org/job/Hive-trunk-hadoop1-ptest/173/])
HIVE-5198: WebHCat returns exitcode 143 (w/o an explanation) (Eugene Koifman
via Thejas Nair) (thejas:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1524617)
*
/hive/trunk/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/ExecServiceImpl.java
> WebHCat returns exitcode 143 (w/o an explanation)
> -------------------------------------------------
>
> Key: HIVE-5198
> URL: https://issues.apache.org/jira/browse/HIVE-5198
> Project: Hive
> Issue Type: Bug
> Components: WebHCat
> Affects Versions: 0.11.0
> Reporter: Eugene Koifman
> Assignee: Eugene Koifman
> Fix For: 0.12.0
>
> Attachments: HIVE-5198.patch
>
>
> The message might look like this:
> {"statement":"use default; show table extended like xyz;","error":"unable to
> show table: xyz","exec":{"stdout":"","stderr":"","exitcode":143}}
> WebHCat has a templeton.exec.timeout property which kills an HCat request
> (i.e. something like a DDL statement that gets routed to HCat CLI) if it
> takes longer than this timeout.
> Since WebHCat does a fork/exec to 'hcat' script, the timeout is implemented
> as SIGTERM sent to the subprocess. SIGTERM value is 15. So it's reported as
> 128 + 15 = 143.
> Error logging/reporting should be improved in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
