[SERVER-39751] Investigate the case when transaction size exceeds all available memory Created: 21/Feb/19  Updated: 06/Dec/22  Resolved: 06/May/19

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

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: bigtxns_testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-39750 Investigate the case when transaction... Closed
Assigned Teams:
Replication
Participants:

 Comments   
Comment by Siyuan Zhou [ 06/May/19 ]

kelsey.schubert, I'm closing this as "Won't fix" since the behavior of larger transactions than the available memory is not different than other out-of-memory cases. We won't have a default limit of transaction size but provides a way to tune it in SERVER-39811.

Comment by Siyuan Zhou [ 09/Apr/19 ]

kelsey.schubert, after discussing with milkie, we believe this should be no difference than other out-of-memory issue. Do we have a general guideline for that case? As a workaround, SERVER-39811 is to add a limit of transaction size. Detecting OOM and continuing gracefully might be hard.

Comment by Kelsey Schubert [ 21/Feb/19 ]

Ideally, the failure mode should include enough diagnostics for a user to determine what went wrong.

Generated at Thu Feb 08 04:53:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.