Hello, if I already have a meltano job running and...
# troubleshooting
s
Hello, if I already have a meltano job running and then if I run another job (different stream but same JOB) with a
--force
flag, what will happen? I am running meltano commands as python subprocesses insided MageAI. I have notices that while Mage sometimes shows that the block execution is completed, I see that the table is not updated. This has started happening since I started running multiple meltano jobs at the same time, with
--force
flag
e
I see that the table is not updated.
which table is that?
s
the tables in the destination Say I have job
tap-A-to-target=B
and I am running it with one stream at a time (with a single python subprocess command per stream) I have --force flag in the command and all the mage python blocks (one stream - one python subprocess per block) are executed at the same time. In this case if I am triggered 5 such blocks, all will result in success, but not all the destinations would have updates (and I checked, there are newer records available at the source which were not loaded). I speculate that somehow the --force flag is killing a previous data load job that might be running
e
It shouldn't kill the process per-se, but it might affect the heartbeat that is used to monitor the job. Might be worth looking at the logs during that time-frame.
s
ok It's possible to run a job to sync multiple streams concurrently right? I just checked meltano logs, and although my Mage logs show me that the mage block was successfully run, but the meltano logs show me that the meltano job for that stream wasn't even triggered?