Grega Poga─Źnik | 29 Sep 22:40 2014
Picon

[jgroups-users] total ordering protocols (sequencer)

Hi,

does SEQUENCER depend on multicast and thus the use of UDP transport? I can imagine that the coordinator needs to send out everything "atomically". I mean else there could be trouble if the coordinator crashes in the middle of the batch. Or how is that handled?

I apologize if that is already covered in some part of the documentation.

I recall reading that jgroups also had a token based solution but that got abandoned. How exactly did that work? What were the problems with it? Any plans to get it "resurrected"?

Thanks.

Regards,
Gregor
------------------------------------------------------------------------------
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
javagroups-users mailing list
javagroups-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/javagroups-users
Bela Ban | 26 Sep 09:11 2014
Picon

[jgroups-users] JGroups 3.5.1.Final released

FYI, I released 3.5.1.Final [1].

It does contain a few important fixes, e.g.

- https://issues.jboss.org/browse/JGRP-1880: UDP.ip_ttl is always set to 
1. This causes JGroups messages sent across multiple switches not to get 
received

- https://issues.jboss.org/browse/JGRP-1885: a bind_addr of 0.0.0.0 now 
throws an exception. Setting bind_addr to the wildcard address, would 
result in members not being able to communicate, and is a silent showstopper

- https://issues.jboss.org/browse/JGRP-1876: MergeView shows incorrect 
subgroups in some cases (the merged view is correct though). This can 
have an impact on merge handling code

- https://issues.jboss.org/browse/JGRP-1865: RELAY2 (xsite) doesn't work 
over FORK

- https://issues.jboss.org/browse/JGRP-187{4,5}: reduce traffic in a 
SYNC case

Note that 3.6 will be baselined on JDK 7, while 3.5.x will continue to 
work with JDK 6.

[1] https://issues.jboss.org/browse/JGRP/fixforversion/12325575

--

-- 
Bela Ban, JGroups lead (http://www.jgroups.org)

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
Kowshik NS | 24 Sep 16:09 2014

Re: [jgroups-users] Node Recognition in Jgroups 3.0.6Final

Thanks Bela. We will check about the issues below

And sorry about the direct e-mail .  I will post this to javagroups-users <at> lists.sourceforge.net

Regards,
Kowshik NS

-----Original Message-----
From: Bela Ban [mailto:belaban <at> yahoo.com] 
Sent: 24 September 2014 15:05
To: Kowshik NS
Subject: Re: Node Recognition in Jgroups 3.0.6Final

Could be a firewall issue. Are the members listening on port 7801 ? Are they binding to the 10.x.x.x
addresses ?
Please post to the JGroups mailing list, not to me directly next time...

On 24/09/14 16:02, Kowshik NS wrote:
> Hi Bela,
>
> We are trying to set up a cluster on two different machines. A,B,C, 
> (Machine 1 nodes ) D,E,F ( Machine 2 nodes)
>
> We did test this on our internal network with this and can see a 
> proper cluster formed
>
> However in our customer environment with the same setting Machine 1 is 
> not able to recognise nodes on Machine 2 and viceversa.
>
> We see machines able to ping each other.
>
> Please could you help us.
>
> We are using Jgroups 3.0.6Final and TCP.xml shipped with 3.0.6FInal
>
> The setting include
>
> -Djgroups.bind_addr=10.125.45.11
> -Djgroups.tcpping.initial_hosts="10.125.45.11[7810],10.125.45.12[7810]"
> -Djava.net.preferIPv4Stack=true
>
> Best Regards,
>
> Kowshik NS
>
> CONFIDENTIALITY: This e-mail (including any attachments) may contain 
> confidential, proprietary and privileged information, and unauthorized 
> disclosure or use is prohibited. If you received this e-mail in error, 
> please notify the sender and delete this e-mail from your system.
>

--
Bela Ban, JGroups lead (http://www.jgroups.org)

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
Bela Ban | 24 Sep 12:30 2014
Picon

[jgroups-users] JGroups 3.6 will require JDK 7

FYI,

as the subject says... JDK 6 was EOL'ed in 2011 [1], so it's time to 
move on.

3.5 and all patch releases off of that branch (3.5.1) will be the last 
release(s) on JDK 6.

[1] http://www.oracle.com/technetwork/java/eol-135779.html

--

-- 
Bela Ban, JGroups lead (http://www.jgroups.org)

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
Caleb Cushing | 18 Sep 18:55 2014
Picon

[jgroups-users] message size (216081) is greater than max bundling size (200000) but frag2 60k

I've asked the question on SO, but I'll repeat it here

http://stackoverflow.com/q/25916835/206466

> [ERROR] [2014-08-28 07:09:17.100] failed sending message to cluster (216081 bytes):
java.lang.Exception: message size (216081) is greater than max bundling size (200000). Set the
fragmentation/bundle size in FRAG and TP correctly, cause: null - protocols.TCP
[http-apr-8080-exec-10] [48488852 ms]

after doing some research about the configuration

    <config xmlns="urn:org:jgroups"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="urn:org:jgroups
http://www.jgroups.org/schema/JGroups-3.1.xsd">
    <TCP bind_port="${ehcacheDistributed.jgroups.bindPort}"
         bind_addr="NON_LOOPBACK"
         loopback="false"
         recv_buf_size="${tcp.recv_buf_size:20M}"
         send_buf_size="${tcp.send_buf_size:640K}"
         discard_incompatible_packets="true"
         max_bundle_size="200K"
         max_bundle_timeout="30"
         enable_bundling="true"
         use_send_queues="true"
         sock_conn_timeout="300"

         timer_type="new"
         timer.min_threads="4"
         timer.max_threads="10"
         timer.keep_alive_time="3000"
         timer.queue_max_size="500"

         thread_pool.enabled="true"
         thread_pool.min_threads="1"
         thread_pool.max_threads="10"
         thread_pool.keep_alive_time="5000"
         thread_pool.queue_enabled="false"
         thread_pool.queue_max_size="100"
         thread_pool.rejection_policy="discard"

         oob_thread_pool.enabled="true"
         oob_thread_pool.min_threads="1"
         oob_thread_pool.max_threads="8"
         oob_thread_pool.keep_alive_time="5000"
         oob_thread_pool.queue_enabled="false"
         oob_thread_pool.queue_max_size="100"
         oob_thread_pool.rejection_policy="discard"/>

    <TCPPING timeout="3000"
             initial_hosts="${ehcacheDistributed.jgroups.tcpping.initialhosts}"
             port_range="1"
             num_initial_members="10"/>
    <MERGE2  min_interval="10000"
             max_interval="30000"/>
    <FD_SOCK/>
    <FD timeout="35000" max_tries="6" />
    <VERIFY_SUSPECT timeout="1500"  />
    <BARRIER />
    <pbcast.NAKACK2 use_mcast_xmit="false"
                   discard_delivered_msgs="true"/>
    <UNICAST />
    <pbcast.STABLE stability_delay="1000" desired_avg_gossip="50000"
                   max_bytes="4M"/>
    <pbcast.GMS print_local_addr="true" join_timeout="3000"

                view_bundling="true"/>
    <UFC max_credits="2M"
         min_threshold="0.4"/>
    <MFC max_credits="2M"
         min_threshold="0.4"/>
    <FRAG2 frag_size="60K"  />
    <!--RSVP resend_interval="2000" timeout="10000"/-->
    <pbcast.STATE_SOCK/>
    </config>

we're using jgroups 3.1.0, it would appear that jgroups isn't breaking
the message apart properly using FRAG2, why is that? what'm I missing?

--

-- 
Caleb Cushing

http://xenoterracide.com

Calendar:
https://www.google.com/calendar/embed?src=xenoterracide%40gmail.com&ctz=America/Chicago

------------------------------------------------------------------------------
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
Bela Ban | 29 Aug 11:01 2014
Picon

[jgroups-users] JGroups 3.5.0.Final released

FYI: http://belaban.blogspot.ch/2014/08/jgroups-350final-released.html

--

-- 
Bela Ban, JGroups lead (http://www.jgroups.org)

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
tdumidu | 25 Aug 10:56 2014
Picon

[jgroups-users] How to send a unicast message to a known member

I have a member called "A_001". I need to send a unicast message to "A_001".
How can i send a unicast message to A_001 member. I tried Message msg=new
Message("A_001",null, "Hi). But it is not working. Can someone tell me the
correct syntax? 

--
View this message in context: http://jgroups.1086181.n5.nabble.com/How-to-send-a-unicast-message-to-a-known-member-tp10323.html
Sent from the JGroups - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
Dieter Cailliau | 20 Aug 16:03 2014
Picon

[jgroups-users] -Djgroups.mping.ip_ttl not applied in 3.4.3

Since my move from AS 7.2.0 (with jgroups 3.2.7) to wildfly 8.1 (with
jgroups 3.4.3), i'm unable to configure the ttl for mping via
-Djgroups.mping.ip_ttl=10.

With wireshark I see that the ttl is always set to 2 in wildfly 8.1.

It is set to my value-of-choice in AS 7.2.0.

I'm testing on a ubuntu machine with java 7:

java -version
java version "1.7.0_55"
OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1~0.12.10.1)
OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
Bela Ban | 19 Aug 11:56 2014
Picon

[jgroups-users] Converted the docs from Docbook --> AsciiDoc

FYI: I converted the tutorial [1] and manual [2] from DocBook to 
AsciiDoc. It is much nicer and therefore more enticing to write 
documentation in AsciiDoc than in DocBook, and the generated HTML looks 
really nice as well. I used AsciiDoctor to do this.

I also dropped the PDF generation, which IMO is not needed as everyone's 
online all the time anyway nowadays.

Note that GitHub supports AsciiDoc natively, so [3] renders directly in 
the browser. 'GitHub Pages' (github.io) doesn't yet support AsciiDoc, 
but once they do, I might move the docs to github.io ... this might 
ultimately lead to more contributions (e.g. typo fixes, changing 
incorrect docs etc) as changes can be made directly on the web page 
(with appropriate permission), similar to a wiki, and then a git pull 
would update the local docu. Very nice, although I have to figure out 
how to handle the part of the docs that we generate from the code (e.g. 
the protocol list).

[1] http://www.jgroups.org/tutorial/index.html

[2] http://www.jgroups.org/manual/index.html

[3] https://github.com/belaban/JGroups/blob/master/doc/manual/api.adoc

--

-- 
Bela Ban, JGroups lead (http://www.jgroups.org)

------------------------------------------------------------------------------
pooja khambhayata | 18 Aug 20:16 2014
Picon

[jgroups-users] In a large cluster of 60 nodes, split happens and Merge is not successful

Hello,

We have a Jgroups 3.3.1.Final deployed on 60 nodes.

If we start servers in groups the jgroups view comes up fine.
But when we bring up all of them together or reboot on some servers happens,

I see following problems.

1. I see n TCP connections but the jgroups view shows much less than n. I believed that
no of connections in TCP channel has to always reflect the jgroups view.

2. I see Multiple co-ordinators in the system. One co-ordinator say node A does detect this case and tries to send Mergeview to other co-ordinator say node B who is supposed to take lead in merging. But such message is dropped on the floor by second co-ordinator node B printing "No physical address found for nodeA" thus never processing any Merge views.

Only way to recover such system is to stop appl on all nodes and then start one and start others in few sets.

3. In a case of Multiple co-ordinators, if I restart the linux node containing one of the co-ordinator , other members in its group still show the rebooted node as co-ordinator.

Attachment (tcp_pers.xml): text/xml, 3517 bytes
------------------------------------------------------------------------------
_______________________________________________
javagroups-users mailing list
javagroups-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/javagroups-users
Bela Ban | 11 Aug 14:19 2014
Picon

[jgroups-users] JGroups 3.4.5 released

More info here: https://issues.jboss.org/browse/JGRP/fixforversion/12324918
--

-- 
Bela Ban, JGroups lead (http://www.jgroups.org)

------------------------------------------------------------------------------

Gmane