I'm not clear on a few points.
First, you say that a producer sends messages to primary_UDN_1 server and
then Consumer_UDN consumes all message types from that server. However,
then the server from which "all message types" have been consumed (i.e.
primary_UDN_1) forwards messages to primary_VM_2 server. If "all message
types" have been consumed from primary_UDN_1 by Consumer_UDN how are there
any messages left to forward to primary_VM_2?
Second, your slide indicated this was a "symmetrical" cluster. In other
words, it's a cluster where every node is configured the same. This is a
common configuration because it allows any client to connect to any node of
the cluster and consume messages sent to any other node in the cluster.
This makes all of the nodes in the cluster functionally equivalent so the
client doesn't need to care exactly which node it's connecting to. However,
you're asking about configuring certain nodes so that they will only
forward messages sent to certain addresses. This means your cluster is no
longer symmetrical. Can you clarify whether you really want a symmetrical
configuration?
Regarding which addresses are actually clustered (i.e. which addresses will
forward to other nodes in the cluster when messages are sent to them),
please refer to the <address> setting on the <cluster-connection>. See the
documentation [1] for details. In your case I think you'd just want to use:
<cluster-connection>
<address>PositionReport</address>
...
</cluster-connection>
Justin
[1]
https://activemq.apache.org/components/artemis/documentation/latest/clusters.html#configuring-cluster-connections
On Thu, Oct 24, 2024 at 4:30 PM tin.m....@lmco.com <tin.m....@lmco.com>
wrote:
> Hi,
>
> Thanks for the feedback! Your points are well received.
>
> Attached are the broker xml files: both are using Static Connectors:
>
> - Producer sends messages to primary_UDN_1 server
> - Consumer_UDN consumes all message types from primary_UDN_1 server
> - primary_UDN_1 server forwards messages to primary_VM_2 server
> - Consumer_VM consumes all message types from primary_VM_2 server
> - Consumer_UDN and Consumer_VM are the same app; just different instances
> with configurations allowing connecting to different Artemis servers
>
> GOAL: Specify messages types to be forwarded from primary_UDN_1 server f
> to primary_VM_2 server. This is to reduce traffic from primary_UDN_1 server
> f to primary_VM_2 server and hope to improve performance.
>
> Added address name="PositionReport“, as shown below in attempt to forward
> only PositionReport to VM node – but all messages still got forwarded from
> primary_UDN_1 server f to primary_VM_2 server:
> <address name="PositionReport">
> <anycast/>
> </address>
>
> QUESTION: How to configure so that primary_UDN_1 server would only forward
> certain message, such as PositionReport, to primary_VM_2 server?
>
> Regards,
> Tin (Tien) Lai
>
>
> -----Original Message-----
> From: Justin Bertram <jbert...@apache.org>
> Sent: Thursday, October 24, 2024 3:47 PM
> To: users@activemq.apache.org
> Subject: Re: EXTERNAL: Re: Artemis MQ 2.36.0 Load Balancing questions
>
> I'm still confused. There's multiple broker configurations in the zip and
> questions about both static and dynamic discovery. For the sake of clarity,
> can we focus on just *one* issue? If possible, provide configuration for
> either static or dynamic discovery (i.e. not both) and ask questions that
> only deal with that particular configuration.
>
> Also, please do not continue sending pptx files. Please use a more
> ubiquitous file format (e.g. txt, pdf, etc.), or better yet, just describe
> your use-case and the problem you're seeing directly in the body of the
> email as is customarily done on this mailing list. Folks providing support
> on this mailing list are doing so on a volunteer basis so it helps when
> folks needing support ask questions which are clear and concise as
> possible. Thanks!
>
>
> Justin
>
> On Thu, Oct 24, 2024 at 3:11 PM tin.m....@lmco.com <tin.m....@lmco.com>
> wrote:
>
> > Hi,
> >
> > I have simplified the configuration as you have suggested. However,
> > the same two issues still exist.
> >
> > The attached zip file contains:
> > - ArtemisMQ_Cluster_Oct172024.pptx This has configuration
> > descriptions and the questions
> > - primary_UDN_2 This folder has the UDN node
> > broker xml files
> > - primary_VM_2 This folder has the VM node
> broker
> > xml files
> >
> > Thank you for your help.
> >
> > Regards,
> > Tin (Tien) Lai
> >
> >
> > -----Original Message-----
> > From: Justin Bertram <jbert...@apache.org>
> > Sent: Thursday, October 24, 2024 12:40 PM
> > To: users@activemq.apache.org
> > Subject: Re: EXTERNAL: Re: Artemis MQ 2.36.0 Load Balancing questions
> >
> > I looked on page 2 of the ArtemisMQ_Cluster_Oct172024.pptx in the
> > archive which you attached to your original email, but I found no
> questions.
> > However, I see that you've added them in your response.
> >
> > I find the questions and the configuration confusing.
> >
> > First, automatic discovery (e.g. via UDP) or static connectors can be
> > used to form a cluster. You cannot, as far as I'm aware, use both
> > simultaneously. Therefore, please choose one or the other. It's not
> > clear why you would even try to use both.
> >
> > Second, you say that messages are not forwarded, but you don't
> > describe the details of the use-case. For example, you make no mention
> > of where messages are sent, where consumers are created, etc.
> >
> > Last, generally speaking it's best to start simple and add complexity
> > once the desired functionality has been validated. In this case you're
> > testing message load-balancing which requires multiple primary
> > servers. It doesn't require any backups. It would be useful to
> > simplify your configuration to eliminate any complexity that isn't
> > absolutely required to reproduce the problem. In this case, you can
> > drop your backups and simply focus on the two clustered primary servers.
> >
> >
> > Justin
> >
> > On Thu, Oct 24, 2024 at 9:42 AM tin.m....@lmco.com
> > <tin.m....@lmco.com>
> > wrote:
> >
> > > Hi,
> > >
> > > Thanks for the name correction.
> > >
> > > The questions are on page 2 of the ArtemisMQ_Cluster_Oct172024.pptx,
> > > which describes the configuration and the questions. They are listed
> > here:
> > >
> > > ------
> > > Issue 1:
> > > - UDN node and VM node all use Dynamic discovery
> > > - Cluster connections were established
> > > - Messages either were not forwarded by UDN node, or were not
> > > received by VM node
> > > - Succeeded ONLY after restarting the UDN Primary Server
> > >
> > > QUESTION 1: How to configure so that UDN node server would forward
> > > messages to VM node server upon startup when all are using Dynamic
> > > discovery?
> > >
> > > ------
> > > Issue 2:
> > > UDN node uses Dynamic discovery , VM uses Static Connectors:
> > > Added address name="PositionReport“, as shown below in attempt to
> > > forward only PositionReport to VM node – but all messages still got
> > > forwarded <address name="PositionReport">
> > > <anycast/>
> > > </address>
> > >
> > > QUESTION 2: How to configure so that UDN node server would only
> > > forward certain message, such as PositionReport, to VM node server?
> > >
> > >
> > > Regards,
> > > Tin (Tien) Lai
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Justin Bertram <jbert...@apache.org>
> > > Sent: Thursday, October 24, 2024 8:30 AM
> > > To: users@activemq.apache.org
> > > Subject: EXTERNAL: Re: Artemis MQ 2.36.0 Load Balancing questions
> > >
> > > Where are the actual questions?
> > >
> > > Also, the broker is named "ActiveMQ Artemis," not "ArtemisMQ."
> > >
> > >
> > > Justin
> > >
> > > On Wed, Oct 23, 2024 at 3:01 PM tin.m....@lmco.com
> > > <tin.m....@lmco.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > >
> > > >
> > > > Attached is a zip file describing the configuration and the
> > > > questions I have with Load Balancing. Let me know if I need to
> > > > provide any additional information.
> > > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Tin (Tien) Lai
> > > >
> > > >
> > > >
> > > > ------------------------------------------------------------------
> > > > --
> > > > - To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
> > > > For additional commands, e-mail: users-h...@activemq.apache.org
> > > > For further information, visit:
> > > > https://activemq.apache.org/contact
> > > >
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
> > > For additional commands, e-mail: users-h...@activemq.apache.org For
> > > further information, visit: https://activemq.apache.org/contact
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
> > For additional commands, e-mail: users-h...@activemq.apache.org For
> > further information, visit: https://activemq.apache.org/contact
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
> For additional commands, e-mail: users-h...@activemq.apache.org
> For further information, visit: https://activemq.apache.org/contact
>
