[cle-release-team] [infrastructure] [Building Sakai] Jira down tonight in an hour (1AM EDT)

[Matthew Jones]

Agreed, looks like it's a known issue for jira as well as Sakai.
http://confluence.atlassian.com/display/JIRAKB/Loss+of+Functionality+due+to+Too+Many+Open+Files+Error


And from the email this is what they did at wush. Hopefully it's increased
to a usable level. That would make sense with the index breaking it.

On Sun, Apr 1, 2012 at 10:42 AM, Seth Theriault <slt at columbia.edu> wrote:

> David Horwitz wrote:
>
> > hmm can't resolve either, something is seriously wrong:
> >
> > java.io.FileNotFoundException:
> > /home/sakai/jira-data/index/issues/segments_14 (Too many open files)
>
> Is it possible that we have run out of space during the index
> rebuild? I have had that happen with Sakai's Search indexer
> and it inevitably leads to a "too many open files" situation
> soon after.
>
> At a minimum, we need the open-files limit increased for the
> user running Jira.
>
> Seth
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20120401/7148f4a1/attachment-0006.html