Re: [Dispatch Router] How to know the Dispatch Router is ready

[Alan Conway <ac...@redhat.com>]

On Fri, 2017-01-20 at 08:12 -0500, Ted Ross wrote:
> Adel,
> 
> There's probably some interesting conversation we could have around
> what�
> you mean by "ready".��That said, when the following log line is
> issued,�
> the router is initialized and open for business.
> 
> SERVER (info) Operational, # Threads Running
> 
> If you are using a network of routers, the routers will start�
> synchronizing with each other _after_ that log is issued.
> 
> -Ted
> 

Check the dispatch tests/system_test.py, it has several tests for
different kinds of "readiness": are connectors connected, are listeners
listening, are�remote routers "known" to the local router.

In principle, most things should be testable via the management
interface - e.g. once a broker reports it knows about a router via
management, it should be synced with that router. In the early days
that wasn't always entirely reliable, so the system_test.py checks
sometimes go further - e.g. actually try to connect to the management
interface of the remote router via the local one. That may not be
necessary anymore - I wrote those checks a long time ago when things
were less developed.

If you find anything interesting in your quest for readiness checking
I'd like to hear about it as we can probably improve the test suite at
this point.

Cheers,
Alan.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Re: [Dispatch Router] How to know the Dispatch Router is ready

[Alan Conway <ac...@redhat.com>]

On Thu, 2017-02-02 at 09:42 -0500, Alan Conway wrote:
> On Fri, 2017-01-20 at 08:12 -0500, Ted Ross wrote:
> > Adel,
> > 
> > There's probably some interesting conversation we could have around
> > what�
> > you mean by "ready".��That said, when the following log line is
> > issued,�
> > the router is initialized and open for business.
> > 
> > SERVER (info) Operational, # Threads Running
> > 
> > If you are using a network of routers, the routers will start�
> > synchronizing with each other _after_ that log is issued.
> > 
> > -Ted
> > 
> 
> Check the dispatch tests/system_test.py, it has several tests for
> different kinds of "readiness": are connectors connected, are
> listeners
> listening, are�remote routers "known" to the local router.
> 
> In principle, most things should be testable via the management
> interface - e.g. once a broker reports it knows about a router via
> management, it should be synced with that router. In the early days
> that wasn't always entirely reliable, so the system_test.py checks
> sometimes go further - e.g. actually try to connect to the management
> interface of the remote router via the local one. That may not be
> necessary anymore - I wrote those checks a long time ago when things
> were less developed.
> 
> If you find anything interesting in your quest for readiness checking
> I'd like to hear about it as we can probably improve the test suite
> at
> this point.

Actually another thing we could do is provide some more consistent and
easily parsed log messages for readiness of various things. We have
long intended to provide more machine-readable management notifications
 which would include readiness notifications but we haven't gotten
there yet. When we do, it will be closely aligned with logging anyway.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org