[ovirt-devel] Redundant stomp connection for SPM
Allon Mureinik
amureini at redhat.com
Tue Jan 24 19:43:54 UTC 2017
In the jsonrpc era, I can't think, offhand, about a good reason to
keep these two connections.
Liron - any insight?
On Tue, Jan 24, 2017 at 6:18 PM, Roy Golan <rgolan at redhat.com> wrote:
> +storage ping
>
> On 17 January 2017 at 12:19, Piotr Kliczewski <piotr.kliczewski at gmail.com>
> wrote:
>>
>> It should be enough to subscribe to irs specific queues. Instead of
>> creating new client we can rely on status of a subscription.
>>
>> On Tue, Jan 17, 2017 at 10:54 AM, Roy Golan <rgolan at redhat.com> wrote:
>> > For each SPM host the engine creates a different stomp connection (See
>> > JsonRpcIIrsServer.java) . This also means another client connection to
>> > maintain on the SPM machine.
>> >
>> > What is the reason we still have it and what does it guarantee? Please
>> > add
>> > any info here prior to opening a bug to remove it for 4.2.
>> >
>> >
>> >
>> > _______________________________________________
>> > Devel mailing list
>> > Devel at ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/devel
>
>
More information about the Devel
mailing list