[KUDU-2315] Inconsistency between -fs_data_dirs and reported data directories in block manager report

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.6.0
• Component/s: fs
• Assignee: Unassigned
• Reporter: William Berkeley
• Created: 20/Feb/18 18:54
• Updated: 20/Feb/18 18:55

Description

There's a difference between what needs to be specified in fs_data_dirs and what gets reported as a data directory:

$ kudu fs check -fs_wal_dir=/tmp/kudu/wal/master/0 -fs_data_dirs=/tmp/kudu/data/master/0
...
I0220 10:45:58.398344 2427953984 fs_manager.cc:430] Opened local filesystem: /private/tmp/kudu/data/master/0,/private/tmp/kudu/wal/master/0
uuid: "d421daa92e13497d8fe3ce8d0c3ada44"
format_stamp: "Formatted at 2018-02-18 17:06:27 on cloudbook.local"
Block manager report
--------------------
1 data directories: /private/tmp/kudu/data/master/0/data
Total live blocks: 0
Total live bytes: 0
Total live bytes (after alignment): 0
Total number of LBM containers: 0 (0 full)
Total missing blocks: 0
Total orphaned blocks: 0 (0 repaired)
Total orphaned block bytes: 0 (0 repaired)
Did not check for full LBM containers with extra space
Did not check for incomplete LBM containers
Did not check for malformed LBM records
Did not check for misaligned LBM blocks
Did not check for partial LBM records

-fs_data_dirs is /tmp/kudu/data/master/0 but the report says the data directory is /tmp/kudu/data/master/0/data. Setting fs_data_dirs to the reported data directory fails the command:

$ kudu fs check -fs_wal_dir=/tmp/kudu/wal/master/0 -fs_data_dirs=/tmp/kudu/data/master/0/data
I0220 10:54:35.072971 2427953984 fs_manager.cc:261] Metadata directory not provided
I0220 10:54:35.073729 2427953984 fs_manager.cc:267] Using write-ahead log directory (fs_wal_dir) as metadata directory
Not found: /private/tmp/kudu/data/master/0/data/instance: No such file or directory (error 2)