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!

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...