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

Samir Ahmic commented on HBASE-13580:
-------------------------------------

Thank you for review [[email protected]] and [~anoop.hbase], 
bq. Are we closing the connection created?
Good one Anoop i will close connection at end of file. 

bq. Why is InclusiveStopFilter removed ?
It cause NPE 
{code}
NativeException: java.lang.NullPointerException: null
        __ensure__ at region_mover.rb:121
  isSuccessfulScan at region_mover.rb:120
  isSuccessfulScan at region_mover.rb:117
{code}
After removing  InclusiveStopFilter exception is gone. And i think we already 
limit scan with:
{code}
122                 scan = Scan.new(r.getStartKey(), r.getStartKey())
{code}

bq, What if region server happens to run on the same host as master ?
Good one Ted i will add port condition in order to remove just regionserver 
started with master process. 






 

 

> region_mover.rb broken with TypeError: no public constructors for 
> Java::OrgApacheHadoopHbaseClient::HTable
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-13580
>                 URL: https://issues.apache.org/jira/browse/HBASE-13580
>             Project: HBase
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 2.0.0
>         Environment: x86_64 GNU/Linux
>            Reporter: Samir Ahmic
>            Assignee: Samir Ahmic
>         Attachments: HBASE-13580.patch
>
>
> I was testing region_mover.rb on master branch  in distributed cluster and 
> hit this error. I have fixed this by using Connection#getTable instead of 
> HTable but look like this script needs some additional work:
> 1. Remove master server from region move targets list
> 2. --exclude=FILE option is not  working for me 
> I will try to get this script in functional state if there is no objections ?
>   



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

Reply via email to