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

Jean-Daniel Cryans updated HBASE-6804:
--------------------------------------

    Attachment: HBASE-6804-0.94.patch

Attaching a first pass for 0.94 but I'm planning to just commit to 0.96.

I added a scheduled executor in {{Replication}} that prints out all the 
statistics for both the sources and the sink every 5 minutes by default. I had 
to add glue methods to get the stats all the way from {{ReplicationSource}} to 
{{Replication}} which is not super clean.

This is what the output looks like for a the sink:

bq. 2012-09-17 17:43:08,418 INFO  [Replication Statistics #0] 
regionserver.Replication$ReplicationStatisticsThread(281): Sink: age in ms of 
last applied edit: 15644, total replicated edits: 7350

And for a source:

bq. 2012-09-17 17:42:19,887 INFO  [Replication Statistics #0] 
regionserver.Replication$ReplicationStatisticsThread(281): Normal source for 
cluster 2: Total replicated edits: 1473, currently replicating from: 
hdfs://localhost:53235/user/jdcryans/hbase/.logs/h-25-185.sfo.stumble.net,53250,1347928807372/h-25-185.sfo.stumble.net%2C53250%2C1347928807372.1347928936043
 at position: 3347

I think I need to do some more work on the "normal" EOFs that occur when 
tail'ing a log file.
                
> [replication] lower the amount of logging to a more human-readable level
> ------------------------------------------------------------------------
>
>                 Key: HBASE-6804
>                 URL: https://issues.apache.org/jira/browse/HBASE-6804
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jean-Daniel Cryans
>             Fix For: 0.96.0
>
>         Attachments: HBASE-6804-0.94.patch
>
>
> We need stop logging every time replication decides to do something. It used 
> to be extremely useful when the code base was younger but now it should be 
> possible to bring it down while keeping it relevant.

--
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

Reply via email to