mirror of https://github.com/hanzoai/tasks.git synced 2026-10-04 02:04:03 +00:00

Files

T

History

David ReissandYichao Yang 60dd7fa065 Fix schedule workflow to CAN after signals (#5799 )

## What changed and why?
If a schedule was paused and received a large number of signals
(trigger, backfill, etc.), it wouldn't be able to continue-as-new and
history size could grow past the suggested limit.

For various reasons the main loop receives and processes signals across
iterations, with checking for CAN in between, so a wakeup due to a
signal (instead of a timer) would prevent CAN. Refactoring is hard due
to the determinism requirement, so the simplest fix is to do a second
check.

## How did you test it?
New unit test

2024-04-26 14:03:36 -07:00

addsearchattributes

Rename metricDefinition getters to follow Go's guidelines (#5185 )

2023-11-30 16:34:29 -08:00

batcher

Implement batch reset to build id (#5208 )

2023-12-08 12:41:20 -08:00

common

Set delete namespace activity concurrency limits (#5013 )

2023-10-24 06:57:49 -07:00

deletenamespace

Match all namespace divisions in internal workflows (#5343 )

2024-01-29 12:24:07 -08:00

dlq

Replace gogo/protobuf with google/protobuf (#5032 )

2023-11-21 15:19:37 -08:00

migration

Match all namespace divisions in internal workflows (#5343 )

2024-01-29 12:24:07 -08:00

parentclosepolicy

Rename metricDefinition getters to follow Go's guidelines (#5185 )

2023-11-30 16:34:29 -08:00

replicator

Rename metricDefinition getters to follow Go's guidelines (#5185 )

2023-11-30 16:34:29 -08:00

scanner

Rename metricDefinition getters to follow Go's guidelines (#5185 )

2023-11-30 16:34:29 -08:00

scheduler

Fix schedule workflow to CAN after signals (#5799 )

2024-04-26 14:03:36 -07:00

fx.go

Add the ability to implement and test custom advanced visibility stores (#4871 )

2023-11-22 16:23:36 -06:00

pernamespaceworker_test.go

make use of ringpop LookN method (#5102 )

2023-11-27 15:04:58 -08:00

pernamespaceworker.go

make use of ringpop LookN method (#5102 )

2023-11-27 15:04:58 -08:00

README.md

Delete the archival workflow code (#4782 )

2023-09-05 15:51:33 -07:00

service.go

Add a history replication DLQ test (#5003 )

2023-10-19 21:54:25 -07:00

worker.go

2023-10-23 16:42:08 -07:00

README.md

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

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

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"

Create global namespaces

tctl --ns sample namespace register --gd true --ac active --cl active standby

Failover between zones:

Failover to standby:

tctl --ns sample namespace update --ac standby

Failback to active:

tctl --ns sample namespace update --ac active