ArvinDevel opened a new issue #1918: Bypass journal ledger feature URL: https://github.com/apache/bookkeeper/issues/1918 Is this a question, feature request, bug report, or bookkeeper proposal? **FEATURE REQUEST** 1. Please describe the feature you are requesting. Currently, BK write journal before flush data to persistent device which will cause two write of data. Since we already have replicas to guarantee the availability and has auto-recovery mechanism, sometimes we don't want this high reliability with writing journal at the cost of write twice of the same data. Especially when the disk bandwidth is precious. 2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue? nice-to-have 3. Provide any additional detail on your proposed use case for this feature. When the source of data has another backup, it's ok to tolerant data lost of the memtable. In addition to that, the bk's auto-recovery could recover the failed bookie's data from other healthy bookies. I think this feature is a bit like #471, but with another method. Hope to see you guys' viewpoint.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
