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.

Sign up for GitHub

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

Jump to bottom

Start-stop race with services enabled. #360

Open
evoskuil opened this issue Mar 26, 2017 · 1 comment
Open

Start-stop race with services enabled. #360

evoskuil opened this issue Mar 26, 2017 · 1 comment
Assignees
@evoskuil
Labels
bug
Milestone
4.0

Comments

@evoskuil
Copy link
Member

evoskuil commented Mar 26, 2017 •
edited
Loading

There is an easy-to-repro stop race when a stop is signaled during a start. This will invalidate the store (leaves flush lock) if write flushing is not enabled. The stop signal is properly handled once but the node.close call fails to terminate the services. The cause is well documented in the server sources, just needs to be refactored to guarantee order or idempotency.
@evoskuil evoskuil added the bug label Mar 26, 2017
@evoskuil evoskuil added this to the 3.1 milestone Mar 26, 2017
@evoskuil evoskuil self-assigned this Mar 26, 2017
@evoskuil evoskuil changed the title [master] Start-stop race with services enabled. Start-stop race with services enabled. Apr 4, 2017
@evoskuil evoskuil modified the milestones: 4.0, 3.1 Apr 7, 2017
@evoskuil
Copy link
Member Author

evoskuil commented Apr 7, 2017

This is not a significant issue, defer to later release, NLT v4.0

@evoskuil evoskuil mentioned this issue Jan 1, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@evoskuil evoskuil

Labels
bug
Projects
None yet
Milestone
4.0
Development

No branches or pull requests
1 participant
@evoskuil