hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16377) ServerName check is ineffective in region_mover.rb
Date Thu, 25 Aug 2016 12:59:21 GMT

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

Hudson commented on HBASE-16377:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-0.98-matrix #392 (See [https://builds.apache.org/job/HBase-0.98-matrix/392/])
HBASE-16377 ServerName check is ineffective in region_mover.rb (apurtell: rev 62690dfba8b6f799ca26adde8a6dd4a8ff9cd0bd)
* (edit) bin/region_mover.rb


> ServerName check is ineffective in region_mover.rb
> --------------------------------------------------
>
>                 Key: HBASE-16377
>                 URL: https://issues.apache.org/jira/browse/HBASE-16377
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.1.2
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>             Fix For: 1.4.0, 0.98.22
>
>         Attachments: 16377.branch-1.v1.txt, 16377.branch-1.v2.txt
>
>
> The following was observed during test of region_mover.rb :
> {code}
> 2016-08-08 11:17:05,341|beaver.machine|INFO|352|139926954637120|MainThread|2016-08-08
11:17:05,340 INFO  [RubyThread-9: hbase-client/bin/thread-pool.rb:28] region_mover: Moving
region  hbase:meta,,1.1588230740 (1 of 14) from xyz.openstacklocal,16020,1470654716593, to
server=xyz.openstacklocal,16020,1470654716593
> {code}
> There is check that target server should not be the same as current server:
> {code}
>     if currentServer and currentServer == servername
>       $LOG.info("Region " + r.getRegionNameAsString() + " (" + counter.to_s +
>         " of " + regions.length.to_s + ") already on target server=" + servername)
>       counter = counter + 1
>       next
>     end
> {code}
> However, the check is not effective.
> See comparison between object1 and object3:
> http://www.skorks.com/2009/09/ruby-equality-and-object-comparison/



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

Mime
View raw message