[
https://issues.apache.org/jira/browse/KUDU-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729493#comment-16729493
]
HeLifu commented on KUDU-2646:
------------------------------
Your case is the same with [~jiaqiyang]'s. Only one disk is in use even if you
have 6 disk.
The '--fs_data_dirs=' should be configured to look something like this:
_fs_data_dirs=/cdh/kudu/tserver/{color:#d04437}disk1{color},/cdh/kudu/tserver/{color:#d04437}disk2{color},/cdh/kudu/tserver/{color:#d04437}disk3{color},/cdh/kudu/tserver/{color:#d04437}disk4{color},/cdh/kudu/tserver/{color:#d04437}disk5{color},/cdh/kudu/tserver/{color:#d04437}disk6{color}_
{code:java}
I1221 16:00:15.634905 135800 fs_report.cc:347] Block manager report
--------------------
1 data directories: /cdh/kudu/tserver/fdd/data
Total live blocks: 33688986
Total live bytes: 134814618486
Total live bytes (after alignment): 259383992320
Total number of LBM containers: 21179 (8196 full)
Did not check for missing blocks
Did not check for orphaned blocks
Total full LBM containers with extra space: 45 (45 repaired)
Total full LBM container extra space in bytes: 4947722240 (4947722240 repaired)
Total incomplete LBM containers: 0 (0 repaired)
Total LBM partial records: 0 (0 repaired){code}
> kudu restart the tablets stats from INITIALIZED change to RUNNING cost a few
> days
> ---------------------------------------------------------------------------------
>
> Key: KUDU-2646
> URL: https://issues.apache.org/jira/browse/KUDU-2646
> Project: Kudu
> Issue Type: Bug
> Reporter: qinzl_1
> Priority: Major
> Fix For: n/a
>
> Attachments: kudu-tserver (1).INFO.gz
>
>
> [^kudu-tserver (1).INFO.gz]i install kudu from cloudera manager ,i have 3
> master and 4 tablet server .do not have any especial config. when i restart
> the server, it can not offer service.i found all tablet server is INITIALIZED
> , and it spend a long time to change to RUNNING
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
