Skip to content

Conversation

@feiyang3cat
Copy link
Contributor

@feiyang3cat feiyang3cat commented Jan 23, 2026

What changed?

block external users using internal temporal-sys-per-ns-tq workers through triggering workflows

Why?

enhanced resilience of the cluster

Detailed Explanation

What is not covered

  • activities (need separate pr, impacts current testing)
  • sticky queues mechanism (need separate pr)
  • internal sys-ns related, APIs exposed by history service

What is covered

  • start-workflows (+cron), signal-with-start, multi-option, child-workflows, continue-as-new workflows, schedulers
  • details:
Workflow Entry Point Access Level Should Block?
StartWorkflowExecution Public API Yes — Done
SignalWithStartWorkflowExecution Public API Yes — Done
ExecuteMultiOperation Public API Yes — Done
Start Child Workflow From Workflow Yes —> check parent workflow task queue
Continue-As-New From Workflow No — Inherits parent
Schedules Public API Yes — Done
Cron Public API Yes — Done, covered thru StartWorkflowExecution
Retry Automatic No — Inherits original workflow
ImportWorkflowExecution Admin API No — Admin-only; used for replication
StartAdminBatchOperation Admin API No — Used to start system batch workflows
Nexus StartOperation/Standalone Activity Public API Yes — not for this pr , syncing related team
Worker Deployment Internal No — Allowed
StartBatchOperation Public API for dedicated purpose No — Allowed

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)
  • added new functional test(s)

Potential risks

side-effects on legal system workflows/activities -> covered by regression testing (either unit or functional)

@feiyang3cat feiyang3cat requested review from a team as code owners January 23, 2026 20:30
@feiyang3cat feiyang3cat force-pushed the feat/block-per-ns-tq-workflow branch from 4080986 to 8e61b58 Compare January 23, 2026 20:30
@feiyang3cat feiyang3cat changed the title Feat/block per ns tq workflow block per-ns-tq from external users - workflow section Jan 23, 2026
}

func (pm *taskQueuePartitionManagerImpl) ephemeralDataChanged(data *taskqueuespb.EphemeralData) {
// for now, only sticky partitions act on ephemeral data, normal partitions ignore it.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this change is only for lint purpose

@yycptt yycptt requested a review from dnr January 26, 2026 01:27
@feiyang3cat feiyang3cat force-pushed the feat/block-per-ns-tq-workflow branch 5 times, most recently from fc600a2 to 3cb1eca Compare January 26, 2026 23:06
wtFailedCause enumspb.WorkflowTaskFailedCause,
err error,
) error {

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yycptt request attention

@feiyang3cat feiyang3cat force-pushed the feat/block-per-ns-tq-workflow branch from 3cb1eca to 270056b Compare January 27, 2026 04:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants