[NETVIRT-3] Optimize rule updates during deletion of a LB member Created: 03/Sep/14 Updated: 09/Mar/18 Resolved: 15/Nov/17 |
|
| Status: | Verified |
| Project: | netvirt |
| Component/s: | None |
| Affects Version/s: | Beryllium |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Srini Seetharaman | Assignee: | Madhu Mohan Nelemane |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Windows |
||
| Description |
|
Currently, delete of a LB member leads to reprogramming the full LB instance on all nodes (Because of the way multipath hash values are used as an index in picking the member). Optimization is essential. This bug is slightly related to |