JanusGraph / JanusGraph/janusgraph
Automatic detection and forced closing of a dead instance
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
We are having quite a bit of problem with schema management when there is one or more dead instances. Gremlin server container crashes or does unclean shutdown somehow and we need to find and clean that dead instance before trying to make a schema change, in particular - adding of an index.
I think with the existing syslog mechanism JG could easily implement some sort of "heartbeat" mechanism where a dead instance would be automatically detected after a couple of minutes and force-closed by all cluster nodes.
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 with the existing syslog mechanism and the schema-management flow, focusing on how adding an index is blocked by dead Gremlin Server instances. Define the detection and force-closing behavior for instances that have been unresponsive for a few minutes, with surviving cluster nodes handling cleanup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100