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

COUNT(DISTINCT(...)) should have a memory size limit

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

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.14.0, 5.0.0
    • Component/s: None
    • Labels:
      None

      Description

      I just managed to kill (hang) a region server by issuing a COUNT(DISTINCT(...)) query over a column with very high cardinality (20m in this case).
      This is perhaps not a useful thing to do, but Phoenix should nonetheless not allow to have a server fail because of a query.

      James R. Taylor, I see there GlobalMemoryManager, but I do not quite see how I'd get a reference to one, once needs a tenant id, etc.

        Attachments

          Activity

            People

            • Assignee:
              larsh Lars Hofhansl
              Reporter:
              larsh Lars Hofhansl

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment