Our database looks the same; however since you can only have one master tracker running at any time, no one will be running updates against your other master DB.
Clint Twelve Horses Mobile Social Web Email Clinton Goudie-Nice Architect / Senior Software Engineer [EMAIL PROTECTED] Phone: +1.801.571.2665 ext 3264 Mobile: +1.801.915.0629 Fax: +1.801.571.2669 LinkedIn: http://www.linkedin.com/in/cgoudie Twelve Horses 13961 Minuteman Drive Suite 125 Draper, UT 84020 www.twelvehorses.com On Wed, 2008-04-09 at 12:51 +0200, Michael A. Toth wrote: > On Wed, Mar 19, 2008 at 9:08 PM, dormando <[EMAIL PROTECTED]> wrote: > > > > I run mogilefs under master-master setups, with the following concessions: > > > > - auto_increment_offset is used to ensure each side gets unique values. > > - writes only go to one *active* side. > > > > Either done via an HA VIP or explicit configuration. > > Hi Dormando, > > I've got a question about your master-master configuration. I checked > the default mogilefs SQL table schemas, and I didn't find any auto > increment column. Do I have to change schema for master-master > replication? Here is my current state: > > mysql> use mogilefs > Database changed > mysql> desc file; > +----------+----------------------+------+-----+---------+-------+ > | Field | Type | Null | Key | Default | Extra | > +----------+----------------------+------+-----+---------+-------+ > | fid | int(10) unsigned | NO | PRI | NULL | | > | dmid | smallint(5) unsigned | NO | MUL | NULL | | > | dkey | varchar(255) | YES | | NULL | | > | length | int(10) unsigned | YES | | NULL | | > | classid | tinyint(3) unsigned | NO | | NULL | | > | devcount | tinyint(3) unsigned | NO | | NULL | | > +----------+----------------------+------+-----+---------+-------+ > 6 rows in set (0.02 sec) > > Thanks, > Michael
