Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-3486

RoundRobinResultIterator doesn't work correctly because of setting Scan's cache size inappropriately in PhoenixInputForamt

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.10.0
    • Labels:

      Description

      RoundRobinResultIterator uses "hbase.client.scanner.caching" to fill caches in parallel for all scans, but by setting Scan.setCaching() in PhoenixInputForrmat(phoenix-hive), RoundRobinResultIterator doesn't work correctly, because if Scan have cache size by setCaching(), HBase uses cache size from Scan.getCaching() to fill cache, not "hbase.client.scanner.caching", and RoundRobinResultIterator scans the table in parallel to fill caches every "hbase.client.scanner.caching", resulting in unintended parallel scan operation, this causes scan performance degradation.

        Attachments

          Activity

            People

            • Assignee:
              Jeongdae Kim Jeongdae Kim
              Reporter:
              Jeongdae Kim Jeongdae Kim
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: