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.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
