Regarding nopreempt and the recent related patches
Assaf Muller <[email protected]>
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello everyone, I'm an OpenStack Neutron dev working on a high availability solution for virtual routers which uses keepalived internally. These two patches that were merged for 1.2.14: e18370cb165d21db954c08ddbce1b39d97858012 13693a2d1b834c749394ef0bdee6afe9eb1fad2d Changed the behavior of nopreempt and I'm seeing a severe regression. Short story: Why does keepalived go to standby when it receives a message with a lower priority? Long story: I opened a RHBZ (I probably should have sent a message here first): https://bugzilla.redhat.com/show_bug.cgi?id=1202584 That has a lot more context and information, including the keepalived.conf we spit out in Neutron code. It also has exerts from syslog that demonstrate the issue. If any more context or information is needed please let me know. I'm also available as 'amuller' on Freenode (keepalived channel as well as openstack-neutron). Thank you, Assaf Muller, Cloud Networking Engineer Red Hat ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/