aroundabout opened a new issue, #2343:
URL: https://github.com/apache/incubator-hugegraph/issues/2343

   ### Problem Type (问题类型)
   
   performance (性能优化)
   
   ### Before submit
   
   - [X] 我已经确认现有的 [Issues](https://github.com/apache/hugegraph/issues) 与 
[FAQ](https://hugegraph.apache.org/docs/guides/faq/) 中没有相同 / 重复问题 (I have 
confirmed and searched that there are no similar problems in the historical 
issue and documents)
   
   ### Environment (环境信息)
   
   - Server Version: 1.0.0 (Apache Release Version)
   - Backend: RocksDB x nodes, HDD or SSD 
   - OS: xx CPUs, xx G RAM, Ubuntu 2x.x / CentOS 7.x 
   - Data Size:  xx vertices, xx edges <!-- (like 1000W 点, 9000W 边) -->
   
   
   ### Your Question (问题描述)
   
   In the current Dockerfile, we use a shell to run three shell in order:
   
   ```Dockerfile
   ENTRYPOINT ["/usr/bin/dumb-init", "--"]
   CMD ["./docker-entrypoint.sh"]
   ```
   
   In `docker-entrypoint.sh`
   ```sh
   ./bin/wait-storage.sh
   ./bin/init-store.sh
   ./bin/start-hugegraph.sh -d false -j "$JAVA_OPTS" -g zgc
   ```
   
   There are some question:
   
   1. Can the `dumb-init` work correctly or does it still make sense to use 
`dumb-init`
   2. If the server is down, will the container exit or not
   3. If the container is down, users should do what to restart the container? 
If they use `docker start`, docker will do `wait-storage` and `init-store` 
again. And if `docker start`, is the expected result consistent with the actual 
one?
   4. The name of `docker-entrypoint.sh` seems to be inappropriate
   
   
   ### Vertex/Edge example (问题点 / 边数据举例)
   
   _No response_
   
   ### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@hugegraph.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to