elasticsearch啟動警告
Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out. Increase RLIMIT_MEMLOCK (ulimit).
內存鎖定值的限制(max locked memory)
這個值只對普通用戶起作用,對超級用戶不起作用,這個問題是由于CAP_IPC_LOCK造成的.linux對內存是分頁管理的,這意味著有不需要時,在物理內存的數據會被換到交換區或磁盤上.有需要時會被交換到物理內存,而將數據鎖定到物理內存可以避免數據的換入/換出.采用鎖定內存有兩個理由:1)由于程序設計上需要,比如oracle等軟件,就需要將數據鎖定到物理內存.2)主要是安全上的需要,比如用戶名和密碼等等,被交換到swap或磁盤,有泄密的可能,所以一直將其鎖定到物理內存.
查看項目進程限制，17497為pid
cat /proc/17497/limits
查看系統限制ulimit -a
core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 1032980 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 600000 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) 600000 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
vim /etc/security/limits.conf增加2行，設為更大的值或者unlimited
- soft memlock unlimited
- hard memlock unlimited
其他可以使用ulimit添加自定義的限制（很多選項系統默認未開啟），可以對一些不同用戶進行限制
# # - core - limits the core file size (KB) # - data - max data size (KB) # - fsize - maximum filesize (KB) # - memlock - max locked-in-memory address space (KB) # - nofile - max number of open files # - rss - max resident set size (KB) # - stack - max stack size (KB) # - cpu - max CPU time (MIN) # - nproc - max number of processes # - as - address space limit (KB) # - maxlogins - max number of logins for this user # - maxsyslogins - max number of logins on the system # - priority - the priority to run user process with # - locks - max number of file locks the user can hold # - sigpending - max number of pending signals # - msgqueue - max memory used by POSIX message queues (bytes) # - nice - max nice priority allowed to raise to values: [-20, 19] # - rtprio - max realtime priority
總結
以上就是這篇文章的全部內容了，希望本文的內容對大家的學習或者工作具有一定的參考學習價值，謝謝大家對服務器之家的支持。
