Files
temporal/service/worker/README.md
Michael Snowden 362c61e7c4 Delete the archival workflow code (#4782)
<!-- Describe what has changed in this PR -->
**What changed?**
This PR deletes all the code for the old workflow-based workflow
archival feature.

<!-- Tell your future self why have you made these changes -->
**Why?**
Originally, the tool to archive workflows was itself written as a
workflow. There were some complications that arose from this, so we
decided to build the archival system closer to the metal as its own
queue similar to the timer and transfer queues. In a previous release,
we disabled the archival workflow, and enabled the new archival queue.
Now that this process is done, we can delete all the dead code for the
archival workflow.

<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
**How did you test it?**
I just searched for "archiv" in our codebase and looked at every
occurrence.

<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**
Maybe there are people still using the old archival workflow, and
they'll now need to migrate.

<!-- Is this PR a hotfix candidate or require that a notification be
sent to the broader community? (Yes/No) -->
**Is hotfix candidate?**
I don't think so.
2023-09-05 15:51:33 -07:00

1.2 KiB

Temporal Worker

Temporal Worker is a role for Temporal service used for hosting any components responsible for performing background processing on the Temporal cluster.

Replicator

Replicator is a background worker responsible for consuming replication tasks generated by remote Temporal clusters and pass it down to processor, so they can be applied to local Temporal cluster.

Quickstart for localhost development

  1. Start Temporal development server for active zone:

    make start-cdc-active
    
  2. Start Temporal development server for standby(passive) zone:

    make start-cdc-standby
    
  3. Connect two Temporal clusters:

    tctl --ad 127.0.0.1:7233 adm cl upsert-remote-cluster --frontend_address "localhost:8233"
    tctl --ad 127.0.0.1:8233 adm cl upsert-remote-cluster --frontend_address "localhost:7233"
    
  4. Create global namespaces

    tctl --ns sample namespace register --gd true --ac active --cl active standby
    
  5. Failover between zones:

    Failover to standby:

    tctl --ns sample namespace update --ac standby
    

    Failback to active:

    tctl --ns sample namespace update --ac active