Github user sijie commented on the issue:
https://github.com/apache/bookkeeper/pull/189
The concern I have is - people don't have to care about this flag.
User should still configure the directories in the way how they are
configuring right now. The bookie can be smart to figure about the directory
and disk-partition layout. You can build the Map<FileStore, List<File>> in
LedgerDirManager. So the LedgerDirManager does the de-duplication and handle
disk filled up correctly. When a DiskPartition fills up, all the directories on
this disk partition should be marked as non-writable.
If the concern is about the duplicated disk partitions fill the ledger
directory checking. we should just fix the behavior, rather than exposing
another configuration setting to the users.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
