Question
K L University
IN
Last activity: 13 Feb 2024 5:25 EST
Search is not working in pega portal
Search is not working within the search bar(top right) in the development. It used to work previously. Does anyone know how to get it working again and I have pyftsincrementalindexer queue processor and I can see in Admin Studio a lot of entries are stuck in the "Ready to Process" state and it is turning off in some time.why these are stuck in "Ready to Process" state and what is the solution for this? =>i tried re-index in configure while records are processing this configure ->settings->search not opening =>restarted ECS node , search worked for 2 days then again it got stopped working =>if i ran the Queue processor manually, it is running for 5 mins and then automatically turned off Does any one knows the permanent fix for this?
Thanks,
Bhavani
Proximus
BE
in Search landing page, is your node flagged as available for rules & data? if not, then it's lost.
You need to have the 3 FTS Job Queue processor running for proper search and it might be that indexing is locked (file node.lock) in your search directory.
If you defined a single node for search, easiest way to make it back fully OK:
- Stop the search node
- Delete in temp directory the folder PegaSearchIndex (you could also clear FTS QP content in kafka-data directory)
- Restart the search node, process will be back fully generated and indexing will also start automatically.
If you defined, several search nodes, ideally, stop all of them and restart them in sequence with the expected master node first.
Regards
Anthony
Updated: 13 Feb 2024 5:06 EST
K L University
IN
Thanks for reply @Anthony_Gourtay
=>I'm using ECS node so when we do restart it clears kafga related things and will get new node
=>I didn't find node.lock file and i found only one FTS Queue processor
=>and even though we did restart ,it only works for 2 to 3 day only
*
Proximus
BE
FTS also needs stream node stability. No error from this earlier in logs?
Nothing else shown in logs before "Couldn't come to a stable state" ?
Something happens leading to this situation.
No issue with file system sizing for the search?
For FTS QP (before PEGA 8.8) there are - FTSBatchIndexer, FTSIncrementalIndexer and FTSClassToBatchIndexer.
Not sure whether it's still valid in your current verison (I'm not yet there :-))
It is strange that it works few days and then stops working. There's clearly an event triggering the issue.
Could be the link with Stream nodes or something with your server itself.
Look deeper & earlier in the logs
Regards
Anthony
Maantic Inc
IN
@BhavaniP7970First thing which of search is applied for you server, is it default pega search, or externalized elastic search or pega cloud native pega search and reporting services (srss) . 1. If its the first one, check if the search node and stream node is up and running admin studio. secondly check the FTS and batch index processor is working and not throwing error for index to work properly. 2. If is external elastic check the elastic search server is up or not in ec2, check for server status. secondly if elastic search api is fetching indices or not.
3. If is pega native SRSS used msp to raise SR incident for pega to sort.