If you are using transactions, the system will also need to add the page-transaction into memory, so you still can get out of memory on that case.
Oh right well im not using transaction either. I wonder why is hornet trying to load all pages into memory at all.
Ok so i managed to get it to come up again by decreasing the number of consumers (to 1 for each queue). I was using 4 for each queue. Could that be the problem? How do i properly size the memory requirements? In other words, how do i know how much memory i need, given Q queues, C consumers, M max size and J journal size?
1 of 1 people found this helpful
What's probably happening then is that you have a large consumer-window size for each consuemr, and that's depaging a lot of stuff?
It's hard to tell.. this is all about sizing on each consumer.