Show Table of Contents
For more information on the configuration files included with JBoss Data Grid refer to Section A.6, “JBoss Data Grid JGroups Configuration Files”.
A.3. UDP Default and Recommended Values
To learn more about JGroups and using TCP and UDP, see Section 30.2, “Configure JGroups (Library Mode)”.
Note
- Values in
JGroups Default Valueindicate values that are configured internally to JGroups, but may be overridden by a custom configuration file or by a JGroups configuration file shipped with JBoss Data Grid. - Values in
JBoss Data Grid Configured Valuesindicate values that are in use by default when using one of the configuration files for JGroups as shipped with JBoss Data Grid. It is recommended to use these values when custom configuration files for JGroups are in use with JBoss Data Grid.
Table A.17. Recommended Values for UDP
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| bind_addr | Any non-loopback | Set address on specific interface |
| bind_port | Any free port | Set specific port |
| loopback | true | true |
| port_range | 50 | Set based on desired range of ports |
| mcast_addr | 228.8.8.8 | Same as default |
| mcast_port | 7600 | Same as default |
| tos | 8 | Same as default |
| ucast_recv_buf_size | 64,000 | 20,000,000 |
| ucast_send_buf_size | 100,000 | 1,000,000 |
| mcast_recv_buf_size | 500,000 | 25,000,000 |
| mcast_send_buf_size | 100,000 | 1,000,000 |
| ip_ttl | 8 | 2 |
| thread_naming_pattern | cl | pl |
| max_bundle_size | 64,000 | Same as default |
| enable_diagnostics | true | false |
| thread_pool.enabled | true | Same as default |
| thread_pool.min_threads | 2 | This should equal the number of nodes. |
| thread_pool.max_threads | 30 | This should be higher than thread_pool.min_threads. For example, for a smaller grid (2-10 nodes), set this value to twice the number of nodes, but for a larger grid (20 or more nodes), the ratio should be lower. As an example, if a grid contains 20 nodes, set this value to 25 and if the grid contains 100 nodes, set the value to 110. |
| thread_pool.keep_alive_time | 30,000 | 60,000 |
| thread_pool.queue_enabled | true | false |
| thread_pool.queue_max_size | 500 | None, queue should be disabled |
| thread_pool.rejection_policy | Discard | Same as default |
| internal_thread_pool.enabled | true | Same as default |
| internal_thread_pool.min_threads | 2 | 5 |
| internal_thread_pool.max_threads | 4 | 20 |
| internal_thread_pool.keep_alive_time | 30,000 | 60,000 |
| internal_thread_pool.queue_enabled | true | false |
| internal_thread_pool.rejection_policy | Discard | Abort |
| oob_thread_pool.enabled | true | Same as default |
| oob_thread_pool.min_threads | 2 | 20 or higher |
| oob_thread_pool.max_threads | 10 | 200 or higher based on the load |
| oob_thread_pool.keep_alive_time | 30,000 | 60,000 |
| oob_thread_pool.queue_enabled | true | false |
| oob_thread_pool.queue_max_size | 500 | None, queue should be disabled |
| oob_thread_pool.rejection_policy | Discard | Same as default |
Note
In JGroups 3.5, the PING timeout value is removed and the pbcast.GMS
join_timeout value indicates the timeout period instead.
Table A.18. Recommended Values for MERGE3
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| min_interval | 1,000 | 10,000 |
| max_interval | 10,000 | 30,000 |
Table A.19. Recommended Values for FD_SOCK
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| client_bind_por | 0 (randomly selects a port and uses it) | Same as default |
| get_cache_timeout | 1000 milliseconds | Same as default |
| keep_alive | true | Same as default |
| num_tries | 3 | Same as default |
| start_port | 0 (randomly selects a port and uses it) | Same as default |
| suspect_msg_interval | 5000 milliseconds. | Same as default |
Table A.20. Recommended Values for FD_ALL
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| timeout | 40,000 | 60,000. The FD_ALL timeout value is set to two times the longest possible stop the world garbage collection pause in the CMS garbage collector. In a well-tuned JVM, the longest pause is proportional to heap size and should not exceed 1 second per GB of heap. For example, an 8GB heap should not have a pause longer than 8 seconds, so the FD_ALL timeout value must be set to 16 seconds. If longer garbage collection pauses are used, then this timeout value should be increased to avoid false failure detection on a node. |
| interval | 8,000 | 15,000. The FD_ALL interval value must be at least four times smaller than the value set for FD_ALL's timeout value. |
| timeout_check_interval | 2,000 | 5,000 |
Table A.21. Recommended Values for FD_HOST
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| check_timeout | 3,000 | 5,000 |
| cmd | InetAddress.isReachable() (ICMP ping) | - |
| interval | 20,000 | 15,000. The interval value for FD_HOST must be four times smaller than FD_HOST's timeout value. |
| timeout | - | 60,000. |
Table A.22. Recommended Values for VERIFY_SUSPECT
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| timeout | 2,000 | 5,000 |
Table A.23. Recommended Values for pbcast.NAKACK2
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| use_mcast_xmit | true | false |
| xmit_interval | 1,000 | Same as default |
| xmit_table_num_rows | 50 | 50 |
| xmit_table_msgs_per_row | 10,000 | 1,024 |
| xmit_table_max_compaction_time | 10,000 | 30,000 |
| max_msg_batch_size | 100 | Same as default |
| resend_last_seqno | false | true |
Table A.24. Recommended Values for UNICAST3
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| xmit_interval | 500 | Same as default |
| xmit_table_num_rows | 100 | 50 |
| xmit_table_msgs_per_row | 1,0000 | 1,024 |
| xmit_table_max_compaction_time | 600,000 | 30,000 |
| max_msg_batch_size | 500 | 100 |
| conn_close_timeout | 60,000 | No recommended value |
| conn_expiry_timeout | 120,000 | 0 |
Table A.25. Recommended Values for pbcast.STABLE
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| stability_delay | 6,000 | 500 |
| desired_avg_gossip | 20,000 | 5,000 |
| max_bytes | 2,000,000 | 1,000,000 |
Table A.26. Recommended Values for pbcast.GMS
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| print_local_addr | true | false |
| join_timeout | 5,000 | 15,000 |
| view_bundling | true | Same as default |
Table A.27. Recommended Values for UFC
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| max_credits | 500,000 | 2,000,000 |
| min_threshold | 0.40 | Same as default |
Table A.28. Recommended Values for MFC
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| max_credits | 500,000 | 2,000,000 |
| min_threshold | 0.40 | Same as default |
Table A.29. Recommended Values for FRAG2
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| frag_size | 60,000 | Same as default |
Table A.30. Recommended Values for SYM_ENCRYPT
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| sym_algorithm | AES | - |
| sym_keylength | 128 | - |
| sym_provider | Bouncy Castle Provider | - |
Table A.31. Recommended Values for ASYM_ENCRYPT
| Parameter | JGroups Default Value | JBoss Data Grid Configured Values |
|---|---|---|
| asym_algorithm | RSA | - |
| asym_keylength | 512 | - |
| asym_provider | Bouncy Castle Provider | - |
| change_keys_on_leave | false | - |
Recommended Values for SASL
See the Red Hat JBoss Data Grid Developer Guide's User Authentication over Hot Rod Using SASL section for details.
Recommended Values for RELAY2
See Chapter 35, Set Up Cross-Datacenter Replication for details.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.