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
[ZOOKEEPER-3146] Limit the maximum client connections per IP in NettyServerCnxnFactory #623
Conversation
43bef3a
to
bf70f5b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. kicking jenkins again.
@hanm looks like the Jenkins job is pending there since you triggered it 5 days ago, it doesn't likely will be run, can you trigger it again? |
The job I triggered on Sep 14 actually succeeded. It's the github integration that's broken. I suspect it's some permission issues around apache github mirror, I'll follow up with this as it's annoying. I think this issue is good to land. If no more comments, I'll commit it on Friday. |
retest this please |
Refer to this link for build results (access rights to CI server needed): |
retest this please |
Refer to this link for build results (access rights to CI server needed): |
retest this please |
Refer to this link for build results (access rights to CI server needed): |
Hey @lvfangmin ,
Thanks. |
the latest jenkins failure is a known flaky test. merging this in.. |
…erverCnxnFactory Add similar max cnxn per ip throttling logic to Netty implementation. Author: Fangmin Lyu <allenlyu@fb.com> Reviewers: hanm@apache.org Closes apache#623 from lvfangmin/ZOOKEEPER-3146
Add similar max cnxn per ip throttling logic to Netty implementation.