Skip to content

Conversation

@sureshanaparti
Copy link
Contributor

@sureshanaparti sureshanaparti commented Feb 9, 2026

@sureshanaparti sureshanaparti added this to the 4.20.3 milestone Feb 9, 2026
@sureshanaparti
Copy link
Contributor Author

@blueorangutan docbuild

@blueorangutan
Copy link

@sureshanaparti a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress.

@blueorangutan
Copy link

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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#. 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#. 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants