[jgroups-users] Protocols' questions

Questions/problems related to using JGroups <[email protected]> Fri, 17 Aug 2018 15:49:36 +0000
Newsgroups gmane.comp.java.javagroups.general
Message-ID <mailman.14192.1534522251.1399.javagroups-users@lists.sourceforge.net>
Hello,

I am trying to make my mind up regarding some of the protocols JGroups provides - I don't have a lot of experience with it  therefore forgive me if some questions
are blatantly naïve - I did read the docs a few times but I am still unsure.

It seems to me that many of the protocols have an UDP "mindset", namely they make most sense when used upon UDP as transport protocol, I am debugging an issue
Whose jgroups' stack involve the following (more or less):

<FRAG>
<STABLE>
<NACK2>
<UNICAST2>
<TCP>

I am investigating if I could simplify it and I few questions popped up

Reading the <UNICAST2> documentation:

>On top of a reliable transport, such as TCP, UNICAST is not really needed. However, concurrent delivery of messages from the same sender is prevented by UNICAST by acquiring a lock on the >sender's retransmission table, so unless concurrent delivery is desired,

What is it actually meant by "concurrent delivery" ?

Does it refer to the fact that JChannel.send() is not synchronized therefore, when sending an bunch messages we could end up with a catastrophic
mess where bits of messages get scattered on the stream and the whole thing becomes un-intelligible to the receiver ?

Does it make sense to have one among UNICAST{1,2,3} and NACKAK{1,2} in the stack ? Wouldn't that be redundant ?

Does STABLE make sense if we are using TCP to deliver messages to the cluster's members ?

Does FRAG make sense if, by using a connection-oriented protocol such as TCP, we don't have a max datagram size to stick to ?

Thanks,
Pietro



Pietro Paolini
Consultant

Alfa
________________________________
e: [email protected] | w: alfasystems.com<https://www.alfasystems.com>
t: +44 (0) 20 7920-2643 | Moor Place, 1 Fore Street Avenue, London, EC2Y 9DT, GB
________________________________

The contents of this communication are not intended to be binding or constitute any form of offer or acceptance or give rise to any legal obligations on behalf of the sender or Alfa. The views or opinions expressed represent those of the author and not necessarily those of Alfa. This email and any attachments are strictly confidential and are intended solely for use by the individual or entity to whom it is addressed. If you are not the addressee (or responsible for delivery of the message to the addressee) you may not copy, forward, disclose or use any part of the message or its attachments. At present the integrity of email across the internet cannot be guaranteed and messages sent via this medium are potentially at risk. All liability is excluded to the extent permitted by law for any claims arising as a result of the use of this medium to transmit information by or to Alfa or its affiliates.

Alfa Financial Software Ltd
Reg. in England No: 0248 2325

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot