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 2016/08/05 19:21:20 UTC
[jira] [Updated] (KUDU-1549) recovery speed of kudu-tserver should
be faster.
[ https://issues.apache.org/jira/browse/KUDU-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adar Dembo updated KUDU-1549:
-----------------------------
Attachment: a14844513e5243a993b2b84bf0dcec4c.short.txt
Here is a truncated log showing about five iterations of the remote bootstrap loop.
> recovery speed of kudu-tserver should be faster.
> ------------------------------------------------
>
> Key: KUDU-1549
> URL: https://issues.apache.org/jira/browse/KUDU-1549
> Project: Kudu
> Issue Type: Improvement
> Environment: cpu: Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
> mem: 252 G
> disk: single ssd 1.5 T left.
> Reporter: zhangsong
> Attachments: a14844513e5243a993b2b84bf0dcec4c.short.txt
>
>
> After experiencing physical node crash, it found recovery/start speed of kudu-tserver is slower than that of usual restart case. There are some message like "Found partial trailing metadata" in kudu-tserver log and it seems cost more than 20 minute to recover these metadata.
> According to adar , it should be this slow.
> attachment is the start log .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)