Possible bug - Multi-Zone fallback

[pat-humphreys]

evcache-client-1.0.5

I am using the ZoneClusteredEVCacheClientPoolImpl with 1 client instance and 6 memcache servers (3 in each zone). If I write a key to both zones and then kill the primary memcache the next read for that key goes to the primary first.

Then realizes that the primary is down, throws an exception which is caught in EVCacheImpl.get(String key, EVCacheTranscoder tc) where it does the following check

Line 244

catch (Exception ex) {
//TODO: Add counter for exception ?
if (log.isDebugEnabled()) {
log.debug("Exception while getting data for key : " + key, ex);
}
if (!_throwException.get()) {
return null;
}
throw new EVCacheException("Exception getting data for key : " + key, ex);
}

it then returns a null.

The next request for this key goes to the secondary and succeeds, should it not try the secondary rather than returning a null?

[smadappa]

Good catch, in the current implementation a calls fails before the fallback can work.
I will work on a fix for this.

[pat-humphreys]

Good to hear its a defect. It was driving me mad :)
If you don't have time to look at it. I can do it for you?

[smadappa]

The would be great. If you are thinking of an approach let me know and i can comment.

[stacey-david]

Hi @smadappa ,

Can you confirm whether this issue was actually fixed?