From 10c4677c86b29c74e8546bc9d8ba3e8e0f0c1372 Mon Sep 17 00:00:00 2001 From: Alex Chi Date: Sun, 9 Mar 2025 16:14:02 -0400 Subject: [PATCH] docs: add question related to #91 Signed-off-by: Alex Chi --- mini-lsm-book/src/week3-05-txn-occ.md | 1 + 1 file changed, 1 insertion(+) diff --git a/mini-lsm-book/src/week3-05-txn-occ.md b/mini-lsm-book/src/week3-05-txn-occ.md index 172465f..430ed6e 100644 --- a/mini-lsm-book/src/week3-05-txn-occ.md +++ b/mini-lsm-book/src/week3-05-txn-occ.md @@ -79,6 +79,7 @@ A batch should be handled in the same mem table and the same WAL, even if it exc * What if the user wants to batch import data (i.e., 1TB?) If they use the transaction API to do that, will you give them some advice? Is there any opportunity to optimize for this case? * What is optimistic concurrency control? What would the system be like if we implement pessimistic concurrency control instead in Mini-LSM? * What happens if your system crashes and leave a corrupted WAL on the disk? How do you handle this situation? +* When you commit the txn, is it necessary to put everything into the memtable in batch, or you can simply put it key by key? Why? ## Bonus Tasks