Skip to content

Make DistributedTelemetryActor more durable and add different retention policy for different tables #2967

@thedavekwon

Description

@thedavekwon
  • If child procmesh is dead or stopped, the root DistribtuedTelemetry Actor should be still able to query rest of the children
  • Different tables need different retention policy. For example, persists actor table indefinitely.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions