This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
What is the problem?
If I do something that causes a lot of block changes (maybe 100+), and I try to roll it back, the rollback will lock up the server (hog all the resources so nothing else can run). The server always comes back afterwards, but it can take a very very long time because the entire server will freeze until the rollback is done. It's a very annoying problem, and I was hoping it would have been fixed in 1.0.5b, but it wasn't (That may be just because the wrong jar file was put into the zip).
I use an offsite MySQL server with a slow upload speed, so that might be a factor. However, hawkeye should never lock up the whole server, even if only for a moment.
What steps will reproduce the problem?
1. Blow up a block of TNT
2. Try to roll it back
What version of HawkEye are you using (shown in console during start-up)?
1.0.5a (However, the jar file was downloaded as 1.0.5b, but the files got mixed up or something and it didn't actually update)
Show me any console errors and/or your start-up console message for HawkEye
There are no console errors at all. The message is:
http://pastebin.com/tAcHDL2V
Show me your config.yml and/or your config.php (REMOVE YOUR PASSWORD)
http://pastebin.com/nWxTcmBH
Have you checked the FAQ page?
What FAQ page?
EDIT: I updated to the real 1.0.5b version, and it still hogs the server when rolling back.
EDIT 2: I turned off deleting data on rollback, and it's much faster now. It's possible that the MySQL writing is causing a block.
Interesting that the deleting data thing causes the hang. Thanks, i'll look into it.
To post a comment, please login or register a new account.