Hi Mario,

If you are using the single-process model, then stuck locks are not the
problem and the lock-clean script is inappropriate to use.  Locks are all
internal in that model.  That is why lock-clean is only distributed as part
of the file-based multiprocess example.

Please tell me more about what you have set up for your jobs on this
example.  How many are there, and how many documents are involved?  The
embedded HSQLDB database has limits because it caches all tables in memory,
so the single-process example is not going to be able to handle huge jobs.

Please have a look at the log to be sure there are no serious errors in it.

Thanks,
Karl
On Tue, Jun 12, 2018 at 9:26 AM Bisonti Mario <[EMAIL PROTECTED]>
wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB