[
https://issues.apache.org/jira/browse/BOOKKEEPER-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065468#comment-16065468
]
ASF GitHub Bot commented on BOOKKEEPER-1033:
--------------------------------------------
Github user sijie commented on the issue:
https://github.com/apache/bookkeeper/pull/189
@jvrao
sorry, what is the performance problem behind this? is there anything I
missed in this conversation?
If a user configures multiple journal directories, can we dedup and use one
journal directory per disk partition? If we dedup, there is no performance
degradation and there is no backward compatibility issue, right?
For example, we open a entrylog file by calling
**ledgerDirsManager.getWritableLedgerDirsForNewLog()** , the dirs manager can
handle the duplication (make sure one directory per disk partition is used) and
return the right directory. By doing this, all the directory/disk partition
related complexity is hidden and managed and people don't have the know the
details.
I don't have any strong opinion adding another setting. My feeling is that
we are not taking the right approach to address the problem here.
> 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)
