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.

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

Set OVS max revalidator delay to 200ms #1584

Merged
merged 1 commit into from
Nov 20, 2020
Merged

Set OVS max revalidator delay to 200ms #1584

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
5 changes: 5 additions & 0 deletions build/images/scripts/start_ovs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,11 @@ function start_ovs {
ovs-vsctl --no-wait set open_vswitch . other_config:flow-restore-wait="true"
log_info $CONTAINER_NAME "ovs-vswitchd set hw-offload to $offload"
ovs-vsctl --no-wait set open_vswitch . other_config:hw-offload=$offload
# Set max revalidator delay to 200ms to ensure that learned flows are added to the
# datapath flow cache faster, so that Service SessionAffinity "takes effect"
# faster in AntreaProxy. It should not have a significant impact on performance.
# See https://github.com/vmware-tanzu/antrea/issues/1583
ovs-vsctl --no-wait set open_vswitch . other_config:max-revalidator=200
/usr/share/openvswitch/scripts/ovs-ctl --no-ovsdb-server --system-id=random start --db-file=$OVS_DB_FILE
log_info $CONTAINER_NAME "Started ovs-vswitchd"
fi
Expand Down