Reporting

Pivot on datasets fails with search job failing and the OOM killer

termcap
Path Finder

I created a large data model with data sets and tried pivot, it worked for a couple of times, but then it started to fail with the following error.

 

splunk-oomkiller.PNG

Labels (1)
0 Karma
1 Solution

termcap
Path Finder

The issue was that I am working with t2.micro AWS cloud instance with really limited RAM, the search job was causing the RAM requirements to shoot up, which was not a problem because behind the scenes it seems I was using my burstable memory credits.

Once I ran out of credit, the OOM killer kicked in and started to kill the Splunkd process that was running the job!

OOM.jpeg

Changing the instance type of the Linux machine fixed the issue.

View solution in original post

0 Karma

termcap
Path Finder

The issue was that I am working with t2.micro AWS cloud instance with really limited RAM, the search job was causing the RAM requirements to shoot up, which was not a problem because behind the scenes it seems I was using my burstable memory credits.

Once I ran out of credit, the OOM killer kicked in and started to kill the Splunkd process that was running the job!

OOM.jpeg

Changing the instance type of the Linux machine fixed the issue.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...