Updated configuration details for Management and KVM Agent services#623
Conversation
|
@blueorangutan docbuild |
|
@sureshanaparti a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
|
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/623. (QA-JID 488) |
source/adminguide/tuning.rst
Outdated
| Disable Omit Stack Trace | ||
| ------------------------ | ||
|
|
||
| JVM by default stop printing some stack traces in the logs. To enable print stack traces always: |
There was a problem hiding this comment.
| JVM by default stop printing some stack traces in the logs. To enable print stack traces always: | |
| The JVM, by default stops printing some stack traces in the logs. To enable printing full stack traces at all times: |
source/adminguide/tuning.rst
Outdated
|
|
||
| /etc/default/cloudstack-management | ||
|
|
||
| #. Add the command-line parameter -XX:-OmitStackTraceInFastThrow to disable omit stack trace flag in JVM so that all |
There was a problem hiding this comment.
| #. Add the command-line parameter -XX:-OmitStackTraceInFastThrow to disable omit stack trace flag in JVM so that all | |
| #. Add the command-line parameter -XX:-OmitStackTraceInFastThrow to disable omit stack trace flag in the JVM so that all |
source/adminguide/tuning.rst
Outdated
| /etc/default/cloudstack-management | ||
|
|
||
| #. Add the command-line parameter -XX:-OmitStackTraceInFastThrow to disable omit stack trace flag in JVM so that all | ||
| the stack traces are always printed on the logs. This flag is enabled by default in JVM to omit the stack traces |
There was a problem hiding this comment.
| the stack traces are always printed on the logs. This flag is enabled by default in JVM to omit the stack traces | |
| the stack traces are always printed on the logs. This flag is enabled by default in the JVM to omit the stack traces |
|
|
||
| - Limit the number of file descriptors | ||
|
|
||
| Default configuration is usually higher, set to lower number explicitly when required. It is observed |
There was a problem hiding this comment.
| Default configuration is usually higher, set to lower number explicitly when required. It is observed | |
| The default configuration is usually higher, set to a lower number explicitly when required. It is observed |
|
|
||
| - Limit the CPU quota | ||
|
|
||
| You can control the CPU allocation. For example,set to allow 2 full cores worth of CPU time as shown below. |
There was a problem hiding this comment.
| You can control the CPU allocation. For example,set to allow 2 full cores worth of CPU time as shown below. | |
| You can control the CPU allocation. For example, set to allow 2 full cores worth of CPU time as shown below. |
| Disable Omit Stack Trace | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| JVM by default stop printing some stack traces in the logs. To enable print stack traces always: |
There was a problem hiding this comment.
| JVM by default stop printing some stack traces in the logs. To enable print stack traces always: | |
| The JVM by default stops printing some stack traces in the logs. To enable print stack traces at all times: |
|
|
||
| /etc/default/cloudstack-agent | ||
|
|
||
| #. Add the command-line parameter -XX:-OmitStackTraceInFastThrow to disable omit stack trace flag in JVM so that all |
There was a problem hiding this comment.
| #. Add the command-line parameter -XX:-OmitStackTraceInFastThrow to disable omit stack trace flag in JVM so that all | |
| #. Add the command-line parameter -XX:-OmitStackTraceInFastThrow to disable the omit stack trace flag in the JVM so that all |
| /etc/default/cloudstack-agent | ||
|
|
||
| #. Add the command-line parameter -XX:-OmitStackTraceInFastThrow to disable omit stack trace flag in JVM so that all | ||
| the stack traces are always printed on the logs. This flag is enabled by default in JVM to omit the stack traces |
There was a problem hiding this comment.
| the stack traces are always printed on the logs. This flag is enabled by default in JVM to omit the stack traces | |
| the stack traces are always printed on the logs. This flag is enabled by default in the JVM to omit the stack traces |
| sudo systemctl restart cloudstack-agent | ||
|
|
||
|
|
||
| Disable Omit Stack Trace |
There was a problem hiding this comment.
This section looks like it is duplicated, perhaps here we can reference to the section defined on tuning.rst?
There was a problem hiding this comment.
ah, that tuning is for cloustack-management
|
@blueorangutan docbuild |
|
@sureshanaparti a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
|
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/623. (QA-JID 491) |
sureshanaparti
requested review from
DaanHoogland,
kiranchavala and
nvazquez
kiranchavala
left a comment
kiranchavala
left a comment
There was a problem hiding this comment.
@sureshanaparti as discussed please add a note for usage and systemvm in the tuning section
|
@blueorangutan docbuild |
|
@sureshanaparti a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
|
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/623. (QA-JID 493) |
sureshanaparti
force-pushed
the
mgmt-server-and-agent-service-config-doc
branch
from
8488bd5 to
6ae42a3
Compare
|
@blueorangutan docbuild |
|
@sureshanaparti a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
|
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/623. (QA-JID 494) |
@kiranchavala check here: |
nvazquez
left a comment
nvazquez
left a comment
There was a problem hiding this comment.
Thanks @sureshanaparti - LGTM
5 participants
📚 Documentation preview 📚: https://cloudstack-documentation--623.org.readthedocs.build/en/623/