-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Question: Do we need any logic on shutdown? #17
Comments
@auxten I was able to create a repro in a single file. Here is an example:
I get the error on every 2-3 runs. I am waiting till I see the message "Press Ctrl+C to stop the script." and I press Ctrl+C few seconds after that. System info:
|
I should fix this issue first chdb-io/chdb#197 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have been playing with chdb-node a lot lately - exploring what can I do with the project. I am working on a proof of concept a local emulator of a cloud based datawarehouse.
I programmed a lot logic in a single index.js file and I was running and stopping the index.js a few times a day.
Today I got a strange error after is was trying to start again the index.js with recent changes:
Attempt 1:
Attempt 2::
After deleting the chdb data folder everything started working fine.
Here comes the question:
We we need to do or can we do something on SIGINT and SIGTERM ? I suppose that there could be cases where we could cause data corruption if we do not stop properly chdb while chdb is still processing data.
For example I noticed this code fragment in another project that takes requests and writes them to file system:
Full source code here: https://github.com/Azure/Azurite/blob/76f626284e4b4b58b95065bb3c92351f30af7f3d/src/blob/main.ts
The text was updated successfully, but these errors were encountered: