Hey, we're having a weird issue with airbyte `0.40...
# replication-troubleshooting
e
Hey, we're having a weird issue with airbyte
0.40.18
- bootloader keeps upgrading
mongodb-v2
connector to the latest version on each deployment (even though, we want to only increase sync workers for example). Which overloads our database when syncing a couple collections. Other connectors are fine. Is this expected behavior? Why? We're deploying via helm.
My mistake, other connectors also get upgraded. It's a real pain at the moment, how can we prevent it?
u
Hello Emilja Dankeviciute, it's been a while without an update from us. Are you still having problems or did you find a solution?
e
Hello, the problem is still prevalent. If we need to redeploy airbyte (using helm) for whatever reason, bootloader runs migrations and upgrades all the connectors.
Wouldn't be that much of a problem, but a couple of them have bugs that we need to avoid for now. And it also introduces some overhead for testing everything.
a
@Saj Dider (Airbyte) Wer’e currently using the newest airbyte chart and application versions and issue still persists? Are there any options to prevent bootloader from auto upgrading connector versions?