Replace DataReplicator's use of ReplicationExecutor with ThreadPoolExecutor

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 18 (08/05/16)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We can use a ThreadPoolTaskExecutor + helper classes to make a nice interface to create the OperationContext and take DB/Coll locks for the callers lambda.

      All internal state will need to be protected by the DataReplicator internal mutex, as is done mostly already.

              Assignee:
              Benety Goh
              Reporter:
              Scott Hernandez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: