3 ms·

nop. we will not ack any write which is not in data or journal. please check the put details in the blog.

• loeg 5mo ago
  You initiate a write to the journal, but do not sync it before ACKing to the client.
  • zzsheng 5mo ago
    journal file was pre-alloacated and we use direct-io for journal write so no need to call fsync.
    • deleted 5mo ago
      [deleted]
    • loeg 5mo ago
      Again, it is not durably persisted before acking to the client. Like I said earlier, that might be fine for your durability model, but it is unusual.
      • thomas_fa 5mo ago
        We would wait for Bss data and journal DirectIO and the acking (sending response back to api_server) in the callback function. What you are implying is what s3 actually doing and you can get see from their paper[1] and we are stronger than that. [1]https://www.amazon.science/publications/using-lightweight-formal-methods-to-validate-a-key-value-storage-node-in-amazon-s3 https://www.amazon.science/publications/using-lightweight-fo....