Janusgraph预包装分销：Cassandra叉子超过超时

发布于 2025-02-04 06:29:04 字数 1026 浏览 3 评论 0原文

我正在计算机上安装janusgraph（以下官方指南）使数据存储在我的计算机上，这也将像客户端一样。我认为最好使用预包装的发行版（janusgraph-full-0.6.1.zip on 官方的janusgraph存储库），该存储库），它是通过样本cassandra/弹性搜索配置预先配置的。

一旦解开文件，如果我想启动Janusgraph（通过bin/janusgraph.sh start），我会获得以下结果：

> bin/janusgraph.sh start
Forking Cassandra...
Running `nodetool statusbinary`................... timeout exceeded (60 seconds)
See /<PATH_TO_JANUSGRAPH>/janusgraph-full-0.6.1/bin/../logs/cassandra.log for Cassandra log output.

虽然它说要查看/＆lt; path_to_to_to_janusgraph＆gt;///// janusgraph-full-0.6.1/bin /../ logs/cassandra.log日志，没有此类文件。

我的想法是，这种分布能够成为独立的工作，而没有任何先前安装Cassandra或弹性搜索。这是我的误解吗？如果没有，超时到底是在哪里修复？

感谢所有会阅读并花点时间的人！

原文

I am installing JanusGraph on my computer (following the official guide) such that the data is stored on my computer which will also act like the client. I figured it would be best to use the Pre-Packaged Distribution (janusgraph-full-0.6.1.zip on the official JanusGraph repository) which is pre-configured with a sample Cassandra/Elastic Search configuration.

Once I have unzipped the file, if I want to launch JanusGraph (through bin/janusgraph.sh start), I obtain the following results:

> bin/janusgraph.sh start
Forking Cassandra...
Running `nodetool statusbinary`................... timeout exceeded (60 seconds)
See /<PATH_TO_JANUSGRAPH>/janusgraph-full-0.6.1/bin/../logs/cassandra.log for Cassandra log output.

While it says to see /<PATH_TO_JANUSGRAPH>/janusgraph-full-0.6.1/bin/../logs/cassandra.log for logs, there is no such file.

My thoughts were that this Distribution was able to work as a standalone, without any prior installation of Cassandra nor Elastic Search. Is it a misunderstanding on my part? If not, where does the timeout comes and how to fix it?

Thanks to everyone who will read it and take the time!

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

梦旅人picnic 2025-02-11 06:29:04

您使用的任何Java版本降级到Java 8

解决方案：在 janusgraph.sh代码我找到了冗长的选项（与其他地方完全相同，可能是下一步的好主意时间）：

>bin/janusgraph.sh -v start
Forking Cassandra...
Running `nodetool statusbinary`.[0.000s][warning][gc] -Xloggc is deprecated. Will use -Xlog:gc:/home/pelegrin/Documents/Progs/JanusGraph/janusgraph-full-0.6.1/bin/../cassandra/bin/../logs/gc.log instead.
intx ThreadPriorityPolicy=42 is outside the allowed range [ 0 ... 1 ]
Improperly specified VM option 'ThreadPriorityPolicy=42'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

当研究intx threadprioritypolicy = 42在Google上的允许范围[0 ... 1]之外时，第一个结果之一是 cassandra和java 9上的stackoverflow问题” Java 8是解决此错误的最简单方法。

确实，安装Java 8并切换到此版本（如果需要的话，请在此处遵循答案。 a>）一切都按预期工作！

Solution: Downgrade from whatever Java version you're using to Java 8

After some slight digging in the janusgraph.sh code I found the verbose option (which is exactly the same as everywhere, might be a good idea for next time):

>bin/janusgraph.sh -v start
Forking Cassandra...
Running `nodetool statusbinary`.[0.000s][warning][gc] -Xloggc is deprecated. Will use -Xlog:gc:/home/pelegrin/Documents/Progs/JanusGraph/janusgraph-full-0.6.1/bin/../cassandra/bin/../logs/gc.log instead.
intx ThreadPriorityPolicy=42 is outside the allowed range [ 0 ... 1 ]
Improperly specified VM option 'ThreadPriorityPolicy=42'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

When researching intx ThreadPriorityPolicy=42 is outside the allowed range [ 0 ... 1 ] on Google, one of the first results is this stackoverflow question on Cassandra and Java 9, where it is said that downgrading the Java version to Java 8 is the simplest way to solve this error.

Indeed, after installing Java 8 and switching to this version (follow the answer here if needed) everything worked as expected!

回复收藏 0 原文

~没有更多了~