[HBASE-21520] TestMultiColumnScanner cost long time when using ROWCOL bloom type

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha-1, 2.2.0, 2.1.2, 1.2.10, 1.4.10, 2.0.5
• Component/s: test
• Hadoop Flags: Reviewed
• Assignee: Zheng Hu
• Reporter: Zheng Hu
• Created: 28/Nov/18 02:14
• Updated: 07/Oct/19 18:29
• Resolved: 15/Dec/18 13:17

Description

The TestMultiColumnScanner is easy to be timeout, you can see HBASE-21517. In my localhost, when I set the parameters to be

{ Compression.Algorithm.NONE, BloomType.ROW, false }

, it took about 5 seconds. but if I set the parameters to be

{ Compression.Algorithm.NONE, BloomType.ROWCOL, false }

, it would take about 45 seconds, which means ROWCOL cost much more time than ROW.

Need to find out what's wrong with this ut.

Issue Links

• is related to: HBASE-21597 Evaluate the performance of ROWCOL bloom type when huge number of columns
• relates to: HBASE-20636 Introduce two bloom filter type : ROWPREFIX_FIXED_LENGTH and ROWPREFIX_DELIMITED
• links to: Review board