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

Provide a cleanup mechanism for cases when source (or destination) no longer exists (DropMirror) #2190

Open
iamKunalGupta opened this issue Oct 25, 2024 · 1 comment
Open

Provide a cleanup mechanism for cases when source (or destination) no longer exists (DropMirror) #2190

iamKunalGupta opened this issue Oct 25, 2024 · 1 comment
Assignees
@iamKunalGupta @heavycrystal @Amogh-Bharadwaj

Comments

@iamKunalGupta
Copy link
Member

During DropFlow, if the source PG does not exists, we run into infinite retries with failed to get source connector: failed to create connection: failed to connect to user=postgres database=postgres:\n\thostname resolving error: lookup db.fsujzxgaybt

Can we (maybe) implement a signal to bypass this activity manually if needed? No need to automate the DropFlow itself
@iamKunalGupta iamKunalGupta changed the title Provide a cleanup mechanism for cases when source postgres no longer exists (DropMirror) Provide a cleanup mechanism for cases when source (or destination) no longer exists (DropMirror) Oct 30, 2024
@heavycrystal
Copy link
Contributor

the retries shouldn't be infinite, the DropFlow cancels after a few minutes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iamKunalGupta iamKunalGupta

@heavycrystal heavycrystal

@Amogh-Bharadwaj Amogh-Bharadwaj

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@iamKunalGupta @heavycrystal @Amogh-Bharadwaj