[
https://issues.apache.org/jira/browse/PHOENIX-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16960313#comment-16960313
]
Vlad Krava commented on PHOENIX-5250:
-------------------------------------
[~gjacoby] according to the statement: _"The new framework doesn't use
IndexedKeyValues"_ there is usage of _IndexedKeyValue_ present in
[IndexedWALEditCodec.class|https://github.com/apache/phoenix/blob/c533eed363aedfdb3fb774d6ff510b287a9660ad/phoenix-core/src/main/java/org/apache/hadoop/hbase/regionserver/wal/IndexedWALEditCodec.java#L38]
(I took for example v4.15) which is must have for SECONDARY (both, LOCAL and
GLOBAL) index creation. Wouldn't it be an impact on the behaviour of new index
framework?
> 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)
