How Other Command Line Options Affect Auto-scaling
- Last Updated: April 14, 2026
- 1 minute read
- MarkLogic Server
- Version 12.0
- Documentation
The following existing command line options also affect the auto-scaling feature:
-
-thread_countand-thread_count_per_split: When these two options are specified, mlcp will use a fixed number of threads and auto-scaling will not happen. -
-max_threads: When-max_threadsis specified, mlcp will cap the maximum thread count, and auto-scaling cannot go beyond this number. This is to prevent the client-side from running out of memory as the DHS cluster may have a huge number of nodes. By default,-max_threadsis not set.