Splunk Search

Fix Error: IndexScopedSearch?

splunk_enjoyer
Explorer

Hello Splunk enjoyers!
I loaded some data(10 000 000), with fields: updated_time, info, user and discription,  to my new index "data_tmp".

So when i search, i got a problem  Error in 'IndexScopedSearch': The search failed. More than 1000000 events found at time 1677582000.

My search:

So i tried to extract by updated_time like:
index = data_tmp
 eval _time = strftime(updated,"%Y-%m-%d %H:%M:%S.%3N")
| convert ctime(_time)
| fieldformat _time = strftime(updated,"%Y-%m-%d %H:%M:%S.%3N")

but nothing works.
Can somebody help me with that?
thank you!




Labels (3)
Tags (2)
0 Karma

abedcx
Explorer

did you fix it ? 

0 Karma

PickleRick
SplunkTrust
SplunkTrust

This is a fundamental problem with the data badly ingested into Splunk.

Splunk returns results in reverse chronological order so it needs to be able to sort the results properly based on the _original_ value of the _time field. (afterwards the _time field can be rewritten during the search pipeline and it won't affect the result order). If you have several hundred thousand events indexed at the same point in time, Splunk cannot sort them due to memory constraints.

It's not a problem with the search as such but it's a problem with the data - fix your data onboarding.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...