[
https://issues.apache.org/jira/browse/KUDU-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724757#comment-16724757
]
jiaqiyang edited comment on KUDU-2638 at 12/19/18 7:40 AM:
-----------------------------------------------------------
this is the kudu cluster one tserver log
[^tserverLog.tar.gz]
the cluster total 19 tservers and 3 masters;
12 sata disk every server
200+ tablet on one tserver;
3 replica every tablet;
there is one question :
why the cluster restart use long time to table avalible , in the log i see that
boostrap very quickly ;but there is very long time spend on major compact; how
can we stop the compact then admin compaction after idle time like HBase
compaction!
was (Author: jiaqiyang):
this is the kudu cluster one tserver log
[^tserverLog.tar.gz]
the cluster total 19 tservers and 3 masters;
12 sata disk every server
200+ tablet on one tserver;
there is one question :
why the cluster restart use long time to table avalible , in the log i see that
boostrap very quickly ;but there is very long time spend on major compact; how
can we stop the compact then admin compaction after idle time like HBase
compaction!
> kudu cluster restart very long time to reused
> ---------------------------------------------
>
> Key: KUDU-2638
> URL: https://issues.apache.org/jira/browse/KUDU-2638
> Project: Kudu
> Issue Type: Improvement
> Reporter: jiaqiyang
> Priority: Major
> Fix For: n/a
>
> Attachments: tserverLog.tar.gz
>
>
> when restart my kudu cluster ;all tablet not avalible:
> run kudu cluster ksck show that:
> Table Summary
>
>
> Name | Status | Total Tablets | Healthy | Under-replicated | Unavailable
> --------------------------------------------------------------------------------+------------
> t1 | HEALTHY | 1 | 1 | 0 | 0
> t2 | UNAVAILABLE | 5 | 0 | 1 | 4
> t3 | UNAVAILABLE | 6 | 2 | 0 | 4
> t3 | UNAVAILABLE | 3 | 0 | 0 | 3
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
