3 ms·
The in-memory memtable gets converted to sstable. The WAL is ONLY read after crashing, to fill a new memtable. Your comment looked like "WAL is sorted and con
by ddorian43 3y ago
The in-memory memtable gets converted to sstable.
The WAL is ONLY read after crashing, to fill a new memtable.
Your comment looked like "WAL is sorted and converted to sstable":
> If a WAL file gets too long then a new one is created and the old one is sorted and written to an sstable asynchronously.
- mike_hearn 3y agoSeems a bit pedantic. The memtable is (when fully flushing writes) a derivative of the WAL. Or vice-versa if you like. They hold equivalent data, organized differently (yes yes modulo tombstones). Anyway you're right, I was being lazy in not writing out memtable explicitly.
- ddorian43 3y agoWAL splitting isn't connected to memtable flushing, they are separate processes.