Skip to content
This repository has been archived by the owner on Nov 17, 2020. It is now read-only.

SASL log grows excessively when federation links repeatedly fail to connect #15

Closed
michaelklishin opened this issue Aug 13, 2015 · 3 comments
Closed

SASL log grows excessively when federation links repeatedly fail to connect #15

michaelklishin opened this issue Aug 13, 2015 · 3 comments
Assignees
@michaelklishin
Labels
bug
Milestone
3.5.5

Comments

@michaelklishin
Copy link
Member

E.g. due to an incorrectly specified port.

This is not very ops-friendly and makes the SASL log grow very fast, very quickly. Effectively
the same thing was reported on the list recently.
@michaelklishin michaelklishin self-assigned this Aug 13, 2015
@michaelklishin michaelklishin added this to the 3.5.5 milestone Aug 13, 2015
@michaelklishin michaelklishin changed the title No log entries in regular log when federation links fail to connect SASL log grows excessively when federation links fail to connect Aug 14, 2015
@michaelklishin
Copy link
Member Author

Clarifying: we do log errors in the regular log but the SASL one still grows rapidly due to child_restarted reports.

@michaelklishin
Copy link
Member Author

Considering various options I think the most straightforward one is to change reconnection delay default from 1 second to 5.

@michaelklishin
Copy link
Member Author

Pull requests:

@michaelklishin michaelklishin changed the title SASL log grows excessively when federation links fail to connect SASL log grows excessively when federation links repeatedly fail to connect Aug 14, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@michaelklishin michaelklishin

Labels
bug
Projects
None yet
Milestone
3.5.5
Development

No branches or pull requests
1 participant
@michaelklishin