yahoo-eng-team team mailing list archive

[Zang MingJie <1261313@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Debian Neutron has set a cron entry to invoke neutron-netns-cleanup
every hour, in ordinary system, it works fine, but in our heavy stress
test environment, I found there are over 10 neutron-netns-cleanup
processes running.

Can we introduce a lock which can prevent spawning new instance when
there is already one running ?

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

  Debian Neutron has set a cron entry to invoke neutron-netns-cleanup
  every hour, in ordinary system, it works fine, but in our heavy stress
  test environment, I found there are over 10 neutron-netns-cleanup
- process running.
+ processes running.
  
  Can we introduce a lock which can prevent spawning new instance when
  there is already one running ?

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1261313

Title:
  prevent multiple neutron-netns-cleanup running simultaneously

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Debian Neutron has set a cron entry to invoke neutron-netns-cleanup
  every hour, in ordinary system, it works fine, but in our heavy stress
  test environment, I found there are over 10 neutron-netns-cleanup
  processes running.

  Can we introduce a lock which can prevent spawning new instance when
  there is already one running ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1261313/+subscriptions