Skip to content

Work around for the issue with close_wait and connection refused #419

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

Work around for the issue with close_wait and connection refused #419

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions jobs/rep/templates/set-rep-kernel-params.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,10 @@ echo 1 > /proc/sys/net/ipv4/tcp_tw_reuse
# Default value is 65536. We set it to a larger number to avoid running out of connections.
echo 262144 > /proc/sys/net/netfilter/nf_conntrack_max

# Default value is 60 (seconds). We set it to a larger number to avoid connection issues with remote endpoints or
# firewalls which keep sessions for half-closed connections for longer than 1 minute.
echo 900 > /proc/sys/net/netfilter/nf_conntrack_tcp_timeout_close_wait

Copy link
Author

@giner giner Mar 7, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nf_conntrack_max and nf_conntrack_tcp_timeout_close_wait should probably be exposed btw

echo 2147483647 > /proc/sys/fs/inotify/max_user_watches
echo 2147483647 > /proc/sys/fs/inotify/max_user_instances
echo 2147483647 > /proc/sys/fs/inotify/max_queued_events
Expand Down