Add troubleshooting entry for killed processes in MTX#2309
Merged
Conversation
Added tips for managing resource bottlenecks during tenant upgrades.
Contributor
Author
|
Merging this in so we can link to it for the Nexus colleagues. @renejeglinsky if there are further comments from your side just review them here and I'll create a follow-up PR. |
| In this case, the process was killed by a `SIGKILL` signal, typically because it exceeded its resource limits, for example memory or CPU, causing the container platform to terminate it. | ||
|
|
||
| ::: tip Distinguish extensibility and non-extensibility scenarios | ||
| While out-of-memory issues are more common, with **extensibility enabled** you’re more likely to run into CPU bottlenecks due to expensive compilations that need to be performed at (MTX) runtime. |
Contributor
There was a problem hiding this comment.
Suggested change
| While out-of-memory issues are more common, with **extensibility enabled** you’re more likely to run into CPU bottlenecks due to expensive compilations that need to be performed at (MTX) runtime. | |
| While out-of-memory issues are more common, with **extensibility enabled** you're more likely to run into CPU bottlenecks due to expensive compilations that need to be performed at (MTX) runtime. |
| While out-of-memory issues are more common, with **extensibility enabled** you’re more likely to run into CPU bottlenecks due to expensive compilations that need to be performed at (MTX) runtime. | ||
| ::: | ||
|
|
||
| MTX uses **four parallel workers** by default to perform tenant upgrades. If your project exceeds a certain complexity threshold, you might run into these resource bottlenecks. We advise you to **follow this algorithm** to mitigate resource overload: |
Contributor
There was a problem hiding this comment.
Suggested change
| MTX uses **four parallel workers** by default to perform tenant upgrades. If your project exceeds a certain complexity threshold, you might run into these resource bottlenecks. We advise you to **follow this algorithm** to mitigate resource overload: | |
| By default, MTX uses **four parallel workers** to perform tenant upgrades. If your project exceeds a certain complexity threshold, you might run into these resource bottlenecks. We advise you to **follow this algorithm** to mitigate resource overload: |
| ``` | ||
| > This won't affect application runtime performance. | ||
|
|
||
| 4. **Increase the number of MTX sidecars (scale out)**: To compensate for eventual performance losses from **3.**, distribute the work across multiple sidecars. |
Contributor
There was a problem hiding this comment.
Maybe it's more future-proof if we describe what 3. refers too :)
Suggested change
| 4. **Increase the number of MTX sidecars (scale out)**: To compensate for eventual performance losses from **3.**, distribute the work across multiple sidecars. | |
| 4. **Increase the number of MTX sidecars (scale out)**: If you decided to decrease workers in async operations, you can compensate eventual performance losses by distributing the work across multiple sidecars. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To have a better guidance for projects running into resource constraints during tenant upgrades.