Question
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689969000/76923fd4-5e68-4208-9493-3a61ec0f9022.jpg?itok=fqmZXer5)
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689969000/76923fd4-5e68-4208-9493-3a61ec0f9022.jpg?itok=fqmZXer5)
Atos
GB
Last activity: 11 Nov 2022 3:18 EST
Rule search not working in Pega 8.5
Rule search is not working in newly installed Pega 8.5.
I click on re-indexing but nothing happens. Screenshot attached.
Any help would be really appreciated.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689968000/54c68a50-22c7-47d5-98f2-63df69104811.jpg?itok=I5MMyPJN)
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689968000/54c68a50-22c7-47d5-98f2-63df69104811.jpg?itok=I5MMyPJN)
Coforge DPA
GB
@Bipul Singh If you scroll down the search tab (same screen that you have attached), remove the node details and add them back again. Then try to reindex.
Regards
Bhavya
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Achmea
NL
@Bipul Singh Please add the PegaRules.log also to this question, I suppose there are errors in there that will lead you to the cause of your search not working. Kind regards, Arjan Maus
![](https://accounts.pega.com/sites/default/files/pega-user-image/122/REG-122119.png?source=PUMINIT)
![](https://accounts.pega.com/sites/default/files/pega-user-image/122/REG-122119.png?source=PUMINIT)
TCS
GB
@Bipul Singh Did you find any solution on the above?
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Capgemini
IN
Any fix for the issue?
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689951000/da7084b9-a9c3-461b-afcc-b04a6c62dff4.png?itok=kHpAAuH4)
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689951000/da7084b9-a9c3-461b-afcc-b04a6c62dff4.png?itok=kHpAAuH4)
Pegasystems Inc.
GB
@SudheerY1191 this post is 1 year old.
If you are experiencing a problem, could I suggest that you go through our available troubleshooting documentation?
Troubleshooting Pega Platform Search
Search returns incomplete or empty results
Solution
Ensure that the following conditions are met:
- Indexing is finished and available.
- The Dynamic System Setting indexing/distributed/search_enabled is set to true.
- On the Search landing page, the option Enable search indexing is selected.
- There are no broken items in FTSIncrementalIndexers or all records are scheduled. (Search runs through Queue Processors; therefore, the Stream service needs to be enabled. If you add a new Stream service, then you must re-index data manually.)
exing stuck in progress
Symptoms
Indexing status is incomplete for a long time. There are broken items in the Queue Processor and failure is caused by the following error:
Batch Indexing request failed. Possible cause: Quorum not met for writes to succeed. Action: Remove any offline nodes as index nodes.
@SudheerY1191 this post is 1 year old.
If you are experiencing a problem, could I suggest that you go through our available troubleshooting documentation?
Troubleshooting Pega Platform Search
Search returns incomplete or empty results
Solution
Ensure that the following conditions are met:
- Indexing is finished and available.
- The Dynamic System Setting indexing/distributed/search_enabled is set to true.
- On the Search landing page, the option Enable search indexing is selected.
- There are no broken items in FTSIncrementalIndexers or all records are scheduled. (Search runs through Queue Processors; therefore, the Stream service needs to be enabled. If you add a new Stream service, then you must re-index data manually.)
exing stuck in progress
Symptoms
Indexing status is incomplete for a long time. There are broken items in the Queue Processor and failure is caused by the following error:
Batch Indexing request failed. Possible cause: Quorum not met for writes to succeed. Action: Remove any offline nodes as index nodes.
Explanation (Root Cause)
The quorum is not met. The number of unreachable Search nodes exceeds a healthy limit.
See also Troubleshooting Elasticsearch, common issues, Best practices, Guideline 3.
Solution
Restart the unhealthy Search nodes.
----> If you still need help post a new question on the forum using the Ask a Question button
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/2023-11/df719c74-cbbc-49c3-8f11-882d1825d13b_0.jpg?h=2a1ca805&itok=iLLOozNa)
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/2023-11/df719c74-cbbc-49c3-8f11-882d1825d13b_0.jpg?h=2a1ca805&itok=iLLOozNa)
LTIMindtree
SA
@Bipul Singh The issue posted like long time back. I could help if you're still facing the same issue either in On-Prem / Containerization Setup environments.