Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1083

Indexing storage can be very slow and sometimes times out

XMLWordPrintable

      Apache Lucene indexing exhibits problems when storing to CNS/GlusterFS. This even leads to ES not running in some scenarios: https://bugzilla.redhat.com/show_bug.cgi?id=1430659. Single node Lucene does work, but is accompanied with errors and delays. NFS is faster, but still slows down indexing noticeably.

      Any reason why indexing can't be ephemeral? In the case of a single node, we can store indexing data within the container and re-index if it is restarted. Perhaps this should also be done for ES?

        1. afterIndexingTimeout.png
          42 kB
          Jakub Schwan
        2. indexingTimout.png
          46 kB
          Jakub Schwan

              bmozaffari-gps-jboss Babak Mozaffari
              bmozaffari-gps-jboss Babak Mozaffari
              Alexandre Porcelli, Filippe Spolti
              Jakub Schwan Jakub Schwan
              Jakub Schwan Jakub Schwan
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: