1.8 KiB
| layout | page_title | sidebar_current |
|---|---|---|
| docs | Frequently Asked Questions | docs-faq |
Frequently Asked Questions
Q: Why is virtual memory usage high?
Consul makes use of LMDB internally for various data storage purposes. LMDB relies on using memory-mapping, a technique in which a sparse file is represented as a contiguous range of memory. Consul configures high limits for these file sizes, and as a result relies on a large chunks of virtual memory to be allocated. However, in practice the limits are much larger than any realistic deployment of Consul would ever use, and the resident memory or physical memory used is much lower.
Q: What is Checkpoint? / Does Consul call home?
Consul makes use of a HashiCorp service called Checkpoint which is used to check for updates and critical security bulletins. Only anonymous information is sent to Checkpoint, and cannot be used to identify the user or host. An anonymous ID is sent which helps de-duplicate warning messages and can be disabled. Using the Checkpoint service is optional and can be disabled.
See disable_anonymous_signature
and disable_update_check.
Q: How does Atlas integration work?
Consul makes use of a HashiCorp service called SCADA which stands for Supervisory Control And Data Acquisition. The SCADA system allows clients to maintain a long-running connection to Atlas which is used to make requests to Consul agents for features like the dashboard and auto joining. Standard ACLs can be applied to the SCADA connection, which has no enhanced or elevated privileges. Using the SCADA service is optional and only enabled by opt-in.
See the Atlas integration guide.