Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Wrap a number of things that run in the background #3604

Merged
merged 3 commits into from
Jul 25, 2018

Conversation

richvdh
Copy link
Member

@richvdh richvdh commented Jul 25, 2018

This will reduce the number of "Starting db connection from sentinel context"
warnings, and will help with our metrics.

richvdh added 3 commits July 25, 2018 09:41
This will reduce the number of "Starting db connection from sentinel context"
warnings, and will help with our metrics.
on_notifier_poke no longer runs synchonously, so we have to do a different hack
to make sure that the replication data has been sent. Let's actually listen for
its arrival.
@richvdh richvdh requested a review from a team July 25, 2018 10:09
@richvdh richvdh merged commit 1bfb5be into develop Jul 25, 2018
richvdh added a commit that referenced this pull request Jul 26, 2018
It turns out that looping_call does check the deferred returned by its
callback, and (at least in the case of client_ips), we were relying on this,
and I broke it in #3604.

Update run_as_background_process to return the deferred, and make sure we
return it to clock.looping_call.
@richvdh richvdh deleted the rav/background_process_fixes branch July 26, 2018 11:54
richvdh added a commit that referenced this pull request Jul 26, 2018
Fix some looping_call calls which were broken in #3604
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants