[SERVER-37025] We should periodically "poke" transaction coordinator objects to drive liveness Created: 06/Sep/18  Updated: 27/Oct/23  Resolved: 01/Nov/18

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

Type: Task Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Gone away Votes: 0
Labels: ShardedTxn:DistributedCommit, transaction-coordinator-management
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-36855 Isolate coordinator liveness logic "p... Closed
is duplicated by SERVER-36862 Ensure we trigger resending commit fo... Closed
is duplicated by SERVER-37230 Ensure shards delete their Transactio... Closed
Sprint: Sharding 2018-10-08, Sharding 2018-10-22, Sharding 2018-11-05
Participants:

 Description   

This should be implemented in the TransactionCoordinatorService with a task executed on a thread pool that reschedules itself when execution finishes if the coordinator exists, and does not reschedule it if the coordinator no longer exists.


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