
glow squid spamming database
mhtvsSFrpHdE opened this issue ยท 4 comments
#fall killed glow_squid
#drowning killed glow_squid
And many more. No one build glow squid farm on my server, they just spawn at random location and die naturally.
These glow squid generated 10613688 database entry in co_block
table and takes 6 GB of disk space.
It's insane.
Plus, #amethyst
grow also has 628 records in past 10 days but seems not too much.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
For those who also troubled by database spamming
I use this code and tool sqlitebrowser to open core protect database and look for what records take most space,
shutdown server and:
select co_block.user as blockUserId, co_user.id as userId, co_user.user as userName, count(*) as userCount
from co_block
inner join co_user on co_user.id = co_block.user
group by co_block.user
order by userCount desc
MAKE BACKUP OF YOUR DATABASE before delete anything.
After delete unwanted database entry, save change to disk, run a database optimization to actually reduce disk space.
After delete and sqlite "vacuum", database size reduced from 6 GB to 986 MB,
In blacklist.txt
, put name that event name don't want to be recorded to prevent them appear again
this is what I do, may not suite for all server confirm by yourself:
#tnt
#hopper
#dropper
#dispenser
#piston
#campfire
#lava
#water
#vine
#bamboo
#amethyst
#snowman
#fire
#decay
#drowning
#fall
#guardian
In config.yml
, set these to false if needed:
# Logs items dropped by players.
item-drops: false
# Logs items picked up by players.
item-pickups: false
# Track all hopper transactions, such as when a hopper removes items from a
# chest, furnace, or dispenser.
hopper-transactions: false