-
|
I have couchdb installed from docker official image and I've noticed that sometimes after container restart my auto generated id's reset theirs prefix values. F.e. I have Maybe this is because container IP is changed? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
The default uuid generation algorithm is "sequential". It generates a random prefix on each CouchDB node and keeps it as state. With each uuid, it increments a suffix at the end with a random increment. The random prefix changes when either a node is restarted or after the increment overflows . https://github.com/apache/couchdb/blob/main/rel/overlay/etc/default.ini#L450-L453 |
Beta Was this translation helpful? Give feedback.
-
|
So I can not rely on sorting by id because after restart it can regenerate prefix? |
Beta Was this translation helpful? Give feedback.
-
|
These are not guaranteed to increment if the prefix changes. There is a high chance you'll get incrementing uuids in the same response if you ask for say a batch of 1000 uuids ( Depending on your setup and use case, the utc_id scheme may be useful, but that's still not a globally unique monotonically incrementing ID service. If that's what is needed you'd have to build it yourself as a separate service. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks you, utc_id is wat i need |
Beta Was this translation helpful? Give feedback.
The default uuid generation algorithm is "sequential". It generates a random prefix on each CouchDB node and keeps it as state. With each uuid, it increments a suffix at the end with a random increment. The random prefix changes when either a node is restarted or after the increment overflows .
https://github.com/apache/couchdb/blob/main/rel/overlay/etc/default.ini#L450-L453