Hello, and Happy Friday! While attempting to calculate an expansion ratio, a client and I initiated manual merges of a ML 7.0-3 database, then recorded the size. We did see the database size decrease, as well as merge-related entries in the log; however, the number of deleted fragments never reached zero. This is different than I remember from previous versions. A scan of release notes for versions 5, 6, and 7 didn't turn up anything.
The merge timestamp is zero, and the system would have been relatively quiet when merge was requested. The number of remaining deleted fragments was relatively low, and did decrease after some merges, just never to zero. Given the size of our documents, these few deleted fragments would not have significantly skewed the results. Nonetheless, curiosity has the better of me. After the second test of the day, there were ~65K documents taking up ~150 MB. There were 879 deleted fragments after a merge. Might this be a display bug, or does the merge process ultimately decide just how far to go? Thanks much. -Brent Brent Hartwig, Solutions Architect | RSI Content Solutions
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
