Description of problem:
Currently, any katello agent requires 1 (sometimes 2) connection(s) / AMQP link(s) via qdrouterd topology to qpidd. The only (TCP and AMQP) connection between qpidd and qdrouterd aggregates all sessions from all Content Hosts.
Per AMQP1.0 specification, one AMQP connection can handle up to 65535 channels/sessions per one AMQP connection.
Therefore, in the current design, Satellite has a hard limit of 64k Content Hosts that can run katello agent.
Version-Release number of selected component (if applicable):
100% (I guess)
Steps to Reproduce:
1. Try to run katello agent on >65535 Content Hosts managed by one Satellite via arbitrary number of Capsules
1. shall not be feasible
1. shall be feasible
- change proton implementing AMQP such that it allows more sessions. proton library would violate AMQP specification, then
- change/extend qdrouterd (or proton?) behaviour such that when it needs to open a session "over the limit", let open a new AMQP connection on the same TCP connection first
- optionally to the above, open a new TCP connection instead (such that 1 TCP connection does not deliver all the traffic for all the >64k clients)
Satellite's upper bounds are limited by AMQP's ceiling. Is this an artifact of a particular version of AMQP (QPID).
(In reply to David Caplan from comment #3)
> Satellite's upper bounds are limited by AMQP's ceiling. Is this an artifact
> of a particular version of AMQP (QPID).
This is a Qpid Dispatch Router issue, not an AMQP issue. AMQP can handle all of the links you need. We will address this limitation in the router in an upcoming release.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.