JanusGraph / JanusGraph/janusgraph
Connection timeout ignored by CQL backend
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
`storage.connection-timeout` setting is not used by CQLStoreManager (Thrift backend takes this setting into account). Probably something like this along the lines of `initializeCluster` is needed:
```
if (configuration.has(CONNECTION_TIMEOUT)) {
builder.withSocketOptions(new SocketOptions()
.setConnectTimeoutMillis((int) configuration.get(CONNECTION_TIMEOUT).toMillis()));
}
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at CQLStoreManager.initializeCluster and compare how the Thrift backend uses the storage.connection-timeout setting. Ensure the CQL backend applies that setting to its connection configuration, then verify that the configured timeout is honored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100