[
https://issues.apache.org/jira/browse/KUDU-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700340#comment-15700340
]
David Alves commented on KUDU-1127:
-----------------------------------
Converted this to a sub-task of KUDU-430. The new safe time managing entity,
the TimeManager, is aware of consensus and is the ideal place to do this.
> Avoid holding RPC handler threads on replicas that are part of a degraded
> tablet
> --------------------------------------------------------------------------------
>
> Key: KUDU-1127
> URL: https://issues.apache.org/jira/browse/KUDU-1127
> Project: Kudu
> Issue Type: Sub-task
> Components: tserver
> Affects Versions: Private Beta
> Reporter: Todd Lipcon
>
> If the client performs a snapshot scan, we may need to wait for the leader to
> tell us that the timestamp is "safe". If the majority of nodes in a tablet
> are down, this will never happen. After KUDU-689, well wait with a deadline,
> but even this multi-second wait will end up blocking a lot of RPC handlers,
> potentially preventing other useful work from getting done.
> We should probably short-circuit the wait in the case that we haven't heard
> from any leader within the election timeout and just respond immediately.
> Alternatively, we could make this an async callback vs a blocking wait on
> handler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
