You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2019/05/02 17:26:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16831789#comment-16831789 ]
Josh Elser commented on PHOENIX-5250:
-------------------------------------
So, we hold onto WALs because the faked waledits for index tables get put into the memstore? And we never get them flushed out? How does the change in HBASE-20781 prevent the filtering from happening – does Phoenix override {{collectFamilies}} or some call made within that method?
> 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
> 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
(v7.6.3#76005)