Re-generate client UID after CRIU restore operation (0.38.0) #17061
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With JITServer Technology, each client JVM has a unique ID that is generated during JVM bootstrap. When checkpointing a JVM that is supposed to be used in client mode, this client UID gets baked into the JVM snapshot, and all JVM processes that are restored from this snapshot will have the same UID, which confuses the server. This comit re-generates the client UID during the snapshot restore operation so that different clients will have different UIDs.
Issue: #17022