Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-4580

Crash when FETCH_FIRST exhausts result set cache

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • Impala 2.8.0
    • Impala 2.8.0
    • Backend
    • None

    Description

      The following sequence can lead to a crash:

      1. Client sets result cache size to N
      2. Client issues query with #results < N
      3. Client fetches all results, triggering eos and tearing down Coordinator::root_sink_.
      4. Client restarts query with FETCH_FIRST.
      5. Client reads all results again. After cache is exhausted, Coordinator::GetNext() is called to detect eos condition again.
      6. GetNext() hits DCHECK(root_sink_ != nullptr).

      Either the QES or the coordinator need to remember that eos was once true, and turn GetNext() into a no-op if so.

      Attachments

        Activity

          People

            henryr Henry Robinson
            henryr Henry Robinson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: