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?
--- 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. ---