-
Notifications
You must be signed in to change notification settings - Fork 369
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
DB::flush_count overflow #88
Comments
you should run the |
Note that the database is being re-architectured in #80. |
electrumx_compact_history seemed to work for me. Problem is now solved. Thank you! |
I also got this issue and posted in kyuupichan/electrumx#185 I am trying to run the compaction script as follows in this link, although it did not work for me. I am running Bitcoin Segwit rather than BCASH/BSV unlike most others running the compaction script mentioned Kyuupichan's repo. Do I have to modify this compaction script to work properly with Bitcoin Segwit ElectrumX? (Spesmilo ElectrumX 1.15) |
@99ytrewq911 no modification is needed. Make sure you run the |
Hello, thank you for the response, Here was my default syntax to execute and the results:
I also attempted to manually set the variables mentioned in the script's comment section as follows, using a .env file. I used a print statement to verify that they were being set: The new import section:
And here was the output:
I feel as if I am missing something quite important and obvious. I sourced the original script from this page: Thank you for your time |
Ah! That script is part of this repo -- it is a living thing like all files in git: you should use the one corresponding to your other files, probably latest. Find the script at the top level folder, latest version atm: |
@SomberNight This was indeed the issue. I see the file now in the root of this repo. Thank you for your assistance! |
Is it possible to update the readme to warn about this error in the meantime, and possibly spit out some warning messages in the logs in advance? We've been taken by surprise with this error as it's just occurred for the first time after more than a year of running the server peacefully without issue. The fixing script takes hours to run, and of course our backup server simultaneously went down with the same error, causing critical interruption to customers. Putting some warnings in would potentially save other developers a lot of aggravation (it's too late for us lol) |
@SomberNight Is it still worth working on a fix / automatic workaround for this issue? Would this concept have any chance at all: Warn in the logs occasionally if flush count higher than 50k, if flush count >= 60k raise special exception that shuts down everything, launch compact history from within main run loop, restart everything from within main run loop. Should be fairly simple. |
The first part of that (logging warnings) sounds simple and still useful. |
You are right, properly restarting from within Python is not trivial. Also shell solutions I could think of all had problems. So I suggest this extended documentation so that users can get up and running again a bit faster: #212 |
I encountered the same issue today, after running it for a few months.
|
Autocompact history via shell script: https://github.com/ghoober/electrumx |
@SomberNight from what I gather, #101 is removing the need for DB compaction. I would appreciate if you could proceed with this - either as part of the above PR or split into a smaller PR if it helps get it merged more quickly. The commit related to this seems simple enough, is there a specific reason it has stalled - any unexpected problem with it? I was reminded of this issue as our compaction cronjob ran at an opportune time 😅 |
My Electrumx crashes everytime during flushing the history with following error:
The text was updated successfully, but these errors were encountered: