[
https://issues.apache.org/jira/browse/PHOENIX-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-5250.
----------------------------------
Fix Version/s: 5.1.1
Release Note:
When updating from an earlier version, and using HBase 2.1.x, HBase 2.2.6 or
earlier, HBase 2.3.3 or earlier, or HBase 2.4.0, HBase is unable to clean up
WAL files that include data for global indexed tables with the old
implementation.
To avoid running out of disk space, use IndexUpgradeTool to upgrade all tables
with global indexes, and then restart all region servers as soon as possible.
Resolution: Fixed
> 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, 5.1.1
>
> 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)
