You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Vlad Krava (Jira)" <ji...@apache.org> on 2019/10/25 21:29:00 UTC
[jira] [Updated] (PHOENIX-5250) The accumulated wal files can't be
cleaned
[ https://issues.apache.org/jira/browse/PHOENIX-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vlad Krava updated PHOENIX-5250:
--------------------------------
Comment: was deleted
(was: [~elserj] [~jaanai]
I assume this issue appears when IndexedWALEditCodec is enabled (must have for LOCAL and GLOBAL index) as it uses IndexedKeyValue, so it's not only related to the filtering after GLOBAL index sync.
Is there any workaround you may propose besides RS restart, taking into consideration that for my needs SECONDARY index is must have?)
> The accumulated wal files can't be cleaned
> ------------------------------------------
>
> Key: PHOENIX-5250
> URL: https://issues.apache.org/jira/browse/PHOENIX-5250
> Project: Phoenix
> Issue Type: Bug
> Reporter: Jaanai Zhang
> Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: image-2019-04-19-21-31-27-888.png
>
>
> Because of the modification of HBASE-20781, the faked WALEdits won't be filtered, all WALEdits will be saved into Memstore with a status that inMemstore is true(uses WAL->append method).
> !image-2019-04-19-21-31-27-888.png|width=755,height=310!
> The family array of IndexedKeyValue is WALEdit.METAFAMILY that is used to describe a fake WALEdit, and it will put into Memstore with WALedits of data table during sync global index.
> WAL files can't be cleaned, except for restarting RS, Many WAL files will decrease the percent of disk free.
> !https://gw.alicdn.com/tfscom/TB1n3cDQVzqK1RjSZFCXXbbxVXa.png|width=422,height=159!
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)