You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/07/30 17:48:00 UTC
[jira] [Resolved] (IMPALA-10006) Better handling of non-writable
/opt/impala/logs in containers
[ https://issues.apache.org/jira/browse/IMPALA-10006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-10006.
------------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> 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: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org