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/05/15 23:23:05 UTC

[jira] [Resolved] (KUDU-1549) LBM should start up faster

     [ https://issues.apache.org/jira/browse/KUDU-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adar Dembo resolved KUDU-1549.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.0

Tentatively marking this fixed. From the list I wrote earlier, Kudu now does #1 (commit e4e59bb) and #3 (commit 91f1f37) at startup. Deployments with qualifying containers should see one somewhat slower startup in Kudu 1.4 (as containers are either deleted or compacted), then much faster startups subsequently.

Further areas of exploration are discussed in KUDU-2014.


> LBM should start up faster
> --------------------------
>
>                 Key: KUDU-1549
>                 URL: https://issues.apache.org/jira/browse/KUDU-1549
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: tablet, tserver
>         Environment: cpu: Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
> mem: 252 G
> disk: single ssd  1.5 T left.
>            Reporter: zhangsong
>              Labels: data-scalability
>             Fix For: 1.4.0
>
>         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.15#6346)