[
https://issues.apache.org/jira/browse/KUDU-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adar Dembo updated KUDU-2636:
-----------------------------
Summary: LBM should delete full and dead containers at runtime (was: LBM
supports deleting the full container which is dead after hole punch)
Just to generalize a bit, I agree that the LBM should delete containers that
are both full and dead outside of startup (i.e. it should also delete them
while the server is running), but I'm not sure hole punching is necessarily the
ideal place to do it.
> LBM should delete full and dead containers at runtime
> -----------------------------------------------------
>
> Key: KUDU-2636
> URL: https://issues.apache.org/jira/browse/KUDU-2636
> Project: Kudu
> Issue Type: Improvement
> Components: fs, util
> Affects Versions: 1.8.0
> Reporter: HeLifu
> Priority: Major
>
> Right now, the LBM does not support deleting the full container which is dead
> after hole punching, and after running for some time, there will be lots of
> dead containers that will affect the startup time. So, it is necessary to
> delete these files while hole punching.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
