Bug 899485 (JBPAPP6-73)
| Summary: | Dynamic-load-provider returns Load:1 regardless of load-metric set | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Michal Karm Babacek <mbabacek> | ||||
| Component: | mod_cluster | Assignee: | Michal Karm Babacek <mbabacek> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.0.0 | CC: | atangrin, mbabacek, paul.ferraro | ||||
| Target Milestone: | --- | ||||||
| Target Release: | EAP 6.0.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/JBPAPP6-73 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: |
RHEL6 x86_64, Sun Jdk (build 1.6.0_24-b07)
|
|||||
| Last Closed: | 2012-11-05 00:44:59 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: | |||||||
| Attachments: |
|
||||||
|
Description
Michal Karm Babacek
2011-08-24 16:03:22 UTC
Link: Added: This issue is a dependency of JBQA-4970 While I'm looking into this, just a side comment: defining a weight is meaningless if you only use 1 load metric. The weight of a metric represents the significance that metric's load relative to other metrics defined in the load provider. @[~pferraro] I know that thanks to our earlier conversation recorded in [DOC-73684|https://docspace.corp.redhat.com/docs/DOC-73684] ;-). I've been just playing with all the available attributes...trying to get something from it. OK - I've found a few problems... The capacity is getting defaulted to 512 for *every* type of load metric. That is very wrong. The context of the capacity value is metric-specific. Also, the weight is getting defaulted to 9, a less critical issue, but still not correct (it should default to 1). I'll file an AS7 jira. The major problem, though, is that the mod_cluster server-side component is never informed of the mbean server. Every existing load metric requires access to the mbean server to calculate their load. No wonder none of them work. I'll file a separate AS7 jira for this. I've just wanted to say it doesn't work even with [jboss-as-7.1.0.Alpha1-SNAPSHOT|https://github.com/jfclere/jboss-as/] from [~jfclere]'s GitHub; however now it's clear it does not work anywhere :-) Thank's Paul for looking into it. Actually, I'm afraid I was barking up the wrong tree. The load metrics *should* still work, since they would attempt to use the platform mbean server. However, the real problem lies in the AS7 ModClusterService, which is reading the model wrong. *sigh* I'll close the irrelevant jiras and reopen a new one. Link: Added: This issue depends AS7-1648 FYI - here's the pull request that fixes this issue. https://github.com/jbossas/jboss-as/pull/223 Attachment: Added: load.png [Commented on GitHub|https://github.com/jbossas/jboss-as/pull/223#issuecomment-1911098], looks OK so far. We've got even a nice picture with {code:xml} <mod-cluster-config advertise-socket="modcluster"> <dynamic-load-provider history="10" decay="2"> <load-metric type="cpu" capacity="1"/> </dynamic-load-provider> </mod-cluster-config> {code} !load.png|thumbnail! ...values are weird a bit though; however that is yet to be tested during the proper test cycle... Scheduling this for DR4, as the upstream issue is fixed for AS 7.1.0.Alpha1 Resolving this issue as it is fixed upstream in AS 7.1.0.Alpha1 and will be available in DR4 build. Please verify in DR4. It was verified quite some time ago, I just forgot to close it: *closing* Docs QE Status: Removed: NEW Fixing Affects and Fix in Version |