This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

Specification of Distributed attribute of Concurrent Rate Limit policy

Posted on 02-05-2018 11:17 PM
Not applicable
Reply posted on --/--/---- --:-- AM

Our team uses OPDK 4.17.01.

I don't understand the specification of the <Distributed> attribute of "Concurrent Rate Limit policy".

For example, consider two rmp installed in each of two DCs. (total of 4 rmp)

If the <Distributed> attribute is true and false, how does counter increase or decrease?

Regards.

0 1 146
Topic Labels
0 Likes
1 REPLY 1

Posted on --/--/---- --:-- AM
ivanzcai
New Member
Reply posted on --/--/---- --:-- AM

If the <Distributed> is set to false, the counter is per message processor. If it is set to true, it will be shared across the 4 message processors.

So if it's "false" you would have potentially have 4x as many concurrent throughput than it is set to "true" as each processor keeps its own counter. I have verified this on edge with 2 message processors, you might want to test it on your OPDK environment to verify this behaviour.

0 Likes