[
https://issues.apache.org/jira/browse/HBASE-23652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013282#comment-17013282
]
Michael Stack commented on HBASE-23652:
---------------------------------------
Bit more info... I see these logs... when the oldWALs cleaner runs:
2020-01-10 00:00:45,232 DEBUG
org.apache.hadoop.hbase.master.cleaner.LogCleaner: Attempting to delete old WAL
file:
HdfsLocatedFileStatus{path=hdfs://nameservice1/hbase/genie/oldWALs/h5%2C16020%2C1578604828426.h5%2C16020%2C1578604828426.regiongroup-0.1578613886971;
isDirectory=false; length=203930698; replication=3; blocksize=268435456;
modification_time=1578614072377; access_time=1578613886978; owner=hbase;
group=supergroup; permission=rw-r--r--; isSymlink=false; hasAcl=false;
isEncrypted=false; isErasureCoded=false}
.... but they never mention 'masterproc' files.
> Move the unsupported procedure type check before migrating to
> RegionProcedureStore
> ----------------------------------------------------------------------------------
>
> Key: HBASE-23652
> URL: https://issues.apache.org/jira/browse/HBASE-23652
> Project: HBase
> Issue Type: Task
> Components: master
> Affects Versions: 2.2.2
> Reporter: Nick Dimiduk
> Assignee: Duo Zhang
> Priority: Blocker
> Fix For: 3.0.0, 2.3.0
>
>
> Per
> [discussion|https://lists.apache.org/thread.html/c5f960e6cf3c89ffbf8f8302afb121462a08fd9a89d384c6795a7b81%40%3Cdev.hbase.apache.org%3E]
> on the list, let's figure out how to make the upgrade from a v2.1 procedure
> store less error-prone. Could be a simple as documenting runbook steps to
> execute during the rolling upgrade, but it would be nice if the software
> could roll over the data versions gracefully.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
