On 06/01/2016 04:18 AM, RuralHunter wrote:
activemq 5.10.2, the gc log show:
2016-06-01 16:26:37,299 | TRACE | not removing data file: 857 as contained
ack(s) refer to referenced file: [834, 850, 832, 849, 833, 855, 854, 836,
837, 857, 856] | org.apache.activemq.store.kahadb.MessageD
atabase | ActiveMQ Journal Checkpoint Worker
But the existing data files start with 856. Are those referenced file with
number less than 856 displayed in the log normal? or it is a bug?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/data-file-gc-log-indicates-ack-refer-to-non-existing-file-tp4712509.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The log line indicates that the given file (857) contains ACKs for all
those referenced files, which might not exist as they could have been
GC'd. The file does have ACK(s) though that reference file 856
according to your info so it won't be GC'd until 856 gets GC'd to
preserve the ACK in case there store has to be recovered by replaying
the journal logs.
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
