[HBASE-12976] Set default value for hbase.client.scanner.max.result.size

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0, 1.1.0, 0.98.11
• Hadoop Flags: Reviewed
• Release Note: With this setting defaulted now, scanner caching should be set to large value unless the caller knows how many rows it needs/expects back.
• Assignee: Lars Hofhansl
• Reporter: Lars Hofhansl
• Created: 05/Feb/15 05:50
• Updated: 06/Apr/18 17:55
• Resolved: 05/Feb/15 23:05

Description

Setting scanner caching is somewhat of a black art. It's hard to estimate ahead of time how large the result set will be.

I propose we hbase.client.scanner.max.result.size to 2mb. That is good compromise between performance and buffer usage on typical networks (avoiding OOMs when the caching was chosen too high).

To an HTable client this is completely transparent.

Sub-Tasks

• Undo parent from 0.98 and 1.0: setting hbase.client.scanner.max.result.size is considered harmful: Closed