[
https://issues.apache.org/jira/browse/KUDU-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-1906:
------------------------------
Description: Running RowCounter against a reasonably small table, I see map
tasks occasionally hanging waiting for a response from a scanner. -It seems to
be correlated with "read timeouts" in the logs. I'm guessing we are not
handling something properly in this case.- (was: Running RowCounter against a
reasonably small table, I see map tasks occasionally hanging waiting for a
response from a scanner. It seems to be correlated with "read timeouts" in the
logs. I'm guessing we are not handling something properly in this case.)
Summary: Java client hangs in scanner nextRows call (was: Java client
hangs in scanner after read timeout)
> Java client hangs in scanner nextRows call
> ------------------------------------------
>
> Key: KUDU-1906
> URL: https://issues.apache.org/jira/browse/KUDU-1906
> Project: Kudu
> Issue Type: Bug
> Components: client
> Affects Versions: 1.3.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
>
> Running RowCounter against a reasonably small table, I see map tasks
> occasionally hanging waiting for a response from a scanner. -It seems to be
> correlated with "read timeouts" in the logs. I'm guessing we are not handling
> something properly in this case.-
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
