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

Maddineni Sukumar updated HBASE-16466:
--------------------------------------
    Release Note: 
Support for snapshots in VerifyReplication tool i.e. verifyrep can compare 
source table snapshot against peer table snapshot which reduces load on RS by 
reading data from HDFS directly using Snapshot scanners. 

Instead of comparing against live tables whose state changes due to writes and 
compactions its better to compare HBase  snapshots which are immutable in 
nature. 

  was:
Support for snapshots in VerifyReplication tool i.e. verifyrep can compare 
source table snapshot against peer table snapshot which reduces load on RS by 
reading data from HDFS directly using Snapshot scanners. 

Instead of comparing against live tables whose state changes due to writes and 
compactions I think its better to compare HBase  snapshots which are immutable 
in nature. 


> HBase snapshots support in VerifyReplication tool to reduce load on live 
> HBase cluster with large tables
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-16466
>                 URL: https://issues.apache.org/jira/browse/HBASE-16466
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbase
>    Affects Versions: 0.98.21
>            Reporter: Sukumar Maddineni
>            Assignee: Maddineni Sukumar
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16466.branch-1.3.001.patch, HBASE-16466.v1.patch, 
> HBASE-16466.v2.patch
>
>
> As of now VerifyReplicatin tool is running using normal HBase scanners. If 
> you  want to run VerifyReplication multiple times on a production live 
> cluster with large tables then it creates extra load on HBase layer. So if we 
> implement snapshot based support then both in source and target we can read 
> data from snapshots which reduces load on HBase



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to