orientechnologies / orientechnologies/orientdb-docs
server configuration file hooks disappear after server shutdown/start
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 59
- Forks
- 165
- PR merge metrics
- No merged PRs in 30d
Description
When I reboot the device, or shutdown/start Orient server the hooks in the server configuration file disappear.
OrientDB is deployed as a Kubernetes Pod and when the pod is deleted/created the hooks also disappear from the server configuration file. Is there a way to persist the hooks in the server config file through restarts without having to shutdown, add hooks, and start?
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the reported loss of server configuration hooks across an OrientDB shutdown/start and Kubernetes Pod recreation. Identify the relevant server-configuration documentation and document whether hooks can be persisted, including the Kubernetes-specific setup needed for them to survive restarts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100