Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Persist Mirror Status in Catalog #2623

Open
iamKunalGupta opened this issue Feb 24, 2025 · 2 comments · May be fixed by #2634
Open

Persist Mirror Status in Catalog #2623

iamKunalGupta opened this issue Feb 24, 2025 · 2 comments · May be fixed by #2634
Assignees
@serprex @iskakaushik @iamKunalGupta

Comments

@iamKunalGupta
Copy link
Member

This is for 2 reasons:

  1. Completed mirrors
    • WF which are beyond temporal retention period
    • Non Determinism of completed workflows
  2. Costs associated with querying workflows
@serprex
Copy link
Member

serprex commented Feb 24, 2025 •
edited
Loading

Alternatively, put caching on the mirror flow status endpoint. Won't address past retention period tho

@iamKunalGupta
Copy link
Member Author

Alternatively, put caching on the mirror flow status endpoint. Won't address past retention period tho

Any upgrades can still break stuff tho. Here catalog can act as a cache itself. Would help in costs if we want to emit a flow status metric for every mirror

@iamKunalGupta iamKunalGupta linked a pull request Feb 26, 2025 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@serprex serprex

@iskakaushik iskakaushik

@iamKunalGupta iamKunalGupta

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: persist flow status in catalog PeerDB-io/peerdb
3 participants
@serprex @iskakaushik @iamKunalGupta