cassandra 2.0.4无法初始化MemoryMeter [英] cassandra 2.0.4 Unable to initialize MemoryMeter
问题描述
我已在5个节点的群集上将cassandra从1.2.13升级到2.0.4。
，当我运行nodetool -h localhost ring时，我最终看到此错误消息：
I've upgraded cassandra from 1.2.13 to 2.0.4 on a cluster of 5 nodes. when i run nodetool -h localhost ring I see this errormessage in the end:
错误10：33：28,324无法初始化MemoryMeter（未将jam指定为javaagent）。这意味着Cassandra将无法准确地测量对象的大小，因此可能会导致OOM。
ERROR 10:33:28,324 Unable to initialize MemoryMeter (jamm not specified as javaagent). This means Cassandra will be unable to measure object sizes accurately and may consequently OOM.
据此：
https://issues.apache.org/jira/browse/CASSANDRA-6404
它应该是固定的。
我正在运行java-1.7.0-oracle-1.7.0.45-1jpp.2.el6_4.x86_64。
it should be fixed. i'm running java-1.7.0-oracle-1.7.0.45-1jpp.2.el6_4.x86_64.
这是过程的开始选项：
/usr/lib/jvm/java-1.7.0-oracle-1.7.0.45.x86_64/jre/bin/java -ea -javaagent：/usr/share/cassandra//lib/jamm-0.2 .5.jar
this is the beginning of the process options: /usr/lib/jvm/java-1.7.0-oracle-1.7.0.45.x86_64/jre/bin/java -ea -javaagent:/usr/share/cassandra//lib/jamm-0.2.5.jar
有没有人能指出我在寻找解决方案的方向？
is there anyone who could point me in a direction where too look for a solution?
这些错误是严重的还是仅仅是表面上的？
these error's, are they serious or mere cosmetic?
// john
推荐答案
如果仅从工具发出此错误，则忽略。如果您还在output.log或system.log中看到它，则可能会出现问题。看来您的JVM版本不错。如果您在此处粘贴的命令提示符来自Cassandra进程，那么您就很好。工具具有不同的脚本来初始化其环境。检查cassandra / bin文件夹并检查工具的脚本以查看它们是否包含此更改：
If this error only emits from tools, then ignore. If you also see it in your output.log or system.log, then it can be problematic. It seems your version of JVM is good. If the command prompt you pasted here is from Cassandra process, then you are good. Tools have a different script to initialize their environment. Check cassandra/bin folder and inspect tools' scripts to see if they include this change:
机会在某种程度上使您的升级过程没有改变。
Chances are somehow your upgrade process didn't change them.
这篇关于cassandra 2.0.4无法初始化MemoryMeter的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
