[
https://issues.apache.org/jira/browse/BOOKKEEPER-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16058018#comment-16058018
]
ASF GitHub Bot commented on BOOKKEEPER-1033:
--------------------------------------------
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.
> Handle DirsPartitionDuplication
> -------------------------------
>
> Key: BOOKKEEPER-1033
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1033
> Project: Bookkeeper
> Issue Type: New Feature
> Reporter: Charan Reddy Guttapalem
> Assignee: Charan Reddy Guttapalem
>
> - Provide configuration for allowDirsPartitionDuplication
> - while calculating total disk metrics account Partition Duplication
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
