open db oom error when the database has a large manifest file

[halibobo1205]

hi, due to the manifest file rewrite when db is reopen, the db is running a very long time, manifest file grew up 4.3G.when i reopen the db, versionset.recover cause a oom error because of this Builder /**

• A helper class so we can efficiently apply a whole sequence
• of edits to a particular state without creating intermediate
• Versions that contain full copies of the intermediate state. */ can this manifest deal with batch?

[pcmind]

Batch could be an option, but I think we can try to find a better way to deal with it without creating multiple versions. In this scenario most of the files in the manifest are from files that where already merged and deleted. Beware that manifest may grow in size with the number of files but also with the size of keys used (smallest/largest).

[halibobo1205]

I test it use goleveldb, it very fast,but use goleveldb open an c++ leveldb db, it will lost xxx .log data, this cloud be goleveldb has special manifest deal . rocksdb can check manifest size whenever append.