Deployment Architecture

loadjob artifact_offset does not work properly in Search Head Cluster

rphillips_splk
Splunk Employee
Splunk Employee

The artifact_offset attribute available to the loadjob command does not work as advertised when used in a search head cluster. When a given savedsearch has several artifacts, the latest artifact is always used no matter what value is set for artifact_offset.
http://docs.splunk.com/Documentation/Splunk/6.5.1/SearchReference/Loadjob
artifact_offset
Syntax: artifact_offset=
Description: Selects a search artifact other than the most recent matching one. For example, if artifact_offset=1, the second most recent artifact will be used. If artifact_offset=2, the third most recent artifact will be used. If artifact_offset=0, selects the most recent. A value that selects past all available artifacts will result in an error.
Default: 0

environment:
Linux
reproduced issue on Splunk 6.3.5, Splunk,6.5.1

0 Karma
1 Solution

rphillips_splk
Splunk Employee
Splunk Employee

This issue is currently tracked under bug SPL-135037

View solution in original post

rphillips_splk
Splunk Employee
Splunk Employee

This issue is currently tracked under bug SPL-135037

jakrueger
Engager

Did SPL-135037 ever get resolved? I'm still seeing it on 6.6.2 (Linux)

Get Updates on the Splunk Community!

Easily Improve Agent Saturation with the Splunk Add-on for OpenTelemetry Collector

Agent Saturation What and Whys In application performance monitoring, saturation is defined as the total load ...

Explore the Latest Educational Offerings from Splunk [January 2025 Updates]

At Splunk Education, we are committed to providing a robust learning experience for all users, regardless of ...

Developer Spotlight with Paul Stout

Welcome to our very first developer spotlight release series where we'll feature some awesome Splunk ...