We should periodically "poke" transaction coordinator objects to drive liveness

XMLWordPrintableJSON

    • Sharding 2018-10-08, Sharding 2018-10-22, Sharding 2018-11-05
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Matthew Saltz (Inactive)
              Reporter:
              Matthew Saltz (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: