Hi,
What you noticed has happened due to sticky sessions. So, once you log-in
to a manager node, all the requests you send will be dispatched to that
manager node. That's why you are seeing one manager doing all the work.
If you try logging in from a different browser, you might get logged into
t
To be more precise, I deploy app1 and the message is sent by manager1.
Then, I deploy app2 and the message is again sent by manager1. Here, I
don't know whether the deployment of the two apps is managed in a round
robin way or managed only by the manager1 (since it is sending the
message). What I t
Yes, there are new ways but I just tried the worker-manager concept just to
play around because I am still in the training period and its good to know
about it.
I don't want the managers to send the same message from all the manager
nodes. I want the managers to send messages in a round robin mann
I think when sending cluster messages, we use Hazelcast elected leader
member and that's a different concept from the worker-manager concept.
If you think of it, it's kind of redundant to send the same message from
all the management nodes to worker nodes.
On Fri, Aug 21, 2015 at 11:36 AM, Dilini
Hi Nirmal,
When I deploy apps in AS, only one manager is always sending the
SynchronizeRepositoryRequest to the other manager and worker nodes (the
manager nodes are not working in a round robin fashion). Is my
configurations wrong or have I understood it in a wrong way?
Regards,
Dilini
When
Hi Dilini,
On Fri, Aug 21, 2015 at 10:32 AM, Dilini Gunatilake
wrote:
> Hi All,
>
> I am playing around creating a worker/manager cluster in Application
> Server (AS) using the deployment pattern 2 [1] where two worker nodes and
> two manager nodes are involved with the load balancer (Here i use
