Vladimir Kotal

For SCMs that are capable of fetching history per directory this can be workarounded by using the `fetchHistoryWhenNotInCache` tunable (see https://github.com/oracle/opengrok/wiki/Indexer-configuration). Still, this might be unwanted if one rather likes...

Also, this error propagation needs to work for any repository for given project. If indexing without projects, this should result in the whole reindex to be terminated.

As a pre-requisite, this needs per-project tunable to ignore failures for certain repositories. E.g. the OpenGrok git repository has some sub-repositories for which it might not be possible to generate...

Trying to index the linux-mainline Git repository with indexer using Java 11 running from IDEA (that I think has 8 GB heap by default) it hit the heap limit sometime...

Exit value 137 means the ctags process was terminated with SIGKILL. OOM Linux killer in action perhaps ?

Also, you can try to see if this is data sensitive (probably is) and isolate the repositories/files that cause the problem.

This means the ctags process did not finish processing of given file in 4 minutes. Did you try running the ctags process standalone as suggested earlier ? Does this happen...

Also, is the `/XXX/src` local or network file system ? Can the ctags process be stuck on I/O ?

The error 137 means the process was forcibly terminated: ``` $ kill -l 137 KILL ``` and the indexer logs above confirm this was due to timeout. You need to...

> Also, there is something which I find weird, even if I limit the threads with -T flag, OpenGrok spawns one process per available thread systematically, Is that normal? I...