https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-quot-ERROR-KVStorageProvider-An-error-occurred/m-p/644875#M27149 <P>Hi Team ,</P><P>We are getting the below internal errors in majority of our indexers</P><P>"timestamp ERROR KVStorageProvider - An error occurred during the last operation ('replSetGetStatus', domain: '15', code: '13053'): No suitable servers found (`serverSelectionTryOnce` set): [connection closed calling ismaster on '[::1]:8191']"</P><P>&nbsp;</P><P>Can someone explain what that error messages indicates</P> Mon, 29 May 2023 05:40:05 GMT raj_mpl 2023-05-29T05:40:05Z https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-quot-ERROR-KVStorageProvider-An-error-occurred/m-p/644875#M27149 <P>Hi Team ,</P><P>We are getting the below internal errors in majority of our indexers</P><P>"timestamp ERROR KVStorageProvider - An error occurred during the last operation ('replSetGetStatus', domain: '15', code: '13053'): No suitable servers found (`serverSelectionTryOnce` set): [connection closed calling ismaster on '[::1]:8191']"</P><P>&nbsp;</P><P>Can someone explain what that error messages indicates</P> Mon, 29 May 2023 05:40:05 GMT https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-quot-ERROR-KVStorageProvider-An-error-occurred/m-p/644875#M27149 raj_mpl 2023-05-29T05:40:05Z https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-quot-ERROR-KVStorageProvider-An-error-occurred/m-p/644948#M27156 <P>It means you are trying run KVStore on indexers unnecessarily.&nbsp; Indexers do not use KVStore so there is no point in running it.&nbsp; Disabling KVStore on the indexers will stop the errors.</P> Mon, 29 May 2023 14:28:49 GMT https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-quot-ERROR-KVStorageProvider-An-error-occurred/m-p/644948#M27156 richgalloway 2023-05-29T14:28:49Z