-
Notifications
You must be signed in to change notification settings - Fork 183
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
Very noisy logging using gossip strategy #16
Comments
It's definitely not expected, it should only be logging that if a connection is lost then re-established, this looks like it's just logging every time. I'll push a fix. |
- Provide a default implementation using `:erlang.nodes([:connected])` - Deprecated `connect_nodes/3` and `disconnect_nodes/3` - Add `connect_nodes/4` and `disconnect_nodes/4` - Use new `list_nodes` option to do differencing and only log connects/disconnects when it's a new event as some strategies can be rather noisy without this (e.g. the gossip implementation) See #16
I just pushed a new minor release, |
Awesome! Thanks for the quick response!
…On Thu, May 4, 2017, 5:00 PM Paul Schoenfelder ***@***.***> wrote:
I just pushed a new minor release, 2.1.0 which addresses this by
requiring strategies to implement a list_nodes function. The default
strategies will all cover this for you, so you should just be able to
upgrade and be good to go!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANh_elIuRiqGWEhSbvl46Wf1ZrsLYBEks5r2makgaJpZM4NROWX>
.
|
Sorry to bug; will you be pushing it to hex soon? :) |
Done! |
Is this expected?
It logs output at least once a second, sometimes more. This seems a bit overly chatty to me, and would blow up our centralized logging service...
The text was updated successfully, but these errors were encountered: