Does the following notify error cause indexing issues?

[cjohnson421]

I have a server running Splunk Enterprise 7.2, and we've been having indexing issues the past week. I found the following error in the splunkd logs for max user watches.

0500 ERROR FilesystemChangeWatcher - Error using inotify to watch filesystem -- /proc/sys/fs/inotify/max_user_watches is probably too low.  Falling back to using timeout-based polling.

Could this error be what is causing the indexing issues?

[MoniM]

Hii @cjohnson421,

You can follow the below answer, it might help you:-
https://answers.splunk.com/answers/147511/filesystemchangewatcher-error-getting-attributes-of-path.h...

[vishaltaneja070]

Not sure about that. but Try to fix the error using the below link:
https://github.com/kubernetes/kubernetes/issues/46230