[jira] [Commented] (CASSANDRA-14883) Let Cassandra support the new JVM, Eclipse Openj9.
[
https://issues.apache.org/jira/browse/CASSANDRA-14883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837144#comment-16837144
]
Alexandre Vermeerbergen commented on CASSANDRA-14883:
-
[~bdeggleston], no I do not have this message - and actually sorry my
production install is still in 2.2.x and not yet in 3.x.
When starting cassandra 2.2.15 (having replaced jamm-0.3.0.jar by
jamm-0.3.3.jar in lib/) with latest AdoptOpenJDK 8 (update 212) with OpenJ9 on
Linux, I get exactly the message quoted in current JIRA:
{{WARN 10:13:34 Non-Oracle JVM detected. Some features, such as immediate
unmap of compacted SSTables, may not work as intended}}
So again, should I fill a Jira for dependency upgrade of jamm to 0.3.3 or is
current Jira enought to track both this dependency update and the rewording or
removal of the "superflous message"?
Kind regards,
Alexandre Vermeerbergen
> Let Cassandra support the new JVM, Eclipse Openj9.
> --
>
> Key: CASSANDRA-14883
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14883
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Environment: jdk8u192-b12_openj9-0.11.0
> cassandra 4.0.0_beta_20181109_build
>Reporter: Lee Sangboo
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: jamm-0.3.2.jar, jamm.zip
>
>
> Cassandra does not currently support the new JVM, Eclipse Openj9. In internal
> testing, Openj9 outperforms Hotspot. I have deployed a modified jamm library
> that has a problem with the current startup, but when I started Cassandra, I
> got a log message saying "Non-Oracle JVM detected." Some features, such as
> unimported compact SSTables, may not work as intended "If there is no
> problem, I would also like to delete the above message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14883) Let Cassandra support the new JVM, Eclipse Openj9.
[
https://issues.apache.org/jira/browse/CASSANDRA-14883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835874#comment-16835874
]
Blake Eggleston commented on CASSANDRA-14883:
-
[~avermeerbergen] do you see this message when starting your Cassandra 3.x
install with OpenJ9?
{quote}Cannot initialize un-mmaper. (Are you using a non-Oracle JVM?) Compacted
data files will not be removed promptly. Consider using an Oracle JVM or using
standard disk access mode{quote}
> Let Cassandra support the new JVM, Eclipse Openj9.
> --
>
> Key: CASSANDRA-14883
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14883
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Environment: jdk8u192-b12_openj9-0.11.0
> cassandra 4.0.0_beta_20181109_build
>Reporter: Lee Sangboo
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: jamm-0.3.2.jar, jamm.zip
>
>
> Cassandra does not currently support the new JVM, Eclipse Openj9. In internal
> testing, Openj9 outperforms Hotspot. I have deployed a modified jamm library
> that has a problem with the current startup, but when I started Cassandra, I
> got a log message saying "Non-Oracle JVM detected." Some features, such as
> unimported compact SSTables, may not work as intended "If there is no
> problem, I would also like to delete the above message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14883) Let Cassandra support the new JVM, Eclipse Openj9.
[ https://issues.apache.org/jira/browse/CASSANDRA-14883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835128#comment-16835128 ] Alexandre Vermeerbergen commented on CASSANDRA-14883: - Hello, I have a need to run Cassandra with OpenJ9 latest version from AdoptOpenJDK8. I have manually patched my install with jamm 0.3.3 and I get the annoying messages mentioned in this JIRA, but have seen no special issues with OpenJ9 apart from these messages, and I see in current thread that these messages are superfluous. I would like to move our Cassandra servers in production with OpenJ9, so I'd like to see how we could move forward with this JIRA for the next fix releases (maybe not waiting for 4.0.x which has no firm date as far as I know) and get rid of the "superfluous" messages since they can scare my IT people who might think we would be running with an unsupported VM type (although it's already widely used for our other applications). Questions: * In trunk we still have *jamm dependency at version 0.3.2*, meaning that by default it fails with OpenJ9 because it's missing this fix: [https://github.com/jbellis/jamm/commit/c712f6b59563a887293fb9832473d402fef25511]. I can open a dedicated JIRA for a jamm dependency update to version *0.3.3* if there none already existing (I haven't found such JIRA), unless current JIRA is supposed to include this dependency update. Is that assumed so? * Current JIRA is flagged for 4.0.x, but my need to is to use OpenJ9 with currently officially released versions of Cassandra. Would there be any objection to tag this JIRA, for say, 3.11.5 version (as the fix sounds reasonably simple) and why not also for older releases who can used in production by other people willing to switch from ORACLE to OpenJ9 (guess why)? Kind regards, Alexandre Vermeerbergen > Let Cassandra support the new JVM, Eclipse Openj9. > -- > > Key: CASSANDRA-14883 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14883 > Project: Cassandra > Issue Type: Improvement > Components: Packaging > Environment: jdk8u192-b12_openj9-0.11.0 > cassandra 4.0.0_beta_20181109_build >Reporter: Lee Sangboo >Priority: Normal > Fix For: 4.0.x > > Attachments: jamm-0.3.2.jar, jamm.zip > > > Cassandra does not currently support the new JVM, Eclipse Openj9. In internal > testing, Openj9 outperforms Hotspot. I have deployed a modified jamm library > that has a problem with the current startup, but when I started Cassandra, I > got a log message saying "Non-Oracle JVM detected." Some features, such as > unimported compact SSTables, may not work as intended "If there is no > problem, I would also like to delete the above message. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14883) Let Cassandra support the new JVM, Eclipse Openj9.
[
https://issues.apache.org/jira/browse/CASSANDRA-14883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689176#comment-16689176
]
Lee Sangboo commented on CASSANDRA-14883:
-
openj9 can edit executable jamm.jar and paste.
{code:java}
// MemoryLayoutSpecification.java 191 line
final String strSpecVersion = System.getProperty("java.specification.version");
final boolean hasDot = strSpecVersion.indexOf('.') != -1;
if (hasDot) {
if ("1".equals(strSpecVersion.substring(0, strSpecVersion.indexOf('.' {
// Java 1.6, 1.7, 1.8
final String strVmVersion = System.getProperty("java.vm.version");
System.out.println("JAMM JAVA VERSION = " + strVmVersion);
if(strVmVersion.startsWith("openj")) {
modernJvm = true;
}else {
final int vmVersion = Integer.parseInt(strVmVersion.substring(0,
strVmVersion.indexOf('.')));
modernJvm = vmVersion >= 17;
};
}
}
{code}
> Let Cassandra support the new JVM, Eclipse Openj9.
> --
>
> Key: CASSANDRA-14883
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14883
> Project: Cassandra
> Issue Type: Improvement
> Components: 4.0, Packaging
> Environment: jdk8u192-b12_openj9-0.11.0
> cassandra 4.0.0_beta_20181109_build
>Reporter: Lee Sangboo
>Priority: Major
> Fix For: 4.0.x
>
> Attachments: jamm-0.3.2.jar, jamm.zip
>
>
> Cassandra does not currently support the new JVM, Eclipse Openj9. In internal
> testing, Openj9 outperforms Hotspot. I have deployed a modified jamm library
> that has a problem with the current startup, but when I started Cassandra, I
> got a log message saying "Non-Oracle JVM detected." Some features, such as
> unimported compact SSTables, may not work as intended "If there is no
> problem, I would also like to delete the above message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14883) Let Cassandra support the new JVM, Eclipse Openj9.
[ https://issues.apache.org/jira/browse/CASSANDRA-14883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689173#comment-16689173 ] Lee Sangboo commented on CASSANDRA-14883: - jamm.zip uploaded. > Let Cassandra support the new JVM, Eclipse Openj9. > -- > > Key: CASSANDRA-14883 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14883 > Project: Cassandra > Issue Type: Improvement > Components: 4.0, Packaging > Environment: jdk8u192-b12_openj9-0.11.0 > cassandra 4.0.0_beta_20181109_build >Reporter: Lee Sangboo >Priority: Major > Fix For: 4.0.x > > Attachments: jamm-0.3.2.jar, jamm.zip > > > Cassandra does not currently support the new JVM, Eclipse Openj9. In internal > testing, Openj9 outperforms Hotspot. I have deployed a modified jamm library > that has a problem with the current startup, but when I started Cassandra, I > got a log message saying "Non-Oracle JVM detected." Some features, such as > unimported compact SSTables, may not work as intended "If there is no > problem, I would also like to delete the above message. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14883) Let Cassandra support the new JVM, Eclipse Openj9.
[ https://issues.apache.org/jira/browse/CASSANDRA-14883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681729#comment-16681729 ] Nate McCall commented on CASSANDRA-14883: - Hi [~leesangboo] thanks for the report. So it sounds like the scope of this ticket from the title is an issue with the JAMM library? That log message is probably superfluous or maybe incorrect and in need of re-wording if there are going to be issues with some features on non-mainstream (probably wrong word?) JVMs. > Let Cassandra support the new JVM, Eclipse Openj9. > -- > > Key: CASSANDRA-14883 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14883 > Project: Cassandra > Issue Type: Improvement > Components: 4.0 > Environment: jdk8u192-b12_openj9-0.11.0 > cassandra 4.0.0_beta_20181109_build >Reporter: Lee Sangboo >Priority: Major > Fix For: 4.0.x > > > Cassandra does not currently support the new JVM, Eclipse Openj9. In internal > testing, Openj9 outperforms Hotspot. I have deployed a modified jamm library > that has a problem with the current startup, but when I started Cassandra, I > got a log message saying "Non-Oracle JVM detected." Some features, such as > unimported compact SSTables, may not work as intended "If there is no > problem, I would also like to delete the above message. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
