akhitev

This issue occurs cause datacenterId resides in the most significant part of generated Id. Java long type stores sign in the most significant bit. So if dataCenterId will be >...

Could anyone from maintainers take a look at this, and confirm whether it is known bug, or we are missing something?