You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Andrew Wong (JIRA)" <ji...@apache.org> on 2018/06/11 17:55:00 UTC
[jira] [Reopened] (KUDU-2314) fs manager checks should list wal and
metadata directories along with data dirs
[ https://issues.apache.org/jira/browse/KUDU-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wong reopened KUDU-2314:
-------------------------------
Looks like this isn't working as intended. Did a little digging and it seems like opening the block manager is trampling over the FsReport, so I'm just seeing a bunch of empty wal and metadata directory strings:
{{wal directory:}}
{{metadata directory:}}
{{1 data directories: /data/8/awong/Repositories/kudu/build/asan/data/data}}
> fs manager checks should list wal and metadata directories along with data dirs
> -------------------------------------------------------------------------------
>
> Key: KUDU-2314
> URL: https://issues.apache.org/jira/browse/KUDU-2314
> Project: Kudu
> Issue Type: Improvement
> Components: fs, ops-tooling
> Affects Versions: 1.6.0
> Reporter: Will Berkeley
> Assignee: Fengling Wang
> Priority: Major
> Fix For: 1.8.0
>
>
> The current block manager report lists the data directories:
> {noformat}
> I0220 10:37:09.937450 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
> {noformat}
> It should also list the metadata and wal directories, maybe looking something like
> {noformat}
> I0220 10:37:09.937450 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
> --------------------
> wal directory: /private/tmp/kudu/wal/master/0
> metadata directory: /private/tmp/kudu/wal/master/0
> 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
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)