Question 121596 in Redis Question posted in
The official documentation can be found here.

Redis – Why I'm getting collisions on UUID v4 generated with node 16 on Cloud Run?

I’m getting a lot of collisions, at least 5 on the last 100.000 generated UUID. Right now wea are checking that generated UUID with a redis instance, so if a collision happen, we can regenerate it.

The service has at least 2 instances always running.

the UUID is generated with

crypto.randomUUID()
Tags:

2

Answers


  1. 0

    I can only asume they are looking at this method and it does not allow a seed parameter.

    I am not sure why this would happen but might have been coincidence that 5 ids were repeated. I suggest looking at other options people have tried, such as including date.now() in order to truly never get a repeat.

    Login or Signup to reply.
  2. 0

    In UUID’s npm page shows support only up to node 14, is that the problem? https://www.npmjs.com/package/uuid

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search