[
https://issues.apache.org/jira/browse/IMPALA-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703727#comment-17703727
]
ASF subversion and git services commented on IMPALA-3292:
---------------------------------------------------------
Commit 65ae5febee868addafb56b01f9276a03601dd039 in impala's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=65ae5febe ]
IMPALA-12014 warning on failed KeepAlive for Kudu scanner
With this patch, there is now a warning message output when
ScannerKeepAlive RPC for a Kudu scanner fails. To avoid flooding the
log with those messages, KLOG_EVERY_N_SECS(WARNING, 60) is used.
I also updated the signature of the KuduScanner::BuildErrorString()
method to become a constant one.
This is a follow-up to IMPALA-3292.
Change-Id: If39f968685797506491d3d5ebc481efb6e43a568
Reviewed-on: http://gerrit.cloudera.org:8080/19643
Reviewed-by: Wenzhe Zhou <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Michael Smith <[email protected]>
> Kudu scanner should not fail if KeepAlive request fails
> -------------------------------------------------------
>
> Key: IMPALA-3292
> URL: https://issues.apache.org/jira/browse/IMPALA-3292
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Kudu_Impala
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Fix For: Impala 2.7.0
>
>
> The KeepKuduScannerAlive() function can fail with ServiceUnavailable if it is
> running against a very heavily-loaded tablet server. This is OK -- it should
> ignore the warning and just try again after a short time, rather than failing
> the whole query.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
