Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1082443

Summary:	[Doc] [RFE][neutron]: Multiple RPC workers
Product:	Red Hat OpenStack	Reporter:	Martin Lopes <mlopes>
Component:	doc-Release_Notes	Assignee:	Martin Lopes <mlopes>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Don Domingo <ddomingo>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 7)	CC:	chrisw, ddomingo, lpeer, markmc, mnewby, nyechiel, rhos-integ, rlandman, yeylon
Target Milestone:	Upstream M3	Keywords:	Documentation, FutureFeature, Triaged
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/multiple-rpc-workers
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	Changing the neutron.conf rpc_workers option's default value of '0' can cause the Networking service to fail.	Story Points:	---
Clone Of:	1063583	Environment:
Last Closed:	2015-02-15 23:43:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1063583
Bug Blocks:

Comment 5 Maru Newby 2014-04-11 14:49:35 UTC

Martin: Unlike RHOS 4.0, which only supported api_workers, 5.0 will support a second configuration option named rpc_workers.  The defaults for both options in 5.0 is 0 pending the testing necessary to validate multi-process behavior.  If/when multi-process behavior proves stable, an operator will be able to configure the Neutron service with both options set to 1 and then increment the options independently when bottlenecks are identified.

Since each worker represents a process, the sum of api_workers and rpc_workers should not exceed the available number of cores on the host.

Comment 7 Maru Newby 2014-06-03 05:35:21 UTC

Setting api_workers and rpc_workers in RHOS 5.0 to non-zero values breaks the Neutron service rather than increasing its scalability.  The documentation will need to discourage changing the values for these configuration settings until further notice.

I've attached a link to an upstream patch that demonstrates the failure mode in question.

Comment 9 Maru Newby 2014-06-04 01:51:20 UTC

I think it would make sense to remove the section in question or limit it to a warning not to change the api_workers and rpc_workers options.  The metadata_workers option does not impact the scalability of the Neutron service, only that of the metadata agent (as per the following bug):

https://bugs.launchpad.net/neutron/+bug/1274536

Comment 10 Martin Lopes 2014-06-04 02:04:17 UTC

Thanks Maru, 

I've removed the section from the book spec, and flagged this BZ for the Release  Notes as a known issue.

Comment 11 Martin Lopes 2014-06-18 00:30:09 UTC

Mention of the api_workers known issue is noted in BZ#1056405

Comment 13 Martin Lopes 2014-10-19 23:09:19 UTC

Setting to verified.