Policies are a really important feature of Blacksmith. They have the effect of adding a reliability layer atop an integration, in a durable and scalable way. Misconfigured policies can lead to an unreliable integration.
policies configuration for an integration shall look like this:
integrations: sql: - name: "my-sql-store" driver: "postgresql" policies: operation: timeout: 45 migration: timeout: 45 load: timeout: 15 initialInterval: 30 backoffCoefficient: 1.75 maximumInterval: 15 maximumAttempts: 60
migration policies are only available for
timeout(in seconds) is the maximum time of a single database operation's execution attempt. This timeout should be as short as the longest possible execution of the operation.
timeout(in seconds) is the maximum time of a single database migration's execution attempt. This timeout should be as short as the longest possible execution of the migration.
timeout(in seconds) is the maximum time of a single data Load execution attempt. This timeout should be as short as the longest possible execution of the Load.
initialInterval(in seconds) is the backoff interval for the first retry.
backoffCoefficientis the coefficient used to calculate the next retry backoff interval. The next retry interval is previous interval multiplied by this coefficient. Must be
maximumInterval(in seconds) is the maximum backoff interval between retries. Exponential backoff leads to interval increase. This value is the cap of the interval. If not interval is provided, the value is
100 * initialInterval.
maximumAttemptsis the maximum number of attempts of retries. When exceeded the retries stop even if not expired yet.
If you notice something we've missed or could be improved on, please follow this link and submit a pull request to the repository. Once we merge it, the changes will be reflected on the website the next time it is deployed.
Thank you for your contributions!