TBMCPlugins/LimitedCreative

Occassional extreme large DB queue with even 45k actions, which sometimes delays shutdown for minutes

Closed this issue · 5 comments

The shutdown was delayed by 5 minutes by waiting for LC:

[12:01:00] [Server thread/INFO]: [LimitedCreative] Disabling LimitedCreative v2.3-SNAPSHOT-ecaecd4136
[12:01:59] [Thread-42/INFO]:  Don't forget to sign up for our forums https://chromagaming.enjin.com/
[12:06:47] [LC BlockState DB-Thread/WARN]: [LimitedCreative] <BlockState> Extrem large DB-Queue in LC BlockState DB-Thread: 5465
[12:06:47] [Server thread/INFO]: [Multiverse-Portals] Disabling Multiverse-Portals v2.5.0-b751

From 2 days ago:

[23:25:38 WARN]: [LimitedCreative] <BlockState> Extrem large DB-Queue in LC BlockState DB-Thread: 45864
[23:25:40 WARN]: [LimitedCreative] <BlockState> Extrem large DB-Queue in LC BlockState DB-Thread: 45757
[23:25:42 WARN]: [LimitedCreative] <BlockState> Extrem large DB-Queue in LC BlockState DB-Thread: 45753
[23:25:44 WARN]: [LimitedCreative] <BlockState> Extrem large DB-Queue in LC BlockState DB-Thread: 45653
[23:25:44 WARN]: [LimitedCreative] <BlockState> Extrem large DB-Queue in LC BlockState DB-Thread: 45428
[23:25:46 WARN]: [LimitedCreative] <BlockState> Extrem large DB-Queue in LC BlockState DB-Thread: 45399
[23:25:47 WARN]: [LimitedCreative] <BlockState> Extrem large DB-Queue in LC BlockState DB-Thread: 45324

It is now common for the shutdown to be delayed for 24-25 minutes.

All the changes from the previously used version are here: possi/LimitedCreative@spigot-1.9...TBMCPlugins:master

I don't know if my changes or the other changes caused the issue, although... it's probably mine.

The first is my message, and I'm not sure it's supposed to fire until the server is started:

[12:17:28] [Server thread/WARN]: [LimitedCreative] <BlockState> Thread is dead, restarting!
[12:17:28] [Server thread/INFO]: [LimitedCreative] <BlockState> Module loaded.

I ain't touching this! But seriously, I have no computer access for, like, a while. About a week?

Oh, right. I'm not 100% it'll be fixed in a week though, so yeah.

Didn't fix the stop delay.

Although it took 5 minutes instead of 20 or so, so it may have improved.