[
https://issues.apache.org/jira/browse/HIVE-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koifman updated HIVE-5198:
---------------------------------
Description:
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.
was:
Filing this bug mostly to help anyone trying to decipher 143 error code which
does not appear in the source code. In 0.12 error reporting was improved and
this reports a stacktrace.
This error code means that Metastore client could not connect to the metastore.
This is likely a config issue with hive.metastore.uris not being set.
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 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.13.0
>
>
> 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
