| 2020-12-22 02:28:24 |
haixin |
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, this is inevitable.
Expected result
===============
ignore earlier service capabilities.
Actual result
=============
update all the service capabilities. |
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. |
|
