A Snowflake id generator sees its clock jump backwards by 50 ms. What should it do?

Options

• ✓ Refuse to issue ids, or wait, until the clock passes the last timestamp it used Correct
• ✗ Reset the sequence to 0 and carry on
• ✗ Pick a new random worker id
• ✗ Ignore it; the sequence keeps ids unique

Why

Reusing timestamps it has already issued ids for would create duplicates with the same worker id and sequence. Waiting out a small jump is safe; a large one should take the generator out of service.

Review this in your daily deck → All cards in Sharding