Closed leima965 closed 4 years ago
looks like it should have a index on workflow_workflow_step.workflow_commands_id.
create index workflow_wf_step_cust_idx01 on workflow_workflow_step(workflow_commands_id);
it fixed the cpu issue
In an effort to focus on bugs and issues that impact currently supported versions of Rundeck, we have elected to notify GitHub issue creators if their issue is classified as stale and close the issue. An issue is identified as stale when there have been no new comments, responses or other activity within the last 12 months. If a closed issue is still present please feel free to open a new Issue against the current version and we will review it. If you are an enterprise customer, please contact your Rundeck Support to assist in your request. Thank you, The Rundeck Team
Hi Team, after we update our rundeck from version 2.4 to 2.6 and our RDS mysql database cpu usage up tp 98%, so we cannot even login to the website. After we upgrade the database from db.m3.medium to db.m3.large. This issue still happens when we run about 15 jobs at the same time. We have about 15 scheduled jobs running every 5 mins to fetch the nodes from foreman. We have same thing setup in version 2.4 but we don't have this issue.