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.

Sign up for GitHub

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

Jump to bottom

automatic logging backoff during erchef crash loops #87

Open
ryancragun opened this issue Feb 10, 2015 · 3 comments
Open

automatic logging backoff during erchef crash loops #87

ryancragun opened this issue Feb 10, 2015 · 3 comments
Labels
Status: To be prioritized Indicates that product needs to prioritize this issue. Triage: Confirmed Indicates and issue has been confirmed as described. Type: Enhancement Adds new functionality.

Comments

@ryancragun
Copy link
Contributor

In the event that backend goes down on a busy Chef Server cluster we commonly see disk I/O on the FE's go through the roof due to bifrost/erchef/nginx logging. I don't know how feasible it is, but it'd be great if this could be detected and noise reduced.
@stevendanna
Copy link
Contributor

I love this idea. Feels like it should be a feature for lager.

@irvingpop
Copy link

https://github.com/basho/lager#overload-protection

@sdelano
Copy link
Contributor

sdelano commented May 27, 2015

Thanks @irvingpop - We should enable this across all of our apps the use lager.

@sdelano sdelano added this to the accepted-minor milestone May 27, 2015
@tas50 tas50 added Type: Enhancement Adds new functionality. and removed enhancement labels Jan 4, 2019
@PrajaktaPurohit PrajaktaPurohit added Status: To be prioritized Indicates that product needs to prioritize this issue. Triage: Confirmed Indicates and issue has been confirmed as described. labels Jul 24, 2020
@stevendanna stevendanna removed this from the accepted-minor milestone Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: To be prioritized Indicates that product needs to prioritize this issue. Triage: Confirmed Indicates and issue has been confirmed as described. Type: Enhancement Adds new functionality.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@ryancragun @sdelano @stevendanna @tas50 @irvingpop @PrajaktaPurohit