-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Consul Snapshot error with serf and raft (windows) #332
Comments
Might have found a fix for the file name problem at least in raft.. Testing atm. EDIT: With this fix I started to get the following errors:
The sending computer also says it couldn't restore snapshot. Will try to figure this out. Just for heads up. |
The secondary problem you're experiencing is due to the fact that when restoring the database, it attempts to map a second 512MB memory block for the in-memory database, and there appears to be a low likelihood (zero?) that a contiguous free memory region of sufficient size is available within the process' address space. Adjusting the |
Awesome thanks for hunting this down! Definitely 32bit presents some challenges with the mmap()'s. I think we can probably safely tune down the size of both the state store and raft log on 32bit systems. |
With dbMaxMapSize32bit set to 256MB the tests still fail. They pass setting it to 128 MB. On the serf snapshot compaction issue "The process cannot access the file because it is being used by another process" unlike posix systems windows doesn't allow to rename open files. See: I tried setting the FILE_SHARE_DELETE as suggested below but still kept getting the error: For now we implemented a workaround of the rename based on a step by step close/rename/delete/reopen process. |
* ServiceRouter support * controllers => controller for logger name
Hello,
We are currently running consul on windows server 2008 r2, windows server 2012, windows server 2012 r2 and windows 8.1 and the non crashing errors seem to happen with all the computers. We are currently running Consul 0.4.0 and the panic attack came with previous version. However the other problems have been duplicated with Consul 0.4.0
So there's actually two errors with raft and one error with serf.
Raft creates a panic error when it hits this (or at least consul restarts and tries again this has happened multiple times):
(I have lots of error log if need be ask it's sadly not time stamped)
Then we have two other errors with serf and raft. Serf error when it happens starts immediately and keeps returning the following:
We did research and the file is used like the following:
And then we have the raft error number two which starts appearing after a while:
I would assume the last one comes from the fact that you are using : as delimiters.
If there's something I did not attach that you need please ask I have quite a lot more log files.
EDIT: added Consul version.
The text was updated successfully, but these errors were encountered: