GitHub user mapleFU added a comment to the discussion: We expect kvrocks to support MVCC
> Thanks, as you say, The `cache` actually is `Customized Computing Node`, like > `BufferPool`, cache operators and merge it, then flush `BatchResult` to > kvrocks. Writing the same server that using hash to partition the server. But > unable to ensure that all data is written accurately kvrocks, that's what > we're worried about. Google MapReduce has a process to assign task and check status, seems that you can recover from WAL in your compute node, so I think you can either write the response to kvrocks straiforward, or caching with a caching policy (like lru / max caching time ) and flushing them. If a server crashs, you can force recover and using max caching time to flush them GitHub link: https://github.com/apache/incubator-kvrocks/discussions/905#discussioncomment-3707123 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
