Clearer log messages in bootstrap checks

This commit clarifies some log messages for the bootstrap checks. The
message is that the user has limits set that are below the minimums that
Elasticsearch requires.

Relates #21423
This commit is contained in:
Robin Clarke 2016-11-09 18:28:51 +01:00 committed by Jason Tedor
parent 474f63ebac
commit 60450a38c4
1 changed files with 4 additions and 4 deletions

View File

@ -261,7 +261,7 @@ final class BootstrapCheck {
public final String errorMessage() {
return String.format(
Locale.ROOT,
"max file descriptors [%d] for elasticsearch process likely too low, increase to at least [%d]",
"max file descriptors [%d] for elasticsearch process is too low, increase to at least [%d]",
getMaxFileDescriptorCount(),
limit
);
@ -313,7 +313,7 @@ final class BootstrapCheck {
public String errorMessage() {
return String.format(
Locale.ROOT,
"max number of threads [%d] for user [%s] likely too low, increase to at least [%d]",
"max number of threads [%d] for user [%s] is too low, increase to at least [%d]",
getMaxNumberOfThreads(),
BootstrapInfo.getSystemProperties().get("user.name"),
maxNumberOfThreadsThreshold);
@ -337,7 +337,7 @@ final class BootstrapCheck {
public String errorMessage() {
return String.format(
Locale.ROOT,
"max size virtual memory [%d] for user [%s] likely too low, increase to [unlimited]",
"max size virtual memory [%d] for user [%s] is too low, increase to [unlimited]",
getMaxSizeVirtualMemory(),
BootstrapInfo.getSystemProperties().get("user.name"));
}
@ -367,7 +367,7 @@ final class BootstrapCheck {
public String errorMessage() {
return String.format(
Locale.ROOT,
"max virtual memory areas vm.max_map_count [%d] likely too low, increase to at least [%d]",
"max virtual memory areas vm.max_map_count [%d] is too low, increase to at least [%d]",
getMaxMapCount(),
limit);
}