[ https://issues.apache.org/jira/browse/IMPALA-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934724#comment-16934724 ]
Sahil Takiar commented on IMPALA-8962: -------------------------------------- Another option would be to make {{FETCH_ROWS_TIMEOUT_MS}} apply across the call to {{ClientRequestState::BlockOnWait}} and {{PlanRootSink::GetNext}}, although that might be a bit messier to implement. > FETCH_ROWS_TIMEOUT_MS should apply before rows are available > ------------------------------------------------------------ > > Key: IMPALA-8962 > URL: https://issues.apache.org/jira/browse/IMPALA-8962 > Project: IMPALA > Issue Type: Bug > Components: Clients > Reporter: Sahil Takiar > Assignee: Sahil Takiar > Priority: Major > > 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. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org