Bug 1158581
| Summary: | Update the product JGroups files based on the values recommended in BZ1122562 | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Alan Field <afield> |
| Component: | JGroups | Assignee: | Alan Field <afield> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Gencur <mgencur> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3.1 | CC: | bban, dmehra, dstahl, jpallich, pslavice, pzapataf, sjacobs, slaskawi, smatasar, wfink |
| Target Milestone: | ER1 | Keywords: | Reopened |
| Target Release: | 6.4.1, 6.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-04-02 12:13:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1153111 | ||
|
Description
Alan Field
2014-10-29 16:54:57 UTC
combining the information from some of my other cases , and conversations with numerous engineers, here is my executive summary: rejection_policy should always be set to "Discard" for the thread pools : OOB - Thread numbers min should be a minimum of 20 - thread number max should be a high number which should be based on load - queue should be disabled Regular thread pool - For the regular thread pool (non-OOB), min number of thread should equal to number of nodes - max number should be slightly larger , so for a small grid(2-10 nodes) the ratio could be 2 times number of nodes , but for a a large grid (20 or more nodes) the ratio should be smaller for example: -- max 25 threads on a 20 node grid -- max 110 threads on a 100 node grid. - queue should be enabled and the max default of 100 is fine Unless needed SAs or customers should probably not tune other setting unless there is a very specific reason Missed two timeout values in *PING protocols in these files: server/integration/jgroups/src/main/resources/jgroups-defaults.xml core/src/main/resources/default-configs/default-jgroups-tcp.xml These values are deprecated and will be ignored by JGroups, but will cause log messages to be written: 09:16:34,666 WARN [org.jgroups.stack.Configurator] (sc-main) JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead IMO, this isn't enough to trigger a CR3, but I'll send another PR with the changes In the JDG 6.4 CR3 build, the protocols used in the server stacks are not the same as the ones used in the embedded configuration files. Here is a PR to fix that: https://github.com/infinispan/jdg/pull/459 Verified with JDG 6.4 CR4 Verified in JDG 6.4.1 ER1 |