#5313: Ejabberd falls over
------------------------------+---------------------------------------------
Reporter: daf | Owner: robot101
Type: defect | Status: assigned
Priority: normal | Milestone: Update.1
Component: telepathy-other | Version:
Resolution: | Keywords:
Verified: 0 |
------------------------------+---------------------------------------------
Changes (by robot101):
* cc: jg, kimquirk (added)
Comment:
He seems to have decided that the problem is that our shared roster is too
large, and that this simply results in too many <presence> messages being
generated internally for mod_pubsub to handle in a reasonable time, so it
runs out of memory due to too many unhandled messages after a certain
number of users log in in quick succession. He says the best thing for us
to do is make smaller shared roster groups.
He suggested a) a shared roster that would automatically only show Online
people, but given the scalability target of 5000 users in a large school,
this would still reach the roster sizes we have at jabber.laptop.org, or
b) groups which are based off some organisational unit at the school, such
as by class or year, although I don't know whether such information is
actually stored on the school server at this juncture, and even if it was
I don't think it would be practical to hook it up to the jabber server on
the Update.1 timescale. Given these constraints, he's going to look at
writing some patches for us for so that we can have the "Nearby" and
"Random" groups as suggested in #5311, and hopefully kill two birds with
one stone.
In the meantime, he suggested trying the trunk version (#5315) which I am
now doing, given that the PEP functionality has undergone some
improvements between the patch we were running, and current trunk, to see
if that helps.
--
Ticket URL: <http://dev.laptop.org/ticket/5313#comment:3>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system