http://defect.opensolaris.org/bz/show_bug.cgi?id=19163
--- Comment #2 from Johan <[email protected]> 2012-02-06 09:43:10 UTC --- (In reply to comment #1) > this is a bit weird > I think it shouldn't happen with latest binaries > It is using opengrok 0.11, or at the very least 0.10 if I failed the upgrade somehow (There seems to be no UI-visible version # to verify?) > afaik our executors have a timeout on forked commands > > below stack shows this: an indexer is stuck indexing "opstools-misc" > and another indexer was started in between (within maybe the timeout of above) > > so basically you have 2 indexers running on the same box and they seem to > clash, check ps axf (or ptree) and let us know > No indexers running at all. It happened for us on 5 repositories, all exhibiting the above problem, so I'm really suspecting something w.r.t the git scm history. All the other directories under /var/opengrok/data/spellIndex has a couple of files ( 672 -rw-r--r-- 1 opengrok opengrok 684629 Nov 28 23:07 _0.cfs 128 -rw-r--r-- 1 opengrok opengrok 130345 Nov 28 23:07 _0.cfx 4 -rw-r--r-- 1 opengrok opengrok 20 Nov 28 23:07 segments.gen 4 -rw-r--r-- 1 opengrok opengrok 246 Nov 28 23:07 segment) > + locking on lucene is supposed to be automatic, I removed forced options on > lock clean ups because of that (and no one complained, so you're the first > one) > > the other Q can be, whether you use latest opengrok ;) Well, most probably 0.11rc2 unless my installation failed and then it would be running 0.10. > > hmm? > L > > note that current 0.11rc and 0.10 didn't have big changes in this area, so the > locking should be the same, however older opengrok versions had old locking, > which was problematic sometimes -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ opengrok-dev mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opengrok-dev
