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

Races caused by unprotected engine access #8842

Closed
e-dard opened this issue Sep 18, 2017 · 0 comments · Fixed by #8847
Closed

Races caused by unprotected engine access #8842

e-dard opened this issue Sep 18, 2017 · 0 comments · Fixed by #8847
Assignees
@e-dard
Labels
kind/bug
Milestone
1.4.0

Comments

@e-dard
Copy link
Contributor

e-dard commented Sep 18, 2017

There are a number of unprotected accesses to the Engine, via the Store, which if triggered can lead to the server panicking.

For example:

  • Interaction between SHOW TAG VALUES and DROP DATABASE.
  • Interaction between opening a shard and DROP DATABASE.
  • Interaction between SHOW FIELD KEYS and DROP DATABASE.
  • Interaction between the monitoring service and DROP DATABASE.
@e-dard e-dard self-assigned this Sep 18, 2017
@e-dard e-dard added this to the 1.4.0 milestone Sep 18, 2017
@e-dard e-dard mentioned this issue Sep 19, 2017
Merged
3 tasks
@ghost ghost added review and removed in progress proposed labels Sep 19, 2017
@ghost ghost removed the review label Sep 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@e-dard e-dard

Labels
kind/bug
Projects
None yet
Milestone
1.4.0
Development

Successfully merging a pull request may close this issue.

Fix various engine races influxdata/influxdb
1 participant
@e-dard