Recently, these messages have been noticed in both tempest
logs, as well as reported by downstream users syslog:
Set IPv4915d358d-2c5b-43b5-9862 is full, maxelem 65536 reached
So the default of 64K is not sufficient enough.
This change adds two config options to control both the number
of elements as well as the hashsize, since they should be
tuned together for best performance. Slightly different
formats were required for 'ipset create' and 'ipset restore'.
The default values for these are now set to 131072 (maxelem) and
2048 (hashsize), which is an increase over their typical default values
of 65536/1024 (respectively), in order to fix the errors seen in
the tempest tests.
Reviewed: https:/ /review. openstack. org/170328 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=b5b919a7a35 69ccb93c3d7d523 c1edfaeddb7cb9
Committed: https:/
Submitter: Jenkins
Branch: master
commit b5b919a7a3569cc b93c3d7d523c1ed faeddb7cb9
Author: Brian Haley <email address hidden>
Date: Thu Apr 2 21:11:06 2015 -0400
Add ipset element and hashsize tunables
Recently, these messages have been noticed in both tempest
logs, as well as reported by downstream users syslog:
Set IPv4915d358d- 2c5b-43b5- 9862 is full, maxelem 65536 reached
So the default of 64K is not sufficient enough.
This change adds two config options to control both the number
of elements as well as the hashsize, since they should be
tuned together for best performance. Slightly different
formats were required for 'ipset create' and 'ipset restore'.
The default values for these are now set to 131072 (maxelem) and
2048 (hashsize), which is an increase over their typical default values
of 65536/1024 (respectively), in order to fix the errors seen in
the tempest tests.
DocImpact
Change-Id: Ic0b5b38a840e73 7dc6be938230f40 52974c8620f
Closes-bug: #1439817