You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2017/09/02 16:43:02 UTC
[jira] [Commented] (KUDU-2131) Tablet copy session may expire
before completion for large tablet
[ https://issues.apache.org/jira/browse/KUDU-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151536#comment-16151536 ]
Adar Dembo commented on KUDU-2131:
----------------------------------
[~hahao] can you elaborate? Is the issue that DownloadBlocks can take >3m (default idle timeout) to commit the new blocks such that the session is terminated before DownloadWALs? How large of a tablet is necessary to trigger this effect?
> Tablet copy session may expire before completion for large tablet
> -----------------------------------------------------------------
>
> Key: KUDU-2131
> URL: https://issues.apache.org/jira/browse/KUDU-2131
> Project: Kudu
> Issue Type: Bug
> Reporter: Hao Hao
> Priority: Blocker
> Fix For: 1.5.0
>
>
> KUDU-1726 introduced an optimization to do a bulk sync-to-disk once the tablet copy operation is complete. However, when tested in a large cluster, I found disk synchronization in batches can result in the tablet session expires before the synchronization complete. There is a flag '--tablet_copy_idle_timeout_ms' to control the amount of time without activity before a tablet copy session expires, but it is tagged as hidden(not user-facing).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)