Skip to content
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

Document the replay mechanism and how to stop it #455

Open
pypingou opened this issue Aug 2, 2017 · 4 comments
Open

Document the replay mechanism and how to stop it #455

pypingou opened this issue Aug 2, 2017 · 4 comments
Labels

Comments

@pypingou
Copy link
Member

pypingou commented Aug 2, 2017

Fedmsg-hub stores on disk in /var/run/fedmsg/status/fedmsg-hub/* the last fedmsg message received by every consumer it is running. This allows the consumer to go and query datagrepper for any newer messages upon restart.

To stop this behavior (just for one restart), simply nuke this file, fedmsg-hub will not know how long it has to go back and ask datagrepper and thus will not do it.

@ralphbean
Copy link
Contributor

Note that you have to 1) stop the hub, 2) rm the file, 3) restart the hub.

If you just nuke it and restart, it might write out another status file right after you nuked it.

@ralphbean
Copy link
Contributor

The code is here.

@cha-ku
Copy link
Contributor

cha-ku commented Oct 14, 2017

I'll take this up.

@jeremycline
Copy link
Member

@Chaiku great!

Just send in a PR - I can't assign the issue to users outside the Github organization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants