Hi all, what happens if we have a tap / target com...
# troubleshooting
d
Hi all, what happens if we have a tap / target combination that is currently running in our infrastructure, and then another job attempts to run for that same tap / target (exact same
meltano
command)? Both commands are sharing the same backend database. Would the second job fail to start because there is an existing pipeline running?
v
Depends on the tap and target honestly. Generally they'd both just run and work fine
I had some issues with DBT when running tons of these at the same time, we're talking 2-5 at a time with ~300 unique jobs all with the same tap/target just selecting different streams
e
Yeah, if you're using the same
meltano run
command, you'll indeed see an error with a message like:
Copy code
Another '...' pipeline is already running
If that's not the desired behavior and you want to run multiple iterations of the pipeline, perhaps with different configurations, you should consider using the
--state-id-suffix
option to differentiate the two runs, or the
--force
to ignore the restriction and proceed with the pipeline: https://docs.meltano.com/reference/command-line-interface/#parameters-3