anchor.diff:  // CONSOLE
   
   If you see that `mlockall` is `false`, then it means that the `mlockall`
  -request has failed.  You will also see a line with more information in the
  -logs with the words `Unable to lock JVM Memory`.
  +request has failed.  You will also see a line with more information in the logs
  +with the words `Unable to lock JVM Memory`.
   
   The most probable reason, on Linux/Unix systems, is that the user running
  -Elasticsearch doesn't have permission to lock memory.  This can be granted as follows:
  +Elasticsearch doesn't have permission to lock memory.  This can be granted as
  +follows:
   
   `.zip` and `.tar.gz`::
   
  
positive.code: --------------
  
  or setting this JVM flag in the jvm.options configuration file.
  
  [[disable-swap-files]]
  ==== Disable all swap files
  
  The second option is to completely disable swap. Usually Elasticsearch
  is the only service running on a box, and its memory usage is controlled
  by the JVM options.  There should be no need to have swap enabled.
  
  On Linux systems, you can disable swap temporarily
  by running: `sudo swapoff -a`. To disable it permanently, you will need
  to edit the `/etc/fstab` file and comment out any lines that contain the
  word `swap`.
  
  On Windows, the equivalent can be achieved by disabling the paging file entirely
  via `System Properties → Advanced → Performance → Advanced → Virtual memory`.
  
  [[swappiness]]
  ==== Configure `swappiness`
  
  Another option available on Linux systems is to ensure that the sysctl value
  `vm.swappiness` is set to `1`. This reduces the kernel's tendency to swap and
  should not lead to swapping under normal circumstances, while still allowing
  the whole system to swap in emergency conditions.
  
negative.code: RPM and Debian::
  
    Set `MAX_LOCKED_MEMORY` to `unlimited` in the
    <<sysconfig,system configuration file>> (or see below for systems using
    `systemd`).
  
  Systems using `systemd`::
  
    Set `LimitMEMLOCK` to `infinity` in the <<systemd,systemd configuration>>.
  
  Another possible reason why `mlockall` can fail is that the temporary directory
  (usually `/tmp`) is mounted with the `noexec` option. This can be solved by
  