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

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

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 4.14.0, 5.0.0
    • None
    • 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.

      jamestaylor, 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

        1. 4148.txt
          9 kB
          Lars Hofhansl
        2. PHOENIX-4148_v2.patch
          24 kB
          James R. Taylor

        Activity

          People

            larsh Lars Hofhansl
            larsh Lars Hofhansl
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: