Rewrite "Perform Long-Running Queries" page to show intended use (DOCS-15065)

[DOCS-15090] Additional example for long running queries Created: 03/Feb/22  Updated: 30/Oct/23  Resolved: 09/Feb/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Sub-task Priority: Minor - P4
Reporter: Brian Lane Assignee: Jeffrey Allen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 2 years, 6 days ago
Story Points: 3

 Description   

Hey jeffrey.allen,

Here are the slides from my .live talk.  Consider adding the example from slides 3&4 which highlights previous version behavior over the new behavior when issuing a snapshot read.  Prior to 5.0 snapshots read could be done in a transaction, but transactions only run on primaries. So the workload isolation part that Jane was referring to is now with this project complete, snapshot reads can be done outside of transactions and thus run on secondaries.  

Also from our notes, a reminder to call out that if a query does run longer than our current 5 min history window, the snapshotTooOld error can be returned.


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