[
https://issues.apache.org/jira/browse/IMPALA-10006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168114#comment-17168114
]
ASF subversion and git services commented on IMPALA-10006:
----------------------------------------------------------
Commit b29cb4ca82a4f05ea7dc0eadc330a64fbe685ef0 in impala's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=b29cb4c ]
IMPALA-10006: handle non-writable /opt/impala/logs
The shutdown script should not abort if it can't write
a log - it should continue to try and shut down impala.
The entrypoint script should abort with an explicit
error if the log directory isn't writable by the
current user.
Change-Id: If32d6eef75422b51f8877478bbfb1a709c02f756
Reviewed-on: http://gerrit.cloudera.org:8080/16237
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Attila Jeges <[email protected]>
Reviewed-by: Andrew Sherman <[email protected]>
> Better handling of non-writable /opt/impala/logs in containers
> --------------------------------------------------------------
>
> Key: IMPALA-10006
> URL: https://issues.apache.org/jira/browse/IMPALA-10006
> Project: IMPALA
> Issue Type: Bug
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Fix For: Impala 4.0
>
>
> I ran into an issues where graceful shutdown didn't work because
> /opt/impala/logs was not writable by HADOOP_USER_NAME.
> I think we should modify the entrypoint script to exit with an error if the
> directory is not writable so that the problem is obvious. We should maybe
> also modify the shutdown script to be more robust if the log file isn't
> writable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
