[
https://issues.apache.org/jira/browse/IMPALA-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765656#comment-16765656
]
ASF subversion and git services commented on IMPALA-8177:
---------------------------------------------------------
Commit fa604fb5059307321a174db02469b4f5fb78410f in impala's branch
refs/heads/master from Bharath Vissapragada
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=fa604fb ]
IMPALA-8177: Log DDL failures in coordinator logs
If a DDL fails for some reason, it helps to log the failure message in
the coordinator logs so that we can differentiate between failed and
successful DDL queries.
For ex:
[0d66cd6004b4:21000] default> drop database foo;
Query: drop database foo
ERROR: ImpalaRuntimeException: Error making 'dropDatabase' RPC to Hive
Metastore:
CAUSED BY: NoSuchObjectException: foo
----- coordinator logs -------
I0208 12:13:26.251695 25474 Frontend.java:1242]
704e86fff482c0b5:f0501f9400000000] Analyzing query: drop database foo
I0208 12:13:26.253773 25474 Frontend.java:1282]
704e86fff482c0b5:f0501f9400000000] Analysis finished.
I0208 12:13:26.419946 25474 client-request-state.cc:176]
704e86fff482c0b5:f0501f9400000000] ImpalaRuntimeException: Error making
'dropDatabase' RPC to Hive Metastore:
CAUSED BY: NoSuchObjectException: foo
I0208 12:13:26.419992 25474 impala-server.cc:1142]
704e86fff482c0b5:f0501f9400000000] UnregisterQuery():
query_id=704e86fff482c0b5:f0501f9400000000
I0208 12:13:26.419997 25474 impala-server.cc:1249]
704e86fff482c0b5:f0501f9400000000] Cancel():
query_id=704e86fff482c0b5:f0501f9400000000
-------------------------------
Testing: Verified manually by running a few DDLs that fail and then inspecting
the coordinator log file.
Change-Id: Ie89291ee27156c701e07cea44ad3ee07ec54ab42
Reviewed-on: http://gerrit.cloudera.org:8080/12414
Reviewed-by: Bharath Vissapragada <bhara...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
> Log DDL exceptions in the coordinator log [supportability]
> ----------------------------------------------------------
>
> Key: IMPALA-8177
> URL: https://issues.apache.org/jira/browse/IMPALA-8177
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend, Catalog
> Affects Versions: Impala 2.13.0, Impala 3.1.0
> Reporter: bharath v
> Assignee: bharath v
> Priority: Major
> Labels: supportability
> Fix For: Impala 3.2.0
>
>
> I ran into this issue while debugging DDL failures.
> If a DDL fails for some reason, we propagate the error back to the shell and
> update the runtime profile, but we do not log the failure message to the
> coordinator logs. This means that the coordinator side logging remains the
> same for both successful and failed DDL queries.
> We need to log the failure status in the coordinator logs so that it is easy
> to differentiate successful vs failed queries.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
