-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
zrepl pull job fails after restarting service, also failures not shown in prometheus #757
Comments
deajan
changed the title
zrepl pull job after restarting service, also failures not shown in prometheus
zrepl pull job fails after restarting service, also failures not shown in prometheus
Oct 23, 2023
Well I've roamed the issues and found that mounting the replicas and doing a single My two cents:
|
This was referenced Dec 12, 2023
Any thoughts on this ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
Playing around with zrepl 0.6.1 on two RHEL 9 systems.
I've setup a source job that get's pulled via TCP transport.
So far so good, I had to stop zrepl on the puller side after some hours (via systemctl stop zrepl).
Now, when I started zrepl again, I get lots of errors:
On source side, I just got a pretty normal error when I shut down the puller side zrepl:
On the puller side, I have lots and lots of errors since:
As a side note, I've setup prometheus to monitor zrepl, and the dashboard doesn't show any errors, which IMO is quite alarming:
Relevant configuration:
Source side
/etc/zrepl/zrepl.yml
:Puller side
/etc/zrepl/zrepl.yml
:I'm fairly new to zrepl, so there might be something I didn't see. But so far, just restarting the service made all replications fail, which terrifies me. Any suggestions ?
Thanks.
The text was updated successfully, but these errors were encountered: