Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-53884

Setting portal to be index.read.only only affects the portal and does not affect the embedded Lucene search engine

    Details

      Description

      Steps to reproduce

      1) Delete $LIFERAY_HOME/data/lucene
      2) Start the portal
      3) Perform a full reindex
      4) Shut the portal down

      Checkpoint: Your lucene directory doesn't contain file write.lock

      5) Set index.read.only=true
      6) Start the portal again
      7) Add the Search portlet to /web/guest/home
      8) Search for "test"

      Checkpoint: It finds user test@liferay.com

      9) Recheck Lucene's directory

      % ls -gG
      total 48
      -rw-r--r--. 1 1603 Feb 27 15:11 _b.cfs
      -rw-r--r--. 1 2859 Feb 27 15:11 _c.fdt
      -rw-r--r--. 1  108 Feb 27 15:11 _c.fdx
      -rw-r--r--. 1  479 Feb 27 15:11 _c.fnm
      -rw-r--r--. 1  612 Feb 27 15:11 _c.frq
      -rw-r--r--. 1  459 Feb 27 15:11 _c.nrm
      -rw-r--r--. 1  212 Feb 27 15:11 _c.prx
      -rw-r--r--. 1   54 Feb 27 15:11 _c.tii
      -rw-r--r--. 1 2076 Feb 27 15:11 _c.tis
      -rw-r--r--. 1 1632 Feb 27 15:11 _d.cfs
      -rw-r--r--. 1   20 Feb 27 15:11 segments.gen
      -rw-r--r--. 1  745 Feb 27 15:11 segments_h
      -rw-r--r--. 1    0 Feb 27 15:27 write.lock
      

      IndexWriter has been initialized and even with index.read.only=true, it's locked the index
      With having index.read.only=true, a lock shouldn't be acquired on the index

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                4 years, 31 weeks, 6 days ago

                Packages

                Version Package
                7.0.0 M5