Bug 1482773

Summary:	Low ARP Tables Limit Causes multiple component failure when going above 1000 content host registrations
Product:	Red Hat Satellite	Reporter:	sbadhwar
Component:	Networking	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	psuriset, sbadhwar
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-04 17:46:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description sbadhwar 2017-08-18 05:41:13 UTC

Description of problem:

Currently, when we try to register more than 1000 hosts, we start to experience network timeouts, which indeed causes pulp scheduler and resource manager not being able to start properly and hence causes new registrations to fail.

The same happens with services like candlepin, which also shows network unreachable.

On some investigation, there were some warnings recorded by systemd journal stating:

net_ratelimit: 300 callbacks suppressed

These problems seem to resolve when we extend the ARP table by setting up the following values in sysctl.conf

net.ipv4.neigh.default.gc_thresh1 = 8192
net.ipv4.neigh.default.gc_thresh2 = 16384
net.ipv4.neigh.default.gc_thresh3 = 32768

Can we by default extend the ARP table during the Satellite install? 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Bryan Kearney 2018-09-04 17:46:36 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.