/graylog2-server

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

Yellow status when journal is almost full #1100

Closed
pdepaepe opened this Issue Apr 8, 2015 · 2 comments

Comments

Assignees

@joschi joschi

Labels
feature
Projects
None yet
Milestone
  2.1.0
5 participants
@pdepaepe @dennusb @eorochena @bernd @joschi
@pdepaepe

pdepaepe commented Apr 8, 2015

Hello,

May you please consider to cast a yellow status on /system/lbstatus/ when journal is almost full (~90%)?

Thanks.
@dennusb

This comment has been minimized.

Sign in to view

dennusb commented Apr 9, 2015

+1
1 similar comment
@eorochena

This comment has been minimized.

Sign in to view

eorochena commented Apr 18, 2015

+1

@bernd bernd added the feature label Aug 6, 2015

@mikkolehtisalo mikkolehtisalo referenced this issue Mar 20, 2016

Closed

THROTTLED status when journal utilization is over threshold #1952

joschi added a commit that referenced this issue May 31, 2016

@joschi
Throttle LB status if journal utilization is too high 
This change set adds the load balancer status "THROTTLED", represented by HTTP status 429 (Too many requests).

The load balancer status will be changed to THROTTLED (HTTP 429) if the journal utilization exceeds a configured
threshold, see `lb_throttle_threshold_percentage` setting, and will be changed to ALIVE (HTTP 200) if the utilization
is lower again.

Originally written by Mikko Lehtisalo (https://github.com/mikkolehtisalo)

Closes #1100
Refs #1952
Loading status checks…
d75dbdf

@joschi joschi referenced this issue May 31, 2016

Merged

Throttle LB status if journal utilization is too high #2312

@joschi joschi added this to the 2.1.0 milestone May 31, 2016

@joschi joschi self-assigned this May 31, 2016

joschi added a commit that referenced this issue May 31, 2016

@joschi
Throttle LB status if journal utilization is too high 
This change set adds the load balancer status "THROTTLED", represented by HTTP status 429 (Too many requests).

The load balancer status will be changed to THROTTLED (HTTP 429) if the journal utilization exceeds a configured
threshold, see `lb_throttle_threshold_percentage` setting, and will be changed to ALIVE (HTTP 200) if the utilization
is lower again.

Originally written by Mikko Lehtisalo (https://github.com/mikkolehtisalo)

Closes #1100
Refs #1952
Loading status checks…
b3022e4

joschi added a commit that referenced this issue Jun 7, 2016

@joschi
Throttle LB status if journal utilization is too high 
This change set adds the load balancer status "THROTTLED", represented by HTTP status 429 (Too many requests).

The load balancer status will be changed to THROTTLED (HTTP 429) if the journal utilization exceeds a configured
threshold, see `lb_throttle_threshold_percentage` setting, and will be changed to ALIVE (HTTP 200) if the utilization
is lower again.

Originally written by Mikko Lehtisalo (https://github.com/mikkolehtisalo)

Closes #1100
Refs #1952
Loading status checks…
a886bd1

@dennisoelkers dennisoelkers closed this in #2312 Jun 7, 2016

dennisoelkers added a commit that referenced this issue Jun 7, 2016

@joschi @dennisoelkers
Throttle LB status if journal utilization is too high (#2312) 
This change set adds the load balancer status "THROTTLED", represented by HTTP status 429 (Too many requests).

The load balancer status will be changed to THROTTLED (HTTP 429) if the journal utilization exceeds a configured
threshold, see `lb_throttle_threshold_percentage` setting, and will be changed to ALIVE (HTTP 200) if the utilization
is lower again.

Originally written by Mikko Lehtisalo (https://github.com/mikkolehtisalo)

Closes #1100
Refs #1952
Loading status checks…
83fabe8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment