Question
LTIMindtree
SA
Last activity: 28 Sep 2022 5:54 EDT
Indexes status is OFFLINE in Dev Studio and Re-indexing is not helpful
Elastic Search Re-indexing option displays "unavailable" although Re-Indexing option invoked in Pega Platform 8.6.3 Version.
Error:
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."}
Accepted Solution
Updated: 28 Sep 2022 5:54 EDT
LTIMindtree
SA
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: 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 for commands used for RCA.