You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2014/07/17 05:32:07 UTC

[jira] [Resolved] (HBASE-2889) Tool to look at HLogs -- parse and tail -f

     [ https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-2889.
--------------------------

    Resolution: Later

Resolving. Old.  When HDFS has a tail, we'll make an issue to implement tail of WAL

> Tool to look at HLogs -- parse and tail -f
> ------------------------------------------
>
>                 Key: HBASE-2889
>                 URL: https://issues.apache.org/jira/browse/HBASE-2889
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>            Reporter: stack
>            Assignee: stack
>         Attachments: 2889.txt, HBASE-2889_2.patch
>
>
> We need a tool for looking at wals.  A tail -f would be sweet though it might be ugly having to open each time it wants to dump next lot of edits out wal log.
> From Kannan:
> {code}20:45 <kannan> WALEdit already has a toString().
> 20:46 <kannan> And append/sync support allows you to read concurrently a file that is being written too... (like JDs replication).
> 20:46 <kannan> So it would be good if I could do a bin/hbase hlogprint -f hdfs://...../.logs/<filename> -v -p
> 20:46 <kannan> much like the HFile pretty printer... except the HLog one is effectively a tail -f.
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)