The CoreProtect database is fucked right now, and to be frank the performance issues we're dealing with simply aren't worth it. This suggestion requests that we wipe the massive ass 60 GB database and start fresh. We could put a download link to the old data in a compressed form so that we can still query it on our own if needed.
Wipe the CoreProtect Database and post a download link to it
Please Note: The TotalFreedom Forum has now been put into a read-only mode. Total Freedom has now closed down and will not be returning in any way, shape or form. It has been a pleasure to lead this community and I wish you all the best for your futures.
-
-
This has been needed for quite some time. People are getting sick of the server becoming a literal constipation station every time they want to use CoreProtect. Vouch.
-
Vouch.
-
Vouch but do it from a few days before (like saturday if you were to do it today which is Thursday)
-
we should be wiping it monthly imo, vouch
-
🦀🦀🦀🦀 The CoreProtect database is fucked 🦀🦀🦀🦀
-
Defeats the point of coreprotect. We won't be wiping the database other than for map resets.
-
To be honest, I think we should wipe it, with a 7 day warning that people need to save their builds as schematics before CoreProtect data is gone.
Also I think we should maybe bring back flatlands wipes every 2-4 weeks, but that's just my opinion - it could save so much storage.
-
I agree it should be wiped, however, only for stuff older than a few weeks at most. 9.9 times out of 10, a person would notice if their building was griefed in that time frame, and would allow core protect to work better.
-
Is the end goal here to wipe the database or to solve the performance issues? Sure, this is a very easy way to solve the performance issues, but I am wondering whether it is the best.
-
Quote
@StevenNL2000#6571 Is the end goal here to wipe the database or to solve the performance issues?
CoreProtect is fucked right now. The server has a crash chunk that won't roll back because CoreProtect just gridlocks the server. There are tens of thousands of tile entities logged, and rollbacks don't work for it.
The goal is to wipe the database to resolve this issue, and stop issues like this occurring in the future.
-
either we find a more optimal plugin that fits with our setup or we wipe the coreprotect data every month.
i see the point if we wanted things to stick around forever that would include logs so long time ago griefs get restored but the way coreprotect is handing the server it is not stable and broken and its kinda hard to sell a broken product if you catch my drift
-
Quote
@Ivan#6566 Also I think we should maybe bring back flatlands wipes every 2-4 weeks, but that's just my opinion - it could save so much storage.
Completely agree, I get not wanting to constantly wipe flatlands but so many different chunks get loaded there that the world size is just gonna keep getting crazier
-
HARD VOUCH, we need to setup monthly CoreProtect Wipes or something
No modification logging plugin is designed to have a 60gb database to swim through so unless we get a plugin that is designed for this then we need to setup periodic wipes -
Vouch
If possible, wipe old data rather than recent.
-
As previously stated, the CoreProtect dB won't be wiped without wiping the respective map(s) that go with it. There is a separate thread discussing that so with both those things in mind, this thread is denied.
-
wild1145
July 17, 2022 at 2:17 PM Moved the thread from forum Imported from Flarum to forum Freedom Game-mode. -
wild1145
July 17, 2022 at 4:55 PM Moved the thread from forum Freedom Game-mode to forum Denied.