--On Tuesday, July 09, 2013 1:49 PM -0700 Howard Chu hyc@symas.com wrote:
Quanah Gibson-Mount wrote:
--On Tuesday, July 09, 2013 1:25 PM -0700 Howard Chu hyc@symas.com wrote:
So the downside would be single point of failure for writes? I.e., if the system with the slapd configured for doing writes went down due to hardware or power issues, you'd need to configure one of the other slapds to accept writes, and then update all the clients to use that server.
Yes. We could do this fairly transparently using something like the chaining overlay. Have it identically configured on all servers, with a prioritized list of write masters. (Could do this to make mirrormode easier to setup too.) If the current node is the write master, allow write ops thru, otherwise chain them to the current write master. Then clients can send ops to any server they want.
Sounds cool to me. :)
We should probably overhaul the connection manager and threadpool before this, otherwise chaining overhead will be too bad.
Sounds like we have a 2.5 roadmap then.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration