On 02-04-2012 10:14:05 -0600, Joseph Brower wrote:

Yes.  We're wanting connection level balancing. :-D  I'm not seeing how to
actually enable this or see how it's working, the documentation is rather
sparse.

       A  default  match  has  implicit  `/*' added to the search, making more
       generic search strings match more specific ones.  Hence, a connect with
       database  dbX is the same as dbX/* and hence matches dbX/master/tableQ.
       Similar, a database connect for */master matches the same  database  as
       before.   Note  that the implicit `/*' is not added if that would cause
       no matches, such as for */master/tableQ which would return all  masters
       for  tableQ,  which  in  our hypothetical example is only dbX.  In con‐
       trast, a database connect for */slave/tableQ matches with either dbY or
       dbZ.   monetdbd  returns the two options to the client in a round-robin
       fashion, such that subsequent connects for the same pattern result in a
       load-balanced connect to either of both databases.

The above might be a bit scarce, I guess monetdbd's discovery and
matching features are hardly used outside our group.

Fabian

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

_______________________________________________
MonetDB-users mailing list
MonetDB-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/monetdb-users