You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have better visibility into bitcask merge activity.
Log events when merge starts?
A public ETS table (very low update frequency, to avoid worries about performance impact) that tracks which bitcask instances are merging (and perhaps also list of input files)?
The text was updated successfully, but these errors were encountered:
+1 I generally use {log_needs_merge, true} to get a start of merge log and any information we can provide on the status or progress of a merge would be fantastic. Data like how long since last merge, merge progress, etc would be a huge win.
How does this sound: an info message when the merge starts, and cleaning up the post merge message to be just the vnode index and a list of file ids so that it doesn't take up so much space in the logs?
I'd also like to make that change to needs_merge logging as well.
It would be nice to have better visibility into bitcask merge activity.
The text was updated successfully, but these errors were encountered: