So we have this issue from time to time. Somethings inside Apigee are not very forgiving of real-world network scenarios. Its worse when you are deploying to multiple datacenters from one management server (like we do in all of our Private Cloud installations...)
Here are the scenarios that have hit us to date:
1) message processor or router is somehow not able to talk to the database. (seems to have been generally resolved since 15.05) - resolved by restarting the MP or Router
2) management service is somehow not able to talk to all of the message processors and routers in the same transaction cycle (just had this problem this morning) - looks like a MP or Router problem but is only resolved by restarting the offending Management Service.
3) management service is unable to talk to one specific message processor or router in a transaction cycle (had this problem last in 15.07) - must restart Management Service.
4) management service is unable to open an rpc connection out (not seen on the network layer as an error, only w/in the software stack) (had this problem last in 15.07) - must restart Management Service.
5) message processor not able to correctly talk to zookeeper (this seems to have been generally resolved since 15.07) - Must restart MP or Router.
I have a series of tickets open with support and we are working through these problems one at a time. It is made more difficult by the tendency to blame "the network". While network conditions may in-fact be a problem - they will ALWAYS be a problem and complex systems must account for this.
Ill leave it up to the SW design experts to fuss over how - while i push the whys on them...
LinkedIn
Twitter
