temporalio / temporalio/temporal

Cross-replicated search attributes are not persistent

Open
#5,853 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

potential-bug teams/cgs
Dominant language
Go
Stars
23.2k
Forks
1.9k
Avg merge
2d 8h
Merged PRs (30d)
228

Description

Expected Behavior

Expected to be able to add search attributes in global namespaces

Actual Behavior

No effect / change to search attributes

Steps to Reproduce the Problem

  1. Set up a cross-replicated global namespace between two clusters
  2. Execute temporal operator search-attribute create --namespace my-ns --name AbcSearch --type Text against active cluster (cluster-a for example purposes)
  3. Execute the same against non-active cluster (no matter how many times this is run, it will always say search attributes have been added, expect to run once and all subsequent executions should raise conflict errors)
  4. Execute temporal operator search-attribute list --namespace my-ns against active cluster (will maybe appear)
  5. Execute the same against non-active cluster (will not appear)
  6. Initiate active cluster failover using temporal namespace update --active-cluster cluster-b my-ns
  7. Re-execute 3 & 5, search attributes will not update

Specifications

  • Version: 1.23.0
  • Platform: Debian

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the behavior with the temporal operator search-attribute create and list commands against both clusters, then test the namespace failover using temporal namespace update. Trace the search-attribute handling for cross-replicated global namespaces; done means creation persists across clusters, duplicate creation reports a conflict, listing is consistent, and failover preserves the attributes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.