[DOCS-15812] Add specific "Flexible Sync" tag to both Advance compaction and Client Max Offline Created: 11/Jan/23  Updated: 14/Mar/23  Resolved: 14/Mar/23

Status: Closed
Project: Documentation
Component/s: Realm
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Josman Perez Exposito Assignee: Lindsey Moore
Resolution: Done Votes: 0
Labels: app-services, realm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by DOCS-15811 Add specific "Flexible Sync" tag to b... Closed
Related
Participants:
Days since reply: 1 year, 4 weeks ago
Epic Link: DOCSP-25822

 Description   

Historically both "Advance compaction" and "Client Max Offline Time" were created for both Device Sync configurations, both PBS and QBS. However, after enabling this for PBS, we found that it introduced a lot of bugs, and so we removed it but kept the idea of adding it in the future, it was later dropped, but the docs still reflect it as being for both.

This creates confusion for clients as well as within the team. New hires don't know that this is really only intended for QBS and the fact that from the UI you can enable Client Max Offline time for PBS doesn't help. In this case, enabling this for PBS has no impact.

Docs: https://www.mongodb.com/docs/atlas/app-services/sync/go-to-production/optimize-sync-atlas-usage/#advanced-backend-compaction



 Comments   
Comment by Drew DiPalma (Inactive) [ 11/Jan/23 ]

Yeah, I've seen enough confusion here that I think it makes sense to note that Client Max Offline is for Flexible Sync only. 

Comment by Josman Perez Exposito [ 11/Jan/23 ]

Hello drew.dipalma@mongodb.com, ward.ianp@gmail.com. Do you agree with changing the docs to reflect this?

Thanks,

Generated at Thu Feb 08 08:13:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.