doc: update Scylladb integration faq (#371) d6c6bcc

docs/_print/index.html

@@ -7809,7 +7809,7 @@
 </span></span></code></pre></div><h6 id=response-body-1>Response Body</h6><div class=highlight><pre tabindex=0 style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-json data-lang=json><span style=display:flex><span><span style=color:#000;font-weight:700>{</span>
 </span></span><span style=display:flex><span>    <span style=color:#204a87;font-weight:700>&#34;mode&#34;</span><span style=color:#000;font-weight:700>:</span> <span style=color:#4e9a06>&#34;RESTORING&#34;</span>
 </span></span><span style=display:flex><span><span style=color:#000;font-weight:700>}</span>
-</span></span></code></pre></div></div><div class=td-content style=page-break-before:always><h1 id=pg-3465b699399f48689cdc6b5e59a10d69>6.5 - FAQ</h1><ul><li><p>How to choose the back-end storage? Choose RocksDB or Cassandra or Hbase or Mysql?</p><p>Judge according to your specific needs. Generally, if the stand-alone machine or the data volume is &lt; 10 billion, RocksDB is recommended, and other back-end clusters that use distributed storage are recommended.</p></li><li><p>Prompt when starting the service: <code>xxx (core dumped) xxx</code></p><p>Please check if the JDK version is Java 11, at least Java 8 is required</p></li><li><p>The service is started successfully, but there is a prompt similar to &ldquo;Unable to connect to the backend or the connection is not open&rdquo; when operating the graph</p><p>init-storeBefore starting the service for the first time, you need to use the initialization backend first , and subsequent versions will prompt more clearly and directly.</p></li><li><p>Do all backends need to be executed before use init-store, and can the serialization options be filled in at will?</p><p>Except memorynot required, other backends are required, such as: <code>cassandra</code>, <code>hbaseand</code>, <code>rocksdb</code>, etc. Serialization needs to be one-to-one correspondence and cannot be filled in at will.</p></li><li><p>Execution <code>init-store</code> error: <code>Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/librocksdbjni3226083071221514754.so: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.10' not found (required by /tmp/librocksdbjni3226083071221514754.so)</code></p><p>RocksDB requires gcc 4.3.0 (GLIBCXX_3.4.10) and above</p></li><li><p>The error <code>NoHostAvailableException</code> occurred while executing <code>init-store.sh</code>.</p><p><code>NoHostAvailableException</code> means that the <code>Cassandra</code> service cannot be connected to. If you are sure that you want to use the Cassandra backend, please install and start this service first. As for the message itself, it may not be clear enough, and we will update the documentation to provide further explanation.</p></li><li><p>The <code>bin</code> directory contains <code>start-hugegraph.sh</code>, <code>start-restserver.sh</code> and <code>start-gremlinserver.sh</code>. These scripts seem to be related to startup. Which one should be used?</p><p>Since version 0.3.3, GremlinServer and RestServer have been merged into HugeGraphServer. To start, use start-hugegraph.sh. The latter two will be removed in future versions.</p></li><li><p>Two graphs are configured, the names are <code>hugegraph</code> and <code>hugegraph1</code>, and the command to start the service is <code>start-hugegraph.sh</code>. Is only the hugegraph graph opened?</p><p><code>start-hugegraph.sh</code> will open all graphs under the graphs of <code>gremlin-server.yaml</code>. The two have no direct relationship in name</p></li><li><p>After the service starts successfully, garbled characters are returned when using <code>curl</code> to query all vertices</p><p>The batch vertices/edges returned by the server are compressed (gzip), and can be redirected to <code>gunzip</code> for decompression (<code>curl http://example | gunzip</code>), or can be sent with the <code>postman</code> of <code>Firefox</code> or the <code>restlet</code> plug-in of Chrome browser. request, the response data will be decompressed automatically.</p></li><li><p>When using the vertex Id to query the vertex through the <code>RESTful API</code>, it returns empty, but the vertex does exist</p><p>Check the type of the vertex ID. If it is a string type, the &ldquo;id&rdquo; part of the API URL needs to be enclosed in double quotes, while for numeric types, it is not necessary to enclose the ID in quotes.</p></li><li><p>Vertex Id has been double quoted as required, but querying the vertex via the RESTful API still returns empty</p><p>Check whether the vertex id contains <code>+</code>, <code>space</code>, <code>/</code>, <code>?</code>, <code>%</code>, <code>&</code>, and <code>=</code> reserved characters of these <code>URLs</code>. If they exist, they need to be encoded. The following table gives the coded values:</p><div class=highlight><pre tabindex=0 style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-fallback data-lang=fallback><span style=display:flex><span>special character | encoded value
+</span></span></code></pre></div></div><div class=td-content style=page-break-before:always><h1 id=pg-3465b699399f48689cdc6b5e59a10d69>6.5 - FAQ</h1><ul><li><p>How to choose the back-end storage? Choose RocksDB, Cassandra, ScyllaDB, Hbase or Mysql?</p><p>The choice of backend storage depends on specific needs. For installations on a single machine (node) with data volumes under 10 billion records, RocksDB is generally recommended. However, if a distributed backend is needed for scaling across multiple nodes, other options should be considered. ScyllaDB, designed as a drop-in replacement for Cassandra, offers protocol compatibility and better hardware utilization, often requiring less infrastructure. HBase, on the other hand, requires a Hadoop ecosystem to function effectively. Finally, while MySQL supports horizontal scaling, managing it in a distributed setup can be challenging.</p></li><li><p>Prompt when starting the service: <code>xxx (core dumped) xxx</code></p><p>Please check if the JDK version is Java 11, at least Java 8 is required</p></li><li><p>The service is started successfully, but there is a prompt similar to &ldquo;Unable to connect to the backend or the connection is not open&rdquo; when operating the graph</p><p>init-storeBefore starting the service for the first time, you need to use the initialization backend first , and subsequent versions will prompt more clearly and directly.</p></li><li><p>Do all backends need to be executed before use init-store, and can the serialization options be filled in at will?</p><p>Before running the <code>init-store.sh</code> command to create the databases that will host the graphs defined in the configuration file, the back-end must be properly configured and running. The only exception is when using memory as the back-end. Supported back-ends include <code>cassandra</code>, <code>hbase</code>, <code>rocksdb</code>, <code>scylladb</code>, etc. It’s important to note that serialization must maintain a strict one-to-one correspondence and cannot be assigned differntly than the recommended values.</p></li><li><p>Execution <code>init-store</code> error: <code>Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/librocksdbjni3226083071221514754.so: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.10' not found (required by /tmp/librocksdbjni3226083071221514754.so)</code></p><p>RocksDB requires gcc 4.3.0 (GLIBCXX_3.4.10) and above</p></li><li><p>The error <code>NoHostAvailableException</code> occurred while executing <code>init-store.sh</code>.</p><p><code>NoHostAvailableException</code> means that the <code>Cassandra</code> service cannot be connected to. If you are sure that you want to use the Cassandra backend, please install and start this service first. As for the message itself, it may not be clear enough, and we will update the documentation to provide further explanation.</p></li><li><p>The <code>bin</code> directory contains <code>start-hugegraph.sh</code>, <code>start-restserver.sh</code> and <code>start-gremlinserver.sh</code>. These scripts seem to be related to startup. Which one should be used?</p><p>Since version 0.3.3, GremlinServer and RestServer have been merged into HugeGraphServer. To start, use start-hugegraph.sh. The latter two will be removed in future versions.</p></li><li><p>Two graphs are configured, the names are <code>hugegraph</code> and <code>hugegraph1</code>, and the command to start the service is <code>start-hugegraph.sh</code>. Is only the hugegraph graph opened?</p><p><code>start-hugegraph.sh</code> will open all graphs under the graphs of <code>gremlin-server.yaml</code>. The two have no direct relationship in name</p></li><li><p>After the service starts successfully, garbled characters are returned when using <code>curl</code> to query all vertices</p><p>The batch vertices/edges returned by the server are compressed (gzip), and can be redirected to <code>gunzip</code> for decompression (<code>curl http://example | gunzip</code>), or can be sent with the <code>postman</code> of <code>Firefox</code> or the <code>restlet</code> plug-in of Chrome browser. request, the response data will be decompressed automatically.</p></li><li><p>When using the vertex Id to query the vertex through the <code>RESTful API</code>, it returns empty, but the vertex does exist</p><p>Check the type of the vertex ID. If it is a string type, the &ldquo;id&rdquo; part of the API URL needs to be enclosed in double quotes, while for numeric types, it is not necessary to enclose the ID in quotes.</p></li><li><p>Vertex Id has been double quoted as required, but querying the vertex via the RESTful API still returns empty</p><p>Check whether the vertex id contains <code>+</code>, <code>space</code>, <code>/</code>, <code>?</code>, <code>%</code>, <code>&</code>, and <code>=</code> reserved characters of these <code>URLs</code>. If they exist, they need to be encoded. The following table gives the coded values:</p><div class=highlight><pre tabindex=0 style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-fallback data-lang=fallback><span style=display:flex><span>special character | encoded value
 </span></span><span style=display:flex><span>------------------| -------------
 </span></span><span style=display:flex><span>+                 | %2B
 </span></span><span style=display:flex><span>space             | %20