[ejabberd] pubsub_item.DAT getting big
sma at turtle-entertainment.de
Mon Sep 29 14:51:29 MSD 2008
any feedback on this? since this really is a major headache right now.
currently we are calling "ejabberdctl delete-expired-messages" every
half hour...that does not really help though, after two days or so that
said file has reached around 800 mb again. once i stop the server,
it wont start up again...ever again. this together with the fact that nodes
cannot be removed in a smooth fashion is really nasty and piles up
nodenames as we speak...
furthermore, once a node goes down, it is absically dead until i
reinstall the server with a clean slate database. how can i adress this?
greetings and thanks in advance,
Von: ejabberd-bounces at jabber.ru [mailto:ejabberd-bounces at jabber.ru] Im Auftrag von Stephan Maihöfer
Gesendet: Freitag, 26. September 2008 17:27
An: ejabberd at jabber.ru
Betreff: [ejabberd] pubsub_item.DAT getting big
we had some problems over the past few days with pubsub_item.DAT
getting bigger and bigger. our server came to a halt when that
file reached around 800MB and we kept all of that in RAM.
i never thought the pupsub-item-database woul get this big, since
we dont do offline message delivery and have no persistance on
the items. it does seem that ejabberd does ignore that though.
i made things less worse by storing that part of the database on
disk only, so system startup is not so slow anymore and ram
usage is reasonable. but still: what is stored in there, and how can
i keep this file as small as possible?
from what i think it should only hold a queue for pubsib items that are
to be delivered _now_, since items are not persistent and we have no
offline storage that should not get THAT big.
am i seeing something wrong here? what can i do?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ejabberd