[
https://issues.apache.org/jira/browse/TS-4909?focusedWorklogId=30199&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-30199
]
ASF GitHub Bot logged work on TS-4909:
--------------------------------------
Author: ASF GitHub Bot
Created on: 05/Oct/16 20:00
Start Date: 05/Oct/16 20:00
Worklog Time Spent: 10m
Work Description: Github user jpeach commented on a diff in the pull
request:
https://github.com/apache/trafficserver/pull/1063#discussion_r82057095
--- Diff: proxy/Main.cc ---
@@ -346,6 +346,54 @@ class DiagsLogContinuation : public Continuation
}
};
+class MemoryLimit : public Continuation
+{
+public:
+ MemoryLimit() : Continuation(new_ProxyMutex()), _memory_limit(0) {
SET_HANDLER(&MemoryLimit::periodic); }
+ ~MemoryLimit() { mutex = NULL; }
+ int
+ periodic(int event, Event *e)
+ {
+ if (event == EVENT_IMMEDIATE) {
+ // rescheduled from periodic to immediate event
+ // this is the indication to terminate
+ delete this;
+ return EVENT_DONE;
+ }
+ if (_memory_limit == 0) {
+ // first time it has been run
+ _memory_limit =
REC_ConfigReadInteger("proxy.config.memory.max_usage");
--- End diff --
Can you re-read this on each check so that it is a dynamic configuration?
Issue Time Tracking
-------------------
Worklog Id: (was: 30199)
Time Spent: 40m (was: 0.5h)
> Throttling based on resident memory usage
> -----------------------------------------
>
> Key: TS-4909
> URL: https://issues.apache.org/jira/browse/TS-4909
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core
> Reporter: Bryan Call
> Fix For: 7.1.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Add a feature to stop accepting connections if the resident memory is over a
> certain limit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
