[
https://issues.apache.org/jira/browse/BOOKKEEPER-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065218#comment-16065218
]
ASF GitHub Bot commented on BOOKKEEPER-1033:
--------------------------------------------
Github user jvrao commented on the issue:
https://github.com/apache/bookkeeper/pull/189
The flag is to allow backward compatibility and warn the user if they
configured multiple journal dirs on the same partition by mistake. Per @sijie's
point, yes we can handle them by monitoring the disk partition, and mark all
dirs on that dir as non-writable. But this doesn't address the perf problem
@reddycharan mentioned. I think we need to look at this in two folds.
1. Add correct metrics for reporting capacity, and keep existing behavior.
This is what @reddycharan did.
2. @sijie suggesting enhancing existing behavior, which can be handeled
with another Jira item.
Thoughts?
> 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)
