This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
In a large cluster shared by 100's of applications from different LOBs, quite often, the a bad application workload might crash or disable servers by:
1) over consumption of system memory
2) filling up the root file systems with core files
3) etc
In the situation of over consumption of system memory case, even with the cgroup memory limit feature over symphony workload is set. We still see cases of system memory over consumption and crashes the server rapidly. The outcome of this is that a bad behaving application workload bring down servers along with the workloads from other applications (especially over long running tasks).
Per our observation, such bad application has the following characteristics:
1) The service instance persists to avoid the latency of starting the service instances
2) The run-time of its tasks is very short (in seconds if not in minutes)
3) If there is memory leak and/or slowness of freeing unused memory, it will resource a large accumulative memory foot print on the system.
4) The bad behavior will also leave no/less memory for other application workloads on the same server/system.
In order to avoid a bad application going wild, a new demand arise to have ability at the application configuration level to stop abusing the server by limiting the maximum number of tasks executed in a persistent service instance. So that, the application could release the memory faster and have the shared server more reliable to other good applications.
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
.Solution and sample code has been provided by Ajith to Andrew.
Solution and sample code has been provided by Ajith to Andrew.