[Bug] After long running Hugegraph, hg-server container status turned unhealty

### Bug Type (问题类型)

server status (启动/运行异常)

### 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.7.0 (Apache Release Version)
- Backend: HStore x 1, SSD
- OS: 4 vCPUs, 8 G RAM, Alinux 4
- Data Size: 100k edges

### Expected & Actual behavior (期望与实际表现)

Server should run in healthy status. If anything wrong happened, it should make some log. But I use `docker logs` command got nothing back.

Is there anything logging relative configuration exists? I wish I could use `docker logs` or some way to visit verbose server log

### Vertex/Edge example (问题点 / 边数据举例)

```javascript

```

### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)

```javascript

```

Start by reproducing the long-running hg-server container failure on HugeGraph 1.7.0 with the stated HStore, OS, CPU, memory, and data-size environment. Inspect the container health status and compare its output with `docker logs`; done means identifying why it becomes unhealthy and establishing a way to expose the relevant server logs.

Written by the indexing model from the issue text.