[
https://issues.apache.org/jira/browse/HBASE-9371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753591#comment-13753591
]
Hudson commented on HBASE-9371:
-------------------------------
FAILURE: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #701 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/701/])
HBASE-9371 Eliminate log spam when tailing files
HBASE-9326 ServerName is created using getLocalSocketAddress, breaks binding to
the wildcard
address. Revert HBASE-8640 (jdcryans: rev 1518430)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/fs/HFileSystem.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogReader.java
> Eliminate log spam when tailing files
> -------------------------------------
>
> Key: HBASE-9371
> URL: https://issues.apache.org/jira/browse/HBASE-9371
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.95.2
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Priority: Minor
> Fix For: 0.98.0, 0.96.0
>
> Attachments: HBASE-9371.patch
>
>
> Tailing a file involves reopening it for each seek, so for example when
> running replication it looks like this every time:
> {noformat}
> 2013-08-28 21:45:00,205 DEBUG
> [regionserver60020-EventThread.replicationSource,1]
> org.apache.hadoop.hbase.fs.HFileSystem:
> /hbase-master/WALs/jdec2hbase0403-5,60020,1377724981186/jdec2hbase0403-5%2C60020%2C1377724981186.1377725847406
> is an HLog file, so reordering blocks, last hostname will be:jdec2hbase0403-5
> 2013-08-28 21:45:00,211 DEBUG
> [regionserver60020-EventThread.replicationSource,1]
> org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader: After reading the
> trailer: walEditsStopOffset: 0, fileLength: 0, trailerPresent: false
> {noformat}
> The frequency makes it more relevant for TRACEing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
