Configure the ConfigSync mode
sync
configuration in the fusion-config-sync
section of the Helm chart configuration, as shown below.system_blobs
collection) and not Zookeeper, consequently there is no ZK watch event fired when a blob has been added, deleted, or updated.
Consequently, the publisher runs a background task that queries the blob store for changes every 20 seconds (configurable via cfg.pub.checkForBlobUpdatesEveryMs
).
If blob changes are detected, the publisher stores the blob in the local repo and normally pushes it to GitHub.
*_query_rewrite
and *_query_rewrite_staging
collections) and not Zookeeper, consequently there is no ZK watch event fired when a rule has been added, deleted, or updated.
Consequently, the publisher runs a background task that queries the rule store for changes every 300 seconds (configurable via cfg.pub.checkForRuleUpdatesEveryMs
).
Rules are stored in the local repo as JSON lines files and normally pushed to GitHub.
*_query_rewrite
and *_query_rewrite_staging
collections.cfg.sync.syncEvery
); a PUSH operation is typically slow and can take several seconds to complete.
PUSH is synchronized so that only one thread is sending updates to GitHub at a time.