[SERVER-70409] Serialize and deserialize HealthLogEntries with multitenancySupport Created: 10/Oct/22 Updated: 29/Oct/23 Resolved: 01/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Mathis Bessa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ntdi_must_have | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Serverless
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-11-14, Server Serverless 2023-08-07, Server Serverless 2023-08-21, Server Serverless 2023-09-04 |
| Participants: | |
| Story Points: | 2 |
| Description |
|
The documents in healthlog collection (local.system.healthlog) are an IDL defined type HealthLogEntry. The documents have an optional namespace field, so we'll need a way to track the tenantId when the namespace is not empty. As a part of this ticket we'll need to decide how to store the tenantId in this case - should we make this collection per tenant? Store the tenantId in a separate field similar to the oplog? Or, continue to prefix similar to the _mdb_catalog? Then, we'll need to change the places we serialize and deserialize this type to behave accordingly. |
| Comments |
| Comment by Githook User [ 01/Sep/23 ] |
|
Author: {'name': 'Mathis Bessa', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |
| Comment by Janna Golden [ 09/Jun/23 ] |
|
We don't migrate this collection today, and I don't think we want to start migrating it, so I actually don't think we should make it per-tenant. So, my vote is for option 2 or 3. |