zowe / zowe/api-layer

Support of configuring new values to tweak resources / performance

Open
#4,152 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Priority: Low size/S
Dominant language
Java
Stars
92
Forks
81
Avg merge
1d 9h
Merged PRs (30d)
46

Description

Is your feature request related to a problem? Please describe.

Regarding https://github.com/zowe/docs-site/pull/4504 there are some values (Tomcat thread pool, direct memory) that cannot be set directly to a service. It is necessary to set via system environment. These are shared between services which does not make sense.

The aim is to support these configuration via script and document it int he article.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Willingness to help
If you are willing to help with feedback on the implementation or with the actual implementation,
please state your willingness to assist in the created issue. We will take it into account when figuring what to work on.

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the configuration approach discussed in docs-site/pull/4504 and identify how service settings are currently supplied through the system environment. Focus on the Tomcat thread pool and direct-memory values, then determine the script changes and article updates needed to configure them per service. Done means the values can be configured through the script and the behavior is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend, documentation, performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.