[
https://issues.apache.org/jira/browse/IMPALA-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17900997#comment-17900997
]
ASF subversion and git services commented on IMPALA-13448:
----------------------------------------------------------
Commit 756d9af1c9a12d40b5f5e23fecfce373c056c693 in impala's branch
refs/heads/master from jiangwel
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=756d9af1c ]
IMPALA-13448: Log cause when failing to flush lineage events, audit events or
profiles
When impala fails to flush lineage events, audit events or profiles,
only the log file name is logged: "Could not open log file: filename".
Now we will log "Could not open log file: filename, reason".
e.g: "Could not open log file: filename, cause: Permission denied"
Testing:
- added custom cluster tests in test_logging.py
Change-Id: I5b281d807e47aad98fc256af4e0c2a9dd417c7ac
Reviewed-on: http://gerrit.cloudera.org:8080/22070
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Impala should log the reason why it fails to open a log file
> ------------------------------------------------------------
>
> Key: IMPALA-13448
> URL: https://issues.apache.org/jira/browse/IMPALA-13448
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Quanlong Huang
> Assignee: jiangwei
> Priority: Critical
> Labels: newbie, ramp-up
>
> When impala fails to flush lineage events, audit events or profiles, only the
> log file name is logged: "Could not open log file: filename". We should also
> log the cause for better troubleshooting.
> Here is an example to use the POSIX-compatible thread-local error number
> variable:
> https://stackoverflow.com/a/5836222
> https://en.cppreference.com/w/cpp/header/cerrno
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
