Warlock to Warlock communication #2

New issue

Closed

opened 2016-11-27 11:23:43 +00:00 by jamie · 8 comments

jamie commented

2016-11-27 11:23:43 +00:00

(Migrated from git.hazaar.io)

I need to get warlock working in a load-balanced multi-host environment. This should not be too hard and I see this working as follows.

Warlock connects to another host with a special connection type (similar to that admin connection)
All messages received on one warlock host are sent to all other connected warlocks.
All messages received by another warlock host are sent to all connected and subscribed clients.
All messages received by another warlock host are sent to all connected hosts except that which is connected.
If a duplicate message is received, it is ignored.

I need to get warlock working in a load-balanced multi-host environment. This should not be too hard and I see this working as follows. * Warlock connects to another host with a special connection type (similar to that admin connection) * All messages received on one warlock host are sent to all other connected warlocks. * All messages received by another warlock host are sent to all connected and subscribed clients. * All messages received by another warlock host are sent to all connected hosts except that which is connected. * If a duplicate message is received, it is ignored.

jamie commented

2017-03-30 02:57:56 +00:00

(Migrated from git.hazaar.io)

More thoughts on this:

Services: Each can be configured to run on one or more hosts. If only running on once host the hosts can attempt to decide amoungst them which one it will run on.
Delayed/Scheduled functions: These can also be allowed to run on multiple hosts. I think for these by default will only run on a single host. Again, the hosts will decide by quorum which one will run the code.

More thoughts on this: * Services: Each can be configured to run on one or more hosts. If only running on once host the hosts can attempt to decide amoungst them which one it will run on. * Delayed/Scheduled functions: These can also be allowed to run on multiple hosts. I think for these by default will only run on a single host. Again, the hosts will decide by quorum which one will run the code.

jamie commented

2017-04-01 00:02:42 +00:00

(Migrated from git.hazaar.io)

assigned to @jamie

jamie commented

2017-04-01 00:02:54 +00:00

(Migrated from git.hazaar.io)

added ~163 label

jamie commented

2017-04-01 00:04:38 +00:00

(Migrated from git.hazaar.io)

changed milestone to %1

jamie commented

2017-04-05 10:21:20 +00:00

(Migrated from git.hazaar.io)

created branch 2-warlock-to-warlock-communication

created branch [`2-warlock-to-warlock-communication`](https://git.hazaarlabs.com/hazaar/hazaar-warlock/compare/master...2-warlock-to-warlock-communication)

jamie commented

2018-07-12 01:25:58 +00:00

(Migrated from git.hazaar.io)

removed ~163 label

jamie commented

2019-05-28 06:57:46 +00:00

(Migrated from git.hazaar.io)

mentioned in merge request !24