[ZCM] [ZC] 2250/ 2 Reject "ZODB .conf no longer supports multiple ZEO Servers for 'failover'"

Issue #2250 Update (Reject) "ZODB .conf no longer supports multiple ZEO Servers for 'failover'"
 Status Rejected, Database/bug critical
To followup, visit:
  http://www.zope.org/Collectors/Zope/2250

==============================================================
= Reject - Entry #2 by tseaver on Dec 5, 2006 12:13 pm

 Status: Pending => Rejected


Uploaded:  "issue_2250.diff"
 - http://www.zope.org/Collectors/Zope/2250/issue_2250.diff/view
I don't think so.  The change (see the attached diff) between the two 'component.xml' files (2.7, 2.8) modifies the 'server' subkey
from 'socket-address' to 'socket-connection-address';  in both
 cases it is a 'multikey', which means that it can be repeated.

The following config stanza works for me on Zope 2.8 (I just tested
that the failover occurs)::

  <zodb_db main>
   mount-point /
   cache-size 5000
   <zeoclient>
    server localhost:9997
    server localhost:9998
    storage 1
    name zeostorage
    var $INSTANCE/var
    cache-size 20MB
   </zeoclient>
  </zodb_db>

________________________________________
= Request - Entry #1 by runyaga on Dec 5, 2006 9:29 am

it looks like from version 2.7 to 2.8/2.9/2.10 somehow the zconfig schema changed on zodb so that it is not possible to assigned a list of zeo servers to a zeo client.  this feature is critical if you have a 'stand by' zeo server.  i believe the schema type changed from 'string-list' to 'socket-address' which sounds like there needs to be 'socket-address-list' to have multiple host:port.

I'm not sure if the multiple server 'feature' is well explained.  it is alluded to in zeo's component.xml describing the server directive and saying its the host for databsae server(s).  

logging it here.  so it doenst get lost. 
==============================================================