Getting Data In

Why does Splunk custom endpoint time out automatically after 500 seconds

keerthana_k
Communicator

Hi,

We have distributed Splunk deployment running version 7.3.0. We have a custom REST endpoint which runs some searches and returns the search results in JSON format. When we run searches for long time ranges, the request times out after 500 seconds with 502 error code even when we see the search running in the Job Manager page. We found this error in the splunkd.log:

ERROR HttpClientRequest - HTTP client error=Read Timeout while accessing server=http://127.0.0.1:8065 for request=http://127.0.0.1:8065

We tried adjusting various timeout values like tools.session.timeout, ui_inactivity_timeout etc. but none of them seemed to help.
Has anyone faced similar issues. How do we fix this to make the request wait till the search completes.

Thanks in advance,
Keerthana

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...

Build and Launch AI Agents from Your Splunk Workflows

  Register We’ve all been there: juggling alerts, runbooks, and endless manual searches. What if you could ...

Splunk Cloud Application Management in Terraform

Register   On Tuesday, August 4 at 11AM PDT / 2PM EDT, we’re diving into how you can bring Infrastructure as ...