Changing MAX_SYNC_WORKERS value in Airbyte instance

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The user wants to change the value of MAX_SYNC_WORKERS in their Airbyte instance installed via abctl and is asking if they need to run ‘abctl uninstall’ and ‘abctl install’ or if there is a way to do it on the running instance.


Question

I would like to apply the change of MAX_SYNC_WORKERS on my Airbyte instance (installed via abctl)

  extraEnvs:
    - name: MAX_SYNC_WORKERS
      value: "2"```
Do I need to run through `abctl uninstall` and `abctl install` or there is some way to do it on running instance?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1725382244437599) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["max-sync-workers", "airbyte-instance", "abctl", "configuration-change"]
</sub>
2

abctl local install should work

Under the hood helm.InstallOrUpgradeChart is executed https://github.com/airbytehq/abctl/blob/29e37a48a4bfb6467db33339ff302ca9423814b0/internal/cmd/local/local/cmd.go#L742-L754|cmd.go#L742-L754

3

Thanks. I could say partially it worked as still some manual work was needed as I have to remove the ingress pod as it was not able to replace it for new one as the port was already in use

4

yeah, it happens from time to time
you could also pass --port XXXX to abctl local install , then in second execution remove it, to use default 8000