Obsolete jdb not being cleaned up
dimoApr 18 2013 — edited May 10 2013Hi,
Setup:
* We are using Oracle NoSQL 1.2.123.
* We have 3 replication groups with 3 replication nodes each.
Problem:
* 2 of the slaves (in 2 different replication groups) occupy much more space in JDB files (10 times more) then all the others. As these are slaves, and writes always go through the master, and all nodes in a replication group have the same data (eventually), I assume that this is stale data that has not been cleaned up by the BDB garbage collection (cleaner threads). Unfortunately the logs do not show anything new (since Dec. last year) and the oldest JDB files are from February.
Questions:
* Any ideas what could have gone wrong?
* What can I do to trigger the cleaners to cleanup the old data? Is that safe to do in production environment and without downtime?
* Is it really safe to assume that the current data in within a replication groups is really the same?
Thank you in advance
Dimo
PS. A thread dump shows 2 cleaner threads that do nothing.