When experimenting with Openshift v3 - I could create and deploy a very simple webapplication with Wildfly & postgres.
When trying to create a very simple SpringBoot application (as a WAR) with Mysql (with 1 table), the MySql volume storage immediately exceeds the quota. As a result the very simple application cannot run properly.
Error creating: pods "springbootmysql-8-" is forbidden: exceeded
quota: compute-resources, requested: limits.cpu=1,limits.memory=512Mi,
used: limits.cpu=2,limits.memory=1Gi, limited:
limits.cpu=2,limits.memory=1Gi 19 times in the last 11 minutes
Update: now I configured both pod's with 480Mi memory - the memory quota's are not exceeded.
I now get an error message stoping the build and deployment:
Error creating: pods "springbootmysql6-2-" is forbidden: exceeded
quota: compute-resources, requested:
limits.cpu=957m,limits.memory=490Mi, used:
limits.cpu=1914m,limits.memory=980Mi, limited:
limits.cpu=2,limits.memory=1Gi
On OpenShift Online Starter, if running both a database and frontend with both using 512MB each, you only have enough resources to use the Recreate deployment strategy. You will need to go into the deployment configuration for the front end and change the deployment strategy from Rolling to Recreate.
If after making the change it is still having the same issue, scale down the number of replicas of the front end to 0, and then back to 1. This will ensure that Kubernetes is not stuck in the prior state since it was still trying to deploy under the old settings. Things should then be okay.
Related
Hi When my Elastic Beanstalk (m5a.large Windows Server with deployed .net Core WebApi) comes under heavy load, the Status in the Health Page for my EC2 instances turns red, my Requests and the Healthcheck are timing out. That happens around 1-3 minutes after having a minimum of 10-20 Req/sec for a server.
I have to launch a lot of servers, so that each server gets a Request/Second count of 1-5 so they do not turn red.
In my logs I saw the following Errors:
Exception=MySql.Data.MySqlClient.MySqlException (0x80004005): Unable to connect to any of the specified MySQL hosts.
---> MySql.Data.MySqlClient.MySqlException (0x80004005): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
These Errors brought me to the topic Connection Pooling so i switched
using MySql.Data.MySqlClient;
to
using MySqlConnector;
Now these Errors do not come up anymore but the Problem remains.
The Monitoring Feature of EB and RDS do not state any obvious Problems. Running Queries in Mysql Workbench against the Database is fast as usual.
At the moment, my Database calls from the server are synchronous and not using the async feature of MysqlConnector.
Does the m5a.large cannot process more than 5 Request/Second?
Kind Regards
I have created an RDS on AWS which initially shows the status of 'available' but when I use my sql client to connect to it I receive the error:
Status : Failure -Test failed: IO Error: Connection reset by peer, Authentication lapse 0 ms
Then when I check the status of the RDS online (AWS dashboard) it says 'stopping'.
When I try to start the RDS again it's status will go from 'starting' to 'stopping' after a couple of minutes and then eventually 'stopped'. I can't find anything online referring to an RDS automatically stopping and I am somewhat a novice to AWS.
Based on the comments.
The solution was found by checking CloudTrial Event history. Based on the search it was identified that StopDBInstance was issued by HIPComplianceWorker user.
This probably means that there is an automation that checks the db instances launched and verifies if they comply with your companies policies. Your instance could be violating such policies, and it was automatically stopped.
You would have to contact your admins to check with them what kind of RDS you can use.
Cannot create persistent volume claim "mysql". persistentvolumeclaims "mysql" is forbidden: exceeded quota: 6176696e6173686b616e74616b-noncompute, requested: requests.storage=1Gi, used: requests.storage=0, limited: requests.storage=0
I have paid account in OpenShift 3.
Can anyone help get this resolved?
Hadoop node manager doesn't satisfy minimum allocations. I am getting the following error:
org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Received
SHUTDOWN signal from Resourcemanager, Registration of NodeManager
failed, Message from Resource Manager: NodeManager from
DP112.Mas.company.com doesn't satisfy minimum allocations, Sending
SHUTDOWN signal to the NodeManager.
RAM -6 GB in my physical box
And I am setting Single node setup for initial testing purpose
The "ResourceManager: NodeManager from *** doesn't satisfy minimum allocations" error is seen when node on which node manager is being started does not have enough resources w.r.t yarn.scheduler.minimum-allocation-vcores and yarn.scheduler.minimum-allocation-mb configurations.
Reduce values of yarn.scheduler.minimum-allocation-vcores and / or yarn.scheduler.minimum-allocation-mb then restart Yarn.
I am running Resque on Heroku, and my database is ClearDB. I am getting this error:
"Mysql2::Error: User 'bdb2aedbee2c38' has exceeded the 'max_user_connections' resource (current value: 10): SHOW FULL FIELDS FROM projects"
That error is coming from my Resque admin of my Heroku app.
How can I figure out how many connections Resque is making to ClearDB?
How can I tell ClearDB to either allow more connections, or tell Resque to create less?
Does "current value: 10" refer to how many connections ClearDB is allowing, or is this how many current connections Resque is trying to make?
Thanks!
Your application server dynos or Resque workers are consuming more connections than your database plan provides.
You have two options:
Scale up your database by upgrading to a higher ClearDB plan (http://dashboard.heroku.com)
Scale down your application by reducing the number of dynos/workers (heroku ps:scale command)
The first link when I googled your addons links to the page describing the service and pricing tiers. You are on the free, 10 connection tier.
https://addons.heroku.com/cleardb