All Apps and Add-ons

Errors messages when pulled log from DB Connect

vikram1583
Explorer

I pulled logs in to the Splunk from a Data base(MSSql) I am getting below errors on search head

[idx-i-01f9410f9c9fa09f8.greendot.splunkcloud.com] Events might not be returned in sub-second order due to search memory limits. See search.log for more information. Increase the value of the following limits.conf setting:[search]:max_rawsize_perchunk.

[idx-i-0ad23d2bab064c5bc.greendot.splunkcloud.com] Error in 'IndexScopedSearch': The search failed. More than 1000000 events found at time 1571382000.

can some one help me in fixing these errors

0 Karma

harishalipaka
Motivator

@vikram1583

HI this error based on _time field.can you change the _time.
Issue is single time repeated morethan 1000000 times ,just change the difference in _time field.

Thanks
Harish
0 Karma

ivanreis
Builder

Are you running on Splunk Cloud? If so there are some limits applied to splunk cloud that does not allowed you to work above the limits, in order to guarantee a good performance to entire system.

Try to bring small chunks of data. If it did not fix the issue, open a support case with splunk for further assistance.

https://docs.splunk.com/Documentation/SplunkCloud/8.0.0/Service/SplunkCloudservice#Service_limits_an....

0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...