Hi Karl,

I have analyzed the error and found out that it was mainly an elasticsearch
problem. I saw in some forums that one of the adopted solution is to modify
elasticsearch.yml and set the http.max_content_length to a greater value.
However, the job got stuck in the last two indexable files ( two pptx files
with 22Mo and 2Mo respectively). The job eventually ended but a stack trace
showed that elasticsearch ran out of memory. For your information, I have
allocated 4Go for elasticsearch execution. Is it enough in order to have a
good performance. You will find attached the stack traces of elasticsearch.

Best regards,

Othman BELHAJ.

On Mon, 4 Sep 2017 at 16:40, Beelz Ryuzaki <[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