Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote restart of pellet server #2

Open
bdionne opened this issue May 11, 2017 · 3 comments
Open

Remote restart of pellet server #2

bdionne opened this issue May 11, 2017 · 3 comments
Assignees

Comments

@bdionne
Copy link
Owner

bdionne commented May 11, 2017

Only sysadmins at NCI have access to the production servers so we need to be able to remotely restart the pellet server similar to what's done with the protege-server

@rgrinberg
Copy link
Collaborator

The restart mechanism will be triggered via an http endpoint like protege right?

@bdionne
Copy link
Owner Author

bdionne commented May 11, 2017

yes, I'll think we'll want to expose it from the menus also, maybe where we pause the server or in the revision history plugin, so we'll want the functionality in the client api also

@bdionne
Copy link
Owner Author

bdionne commented Aug 3, 2017

This is kind of working, this issue is tied up with #4 - If we do a restart after squashing history and producing a new snapshot, the pellet server files need to be synced up - looks like deleting both HEAD and the reasoner_state.bin is required

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants