[
https://issues.apache.org/jira/browse/KUDU-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725550#comment-16725550
]
jiaqiyang edited comment on KUDU-2638 at 12/20/18 4:06 AM:
-----------------------------------------------------------
Thank you for your attention!
I'm sorry there is one disk on my tserver!
>From your Suggestion i know there are three questions in my now kudu cluster：
Firstly, one disk and --num_tablets_to_open_simultaneously default will only
bootstrap one tablet at a time ; Secondly, the disk io-state is very busy up to
100%; Thirdly,there is many small block;
But i have some question:
1.one tablet lifecycle from INITIALIZ to RUNNING spent time affected by major
compact ?
2.by manual trigger major compact can reduce small block ,but compact/flush
Op manage by
MaintenanceManager
Use Case:
there is many UPDATEs in my case:
mysql binlog realtime Synchronize to kudu so there is many UPDATEs events
we want to use kudu as a retime OLAP engion
was (Author: jiaqiyang):
Thank you for your attention!
yes i think so:there is many UPDATEs in my case:
mysql binlog realtime Synchronize to kudu so there is many UPDATEs events
we want to use kudu as a retime OLAP engion
> 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: kudu16.tc.tablet.png, 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)
