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.

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

redpanda: expose tcp listen backlog #1910

Closed
emaxerrno opened this issue Jul 27, 2021 · 3 comments · Fixed by #1952
Closed

redpanda: expose tcp listen backlog #1910

emaxerrno opened this issue Jul 27, 2021 · 3 comments · Fixed by #1952
Assignees

Comments

@emaxerrno
Copy link
Contributor

https://github.com/scylladb/seastar/blob/4d5c3345331c1dd5e1781bd117b1ae643bc69cf1/include/seastar/net/api.hh#L333

jcsp added a commit to jcsp/redpanda that referenced this issue Aug 2, 2021
Fixes: redpanda-data#1910

Signed-off-by: John Spray <jcs@vectorized.io>
@jcsp
Copy link
Contributor

jcsp commented Aug 2, 2021

#1952

@jcsp
Copy link
Contributor

jcsp commented Aug 2, 2021

@senior7515 do you have any shareable context on how this came up for real users? Current release note on PR is a bit generic (ask people to refer to the underlying linux setting), but a "when RedPanda has X problem adjust Y setting" would really pop.

@emaxerrno
Copy link
Contributor Author

@jcsp - click on the private repo link of support #86 for customer context.

jcsp added a commit to jcsp/redpanda that referenced this issue Aug 3, 2021
Fixes: redpanda-data#1910

Signed-off-by: John Spray <jcs@vectorized.io>
jcsp added a commit to jcsp/redpanda that referenced this issue Aug 4, 2021
Fixes: redpanda-data#1910

Signed-off-by: John Spray <jcs@vectorized.io>
(cherry picked from commit ec5018c)
jcsp added a commit that referenced this issue Aug 6, 2021
Fixes: #1910

Signed-off-by: John Spray <jcs@vectorized.io>
(cherry picked from commit ec5018c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants