Bug 400761 - Bug number increased by 10, not one?
Bug number increased by 10, not one?
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs (Show other bugs)
All Linux
low Severity low (vote)
: ---
: ---
Assigned To: PnT DevOps Devs
Depends On:
  Show dependency treegraph
Reported: 2007-11-27 06:25 EST by Mamoru TASAKA
Modified: 2013-06-23 22:13 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-27 08:22:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mamoru TASAKA 2007-11-27 06:25:25 EST
Description of problem:
It seems recently when we create new bug report, bug number
seems to increase by 10, not one?

Example A:
bug 380081 and bug 380091 .
Bug reports says that I created the latter bug 0 seconds after
the former...

Example B.
I checked bug 400001 - 400011 and bug 400002 through 400010
does not exist, however 400011 exists.

Additional info:
Around bug 200000, bug number seems to increase by one.
Comment 1 Noura El hawary 2007-11-27 08:22:03 EST
With our new move to a replicated MySQL server environment, we had to change the
increment value to 20. This allows future growth when dealing with master to
master server replication. So this would explain what you are seeing.

This link explains some of the reason it must be configured this way.


It is also well documented in the MySQL documentation but I can't find the link
at the moment. We plan to have multiple masters spread around geographically in
the future. The gaps you have in your primary keys determine how many masters
you can have so currently this would limit us to 10. We used to have this set to
20 and 
since lowered it to 10.

Note You need to log in before you can comment on or make changes to this bug.