NO-JIRA update missed docs for JGroups upgrade
This commit is contained in:
parent
0e799ca1c9
commit
c3b304779e
|
@ -178,56 +178,38 @@ following:
|
||||||
The following is an example of a JGroups file
|
The following is an example of a JGroups file
|
||||||
|
|
||||||
```xml
|
```xml
|
||||||
<config xmlns="urn:org:jgroups"
|
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
||||||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
xmlns="urn:org:jgroups"
|
||||||
xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/JGroups-3.0.xsd">
|
xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd">
|
||||||
<TCP loopback="true"
|
<TCP bind_addr="${jgroups.bind_addr:site_local}"
|
||||||
recv_buf_size="20000000"
|
bind_port="${jgroups.bind_port:7800}"
|
||||||
send_buf_size="640000"
|
external_addr="${jgroups.external_addr}"
|
||||||
discard_incompatible_packets="true"
|
external_port="${jgroups.external_port}"
|
||||||
max_bundle_size="64000"
|
thread_pool.min_threads="0"
|
||||||
max_bundle_timeout="30"
|
thread_pool.max_threads="200"
|
||||||
enable_bundling="true"
|
thread_pool.keep_alive_time="30000"/>
|
||||||
use_send_queues="false"
|
<RED/>
|
||||||
sock_conn_timeout="300"
|
|
||||||
|
|
||||||
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="run"
|
|
||||||
|
|
||||||
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="run"/>
|
|
||||||
|
|
||||||
|
<!-- a location that can be found by both server's running -->
|
||||||
<FILE_PING location="../file.ping.dir"/>
|
<FILE_PING location="../file.ping.dir"/>
|
||||||
<MERGE2 max_interval="30000"
|
<MERGE3 min_interval="10000"
|
||||||
min_interval="10000"/>
|
max_interval="30000"/>
|
||||||
<FD_SOCK/>
|
<FD_SOCK2/>
|
||||||
<FD timeout="10000" max_tries="5" />
|
<FD_ALL3 timeout="40000" interval="5000" />
|
||||||
<VERIFY_SUSPECT timeout="1500" />
|
<VERIFY_SUSPECT2 timeout="1500" />
|
||||||
<BARRIER />
|
<BARRIER />
|
||||||
<pbcast.NAKACK
|
<pbcast.NAKACK2 use_mcast_xmit="false" />
|
||||||
use_mcast_xmit="false"
|
<UNICAST3 />
|
||||||
retransmit_timeout="300,600,1200,2400,4800"
|
<pbcast.STABLE desired_avg_gossip="50000"
|
||||||
discard_delivered_msgs="true"/>
|
max_bytes="4M"/>
|
||||||
<UNICAST timeout="300,600,1200" />
|
<pbcast.GMS print_local_addr="true" join_timeout="2000"/>
|
||||||
<pbcast.STABLE stability_delay="1000" desired_avg_gossip="50000"
|
<UFC max_credits="2M"
|
||||||
max_bytes="400000"/>
|
min_threshold="0.4"/>
|
||||||
<pbcast.GMS print_local_addr="true" join_timeout="3000"
|
<MFC max_credits="2M"
|
||||||
view_bundling="true"/>
|
min_threshold="0.4"/>
|
||||||
<FC max_credits="2000000"
|
<FRAG2 frag_size="60K" />
|
||||||
min_threshold="0.10"/>
|
<!--RSVP resend_interval="2000" timeout="10000"/-->
|
||||||
<FRAG2 frag_size="60000" />
|
|
||||||
<pbcast.STATE_TRANSFER/>
|
<pbcast.STATE_TRANSFER/>
|
||||||
<pbcast.FLUSH timeout="0"/>
|
|
||||||
</config>
|
</config>
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
|
@ -141,6 +141,15 @@ Highlights:
|
||||||
drop it or execute the proper `ALTER TABLE` statement for your database. If you
|
drop it or execute the proper `ALTER TABLE` statement for your database. If you
|
||||||
drop the table then it will be automatically recreated when broker restarts and
|
drop the table then it will be automatically recreated when broker restarts and
|
||||||
repopulated with a new, auto-generated node ID.
|
repopulated with a new, auto-generated node ID.
|
||||||
|
3. **If you're using JGroups** then due to the changes in
|
||||||
|
[ARTEMIS-2413](https://issues.apache.org/jira/browse/ARTEMIS-2413) where JGroups
|
||||||
|
was updated from 3.x to 5.x you will need to update your JGroups configuration.
|
||||||
|
Many of the protocols have changed, and there's no automated tool to bring legacy
|
||||||
|
configurations up to date so please refer to the
|
||||||
|
[JGroups documentation](http://jgroups.org/manual5/index.html#protlist) for more
|
||||||
|
details on the new configuration. You can find example configurations in the
|
||||||
|
[JGroups repository](https://github.com/belaban/JGroups/tree/master/conf) (e.g.
|
||||||
|
`tcp.xml` and `udp.xml`).
|
||||||
|
|
||||||
|
|
||||||
## 2.20.0
|
## 2.20.0
|
||||||
|
|
Loading…
Reference in New Issue