Drupal reassigns node IDs

[mjordan]

I have narrowed down circumstances in which Drupal reassigns node IDs. The conditions for this to happen are that that no nodes exist (in other words, the highest node ID value at the time is 0), and it only happens just after you boot the Vagrant. You can replicate this behavior by doing the following:

1. delete all nodes from your Vagrant and vagrant halt it.
2. vagrant up it.
3. create a new node (content type doesn't matter).
4. it will have the node ID of 1.

I am assuming that this behavior is a side effect of how MySQL's autoincrement fields work, so it should not be a problem in production (where you wouldn't be restarting at 0). But, at least I can say I was not imagining this.

[dannylamb]

Wow...

Artifact of mysql peculiarities plus virtualization subtleties...

That's a scary one.

[mjordan]

Could also explain things @manez was describing, since orphaned media would be associated with a node ID that was reused.

[mjordan]

Closed during July 17 tech call.