On 07/08/2010 09:51 AM, Jason Dobies wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1Yes it does. If we stick with only synchronous requests to that agent and leave asynchronous stuff to the pulp Task engine, temporary (non-durable) queues will be a good approach to pruning dead queues.One more question on this and I'll shut up until the voice call. If all requests are synchronous, is this gonna scale? What happens when we fire off messages to 10K agents and/or if those requests take minutes (if not more) to execute? Even if it's executing in the async task queue, won't this be a fierce burden on the server (it may not be, I'm kinda thinking out loud here).
If the thinking is that: asynchronous = pub/sub = efficiencyThen, an important consideration is: How does qpid implements *durable* subscription to topics (pub/sub)? The durable nature of the subscription usually requires that brokers implement using queues where messages are routed to subscriber queues based on topic/subject and selectors. Asynchronous request/response assumes guaranteed delivery. This means that the message must be queued so it can be delivered to consumers that are not connected when the message is published. This is the definition of durable subscription. So, publishing a message to 10k agents probably still requires 10k queues.
But, if we anticipate this kind of mass operation, then asynchronous will be much more efficient and worth the extra complexity because we can have all the agents performing the operation in parallel. If we did this synchronously, we'd be limited to the Task thread limit.
- -- Jason Dobies RHCE# 805008743336126 Freenode: jdob -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMNeXaAAoJEOMmcTqOSQHCLkEH/0U/qD/yN4LvTn+FaA9svCV4 Jibrwm2NjeLdQ3nzyT2cMvcp73VZdqIVuUg51WTT6wk2kblQ525k6AttTSwZEfku EEvp12IaMNihJWjSQwMlV/KtKoMGzD8q4ggiEGK38bRYLiP5WUlfxjF6uLftvfsl 9H9zl5z+gFC5J0fMakdH8kfR0wxdllQcpPnEUhH0aHheekoPD9sFDyyojDXdpmU5 POIfk4gpEK6ufz28xrSWOF6bWZBPIPuux2QdaUT+WioTS7Vllkqq+1HRszcF1GxC /92VoOHWUX/lt+u+Gft64gXNIqCZy2W7EcSDLfJ11WHlXNjSZDoBAVhHuCBuXNM= =dYFm -----END PGP SIGNATURE----- _______________________________________________ Pulp-list mailing list Pulp-list redhat com https://www.redhat.com/mailman/listinfo/pulp-list
Description: S/MIME Cryptographic Signature