chorus icon indicating copy to clipboard operation
chorus copied to clipboard

Syncing at startup

Open AndrewOga opened this issue 1 year ago • 4 comments

Hi Please tell me, when I launch the standalone version, synchronization starts immediately. When I run in the k8s, the synchronization only works on new objects. What do I need to fix, which configuration file is responsible for the initial synchronization?

AndrewOga avatar Dec 04 '24 05:12 AndrewOga

Hi, this behaviour is controlled by storage.createReplication worker config paramenter. The default values is false. After setting it to true, chorus worker will list all existing buckets for all users from main storage in config and will start sync to all other storages.

arttor avatar Dec 09 '24 13:12 arttor

Hi everyone! I have a similar troubles.

storage: createReplication: true

When I start worker service (with/without proxy), bucket differense does not sync. And chorctl show defference but I couldn't understand how to command it to synchronize the data. Trying to solve the problem for a few days.

vncviewer_Oegalp5mqc

gardencash avatar Dec 13 '24 08:12 gardencash

can it be related to #53 bug? There is a problem with sync if replication was removed and added again.

arttor avatar Dec 17 '24 08:12 arttor

Hi. Yes my case is similar to #53 bug, but it occurs when running worker and proxy separately. At the same time it works correctly in standalone mode in my case.

Thank you for your answer and I apologize for my late reply! Got distracted from the task for a couple weeks, will try again.

gardencash avatar Dec 30 '24 04:12 gardencash