[JBoss Cache: Core Edition] - event queue size is at 98% threshold
by lovelyliatroim
Hi Guys,
Im seeing alot of this in my log files,
anonymous wrote :
| 16:38:40,367 [STREAMING_STATE_TRANSFER sender,10.251.145.205:53173] WARN org.jboss.cache.RegionImpl - putNodeEvent(): eviction node event queue size is at 98% threshold value of capacity: 200000 Region: /realtime/quotes/ You will need to reduce the wakeUpIntervalSeconds parameter.
|
Now whats happening is this, my app receives a notification to transfer a region to another node, the node transfers the data which can be up to 500,000 records from that node to the other node. After transfer it will look to delete/remove the 500,000 records from its cache. When the deletion occurs I assume it starts creating all the node events on the queue.
Now wakeUpInterval is set to 1 so that cant be made any better/quicker but the queue size is obviously too small, this kind of event should happen rarely, its only if something goes wrong.
What are the implications of increasing the eventQueue size?? Just more memory i would say. What happens when events are fired and cant get on the eviction queue?? Im seeing something that suggests to me that its dropped because after i call the remove for a region, i still see records in that region when it should be empty, does that make sense to you guys?? If not then its something else going on!!
Also is there a difference between cache.removeRegion(FQN) and cache.removeNode(FQN)?? Currently using removeNode(), will try with region and see if it makes any difference, otherwise i will have to up the queueSize.
Thanks for your time,
LL
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192548#4192548
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192548
17 years, 5 months
[Beginners Corner] - Re: JBoss not bound as a global element
by jhsingle
Thanks for all the feedback (and for escalating this question to a more advanced forum). Here's what I've found this morning.
1. Added the port-component-name and still got the same error. (does the name value have to match another attribute somewhere else?)
1a. Yes, there is a closing tag, it just escaped my cut-paste.
2. I tried using the DTD and my EJB now deploys successfully. My JUnit tests are now failing with an access authorization error but I will assume that is a separate configuration problem with the test user certificate.
3. After discussing with co-workers, I removed the "xmlns" attribute from the jboss tag of my instance document (jboss.xml), so the jboss tag is now no longer attached to a namespace (it is now global?) and again the EJB deploys successfully and I get the same access errors as with the DTD solution. Is this de-namespacing of the instance document a "bad" thing to do?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192533#4192533
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192533
17 years, 5 months