Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-12976

Set default value for hbase.client.scanner.max.result.size

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.0, 1.1.0, 0.98.11
    • Component/s: None
    • Labels:
      None
    • 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.

      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.

        Attachments

        1. 12976.txt
          0.8 kB
          Lars Hofhansl
        2. 12976-v2.txt
          2 kB
          Lars Hofhansl
        3. TestMaxResultSize.txt
          3 kB
          Lars Hofhansl

          Activity

            People

            • Assignee:
              larsh Lars Hofhansl
              Reporter:
              larsh Lars Hofhansl
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: