AMQP: Notifications on RPC peer lifecycle
If you have an RPC client, it often can't do anything while the RPC server is down (e.g. hasn't started yet). When starting both processes there can be a race.
Right now if the server is down you just get a bunch of stack traces.
It would be nice if the client could get messages when the server queue appears and disappears. Then, the client could cleanly wait for the server to be present.
Or if the server restarts, the client could put up a maintenance page (for example, if the client is a web app) during the time that it's down.
Right now if the server is down you just get a bunch of stack traces.
It would be nice if the client could get messages when the server queue appears and disappears. Then, the client could cleanly wait for the server to be present.
Or if the server restarts, the client could put up a maintenance page (for example, if the client is a web app) during the time that it's down.
Leave a comment
on 2011-10-07 17:41 *
By viktorklang
Summary changed from Notifications on RPC peer lifecycle to AMQP: Notifications on RPC peer lifecycle
Updating tickets (#1129, #1132, #1138, #1149, #1153, #1154, #1157, #1161, #1163, #1168, #1170, #1171, #1172, #1176, #1177, #1178, #1180, #1199, #1217, #1218, #1219, #1237, #1238, #1239, #1244, #1246, #1249, #1250, #1251, #1252, #1256, #1301, #1302, #1306, #1395, #1396, #1409, #1418, #455, #891, #895, #912, #956, #972, #1031, #1374, #880, #1125, #1146)