Manju Rajashekhar

from @jokea Can not reopen this issue, so I'm commenting here. This issue should be solved at the server side by rejecting any new connections when the max open files...

@bmatheny how do you handle this at tumblr?

@harishd one workaround is to increase the default file description limit. see http://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files/

@harishd you probably want twemproxy to be deployed as local proxy (see slide 4 here: https://speakerdeck.com/justinmares/twemproxy). Deploying it as local proxy has better fault tolerance semantics and doesn't end up...

@bmatheny You are right. The FD count is: x = (pool_count \* client_connections_per_pool) + (pool_count \* backends_per_pool \* server_connections) Usually we want to set the file descriptor limit to 2x...

@mthenw could you describe the scenario in detail that you are attempting to solve with a pubsub support in twemproxy

The last approach (scalable approach) proposed by @tejacques makes sense and might become a viable solution given the constraints of pub-sub. Anyone wants to take a stab at solving pub-sub...

would prefer _NC_EVENT_H_ renamed as NC_EVENT_H without the uuid as suggested in https://www.securecoding.cert.org/confluence/display/seccode/DCL37-C.+Do+not+declare+or+define+a+reserved+identifier#DCL37-C.Donotdeclareordefineareservedidentifier-NoncompliantCodeExample%28HeaderGuard%29

Questions: - Is this patch being actively used in production somewhere? -- I'm more likely to merge this to master if that is the case. - Would someone take ownership...

Working on this. Will merge this patch after I finish merging the config reload patch.