scheduler should ignore earlier time service capabilities
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
haixin |
Bug Description
Description
===========
if rabbitmq is too much pressure or blockage.scheduler will not received service capabilities,
but once the message queue(rabbitmq) returns to normal, scheduler willreceived many service capabilities, these service capabilities are acquired by manila share at different times, so
the timestamp shoud added at share manage layer(before rpc), but not scheduler layer(after rpc)
once scheduler get an newer service capabilities, there is no need to update an earlier service capabilities.
Steps to reproduce
==================
In large-scale environments, or in highly concurrent
situations, rabbitmq is too much pressure or blockage,
this is inevitable.
Expected result
===============
ignore earlier service capabilities.
Actual result
=============
update all the service capabilities.
Changed in manila: | |
assignee: | nobody → haixin (haixin77) |
description: | updated |
Changed in manila: | |
milestone: | wallaby-2 → wallaby-3 |
status: | New → In Progress |
tags: | added: wallaby-rc-bugsquash |
Changed in manila: | |
milestone: | wallaby-3 → wallaby-rc1 |
tags: |
added: wallaby-backport-potential removed: wallaby-rc-bugsquash |
tags: |
added: wallaby-rc-bugsquash removed: wallaby-backport-potential |
Changed in manila: | |
status: | In Progress → Fix Released |
https:/ /review. opendev. org/c/openstack /manila/ +/768137