[rt-users] Re: InnoDB Ticket IDs incrementing by 10?
mike
mike at bseder.org
Wed May 2 12:48:55 EDT 2007
hate to be repetitive, but i also don't like bouncing production databases
(our mysql handles a lot more than our RT system)....do I need to
reload/restart mysql for the auto_increment_increment change to take hold?
our tickets are still incrementing n+10 rather than n+1, and the slave's
config is set for auto_increment_offset=2 rather than 1 like the master is.
thanks!
On 5/1/07, mike <mike at bseder.org> wrote:
>
> hmm....does this require a restart of mysql? It now *looks* correct, but
> is still incrementing n+10?
>
> mysql> SHOW VARIABLES LIKE 'auto_inc%';
> +--------------------------+-------+
> | Variable_name | Value |
> +--------------------------+-------+
> | auto_increment_increment | 1 |
> | auto_increment_offset | 1 |
> +--------------------------+-------+
>
> I made this change as as the root/dba account, so I'm confused...
>
>
>
> On 5/1/07, mike <mike at bseder.org> wrote:
> >
> > yes indeed - the master is now set to
> >
> > mysql> SHOW VARIABLES LIKE 'auto_inc%';
> > +--------------------------+-------+
> > | Variable_name | Value |
> > +--------------------------+-------+
> > | auto_increment_increment | 1 |
> > | auto_increment_offset | 1 |
> > +--------------------------+-------+
> >
> > and the slave is
> >
> > mysql> SHOW VARIABLES LIKE 'auto_inc%';
> > +--------------------------+-------+
> > | Variable_name | Value |
> > +--------------------------+-------+
> > | auto_increment_increment | 1 |
> > | auto_increment_offset | 2 |
> > +--------------------------+-------+
> > 2 rows in set (0.00 sec)
> >
> > prior to making the change suggested, the master was configured as:
> >
> >
> > Current database: rt3
> >
> > +--------------------------+-------+
> > | Variable_name | Value |
> > +--------------------------+-------+
> > | auto_increment_increment | 10 |
> > | auto_increment_offset | 1 |
> > +--------------------------+-------+
> > 2 rows in set (0.00 sec)
> >
> > do I need to reload mysql, or is this a hot-fix? needless to say, i am
> > not a DBA, let alone terribly cluey with MySQL (but learning more every
> > day) ;).
> >
> > Thank you very much for the assistance, it's very much appreciated and I
> > owe Mark Roedel a six-pack for the initial assist :)
> >
> >
> >
> > On 5/1/07, Graham Dunn <gdunn01 at harris.com> wrote:
> > >
> > > mike wrote:
> > > > Hello,
> > > >
> > > > Since upgrading to RT 3.6.3, I've noticed that all of our tickets
> > > are
> > > > incrementing their ticket numbers/IDs by n+10 -
> > > >
> > > Are you using multiple-master replication?
> > >
> > > http://dev.mysql.com/doc/refman/5.0/en/replication-auto-increment.html
> > >
> > >
> > > _______________________________________________
> > > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> > >
> > > Community help: http://wiki.bestpractical.com
> > > Commercial support: sales at bestpractical.com
> > >
> > >
> > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> > > Buy a copy at http://rtbook.bestpractical.com
> > >
> >
> >
> >
> > --
> > --
> > One way or another, everyone stops bleeding.
> >
> >
> > --
> > --
> > One way or another, everyone stops bleeding.
> >
>
>
>
> --
> --
> One way or another, everyone stops bleeding.
>
--
--
One way or another, everyone stops bleeding.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20070502/68ae61e8/attachment.htm>
More information about the rt-users
mailing list