Bug 1272528
Summary: | New Storage Node property file wrong parameters | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Vojta Prusa <vprusa> |
Component: | Storage Node | Assignee: | Michael Burman <miburman> |
Status: | CLOSED NOTABUG | QA Contact: | Mike Foley <mfoley> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | JON 3.3.4 | CC: | fbrychta, jsanda, skondkar, vprusa |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
RHEL 7.1
Server and remote agent registered, default location of storage
|
|
Last Closed: | 2015-10-29 14:45:39 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: |
Description
Vojta Prusa
2015-10-16 16:03:03 UTC
Additional Info: Facing the same issue when trying to verify bug#1230411. After applying the patch to already installed JBoss ON 3.3GA, and merging the 'cassandra-jvm.properties.new' with 'cassandra-jvm.properties', GUI shows the storage node availability as down. Can you share your new/updated cassandra-jvm.properties? In particular I am interested in the JMX_OPTS property. Take a look at https://bugzilla.redhat.com/show_bug.cgi?id=1229978#c4. The JMX_OPTS property should be changed to, JMX_OPTS="-Djava.rmi.server.hostname=localhost" John, could you clarify if JMX_OPTS from previous comment are correct? Because looking at bz1229978 comment 4, cassandra-jvm.properties.new contains JMX_OPTS="-Dcassandra.jmx.local.port=${jmx_port}" and not JMX_OPTS="-Djava.rmi.server.hostname=localhost" Basically when you use JMX_OPTS from .new (JMX_OPTS="-Dcassandra.jmx.local.port=${jmx_port}) storage node is down in UI, but this issue is caused by not yet updated plugins on agent side. When the plugin is updated, storage node is up. Other relevant issues from this bz are probably just following: - original cassandra-jvm.properties has jmx_port and heap and stack sizes without quotes - cassandra-jvm.properties.new has jmx_port and heap and stack sizes with quotes Quotes are causing bz1272239 |