Skip to content

Document how to use the SYN eater iptables change to protect router reloads #1987

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

Merged
merged 1 commit into from
Jul 1, 2016

Conversation

knobunc
Copy link
Contributor

@knobunc knobunc commented May 3, 2016

This documents the steps needed to enable the SYN eater to prevent
connection drops when the haproxy used by the router reloads. In
order to work its magic it needs to use iptables, which entails all
sorts of fussing to get the router user to have the needed
permissions, and to patch the deployment config to make it request a
privileged container.

reload window. However, doing so means that the router needs to run
with elevated privilege so that it can manipulate *_iptables_* on the
host. It also means that connections that happen during the reload
are temporarily ignorred and will have to retransmit their connection
Copy link

Choose a reason for hiding this comment

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

"ignored"

@knobunc
Copy link
Contributor Author

knobunc commented May 6, 2016

@adellape PTAL

@@ -609,6 +609,58 @@ $ echo " router metrics at: http://<ip>:9090/consoles/haproxy.html "
====


=== Preventing Connection Failures During Restarts ===
Copy link
Contributor

Choose a reason for hiding this comment

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

You can remove the concluding === in the heading (we only need the ones in the beginning)

@ahardin-rh
Copy link
Contributor

@knobunc just a few minor comments. Looks like we also need a rebase 🙇

Also, is this for 3.3 (future release)? Thanks!

…eloads

This documents the steps needed to enable the SYN eater to prevent
connection drops when the haproxy used by the router reloads.  In
order to work its magic it needs to use iptables, which entails all
sorts of fussing to get the router user to have the needed
permissions, and to patch the deployment config to make it request a
privileged container.
@knobunc
Copy link
Contributor Author

knobunc commented Jul 1, 2016

@ahardin-rh Thanks for the review. This is for 3.2.

@ahardin-rh
Copy link
Contributor

@knobunc Thanks!

@ahardin-rh ahardin-rh merged commit 9986591 into openshift:master Jul 1, 2016
@ahardin-rh
Copy link
Contributor

[rev_history]
|xref:../install_config/install/deploy_router.adoc#install-config-install-deploy-router[Deploying a Router]
|Added a Preventing Connection Failures During Restarts section.
%

@adellape adellape modified the milestones: Next Release, Staging Jul 11, 2016
@adellape adellape modified the milestones: Staging, Next Release Jul 11, 2016
@@ -1030,6 +1030,57 @@ $ echo " router metrics at: http://<ip>:9090/consoles/haproxy.html "
====


=== Preventing Connection Failures During Restarts
Copy link
Contributor

Choose a reason for hiding this comment

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

Add unique ID.

@adellape adellape modified the milestones: Next Release, Staging Jul 11, 2016
@adellape
Copy link
Contributor

@ahardin-rh Made a few comments to you for a follow-up PR. Moving this back to Next Release w/ a to_followup label for now.

@ahardin-rh
Copy link
Contributor

@adellape Thanks! Good catches. Created a follow-up PR.

@knobunc knobunc deleted the syn-eater branch July 12, 2016 13:34
@bfallonf bfallonf modified the milestones: Next Release, Staging Jul 26, 2016
@vikram-redhat vikram-redhat modified the milestones: Staging, Staging - Picked, Published - 07/27/16 Jul 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants