英文:
Apache Ignite H2 Debug Console doesn't start
问题
OS: Ubuntu 18.04
Apache Ignite: 2.9.0
Browser: Firefox 81.0.2
我按照文档中的说明进行操作：
https://apacheignite.readme.io/docs/sql-performance-and-debugging#using-h2-debug-console
并在终端中运行了 export JVM_OPTS="-DIGNITE_H2_DEBUG_CONSOLE=true"。
然后我运行了 ./ignite.sh，但控制台根本没有启动。
我之后尝试设置了环境变量：export IGNITE_H2_DEBUG_CONSOLE=true，但同样没有成功。
日志：
https://pastebin.com/zP450eMP
要点：
[18:12:12,249][INFO][main][IgniteKernal] IGNITE_HOME=/home/me/Programs/apache-ignite-2.9.0-bin
[18:12:12,249][INFO][main][IgniteKernal] VM arguments: [-XX:+AggressiveOpts, -DIGNITE_H2_DEBUG_CONSOLE=true, -Dfile.encoding=UTF-8, -DIGNITE_QUIET=true, -DIGNITE_SUCCESS_FILE=/home/me/Programs/apache-ignite-2.9.0-bin/work/ignite_success_8a7ec5b2-6e10-4824-a98e-f3ae20e6291d, -Dcom.sun.management.jmxremote, -Dcom.sun.management.jmxremote.port=49122, -Dcom.sun.management.jmxremote.authenticate=false, -Dcom.sun.management.jmxremote.ssl=false, -DIGNITE_HOME=/home/me/Programs/apache-ignite-2.9.0-bin, -DIGNITE_PROG_NAME=./ignite.sh]
...
[18:12:13,150][WARNING][main][IgniteH2Indexing] 已启用 H2 中的 Java 对象序列化。
...
[18:12:14,809][INFO][disco-notifier-worker-#41][IgniteH2Indexing] SQL 参数 'sql.disabledFunctions' 已从 'null' 更改为 '[FILE_WRITE, CANCEL_SESSION, MEMORY_USED, CSVREAD, LINK_SCHEMA, MEMORY_FREE, FILE_READ, CSVWRITE, SESSION_ID, LOCK_MODE]'。
正如您所看到的，DIGNITE_H2_DEBUG_CONSOLE 正确地作为 JVM 选项接收，并且其值为 true。
日志中只有上述两行与 H2 相关。关于 H2 控制台或 H2 本身，没有其他错误或警告。
我应该如何启动 H2 控制台，为什么它没有自动启动呢？
英文:
OS: Ubuntu 18.04 <br>
Apache Ignite: 2.9.0 <br>
Browser: Firefox 81.0.2 <br>
I followed the documentation at:
https://apacheignite.readme.io/docs/sql-performance-and-debugging#using-h2-debug-console
and ran export JVM_OPTS="-DIGNITE_H2_DEBUG_CONSOLE=true" in my terminal.
Then I ran ./ignite.sh but it did not start the console at all.
I then tried to set the environment variable: export IGNITE_H2_DEBUG_CONSOLE=true
but again to no avail.
Logs:
https://pastebin.com/zP450eMP
Highlights:
[18:12:12,249][INFO][main][IgniteKernal] IGNITE_HOME=/home/me/Programs/apache-ignite-2.9.0-bin
[18:12:12,249][INFO][main][IgniteKernal] VM arguments: [-XX:+AggressiveOpts, -DIGNITE_H2_DEBUG_CONSOLE=true, -Dfile.encoding=UTF-8, -DIGNITE_QUIET=true, -DIGNITE_SUCCESS_FILE=/home/me/Programs/apache-ignite-2.9.0-bin/work/ignite_success_8a7ec5b2-6e10-4824-a98e-f3ae20e6291d, -Dcom.sun.management.jmxremote, -Dcom.sun.management.jmxremote.port=49122, -Dcom.sun.management.jmxremote.authenticate=false, -Dcom.sun.management.jmxremote.ssl=false, -DIGNITE_HOME=/home/me/Programs/apache-ignite-2.9.0-bin, -DIGNITE_PROG_NAME=./ignite.sh]
...
[18:12:13,150][WARNING][main][IgniteH2Indexing] Serialization of Java objects in H2 was enabled.
...
[18:12:14,809][INFO][disco-notifier-worker-#41][IgniteH2Indexing] SQL parameter 'sql.disabledFunctions' was changed from 'null' to '[FILE_WRITE, CANCEL_SESSION, MEMORY_USED, CSVREAD, LINK_SCHEMA, MEMORY_FREE, FILE_READ, CSVWRITE, SESSION_ID, LOCK_MODE]'
As you can see, DIGNITE_H2_DEBUG_CONSOLE was correctly received as a JVM option with the value of true.
The logs only had the above two lines which dealt with H2. No other error or warning was present with regards to the H2 console or H2 itself.
How do I start H2 console and why is it not starting automatically?
答案1
得分: 1
请不要使用H2控制台，它在许多版本的Apache Ignite中是不相关的，实际上在某些版本中是不可用的。不幸的是，它仍然出现在文档中。
它在Apache Ignite 2.8中被移除：IGNITE-11333
我将尝试编辑文档。
您可以使用一些外部工具，如DBeaver或内置的sqlline。
英文:
Please do not use H2 console, it is irrelevant for many releases of Apache Ignite and in fact broken in some releases. Unfortunately it still appears in the docs.
It was removed in Apache Ignite 2.8: IGNITE-11333
I will try to edit doc.
You can use some external tooling such as DBeaver or built-in sqlline.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论