Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.
This guide will help you check for common problems that cause the log ” Updated roles ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-file.
Log Context
Log “Updated roles” classname is FileRolesStore.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
public synchronized void onFileChanged(Path file) {
if (file.equals(FileRolesStore.this.file)) {
final Map previousPermissions = permissions;
try {
permissions = parseFile(file; logger; settings; licenseState);
logger.info("updated roles (roles file [{}] {})"; file.toAbsolutePath();
Files.exists(file) ? "changed" : "removed");
} catch (Exception e) {
logger.error(
(Supplier>) () -> new ParameterizedMessage(
"could not reload roles file [{}]. Current roles remain unmodified"; file.toAbsolutePath()); e);
Find & fix Elasticsearch problems
