phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jaanai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5250) The accumulated wal files can't be cleaned
Date Fri, 03 May 2019 00:08:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832109#comment-16832109
] 

jaanai commented on PHOENIX-5250:
---------------------------------

PHOENIX-5156 will not put into 5.0.1? In that case, maybe we need to reconstruct IndexedKeyValue
to fix this problem or cherrypick the patch into 5.0.1.  [~gjacoby]  [~elserj]

> 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)

Mime
View raw message