execprocessor queue is %819 percent, is hesplfwd002 an indexer ? execprocessor would not typically stop indexing. you can restart that instance anyways.
for file operation errors in the indexer cluster( typically from antivirus or account permissions) , I can suggest you this search also:
index=_internal (log_level=ERROR OR log_level=WARN) (host=myindexers) (component=PeriodicReapingTimeout OR component=BucketMover OR component=BucketReplicator OR component=CMRepJob OR component=DatabaseDirectoryManager OR component=DispatchCommandProcessor OR component=HttpClientRequest OR component=HttpListener OR component=IniFile OR component=ProcessRunner OR component=TPool OR component=TcpInputProc OR component=TcpOutputFd OR component=IndexerService OR component=S2SFileReceiver)
| stats values(host) dc(host) last(_raw) count by punct,component
| fields - punct
This will get you last error of each type , and components to check for issues. if this points to anything, you could adjust logging levels on that component to see what is failing.
if it is an indexer in cluster, do in CLI to restart :
splunk offline
this will take some time, then:
splunk start
Finally, check bucket status on the Cluster Master. Check which server has copies failing.
... View more