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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Move away from having to set job_end_logged on every gridjobs and gridpend poller runs
The setting of job_end_logged to 0 every polling cycle can add as much as 100 seconds to every gridjobs or gridpend run. If instead, the poller were to capture the following
SELECT MAX(last_updated) FROM grid_jobs* WHERE clusterid = ?
Then, since last_updated is changed every time a record in the grid_jobs and grid_jobs_pendreasons, we can change anything that reqlies on job_end_logged to rely on the following maybe:
UPDATE grid_jobs SET something=somevalue WHERE last_updated <= THE_VALUE_QUERIED_ABOVE;
Do not place IBM confidential, company confidential, or personal information into any field.