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

FETCH_ROWS_TIMEOUT_MS should apply before rows are available

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • Impala 3.4.0
    • Clients
    • None
    • ghx-label-5

    Description

      IMPALA-7312 added a fetch timeout controlled by the query option FETCH_ROWS_TIMEOUT_MS. The issue is that the timeout only applies after the first batch of rows are available. The issue is that both Beeswax and HS2 clients call request_state->BlockOnWait inside ImpalaServer::FetchInternal. The call to BlockOnWait blocks until rows are ready to be consumed via ClientRequestState::FetchRows.

      So clients can still end up blocking indefinitely waiting for the first row batch to appear.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. IMPALA-9032 Impala returns 0 rows over hs2-http without waiting for fetch_rows_timeout_ms timeout

          • Major - Major loss of function.
          • Resolved
          is related to

          Sub-task - The sub-task of the issue IMPALA-7312 Non-blocking mode for Fetch() RPC

          • Major - Major loss of function.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. IMPALA-10566 Change the default value of FETCH_ROWS_TIMEOUT_MS to 0

          • Major - Major loss of function.
          • Open

          Activity

            People

              stakiar Sahil Takiar
              stakiar Sahil Takiar
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: