[SERVER-42976] Create an internal-facing transaction parameter to extend the lifetime for a given transaction Created: 22/Aug/19  Updated: 08/Oct/19  Resolved: 08/Oct/19

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

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Blake Oler
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding 2019-09-09, Sharding 2019-09-23, Sharding 2019-10-07, Sharding 2019-10-21
Participants:

 Description   

This will involve a parameter along the line of transactionLifetimeExtensionSeconds, which will add the given amount of seconds to the expiration for a given transaction.

Detailed approach to follow.



 Comments   
Comment by Blake Oler [ 08/Oct/19 ]

The context for this ticket was to enable the Refine Collection Shard Key Project (PM-1327) to allow users with sufficiently large chunks collections to be able to refine their collection's shard key with a transaction that would run longer than 60 seconds.

We've decided to Won't Fix this:

  1. A user will likely try to refine their shard key in the early stages of a collection's lifetime, reducing the likelihood of a chunks collection being large enough to reach the transaction lifetime limit.
  2. If a user wants to refine their shard key, and possesses a chunks collection large enough to cause issues, we can simply direct this user to restart their config server with the updated transaction lifetime limit for all transactions.
Generated at Thu Feb 08 05:01:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.