[HBASE-13475] Small spelling mistake in region_mover#isSuccessfulScan causes NoMethodError

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 0.98.11, 0.98.12
• Fix Version/s: 1.1.0, 0.98.13, 2.0.0
• Component/s: scripts
• Hadoop Flags: Reviewed
• Assignee: Victor Xu
• Reporter: Victor Xu
• Created: 15/Apr/15 06:58
• Updated: 03/Jun/15 15:28
• Resolved: 15/Apr/15 12:10

Description

A small spelling mistake in region_mover#isSuccessfulScan method can cause NoMethodError while rolling upgrade:
15/04/15 11:47:23 INFO region_mover: Waiting for the pool to complete
NoMethodError: undefined method `InclusiveStopFilter' for main:Object
isSuccessfulScan at /home/hadoop/hadoop_hbase/hbase-current/bin/region_mover.rb:105
unloadRegions at /home/hadoop/hadoop_hbase/hbase-current/bin/region_mover.rb:331
call at org/jruby/RubyProc.java:270
call at org/jruby/RubyProc.java:220
initialize at /home/hadoop/hadoop_hbase/hbase-current/bin/thread-pool.rb:33
loop at org/jruby/RubyKernel.java:1439
initialize at /home/hadoop/hadoop_hbase/hbase-current/bin/thread-pool.rb:31
catch at org/jruby/RubyKernel.java:1212
initialize at /home/hadoop/hadoop_hbase/hbase-current/bin/thread-pool.rb:30
call at org/jruby/RubyProc.java:270
call at org/jruby/RubyProc.java:224

This bug is from HBASE-12957

Issue Links

• is duplicated by: HBASE-13629 Add to 1.0: HBASE-12957 region_mover#isSuccessfulScan may be extremely slow on region with lots of expired data