Todd Lipcon commented on KUDU-1774:

That's the most safe way, for sure.

If you want to try something that is more risky, I _think_ it would work to do 
the following:

- copy the 'instance' file from one of your existing directories to the new one
- move some of the '.data' and corresponding '.metadata' files from the 
existing disk into the new directory

I've never tried this, though, so if it's important data, I would try the 
procedure first in a test environment.

> add dirs use flag fs_data_dirs, but restart tserver failed
> ----------------------------------------------------------
>                 Key: KUDU-1774
>                 URL: https://issues.apache.org/jira/browse/KUDU-1774
>             Project: Kudu
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: CentOS 6.x
> Kudu 1.0.1
>            Reporter: zhangguangqiang
> before restart tserver, the flags is:
> -fs_data_dirs= /data1/kudu/tserver_data/
> -fs_wal_dir=/data/kudu/tserver_wal
> when I update the flag fs_data_dirs to
> -fs_data_dirs= /data1/kudu/tserver_data/, /data2/kudu/tserver_data/, 
> /data3/kudu/tserver_data/
> and restart the tserver. the error messages shows below:
> I1130 11:29:35.860208 56435 hybrid_clock.cc:178] HybridClock initialized. 
> Resolution in nanos?: 1 Wait times tolerance adjustment: 1.0005 Current 
> error: 334145
> I1130 11:29:35.861098 56435 server_base.cc:164] Could not load existing FS 
> layout: Not found: /data2/kudu/tserver_data/instance: No such file or 
> directory (error 2)
> I1130 11:29:35.861104 56435 server_base.cc:165] Creating new FS layout
> F1130 11:29:35.861150 56435 tablet_server_main.cc:55] Check failed: _s.ok() 
> Bad status: Already present: Could not create new FS layout: FSManager root 
> is not empty: /data/kudu/tserver_wal
> So I want to know is this a bug or not supported yet ?

This message was sent by Atlassian JIRA

Reply via email to