|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
tim-distributed-cache evictor excepetionhi, I am getting following exception when running evictor with tim-searchable. INFO] [evictiontest] Exception in thread "Default Evictor" java.lang.IllegalStateException: not locked [INFO] [evictiontest] at org.terracotta.cache.evictor.EvictorLock.unlock(EvictorLock.java:34) [INFO] [evictiontest] at org.terracotta.cache.evictor.OrphanEvictionListener.onShutdown(OrphanEvictionListener.java:132) [INFO] [evictiontest] at org.terracotta.cache.evictor.Evictor.postRun(Evictor.java:58) [INFO] [evictiontest] at org.terracotta.cache.evictor.EvictionScheduler$EvictionRunner.run(EvictionScheduler.java:98) [INFO] [evictiontest] at java.lang.Thread.run(Thread.java:637) One Question : Selection of orphan listener is done with every run or once its selected its fixed? I am asking this because in logs i saw following line only once. [INFO] [evictiontest] 9185 [Default Evictor] INFO com.tc.dmap.eviction - [13] Elected to be orphan evictor [INFO] [evictiontest] 9185 [Default Evictor] INFO com.tc.dmap.eviction - [13] Local eviction started [INFO] [evictiontest] 9186 [Default Evictor] INFO com.tc.object.applicator.SearchableMapApplicator - Nothing to do for local eviction [INFO] [evictiontest] 9186 [Default Evictor] INFO com.tc.dmap.eviction - [13] Local eviction finished [INFO] [evictiontest] 9186 [Default Evictor] INFO com.tc.dmap.eviction - [13] Running orphan eviction (evictionCount = 0, orphanEvictionFrequency = 1) After these all eviction cycle printed following line with no announcement of orphan evictor. I am running only one Node. [INFO] [evictiontest] 16216 [Default Evictor] INFO com.tc.dmap.eviction - [13] Local eviction started [INFO] [evictiontest] 16216 [Default Evictor] INFO com.tc.object.applicator.SearchableMapApplicator - Nothing to do for local eviction [INFO] [evictiontest] 16217 [Default Evictor] INFO com.tc.dmap.eviction - [13] Local eviction finished [INFO] [evictiontest] 16217 [Default Evictor] INFO com.tc.dmap.eviction - [13] Running orphan eviction (evictionCount = 0, orphanEvictionFrequency = 1) Best regards, Tushar Khairnar, Performance Engineer, Terracotta Software India Pvt. Ltd., Skype : tushar.khairnar, gtalk : tushar.khairnar _______________________________________________ tc-dev mailing list tc-dev@... http://lists.terracotta.org/mailman/listinfo/tc-dev |
|
|
Re: tim-distributed-cache evictor excepetionHi,
Update I was running it with TTI=10 seconds when I changed it to 60 seconds exception vanished. Regards, Tushar On Jul 17, 2009, at 6:05 PM, Tushar Khairnar wrote:
Best regards, Tushar Khairnar, Performance Engineer, Terracotta Software India Pvt. Ltd., Skype : tushar.khairnar, gtalk : tushar.khairnar _______________________________________________ tc-dev mailing list tc-dev@... http://lists.terracotta.org/mailman/listinfo/tc-dev |
|
|
Re: tim-distributed-cache evictor excepetionIf you have something reproducible could you file a jira so we can look at it?
On the question, the orphan listener is done with a tryLock and so only one node will succeed. That node will continue to be the orphan evictor unless the node dies and the lock is released - at that point another node would pick up as orphan evictor. It's definitely possible that in the future this will change slightly. On Jul 17, 2009, at 7:54 AM, Tushar Khairnar wrote:
_______________________________________________ tc-dev mailing list tc-dev@... http://lists.terracotta.org/mailman/listinfo/tc-dev |
| Free embeddable forum powered by Nabble | Forum Help |