hot unregistration in crossbar load distribution scenario

#1

In crossbar you can use shared registrations to distribute calls to multiple workers.( docs )
Basically that’s registering more than one worker under one URI.

From the AutobahnPython documentation I can not see if unregistration of a worker happens “safely”.

If you unregister a worker, does it finish it’s current task, return the result and only then unregister?

Do you get a defered notifying you when unregistration succeded?

Can you also “force unregister” a registration to discard the current task and unregister immediately?

(Actually that question is not related to shared registrations. It is just a use case where this requirement is likely to occure)

0 Likes

#2

When a callee unregisters, it won’t receive new calls, but outstanding calls (calls on the fly) are still processed.

Unregister returns an empty result on success.

“Force unregister” … not sure what that means. You can of course fail the current call (raise an exception) and then unregister too.

···

Am Dienstag, 26. Januar 2016 11:59:01 UTC+1 schrieb Marko Petzold:

In crossbar you can use shared registrations to distribute calls to multiple workers.( docs )
Basically that’s registering more than one worker under one URI.

From the AutobahnPython documentation I can not see if unregistration of a worker happens “safely”.

If you unregister a worker, does it finish it’s current task, return the result and only then unregister?

Do you get a defered notifying you when unregistration succeded?

Can you also “force unregister” a registration to discard the current task and unregister immediately?

(Actually that question is not related to shared registrations. It is just a use case where this requirement is likely to occure)

0 Likes