[
https://issues.apache.org/jira/browse/IMPALA-8775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989284#comment-16989284
]
Michael Ho commented on IMPALA-8775:
------------------------------------
One idea is to hook into {{ExecEnv::~ExecEnv()}} in which the RpcMgr and other
subsystems' shutdown happen. Ideally, we want to support proper shutdown
sequence of all subsystems which should be invoked by graceful shutdown before
calling exit(0). The existing state of relying on doing the shutdown in
destructor of some global objects seems risky as the state of other global
objects are unknown among other things.
> Have the option to delete data cache files on Impala shutdown
> -------------------------------------------------------------
>
> Key: IMPALA-8775
> URL: https://issues.apache.org/jira/browse/IMPALA-8775
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 3.3.0
> Reporter: Michael Ho
> Assignee: Joe McDonnell
> Priority: Major
>
> Currently, Impala will delete old data cache files upon restart but it only
> does so when data cache is enabled. However, if the user turns off the data
> cache after restart, the old data cache files may be left hanging around
> until the next restart with the cache enabled. We should have an option to
> delete the data cache files on Impala shutdown. The initial implementation of
> the data cache has the unlink-on-create behavior but it was confusing to
> users as there will be unaccounted usage on the storage side (as the file is
> not easily visible after unlink). We may want to consider support this
> "unlink-on-create" behavior behind a flag in case users prefer to have the
> data cache files removed upon Impala's exit. In the long run, we probably
> want to have an "exit handler" in Impala to make sure resources are freed up
> on Impala exit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
