Github user athanatos commented on the issue:
https://github.com/apache/bookkeeper/pull/193
@sijie Oops, I just noticed the comments. I guess you just changed the
title?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
GitHub user athanatos opened a pull request:
https://github.com/apache/bookkeeper/pull/193
BOOKKEEPER-1086: ZkUnderreplicationManager cache watcher
Previously, getLedgerToReplicate left watches each time it traversed the
tree until it found a suitable replication target. Since
Github user athanatos commented on the issue:
https://github.com/apache/bookkeeper/pull/80
@sijie @eolivelli If I'm reading this right, you are trying to use
sync_file_range to avoid calling FileChannel.force, which presumably calls
fsync. You actually can't use sync_file_range
Github user athanatos commented on the issue:
https://github.com/apache/bookkeeper/pull/130
Cool, what's the next step?
---
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
Github user athanatos commented on the issue:
https://github.com/apache/bookkeeper/pull/130
Build's failing due to
Tests in error:
BookieRecoveryTest.ensurePasswordUsedForOldLedgers[4] »
BKNoSuchLedgerExists
BookieRecoveryTest.ensurePasswordUsedForOldLedgers[5] Â
GitHub user athanatos opened a pull request:
https://github.com/apache/bookkeeper/pull/130
BOOKKEEPER-1031: close the ledger handle in ReplicationWorker.rerepliâ¦
â¦cate
Otherwise, we build up an unbounded set of Listeners in the
AbstractZkLedgerManager listenerSet
