What will be the behavior of subscription and notifications in the Orion load balancing scenario?

Based on this answer on how to scale the Orion Context Broker with load balancing https://stackoverflow.com/questions/1607322/ ... what should be the behavior of the subscription as well as the notifications?

Witch server should it come out? What is a workflow?

Could this cause some disturbe or cloned subscriptions?

+1
source share
1 answer

Consider various cases, depending on the use of the subscription cache. Let's consider two Orion nodes (A and B) without loss of generality, both using the same instance of MongoDB.

(.. -noCache )

(, node A). node A ( node A) . , node B , . , -subCacheIval.

( /, ). , node ( ), :

  • node B (.. -subCacheIval ). , node B , .

  • node B (.. -subCacheIval ). node B , .

  • node A, , . node A , , . , .

: -subCacheIval , CB, . , -subCacheIval . Orion.

, Orion:

, Orion -. CB , Orion node. node , ( ), , node , 100% .

, , , , Orion.

(.. -noCache)

. , , node ( A B) , . , , A B , , .

, ( ) ( ), .

, , , , .

+2

Source: https://habr.com/ru/post/1607326/


All Articles