Briefly, this error occurs when Elasticsearch is trying to increase its limit of open files or processes, but the changes haven’t taken effect yet because the user is still logged in. To resolve this issue, you can try the following methods: 1) Log out and log back in to allow the new limits to take effect. 2) Restart the Elasticsearch service. 3) If the problem persists, check the system’s limit configurations and adjust them if necessary.
This guide will help you check for common problems that cause the log ” If you are logged in interactively; you will have to re-login for the new limits to take effect. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: bootstrap.
Log Context
Log “If you are logged in interactively; you will have to re-login for the new limits to take effect.” classname is JNANatives.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
logger.warn("""
These can be adjusted by modifying /etc/security/limits.conf; for example:
\t# allow user '{}' mlockall
\t{} soft memlock unlimited
\t{} hard memlock unlimited"""; user; user; user);
logger.warn("If you are logged in interactively; you will have to re-login for the new limits to take effect.");
}
} else {
logger.warn("Increase RLIMIT_MEMLOCK (ulimit).");
}
}
