Re: kahadb recovery

2017-04-22 Thread Steve Hill
The version is 5.14.3 On 4/22/17 6:55 PM, Timothy Bish wrote: On 04/22/2017 05:56 PM, Steve Hill wrote: We now realize that the number after the @ is the file number being processed and after the colon is the offset in the file. Eg, 97226:18610005 means db-97226.log is being processed. Based

Re: kahadb recovery

2017-04-22 Thread Timothy Bish
On 04/22/2017 05:56 PM, Steve Hill wrote: We now realize that the number after the @ is the file number being processed and after the colon is the offset in the file. Eg, 97226:18610005 means db-97226.log is being processed. Based on this at least we now know how far we are through the startup

Re: kahadb recovery

2017-04-22 Thread Steve Hill
We now realize that the number after the @ is the file number being processed and after the colon is the offset in the file. Eg, 97226:18610005 means db-97226.log is being processed. Based on this at least we now know how far we are through the startup. It looks like it will take a further 2

kahadb recovery

2017-04-22 Thread Steve Hill
Hi! Can anyone provide guidance on why restarting ActiveMQ can take hours? We were seeing lots of message not found in sequence and it is currently at 5.9M entries recovered. Is there a way to know how many entries there are so we have an idea when it might finish? There are currently abou