Question
Telstra
IN
Last activity: 26 Dec 2022 9:33 EST
pyFtsIncrementalIndexer is turning off automatically
Hello,
We've upgraded our environment from 8.5.2 to 8.7.1 one month before. We're operating on two stream nodes and six webuser nodes.
Couple of days back Kafka stream service wasn't working on both of our stream nodes. Now we brought up the Kafka services, but the searching functionality isn't working.
We noticed that the pyFtsIncrementalIndexer is turning off automatically, and when we try to manually turn it on, after few minutes it's going to "Not Running" status.
We've shut down both of the stream nodes, cleaned up the search index directory, then rebooted the server. After doing all these steps we've manually run the pyFtsIncrementalIndexer queue processor from admin studio, but after couple of minutes it's turning off automatically.
Also in the Catalina.log files we've multiple errors related to this queue processor.
As this is happening on production environment, there's a huge business impact because of this. Please let us know what can we do to resolve this issue.
Maantic Inc
US
1. Is it happening in lower region or prod?
2. hope you are running pyFtsIncrementalIndexer in stream node, when pyFtsIncrementalIndexer is not running, do you see any nodes moved away from cluster
3.Could you share exception in log
4. From admin studio by clicking three dots in queue processor pyFtsIncrementalIndexer, open the data flow, check do you see any any error?
5. Go to config -> decision -> infrastructure -> check stream node status
LTIMindtree
SA
You'll need to perform the following steps when you bring down the entire application.
1. Stop the server 2. Truncate: PR_SYS_QUEUE_FTSINDEXER table 3. Truncate: pr_log_cluster table 4. Correct entries or remove any wrong node entries in pr_sys_statusnode table 5. Deleted all search indexes folders defined on search landind page 6. Restart server
Queries:
1) Truncate table <Data-Schema>.PR_SYS_QUEUE_FTSINDEXER;
2) Truncate table <Data-Schema>.pr_log_cluster;
LTIMindtree
SA
Did you try the inputs provided from my end on the issue? if yes and worked, you can mark the solution accepted.