[rabbitmq-discuss] Extremely slow responses

Marcin Krol mrkafk at gmail.com
Tue Jan 25 20:25:59 GMT 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marek Majkowski wrote:

Thanks to everyone for replies!

I rewrote rpc server and client from scrach, accounting for feedback I
received it mostly works now.

> And the last thing: clustering != HA.
> Clustering doesn't mean that the messages are replicated.
> Every queue 'lives' on a single node, if that node goes down,
> that queue goes down.

Absolutely, this is why I will implement my own (Postgres) serial
transaction id in RPC server to know when the node has its data out of
sync with other nodes.

(disclosure: you may view it as strange, but all I needed really was RPC
+ basic multi-master replication for PG for data redundancy, not
performance, and in testing I found that unfortunately none of the
existing solutions fits the bill for production-readiness, including
pgpool-II unfortunately).


- --

Regards,
mk

- --
Premature optimization is the root of all fun.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNPzHXAAoJEFMgHzhQQ7hOqH0H/Agrcbmqj2Ttfs5q7YOCl5W1
9I4FNSeZ62a11Wf8qhP0ITGsnba1PzO9zmdYN2EWreZzW/mtzI9RO7D7jn8LzpIU
pt+EvmiPTurSDhvab/KcOs5h5/z0fp2dUSUK5X4F99wYmizGfh8CVWo118TJghGn
J5QKrCxao/NEmNoFEu99p3L1kBelHF9A0TpdMoxY1G1uvJ7vQ/S8L4bbedKU1fR3
TE91uMjaujG2gSxakGOZFinA+oaMFeb7Y0fvL1sZtjzXLT90B8nvklINX5UrdnOR
48t5Z81jcrENYZYyFrSFji+L034adqWn9yxyX5fNM4T176QFohSHPvsnedARKlU=
=haU3
-----END PGP SIGNATURE-----


More information about the rabbitmq-discuss mailing list