Had a Riak instance in production where there were a lot of leveled_cdb instances that had a large amount of binary memory referenced. This could be cleared through garbage_collect() but garbage collection didn't seem to be trying to do this.
The binaries referenced may have been in the active journal. This was after a riak restart, so perhaps related to scan on startup?
Had a Riak instance in production where there were a lot of leveled_cdb instances that had a large amount of binary memory referenced. This could be cleared through garbage_collect() but garbage collection didn't seem to be trying to do this.
The binaries referenced may have been in the active journal. This was after a riak restart, so perhaps related to scan on startup?