Hi,
my setup looks like this, where the number of instances is setup using docker swarm scaling https://docs.docker.com/engine/swarm/swarm-tutorial/scale-service/
Redis <-> db_instances <-> scheduler <-> worker
Every instance runs inside a docker container and at the moment there is only one redis instance. I intend to move to a redis cluster setup at some point. I am using
db_instances:router <-> scheduler:dealer scheduler:router <-> worker:dealer socket setup.
Currently I connect the dealer sockets like this tcp://scheduler:5000, and docker swarm automatically directs the message to one out of the set of scaled scheduler services.
It is possible to connect directly to one instance of scheduler, tcp://scheduler.1:5000 with that would i t make sense to have one socket per connected service instance?
And then using a LRU scheduling approach to direct my requests?
I hope the my setup became clearer.
Thanks
Gesendet: Dienstag, 27. Juni 2017 um 12:00 Uhr
Von: [email protected]
An: [email protected]
Betreff: zeromq-dev Digest, Vol 15, Issue 14
Von: [email protected]
An: [email protected]
Betreff: zeromq-dev Digest, Vol 15, Issue 14
Send zeromq-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of zeromq-dev digest..."
Today's Topics:
1. Re: publish dynamic port (Luca Boccassi)
2. testing new merges (Mos Yud)
3. Re: testing new merges (Luca Boccassi)
4. Re: Stateless service protocols (Marcin Romaszewicz)
----------------------------------------------------------------------
Message: 1
Date: Mon, 26 Jun 2017 12:03:24 +0100
From: Luca Boccassi <[email protected]>
To: ZeroMQ development list <[email protected]>
Subject: Re: [zeromq-dev] publish dynamic port
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
On Mon, 2017-06-26 at 11:38 +0300, Mos Yud wrote:
> Hi,
>
> I am using zmq- 4.2.1.
>
> I would like to establish P2P connection (client-server). Server bind
> to a
> dynamic port and client should be familiar with the port number in
> order to
> connect to it.
> What is best way to publish the port number to the client?
>
> Thx.
> Moshe.
Zyre can be used for autodiscovery and forming groups:
https://github.com/zeromq/zyre
If over the same LAN then the default will work with broadcast,
otherwise you'll need a well-known "hub" in gossip mode.
Alternatively if what you need is a small range of dynamic ports for
the server, then you can use CZMQ which supports that:
zsock_bind(sock, "tcp://127.0.0.1:![55000-55009]")
This will bind to the first free port in that range. Then your client
can connect to the whole range, and the one that succeeds will be
automatically used. Of course if the range is large then it becomes
very inconvenient.
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170626/d48bb85a/attachment-0001.sig>
------------------------------
Message: 2
Date: Mon, 26 Jun 2017 16:47:26 +0300
From: Mos Yud <[email protected]>
To: ZeroMQ development list <[email protected]>
Subject: [zeromq-dev] testing new merges
Message-ID:
<CAM=tgg3y9crrsf1yigmcyar0r9fauvcw3xkoodlkmp+fxl-...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
Is any new merged patch is tested on the following build machines (taken
from zmq web page):
- Master (Linux / Debian / x86)
- solaris10 (Solaris / SunOS 5.10 / x86)
- win7 (Windows 7 / x86)
- freebsd8.1 (BSD / FreeBSD 8.1 / x86)
- linux_s390x (Linux / SLES11 / s390x
Are there any tests for windows XP. Is new committed code should support
windows XP?
Thx,
Moshe.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170626/b969df61/attachment-0001.html>
------------------------------
Message: 3
Date: Mon, 26 Jun 2017 15:36:46 +0100
From: Luca Boccassi <[email protected]>
To: ZeroMQ development list <[email protected]>
Subject: Re: [zeromq-dev] testing new merges
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
On Mon, 2017-06-26 at 16:47 +0300, Mos Yud wrote:
> Hi,
>
> Is any new merged patch is tested on the following build machines
> (taken
> from zmq web page):
>
> ???- Master (Linux / Debian / x86)
> ???- solaris10 (Solaris / SunOS 5.10 / x86)
> ???- win7 (Windows 7 / x86)
> ???- freebsd8.1 (BSD / FreeBSD 8.1 / x86)
> ???- linux_s390x (Linux / SLES11 / s390x
>
> Are there any tests for windows XP. Is new committed code should
> support
> windows XP?
We have automated testing for all of the following.
Linux:
Debian 7/8/9/Unstable i386/x86_64
Ubuntu 12.04/14.04/16.04/16.10/17.04 i386/x86_64
Fedora 24 i386/x86_64
Fedora 25 i386/x86_64/arm64/armv7
Fedora Rawhide x86_64/arm64/arm7
Centos 7 x86_64
RHEL 7 x86_64/ppc64
Suse 12SP2 x86_64/s390x/arm64/ppc64le
Suse Leap 42.1/42.2 i386/x86_64
Suse Tumbleweed i586/x86_64/arm64/armv7
Apple:
OSX 10.11 XCode 7.3 x86_64
Windows:
Windows 7 32/64 Visual Studio 14
Windows 7 32 Visual Studio 12
As far as I am aware there is no automated test for Windows XP, but it
should still work.
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170626/a60ecfc8/attachment-0001.sig>
------------------------------
Message: 4
Date: Mon, 26 Jun 2017 13:37:30 -0700
From: Marcin Romaszewicz <[email protected]>
To: ZeroMQ development list <[email protected]>
Subject: Re: [zeromq-dev] Stateless service protocols
Message-ID:
<CACKFMAXr3mFuNw_ry7ir_R-sY=fnvmfejcvbtunsskaka6o...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
A "stateless" protocol would be one where your message has to contain all
the information needed to handle it, so that the server contains no state.
It sounds like a very large constraint. I work on a large load-balanced set
of microservices, and they're all stateful, using shared state via a
postgres database, so it doesn't matter which service instance my requests
go to, since all of them contain the correct state.
What is it that you are trying to do?
On Sun, Jun 25, 2017 at 1:51 PM, <[email protected]> wrote:
> Hi,
>
> a few days ago I posted a question here regarding the combination of
> Zeromq and Docker Swarm.
>
> As a follow up to this thread. Since it is not possible to really use a
> stateful connections with the load balancer provided by Docker Swarm, I am
> curious if it is possible to write distributed architectures with entirely
> stateless protocols?
>
> Thanks,
>
> Florian
>
> _______________________________________________
> zeromq-dev mailing list
> [email protected]
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170626/bef9c1fa/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
zeromq-dev mailing list
[email protected]
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
------------------------------
End of zeromq-dev Digest, Vol 15, Issue 14
******************************************
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of zeromq-dev digest..."
Today's Topics:
1. Re: publish dynamic port (Luca Boccassi)
2. testing new merges (Mos Yud)
3. Re: testing new merges (Luca Boccassi)
4. Re: Stateless service protocols (Marcin Romaszewicz)
----------------------------------------------------------------------
Message: 1
Date: Mon, 26 Jun 2017 12:03:24 +0100
From: Luca Boccassi <[email protected]>
To: ZeroMQ development list <[email protected]>
Subject: Re: [zeromq-dev] publish dynamic port
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
On Mon, 2017-06-26 at 11:38 +0300, Mos Yud wrote:
> Hi,
>
> I am using zmq- 4.2.1.
>
> I would like to establish P2P connection (client-server). Server bind
> to a
> dynamic port and client should be familiar with the port number in
> order to
> connect to it.
> What is best way to publish the port number to the client?
>
> Thx.
> Moshe.
Zyre can be used for autodiscovery and forming groups:
https://github.com/zeromq/zyre
If over the same LAN then the default will work with broadcast,
otherwise you'll need a well-known "hub" in gossip mode.
Alternatively if what you need is a small range of dynamic ports for
the server, then you can use CZMQ which supports that:
zsock_bind(sock, "tcp://127.0.0.1:![55000-55009]")
This will bind to the first free port in that range. Then your client
can connect to the whole range, and the one that succeeds will be
automatically used. Of course if the range is large then it becomes
very inconvenient.
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170626/d48bb85a/attachment-0001.sig>
------------------------------
Message: 2
Date: Mon, 26 Jun 2017 16:47:26 +0300
From: Mos Yud <[email protected]>
To: ZeroMQ development list <[email protected]>
Subject: [zeromq-dev] testing new merges
Message-ID:
<CAM=tgg3y9crrsf1yigmcyar0r9fauvcw3xkoodlkmp+fxl-...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
Is any new merged patch is tested on the following build machines (taken
from zmq web page):
- Master (Linux / Debian / x86)
- solaris10 (Solaris / SunOS 5.10 / x86)
- win7 (Windows 7 / x86)
- freebsd8.1 (BSD / FreeBSD 8.1 / x86)
- linux_s390x (Linux / SLES11 / s390x
Are there any tests for windows XP. Is new committed code should support
windows XP?
Thx,
Moshe.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170626/b969df61/attachment-0001.html>
------------------------------
Message: 3
Date: Mon, 26 Jun 2017 15:36:46 +0100
From: Luca Boccassi <[email protected]>
To: ZeroMQ development list <[email protected]>
Subject: Re: [zeromq-dev] testing new merges
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
On Mon, 2017-06-26 at 16:47 +0300, Mos Yud wrote:
> Hi,
>
> Is any new merged patch is tested on the following build machines
> (taken
> from zmq web page):
>
> ???- Master (Linux / Debian / x86)
> ???- solaris10 (Solaris / SunOS 5.10 / x86)
> ???- win7 (Windows 7 / x86)
> ???- freebsd8.1 (BSD / FreeBSD 8.1 / x86)
> ???- linux_s390x (Linux / SLES11 / s390x
>
> Are there any tests for windows XP. Is new committed code should
> support
> windows XP?
We have automated testing for all of the following.
Linux:
Debian 7/8/9/Unstable i386/x86_64
Ubuntu 12.04/14.04/16.04/16.10/17.04 i386/x86_64
Fedora 24 i386/x86_64
Fedora 25 i386/x86_64/arm64/armv7
Fedora Rawhide x86_64/arm64/arm7
Centos 7 x86_64
RHEL 7 x86_64/ppc64
Suse 12SP2 x86_64/s390x/arm64/ppc64le
Suse Leap 42.1/42.2 i386/x86_64
Suse Tumbleweed i586/x86_64/arm64/armv7
Apple:
OSX 10.11 XCode 7.3 x86_64
Windows:
Windows 7 32/64 Visual Studio 14
Windows 7 32 Visual Studio 12
As far as I am aware there is no automated test for Windows XP, but it
should still work.
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170626/a60ecfc8/attachment-0001.sig>
------------------------------
Message: 4
Date: Mon, 26 Jun 2017 13:37:30 -0700
From: Marcin Romaszewicz <[email protected]>
To: ZeroMQ development list <[email protected]>
Subject: Re: [zeromq-dev] Stateless service protocols
Message-ID:
<CACKFMAXr3mFuNw_ry7ir_R-sY=fnvmfejcvbtunsskaka6o...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
A "stateless" protocol would be one where your message has to contain all
the information needed to handle it, so that the server contains no state.
It sounds like a very large constraint. I work on a large load-balanced set
of microservices, and they're all stateful, using shared state via a
postgres database, so it doesn't matter which service instance my requests
go to, since all of them contain the correct state.
What is it that you are trying to do?
On Sun, Jun 25, 2017 at 1:51 PM, <[email protected]> wrote:
> Hi,
>
> a few days ago I posted a question here regarding the combination of
> Zeromq and Docker Swarm.
>
> As a follow up to this thread. Since it is not possible to really use a
> stateful connections with the load balancer provided by Docker Swarm, I am
> curious if it is possible to write distributed architectures with entirely
> stateless protocols?
>
> Thanks,
>
> Florian
>
> _______________________________________________
> zeromq-dev mailing list
> [email protected]
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170626/bef9c1fa/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
zeromq-dev mailing list
[email protected]
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
------------------------------
End of zeromq-dev Digest, Vol 15, Issue 14
******************************************
_______________________________________________ zeromq-dev mailing list [email protected] https://lists.zeromq.org/mailman/listinfo/zeromq-dev
