Question
Yapi Ve Kredi Bankasi As
TR
Last activity: 28 Sep 2022 5:55 EDT
Pega Dev Studio re-index is not working
Hi Dear supporter,
after go to Pega Dev Studio, When I go into index settings and click on re-index , it does not makes status available , it is stuck on unavailable , although I received mail from system that indexing progress is completed. I have restarted web servers just for search. I will be waiting for your help,
thank you in advance.
Accenture
GB
@recepayabakan Hi, Greetings. How many nodes are in a cluster and can you check if the nodes that are classified as Search are online? If not, you might need to clear the index directory in the instance and restart them, starting with Search Nodes and at the end webuser nodes.
Regards,
Bharat
Updated: 28 Sep 2022 5:55 EDT
LTIMindtree
SA
I have solution but unable to post it here in-detailed. it's a BUG-707482 in Pega Platform 8.6.3 and HFIX: 82911 is available in Hotfix catalog already. issue will be fixed upon the installation.
Error Found in the logs in our environment:
The issue occured for us in one environment ONLY with Pega Platform 8.6.3
Unable to get indices info. com.pega.pegarules.priv.search.nextgen.FTSSearchRequestFailedException: {"root_cause":[{"type":"too_long_frame_exception","reason":"An HTTP line is larger than 4096 bytes."}],"type":"too_long_frame_exception","reason":"An HTTP line is larger than 4096 bytes."}
Because there are approximately 87 dedicated indexes, the name for each of them is sent over the url, resulting in this error message.
Root Cause: When the Indices size is more than the defined limit (i think 4096 bytes showed in the above error), Indices status comunication issue occuring and the same has been confirmed by Pega GCS. It's the same reason although indices are available it's not communication back to the status field and you can validate it through the below commands:
So then Pega GCS confirmed it's a BUG and HFIX:82911 is relased for Pega Platform 8.6.3 with INC-216416 reference (raised by us). Issue is reoslved post the hotfix installation.
I have solution but unable to post it here in-detailed. it's a BUG-707482 in Pega Platform 8.6.3 and HFIX: 82911 is available in Hotfix catalog already. issue will be fixed upon the installation.
Error Found in the logs in our environment:
The issue occured for us in one environment ONLY with Pega Platform 8.6.3
Unable to get indices info. com.pega.pegarules.priv.search.nextgen.FTSSearchRequestFailedException: {"root_cause":[{"type":"too_long_frame_exception","reason":"An HTTP line is larger than 4096 bytes."}],"type":"too_long_frame_exception","reason":"An HTTP line is larger than 4096 bytes."}
Because there are approximately 87 dedicated indexes, the name for each of them is sent over the url, resulting in this error message.
Root Cause: When the Indices size is more than the defined limit (i think 4096 bytes showed in the above error), Indices status comunication issue occuring and the same has been confirmed by Pega GCS. It's the same reason although indices are available it's not communication back to the status field and you can validate it through the below commands:
So then Pega GCS confirmed it's a BUG and HFIX:82911 is relased for Pega Platform 8.6.3 with INC-216416 reference (raised by us). Issue is reoslved post the hotfix installation.
Note: Please accept the solution if it worked for you. Contact me at Proprietary information hidden if needed any further assitance on the issue and required commands to find the issue else refer the attachment which enclosed with commands used for RCA in containerization environment.