ADS-connectivity Error-Searches-NESTE

[ThulasiP3]

Describe the bug In NESTE Searches, Whenever we try to fetch records more than 1lakh (approx). We are getting the below error.

Additional context Build no : Region :NESTE Client :

[suseela22]

While trying to clone the search, the same issue is occurring after 60 seconds. After refreshing the page it displays the cloned search.

[ClementJosh21]

@suseela22
Can you attach the network trace for the above scenario?

[suseela22]

clone_issue- afterrefresh.txt clone_issue-beforerefresh.txt

[suseela22]

Findings: Search Execution, Cloning the search - wherever the screen is on standby for 60 second this issue occurs

[prashanthtk33]

The RCA of this issue is the idle_timeout (a load balancer attribute), which is currently set to 60 seconds in the respective region. During a search operation that takes longer than 60 seconds to complete, the load balancer terminates the connection, resulting in a 503 Gateway Timeout error. We have tested this scenario in the test environment, and after increasing the idle timeout, the search operation now completes successfully without errors.

https://platform3solutionsllc-my.sharepoint.com/:v:/g/personal/clement_m_platform3solutions_com/EUG8aA4lPglIvl8c-AbcDC0BlKQflXbfHYOHhjs5VQcQ7g?e=00hpTr

[harsha-kotha]

idle_timeout (a load balancer attribute Old Timeout : 60 Seconds New Timeout : ?? Why is the error message shown on the screen showing inappropriate error message: as "Unable to Establish connection, Please try later" - can we provide appropriate Error message? Where is this Timeout specified? Are we giving any warning to the user that the time limit is about to reach? How can you ensure this issue will not occur next time with a even higher volume search?

[kilam005]

Load balanced time out will be 5 mins will be the timeout. at 5 min, serch will be forced to be cancelled or scheduled to BG.

[santhanakumari15]

Server : https://uat-ads.platform3solutions.com/login Version : 2024.09.45542_P5

Working as expected, In searches, when trying to fetch more than 1 lakh records, the search schedules as a background search without any error, and the job gets completed, and also view the records without any errors. And The searches can clone successfully without any error.

Perform Search

Clone:

[kilam005]

@ThulasiP3 The timeout configurations have been updated as previous indicated. Kindly check and confirm the fix from Neste's environment.

[ThulasiP3]

Issue resolved in NESTE ..