Lookup cache timed out - Message processor Logs - How can i debug ?

[anilsr]

2016-06-30 10:21:42,895 Apigee-Timer-6 ERROR S.LOOKUP_CACHE - LookupCacheStepDefinition$1.run() : LookupCacheExecution.fetchCachedEntry : Fetch operation has timed out for cache entry XXX__XXX____978e3bd6-dd73-42b4-b464-85ef69c71798. Cache name = XXX__XXX__session-cache & time out = 30000 MILLISECONDS

So it’s timing out after trying to do a cache lookup for over 30 seconds… That’s a crazy long time, but what I don’t see is that the cassandra boxes are ever truly stressed. CPU util peaks at below 50% and the message processors likewise have room with cpu peaking at about 55%.

What's the good starting point to debug similar issue in Private Cloud ?

~~Q:S:S~~

[#2]

Hi,

This article will help turn on debugging for the MP.

https://community.apigee.com/articles/1533/how-to-enable-debug-in-the-apigee-edge-router-and.html

Russell

[anilsr]

Thanks @Russell Blewitt for the pointer, it's helpful.

[anilsr]

@Russell Blewitt , I have heard similar issues like above after upgrading from 4.15.07 to 16.01.

Seems liks turning on debugging kills the MP performance and then we no longer see the error. Any idea ?