[ 
https://issues.apache.org/jira/browse/HBASE-15611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233040#comment-15233040
 ] 

Sean Busbey commented on HBASE-15611:
-------------------------------------

h3. how can I test that replication has caught up and is not blocked for all 
region servers handling a given table?

Presuming you know the column families that are set for replication already, 
you can hard code them and put a column for each region on the source cluster:

{code}
hbase(main):066:0> example_table = get_table 'MyTable'
hbase(main):067:0> @hbase.admin(@formatter).instance_eval do 
@admin.get_table_regions(example_table.table.get_name).each do |region|
hbase(main):068:2*   test_row = String.from_java_bytes(region.get_start_key + 
"-replication_test".to_java_bytes)
hbase(main):069:2>   example_table.put test_row, "f1:replication_test", 'foo'
hbase(main):070:2>   example_table.put test_row, "f3:replication_test", 'foo'
hbase(main):071:2>   example_table.put test_row, "f4:replication_test", 'foo'
hbase(main):072:2> end end 
{code}

Then on each side of replication, a scan should succeed that looks just for 
those columns

{code}
hbase(main):086:0> example_table = get_table 'MyTable'
hbase(main):087:0> example_table.scan COLUMNS => ['f1:replication_test', 
'f3:replication_test', 'f4:replication_test']
{code}

If any of the row/column combinations don't show up, then you will have the 
region name of those stuck replication endpoints. 

> add examples to shell docs 
> ---------------------------
>
>                 Key: HBASE-15611
>                 URL: https://issues.apache.org/jira/browse/HBASE-15611
>             Project: HBase
>          Issue Type: Improvement
>          Components: documentation, shell
>            Reporter: Sean Busbey
>              Labels: beginner
>             Fix For: 2.0.0
>
>
> It would be nice if our shell documentation included some additional examples 
> of operational tasks one can perform.
> things to include to come in comments. when we have a patch to submit we can 
> update the jira summary to better reflect what scope we end up with.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to