[SERVER-55190] Generate and attach UUID for each Client Created: 15/Mar/21  Updated: 29/Oct/23  Resolved: 19/Mar/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Benjamin Caimano (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-24912 Include Client Metadata in audit logs Closed
Related
is related to SERVER-55041 Benchmark UUID generation performance Closed
Backwards Compatibility: Fully Compatible
Sprint: Security 2021-03-22
Participants:

 Description   

For the purposes of log streams that persist over the course of multiple server lifetimes, connection id is not a unique identifier. Since UUID generation costs less than a microsecond for us, we should attach a UUID to each Client upon creation.



 Comments   
Comment by Githook User [ 17/Mar/21 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-55190 Generate and attach UUID for each Client
Branch: master
https://github.com/mongodb/mongo/commit/5bcfde0d8399ef17b384a350e63004c0ef335374

Comment by Benjamin Caimano (Inactive) [ 15/Mar/21 ]

Thanks for the heads up, Kal. I think this might be an orthogonal concept but it all ties into a bigger picture of cross-server context tracking.

Comment by Kaloian Manassiev [ 15/Mar/21 ]

FYI, we also have something called TrackinMetadata which is essentially UUID to track an operation across the cluster. Not sure if this is a proposal for a similar concept, but it would be nice to unify them.

Generated at Thu Feb 08 05:35:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.