Search not working unless prefixed with "old:"
I recently upgraded my QA server from 7.1.9 to 7.2 and now the search feature will not find a rule that is in my current application. If I prefix the search with old: then the rule is found.
I have used the search landing page and accomplished the following:
- Reindex all rules
- Entered the correct Search Index Host Node ID which I obtained from the clipboard using System Pages > pxProcess > pxSystemNodeID
- Expanded Automated Search Alerts and ensured that Automatically Monitor Files is selected.
- Clicked Submit
I searched for resolutions to this issue on the PDN and the Mesh and found these, but none of them helped to resolve this issue:
Accepted Solution
Updated: 4 Apr 2016 2:53 EDT
Pegasystems
IN
Thanks for the details. From the tracer I was able to figure out that in line 1803, the check for whether to use distributed mode (Elastic Search) is coming as false because of which it is searching in the older Lucene index rather the Elastic Search index.
Please check the values of the following Data-Admin-System-Settings instances
indexing/distributed/enabled
indexing/distributed/index_enabled
indexing/distributed/search_enabled
Note that all of them should be true. If not, please change them to true and re-index work.
Pegasystems Inc.
US
Hello Sean,
While I don't actually know the solution to your search problem, I can explain why "old:" works. That uses a different search/indexing mechanism. My understanding is that it's not as efficient, but it's nice to have as a backup. That said, when you try and search without it, do you get any errors in the logs? If you run tracer, do you get any errors there?
Thanks,
Mike
Pegasystems
US
I have to admit, in my experience of using a lot of different Pega instances here within Pega itself, quite often when I search for something, say FOO, I get nothing-matched, so I merely type old:FOO and then I get stuff. It's almost gotten to the point where I immediately type old:FOO without even bothering with the non-old attempt first. /Eric
Pegasystems Inc.
US
Hi Manjunatha, you are correct - indexing/distributed/search_enabled was set to false. After setting it to true it worked.
Thanks,
Sean
Pegasystems
IN
Rules marked internal or deprecated are not found by default from the search box unless you use "old:".
Some questions and details requested
1) Were the rules found before the upgrade?
2) Please share the screenshots for the search landing page with all sections expanded.
3) Please share the screenshot of the popup that comes up when you click the "check" button for rules index on the search landing page
4) Is the FTSIncrementalIndexer agent running on all nodes?
5) How many nodes are there in this cluster? A dump or pr_sys_statusnodes table would be useful.
6) Please share the log file and tracer XML when searching
Accepted Solution
Updated: 4 Apr 2016 2:53 EDT
Pegasystems
IN
Thanks for the details. From the tracer I was able to figure out that in line 1803, the check for whether to use distributed mode (Elastic Search) is coming as false because of which it is searching in the older Lucene index rather the Elastic Search index.
Please check the values of the following Data-Admin-System-Settings instances
indexing/distributed/enabled
indexing/distributed/index_enabled
indexing/distributed/search_enabled
Note that all of them should be true. If not, please change them to true and re-index work.
Pegasystems Inc.
US
Hi Rajiv,
Thanks for all your help. Providing me with the complete path "indexing/distributed/search_enabled" made it easier to find the DSS entry. I saw that it was set to false - I set it to true and now it works.
Thanks again,
Sean
Sopra Group
FR
Hi Rajiv,
Is there a config settings reference that describes these settings ? It can be helpful, like for ealier versions of PRPC having a config settings reference document.
Unfortunately this document is not maintained for Pega 7 (or have I missed something ?).
Regards,
Halim
Pegasystems
IN
In general you should not worry about setting these. If the upgrade guide was followed correctly, where all the indices were built from the search landing page, this setting would have been set to true by the platform itself. Looks like, it did not happen in this case. You can refer to the details in this PDN post (upgrade guide is referred at the very end) - https://community.pega.com/knowledgebase/release-note/improved-full-text-search