2.0 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 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, which cannot be used to identify the user or host, is sent to Checkpoint . An anonymous ID is sent which helps de-duplicate warning messages. This anonymous ID can can be disabled. In fact, 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 (Supervisory Control And Data Acquisition). The SCADA system allows clients to maintain long-running connections to Atlas. Atlas can in turn provide auto-join facilities for Consul agents (supervisory control) and an integrated dashboard showing the health of all connected agents (data acquisition).
Standard ACLs can be applied to the SCADA connection, ensuring that Atlas is given only those privileges that make sense for your deployment.
Using the SCADA service is optional. SCADA is only enabled by opt-in.
See the Atlas integration guide for more details.