[
https://issues.apache.org/jira/browse/HBASE-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914274#action_12914274
]
Nicolas Spiegelberg commented on HBASE-2889:
--------------------------------------------
FYI: the current patch downgrades all derived classes to an IOE. e.g. any code
to detect EOFExceptions will not be triggered. The general problem we seem to
have is that we need to differentiate between a Network IOE and a File Format
IOE.
Network = we need to fail and let another server try to take over
FileFormat = our file was written or parsed incorrectly. retrying won't fix
anything. We need to just open what we have and store the original file away
for later analysis.
> 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
> Fix For: 0.90.0
>
> Attachments: 2889.txt
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
