I'm trying to temporarily disable performance insights for an RDS MySQL t4g instance (which is using the latest MySQL version and has performance insights already enabled and in effect). The RDS documentation describes a "Performance Insights" section where this can be toggled, which I remember using when setting up the instance:
But this section is entirely missing when I go to the "Modify" view from the instance page. This is true even when I click on the option to "Modify retention tier" from the performance insights page directly:
Also (and I'm only mentioning this as possibly another effect of the same underlying issue), when I've visited the insights page for this instance in the past couple days, about 2 out of 3 times all the performance insight data over any timespan just appears as NaN, even after a system update and multiple reboots.
I do get these metrics to appear if I hard refresh enough times, but for another instance it always shows up right away.
I have combed over the entire performance insights documentation and have not found any reason why this section wouldn't appear, but I feel like I'm missing something that would be causing this to happen. Is there anywhere else I should be looking?
EDIT: I just tried to change a different (unrelated) setting on the same instance and got this message that my instance with already-enabled performance insights doesn't support performance insights, so I have to disable it...when I don't even have the option!
Related
I have been trying to setup a Deep Learning VM but I am not able to request for an increase in quota even after upgrading my account. I have found various answers on the internet detailing the steps but I can't seem to relate with them. My quotas page looks so much different than the others on the internet. I can't see any column for metrics and all etc. I am attaching a screenshot of my quota page with this query. After pressing the edit quotas option and Before pressing the edit quotas optionThere are two screeshots: one before pressing the edit quotas option and one after it.
I couldn't seem to find a solution as the whole layout of the webpage is different. Please help me.
it's not a problem of account type but an issue in your location. Have a look to that documentation page to see what is available in your region.
You can see that M1 VM or NVidia GPUs aren't available, it's not a quota issue, it a service availability issue.
The title pretty much says it all, but just to clarify:
Redis afaik has a performance metric mem_fragmentation_ratio, giving the ratio of memory used as seen by the OS (used_memory_rss) to memory allocated by Redis (used_memory).
Is it possible to find this metric (or calculate it using other existing metrics) in Cloud Monitoring?
Unfortunately the answer is no. Only the GCP support team is able to verify this metric with their internal tools :(, nevertheless, I found this Public Issue tracker that is requesting to add this metric to monitor the instance. I suggest you do a comment and start the issue so you can get notifications about this :)
on the other hand, about the calculation, I found this link. It seems that the formula is:
MemoryFragmentationRatio= Used_Memory_RSS / Used_Memory
With the command "info all" you can get these values.
I really hope that the aforementioned information helps you.
I enabled Performance Insights on an existing SQL Server database (MySql 5.6.46) in AWS RDS.
But still, it shows 0 sessions and “No active sessions in the selected time range” no matter what duration I've select from the top list.
Is there some condition I need to meet in order to have my query get recorded in Performance Insights? What're the criteria? How can I troubleshoot this?
I created AWS Support case where AWS Engineer explained to me:
Unfortunately, this is a known issue from our end where Performance Insights does not get enabled when it is issued in the same API call as engine version upgrade as RDS follows a priority in executing multiple requests that have been submitted as part of the same API call - for example in this case, request to enable Performance Insights and request to upgrade the instance to 11.1 version. Performance Insights call is evaluated first followed by the engine upgrade. This means that when Performance Insights request was being considered, the instance was still on the previous incompatible version, hence the request did not go through successfully.
The workaround to resolve this issue is to disable Performance insights, wait a few minutes and then re-enable Performance Insights.
Enabling/disabling Performance Insights does not cause an outage/downtime. The Performance Insights agent is designed to stay out of your database workloads' way. When Performance Insights detects heavy load or depleted resources, it backs off, still collecting data, but only when it is safe to do so.
not have enough resources available to fulfill the request try a different zone
All of my machines in the different zone
have the same issue and can not run.
"Starting VM instance "home-1" failed.
Error:
The zone 'projects/extreme-pixel-208800/zones/us-west1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later."
I am having the same issue. I emailed google and figured out this has nothing to do with quota. However, you can try to decrease the need of your instance (eg. decrease RAM, CPUs, GPUs). It might work if you are lucky.
Secondly, if you want to email google again, you will get the message sent from the following template.
Good day! This is XX from Google Cloud Platform Support and I'll be
glad to help you from here. First, my apologies that you’re
experiencing this issue. Rest assured that the team is working hard to
resolve it.
Our goal is to make sure that there are available resources in all
zones. This type of issue is rare, when a situation like this occurs
or is about to occur, our team is notified immediately and the issue
is investigated.
We recommend deploying and balancing your workload across multiple
zones or regions to reduce the likelihood of an outage. Please review
our documentation [1] which outlines how to build resilient and
scalable architectures on Google Cloud Platform.
Again, we want to offer our sincerest apologies. We are working hard
to resolve this and make this an exceptionally rare event. I'll be
keeping this case open for one (1) business day in case you have
additional question related to this matter, otherwise you may
disregard this email for this ticket to automatically close.
All the best,
XXXX Google Cloud Platform Support
[1] https://cloud.google.com/solutions/scalable-and-resilient-apps
So, if you ask me how long you are expected to wait and when this issue is likely to happen:
I waited for an average of 1.5-3 days.
During the weekend (like from Friday to Sunday) daytime EST, GCP has a high probability of unavailable resources.
Usually when you have one instance that has this issue, others too. For me, keep trying in different region waste my time. (But, maybe it just that I don't have any luck)
The error message "The zone 'projects/[...]' does not have enough resources available to fulfill the request. Try a different zone, or try again later." is always in reference to a shortage of resources in a zone.
Google recommends spreading your workload across different zones to reduce the impact of these issues on your workload. Otherwise, there isn't much else to do other than wait or try another zone/region
Faced this Issue yesterday [01/Aug/2020] when GCP free credit was over and below steps helped to workaround this.
I was on asia-south-c zone and moved to us zone
Going to my Google Cloud Platform >>> Compute Engine
Went to Snapshots >>> created a snapshot >>> Select your Compute Engine instance
Once snapshot was completed I clicked on my snapshot.
Ended up under "snapshot details". There, on the top, just click create instance. Here you are basically creating an instance with a copy of your disk.
Select your new zone, don't forget to attach GPUs, all previous setting, create new name.
Click create, that's it, your image should now be running in your new zone
No worry of losting configuration as well.
Today (15/06/2018) we found two reserved addresses were disassociated from two GCE instances.
Nobody ordered this disassociation, in fact in the activity logs we do not found any activity on this two reserved addresses.
We manually re-associate the two reserved addresses to our machines to solve the problem.
Is it possible to know what happened?
Good sources to see what happened are the "Activity" tab in the Cloud Console as well as the AuditLog entries in Stackdriver Logging. If it is still not clear what happened based on that, please file a support case for further investigation.
If your instances were in the stopped state at the time it may be related to this incident:
https://status.cloud.google.com/incident/compute/18005
By reading this link I ran the following advanced filter from Stackdriver:
resource.type="gce_instance"
jsonPayload.event_subtype="compute.instances.deleteAccessConfig"
This filter shows the actor (user or a service account) and the event type (how it happened).
If you need further information, I would suggest filling an issue here.