You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alexandre Vermeerbergen (JIRA)" <ji...@apache.org> on 2019/05/07 21:20:00 UTC
[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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org