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

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 4.10.0
    • None

    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

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

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

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment