You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2019/11/14 01:24:00 UTC

[jira] [Commented] (HBASE-23291) ProcedureStoreReader Tool

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

Michael Stack commented on HBASE-23291:
---------------------------------------

Above patch needs this tooo....  if running out of hbase-examples
{code}
diff --git a/hbase-examples/pom.xml b/hbase-examples/pom.xml
index 7a77579c8d..f9abda26ae 100644
--- a/hbase-examples/pom.xml
+++ b/hbase-examples/pom.xml
@@ -174,6 +174,11 @@
       <artifactId>mockito-core</artifactId>
       <scope>test</scope>
     </dependency>
+      <dependency>
+          <artifactId>mockito-core</artifactId>
+          <groupId>org.mockito</groupId>
+          <scope>compile</scope>
+      </dependency>
   </dependencies>
   <profiles>
     <!-- Skip the tests in this module -->
{code}

> ProcedureStoreReader Tool
> -------------------------
>
>                 Key: HBASE-23291
>                 URL: https://issues.apache.org/jira/browse/HBASE-23291
>             Project: HBase
>          Issue Type: New Feature
>          Components: proc-v2, tooling
>            Reporter: Michael Stack
>            Priority: Major
>         Attachments: 0001-HBASE-23291-ProcedureStoreReader-Tool.patch
>
>
> Need a tool to read a MasterProcWALs directory and dump out debug and status per log file, outstanding edits, etc.
> In UI, under 'Procedures and Locks' tab we can see list of outstanding pv2 WALs. There is even a tab which allows you see if a file is corrupt. Even still, sometimes WALs persist and are not cleaned up. Why is opaque. A tool which read the directory and perhaps dumped out problematic procedures would be of use.
> I tried to start one but it is a little awkward as any such tool would depend on hbase-server (if it the default WALProcedureStore implementation) so the tool would have to be in hbase-server or downstream from it. Let me attach what I have so far which currently lives in hbase-examples... which is wrong place for it. More work to do....



--
This message was sent by Atlassian Jira
(v8.3.4#803005)