[
https://issues.apache.org/jira/browse/HBASE-15100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109287#comment-15109287
]
Matteo Bertozzi commented on HBASE-15100:
-----------------------------------------
that "removed logs: [a, b, c]" is a bad log message it is fixed now. that is
the list of "active logs"
the out of order deletion is a bug which is fixed by the patch attached. which
should be the problem of the lots of logs staying around.
The ServerCrashProcedure is something else I was looking at, especially in case
where we fail an assignment or something like that. unsure if that procedure
may hang forever spinning in a retry assign, but that should be easy to catch
by listing the procedures running from the shell.
> Master WALProcs still never clean up
> ------------------------------------
>
> Key: HBASE-15100
> URL: https://issues.apache.org/jira/browse/HBASE-15100
> Project: HBase
> Issue Type: Bug
> Components: master, proc-v2
> Affects Versions: 1.2.0
> Reporter: Elliott Clark
> Assignee: Matteo Bertozzi
> Priority: Blocker
> Attachments: HBASE-15100-logs.zip, HBASE-15100-v0.patch,
> TestWalProcedure.java, procs.log
>
>
> {code}
> bin/hdfs dfs -ls /hbase/MasterProcWALs | wc -l
> 218631
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
