delta/rabbitmq-server.git, branch bug25638hg.rabbitmq.com: Obsolete (use rabbitmq-server-git)
Add a TODO for if we are ever unbusy enough to look at removing this code.2013-06-21T10:28:32+00:00Simon MacMullensimon@rabbitmq.com2013-06-21T10:28:32+00:0085953f05729171ae2a6a3285ca0bb63e353d6654
Don't persist gm_pids; by definition when all we have is the rabbit_durable_queue record the cluster has gone down completely so there can't be any pids. Fixes gm_pids leak. Since we're here, fix a similar but less severe leak in sync_slave_pids. (Less severe because rabbit_mirror_queue_misc:store_updated_slaves/1 has the effect of cleaning it up periodically. But it's still wrong.)2013-06-21T10:26:15+00:00Simon MacMullensimon@rabbitmq.com2013-06-21T10:26:15+00:000c3f3e71f9d41361f8afcd903c54db18a5d8385e
cosmetic: state the not-immediatly-obvious2013-06-17T17:04:06+00:00Matthias Radestockmatthias@rabbitmq.com2013-06-17T17:04:06+00:00b106047a4df6a5d230097a4ada549be69fade0c7
Throw the key too. And if the server side still fails try to fail with more information.2013-06-17T15:38:59+00:00Simon MacMullensimon@rabbitmq.com2013-06-17T15:38:59+00:005f0614d143470458910ca9c262599e6f24fcf1d3
rabbit_node_monitor should depend on rabbit_alarm2013-06-17T15:34:23+00:00Emile Joubertemile@rabbitmq.com2013-06-17T15:34:23+00:00484f2158f0c17c4833951e1c7d693a347a1891eb
Check value when clients update flying_ets2013-06-17T13:01:51+00:00Emile Joubertemile@rabbitmq.com2013-06-17T13:01:51+00:009fd4a06fcb563df24689c3e87b8d38e6242c230a
merge bug25600 into stable2013-06-14T13:33:44+00:00Tim Watsontim@rabbitmq.com2013-06-14T13:33:44+00:00b0ac434e4b3f06c555f2b9f737152178b3b7b95d