yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #46773
[Bug 1548633] [NEW] One of the Network node out of five is over utilized (has more dhcp namespaces) than the others.
Public bug reported:
I have 5 Network nodes (NN's) on my setup each with 32 GB RAM. All have
same configuration (Created from the same ubuntu template).
I am running a scale scenario under which I am creating 4K networks each
with one subnet using rally with 100 concurrency. Ideally all the
network namespaces should have been equally divided among all the 5 NN’s
but one NN is over utilized which in turn creates resource crunch and
future requests start failing on it.
The number of namespace on the faulty NN is 1175 while other NN's have
650 to 750 namespaces. I ran the scenario twice and both the times the
result was same.
Please note if I create networks one by one without any concurrency the
namespace distribution is even and the problem is not seen.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1548633
Title:
One of the Network node out of five is over utilized (has more dhcp
namespaces) than the others.
Status in neutron:
New
Bug description:
I have 5 Network nodes (NN's) on my setup each with 32 GB RAM. All
have same configuration (Created from the same ubuntu template).
I am running a scale scenario under which I am creating 4K networks
each with one subnet using rally with 100 concurrency. Ideally all the
network namespaces should have been equally divided among all the 5
NN’s but one NN is over utilized which in turn creates resource crunch
and future requests start failing on it.
The number of namespace on the faulty NN is 1175 while other NN's have
650 to 750 namespaces. I ran the scenario twice and both the times the
result was same.
Please note if I create networks one by one without any concurrency
the namespace distribution is even and the problem is not seen.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1548633/+subscriptions
Follow ups