-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
OAuth: resync RemoteRepository
weekly for active users
#9410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Trigger a daily task to compare user's last login isoweekday with today's isoweekday for all active users. If they matches, we resync the `RemoteRepository` for this user. This logic is the same as "resync `RemoteRepository` once a week per each user". We consider active users those that have logged in at least once in the last 90 days. Related: #8229 Related: #9409
1454e27
to
d76f145
Compare
Note that this is about 2k users to resync per day, which I don't think it's terrible, but it's definitely a lot more than what we are doing currently:
This may stress our There are some improvements to do here too:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a good approach, but I'd much rather tie up 1 celery process and take a long time vs. totally block celery.
Co-authored-by: Eric Holscher <[email protected]>
…mitos/resync-remoterepository-weekly
Weekly resync will use only one Celery process to avoid backing up our queue.
00dbbbd
to
d26eb93
Compare
There is an unrelated problem with the docs,
|
Trigger a daily task to compare user's last login isoweekday with today's
isoweekday for all active users. If they matches, we resync the
RemoteRepository
for this user.This logic is the same as "resync
RemoteRepository
once a week per each user".We consider active users those that have logged in at least once in the last 90
days.
Related: #8229
Related: #9409