dpol1 opened a new issue, #3009: URL: https://github.com/apache/hugegraph/issues/3009
### Bug Type (问题类型) logic (逻辑设计问题) ### 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 边) --> ### Expected & Actual behavior (期望与实际表现) Follow-up from #2997 / #2740. ### Expected behavior When Cassandra is temporarily unavailable or restarted, the Cassandra backend should handle transient connectivity failures consistently between synchronous and asynchronous write paths. `CassandraSessionPool.Session.commit()` now uses `executeWithRetry()` and can retry transient failures such as `NoHostAvailableException`. `commitAsync()` should either provide equivalent retry support for async writes, or explicitly define and document different reliability semantics. ### Actual behavior `CassandraSessionPool.Session.commitAsync()` bypasses `executeWithRetry()` and calls Datastax `Session.executeAsync(...)` directly. During a Cassandra restart, async writes issued through `commitAsync()` can fail with transient driver errors such as `NoHostAvailableException`. The failure is only surfaced through the Datastax `ResultSetFuture` / `getUninterruptibly()` flow. Callers that do not inspect these futures carefully may miss failed async writes. This creates inconsistent behavior: ```text commit() -> executeWithRetry() -> transient retry support commitAsync() -> executeAsync() -> no async retry support ### Vertex/Edge example (问题点 / 边数据举例) ```javascript ``` ### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构) ```javascript ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
