kudu-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Lipcon <t...@cloudera.com>
Subject Re: executed kudu fs check error
Date Fri, 28 Jul 2017 15:32:59 GMT
On Fri, Jul 28, 2017 at 1:02 AM, lizhong0815@qq.com <lizhong0815@qq.com>
wrote:

> Hi, guys!
>      I executed the kudu fs check command encountered an error:
> Command: kudu fs check -fs_wal_dir = /app/kudu/tserver/ -
> fs_data_dirs = /app/kudu/tserver -repair = true
>

Is this the exact command you executed? You should not have any space
characters between the flag and its argument. eg instead use:

kudu fs check --fs_wal_dir=/app/kudu/tserver --repair

If you can paste the exact output as well, that would be helpful. I don't
see any error message below, just "INFO" level status messages.


> Error log:
> I0728 15: 55: 43.958799 32600 env_posix.cc:1460] Not
> raising process file limit of 131072; it is already as high as it can go
> I0728 15: 55: 44.334758 32600 file_cache.cc:463]
> Constructed file cache lbm with capacity 52428
> I0728 15: 55: 44.638924 32600 fs_manager.cc:263] Time spent
> opening block manager: real 0.000s user 0.000s sys 0.000s
> Password error / app / kudu / tserver / data / block_man
> What do I need to pay attention to when I use this
> command? Need to stop kudu cluster?
> I use the kudu version: kudu 1.4.0-cdh5.12.0
>
> ------------------------------
> with best regards, lizhong
>



-- 
Todd Lipcon
Software Engineer, Cloudera

Mime
View raw message