-
Notifications
You must be signed in to change notification settings - Fork 122
Updated configuration details for Management and KVM Agent services #623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 4.20
Are you sure you want to change the base?
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) |
| 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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: |
|
|
||
| /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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| #. 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 |
| /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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| #. 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section looks like it is duplicated, perhaps here we can reference to the section defined on tuning.rst?
📚 Documentation preview 📚: https://cloudstack-documentation--623.org.readthedocs.build/en/623/