[jgroups-dev] Version 2.8.10, 2.10.0 test result for ReIncarnation problem
Kuwon Kang <[email protected]>
| Newsgroups | gmane.comp.java.javagroups.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello. Bela.
Thanks for your support for our problem and according to your advice I'm
trying to test for upgrade.
This test's focus is to remove and change few options in JGroups for
start_port and end_port.
And another thing is to use optimized version of JGroups.
I tested version 2.8.1.0 and 2.10.0 to avoid reincarnation issue.
And I have a few unexpected result below shown.
*The entire JGroups configuration which is experimented is below shown.*
Test configuration file gathered from the JGroups's release archive.
<!--
TCP based stack, with flow control and message bundling. This is usually
used when IP
multicasting cannot be used in a network, e.g. because it is disabled
(routers discard multicast).
Note that TCP.bind_addr and TCPPING.initial_hosts should be set,
possibly via system properties, e.g.
-Djgroups.bind_addr=192.168.5.2 and
-Djgroups.tcpping.initial_hosts=192.168.5.2[7800]
author: Bela Ban
version: $Id: tcp.xml,v 1.40 2009/12/18 09:28:30 belaban Exp $
-->
<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-2.8.xsd">
<TCP bind_port="7820"
loopback="true"
recv_buf_size="${tcp.recv_buf_size:20M}"
send_buf_size="${tcp.send_buf_size:640K}"
discard_incompatible_packets="true"
max_bundle_size="64K"
max_bundle_timeout="30"
enable_bundling="true"
use_send_queues="true"
sock_conn_timeout="300"
timer.num_threads="4"
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="${jgroups.tcpping.initial_hosts:100.254.161.11[7820]}"
port_range="5"
num_initial_members="1"/>
<MERGE2 min_interval="10000"
max_interval="30000"/>
<FD_SOCK/>
<FD timeout="3000" max_tries="3" />
<VERIFY_SUSPECT timeout="1500" />
<BARRIER />
<pbcast.NAKACK
use_mcast_xmit="false" gc_lag="0"
retransmit_timeout="300,600,1200,2400,4800"
discard_delivered_msgs="true"/>
<UNICAST timeout="300,600,1200" />
<pbcast.STABLE stability_delay="1000" desired_avg_gossip="50000"
max_bytes="400K"/>
<pbcast.GMS print_local_addr="true" join_timeout="3000"
view_bundling="true"/>
<FC max_credits="2M"
min_threshold="0.10"/>
<FRAG2 frag_size="60K" />
<pbcast.STREAMING_STATE_TRANSFER/>
<!-- <pbcast.STATE_TRANSFER/> -->
</config>
*Q1. The first thing that I want to know is the name of member that captured
from the event using 'public void viewAccepted(View new_view)'.*
*The name in red color below is not seem to be normal name. Could you
explain this name?*
[FLPREA01-64634, FLPREA01-30427, FLPREA01-45965]
[FLPREA01-64634, FLPREA01-30427, FLPREA01-45965,
1982f205-32b0-76ec-b02c-824c72ca594e]
[FLPREA01-64634, FLPREA01-30427, FLPREA01-45965, FLPREA01-39563,
09c02c5b-1606-bf6e-2f80-6dc2925f6931]
[FLPREA01-30427, FLPREA01-45965, FLPREA01-39563,
09c02c5b-1606-bf6e-2f80-6dc2925f693]
*And, is there a way to see the member information like previous
version(2.7.0.0) which is shown the ip and port.*
For exmaple: [100.254.163.51:7800, 100.254.163.51:7801, 100.254.161.13:7800,
100.254.161.12:78
01, 100.254.161.12:7800, 100.254.161.11:7800, 100.254.161.13:7801,
100.254.161.11:7801]
*Q2. While I'm starting and shutdown each node in same clustering(GMS) with
above configurations, sometimes(Obviously very often) show warning and error
messages in red text below shown:*
-------------------------------------------------------------------
GMS: address=FLPCOA01-54138, cluster=reincarnation, physical address=
100.254.161.11:7823
-------------------------------------------------------------------
[FLPCOA01-54138]
2010. 8. 20 오후 4:41:47 org.jgroups.logging.JDKLogImpl warn
*경고: FLPCOA01-54138: dropped message from FLPCOA01-22023 (not in xmit_table)
*, keys are [FLPCOA01-54138], view=[FLPCOA01-54138|0] [FLPCOA01-54138]
[FLPCOA01-30123, FLPCOA01-22023, FLPCOA01-12843, FLPCOA01-54138]
-------------------------------------------------------------------
GMS: address=FLPCOA01-56629, cluster=reincarnation, physical address=
100.254.161.11:7823
-------------------------------------------------------------------
[FLPCOA01-56629]
2010. 8. 20 오후 4:30:12 org.jgroups.logging.JDKLogImpl warn
경고: FLPCOA01-56629: dropped message from
9609a764-2d21-2757-f8f7-63b36a4ac3c2 (not in xmit_table), keys are
[FLPCOA01-56629], view=[FLPCOA01-56629|0] [FLPCOA01-56629]
2010. 8. 20 오후 4:30:13 org.jgroups.logging.JDKLogImpl warn
경고: FLPCOA01-56629: dropped message from
f558fea5-af6f-1a40-4362-18c1106aab4d (not in xmit_table), keys are
[FLPCOA01-56629], view=[FLPCOA01-56629|0] [FLPCOA01-56629]
2010. 8. 20 오후 4:30:14 org.jgroups.logging.JDKLogImpl warn
경고: FLPCOA01-56629: dropped message from
99b86520-24c8-91c3-ebad-5d7d64e6f72c (not in xmit_table), keys are
[FLPCOA01-56629], view=[FLPCOA01-56629|0] [FLPCOA01-56629]
2010. 8. 20 오후 4:30:15 org.jgroups.logging.JDKLogImpl warn
경고: FLPCOA01-56629: dropped message from
99b86520-24c8-91c3-ebad-5d7d64e6f72c (not in xmit_table), keys are
[FLPCOA01-56629], view=[FLPCOA01-56629|0] [FLPCOA01-56629]
2010. 8. 20 오후 4:30:31 org.jgroups.logging.JDKLogImpl warn
경고: FLPCOA01-56629: dropped message from FLPCOA01-44695 (not in xmit_table),
keys are [FLPCOA01-56629], view=[FLPCOA01-56629|0] [FLPCOA01-56629]
[FLPCOA01-44695, FLPCOA01-15189, FLPCOA01-62566, FLPCOA01-56629]
2010. 8. 20 오후 4:30:32 org.jgroups.logging.JDKLogImpl warn
경고: FLPCOA01-56629: no physical address for FLPCOA01-62566, dropping message
-------------------------------------------------------------------
GMS: address=FLPREA01-24739, cluster=reincarnation, physical address=
100.254.161.55:7822
-------------------------------------------------------------------
[FLPREA01-3601, FLPREA01-24739]
2010. 8. 20 오후 4:34:26 org.jgroups.logging.JDKLogImpl warn
경고: FLPREA01-24739: dropped message from FLPREA01-47329 (not in xmit_table),
keys are [FLPREA01-3601, FLPREA01-24739], view=[FLPREA01-3601|1]
[FLPREA01-3601, FLPREA01-24739]
[FLPREA01-24739, FLPREA01-47329, FLPREA01-3601]
[FLPREA01-24739, FLPREA01-47329, FLPREA01-3601, FLPREA01-43105]
2010. 8. 20 오후 4:34:27 org.jgroups.logging.JDKLogImpl warn
경고: FLPREA01-24739: received view < current view; discarding it (current
vid: [FLPREA01-24739|3], new vid: [FLPREA01-24739|2])
[FLPREA01-24739, FLPREA01-47329, FLPREA01-3601, FLPREA01-43105,
FLPREA01-24882]
-------------------------------------------------------------------
GMS: address=FLPREA01-47329, cluster=reincarnation, physical address=
100.254.161.55:7821
-------------------------------------------------------------------
[FLPREA01-47329]
2010. 8. 20 오후 4:34:25 org.jgroups.logging.JDKLogImpl warn
경고: FLPREA01-47329: dropped message from FLPREA01-3601 (not in xmit_table),
keys are [FLPREA01-47329], view=[FLPREA01-47329|0] [FLPREA01-47329]
2010. 8. 20 오후 4:34:26 org.jgroups.logging.JDKLogImpl warn
경고: FLPREA01-47329: dropped message from FLPREA01-3601 (not in xmit_table),
keys are [FLPREA01-47329], view=[FLPREA01-47329|0] [FLPREA01-47329]
[FLPREA01-24739, FLPREA01-47329, FLPREA01-3601]
[FLPREA01-24739, FLPREA01-47329, FLPREA01-3601, FLPREA01-43105]
2010. 8. 20 오후 4:34:27 org.jgroups.logging.JDKLogImpl warn
경고: FLPREA01-47329: received view < current view; discarding it (current
vid: [FLPREA01-24739|3], new vid: [FLPREA01-24739|2])
[FLPREA01-24739, FLPREA01-47329, FLPREA01-3601, FLPREA01-43105,
FLPREA01-24882]
2010. 8. 20 오후 5:20:16 org.jgroups.logging.JDKLogImpl error
심각: failed sending message to FLPCOA01-35801 (83 bytes):
java.lang.Exception: Queue closed since sender thread has died,
running=false, underlying connection open= false
Thanks for your help.
--
Blessings.
Kuwon Kang
............................................................
IT specialist and architect.
Java technology engineer.
JavaEE architect/developer.
Spring Framework specialist.
Solution developer.
- Model Driven Architecture.
- Test Driven Development.
- Test Driven Software Design.
- Refactoring Oriented Development.
- Practical design and modeling.
- Robust Software Design and Engineering.
............................................................
Prever,Inc.
http://www.prever.co.kr/
Blog:
http://josh.prever.co.kr/
............................................................
God's love is eternal and leads us to live for heaven and His glory
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Javagroups-development mailing list