PubSub service having issue? - google-cloud-platform

It seems like api's are timing out when creating subscription for already existing topics. My tests which validate this was working until few minutes back but now they started failing. I am not even able to create subscription using Google's console either.
Though Google's dashboard shows service as working. Anyone else seeing this? I am not sure what else I can do to gather more info.

Yes, we had an issue with error rates higher than expected around that time. The users should have seen 504 errors during the outage. As of 1:30PM, the issue has been resolved, and everything should be back to normal. Sorry about the inconveniences.
We do have SLA. Cloud Pub/Sub SLA is described here:
https://cloud.google.com/pubsub/sla
If you think you're eligible, you can request a refund from that page.
Sorry again for the inconveniences you may have had.

Related

ZONE_RESOURCE_POOL_EXHAUSTED for DataFlow & DataPrep

Alright team...Dataprep running into BigQuery. I cannot for the life of me find out why I have the ZONE_RESOURCE_POOL_EXHAUSTED issue for the past 5 hours. The night before, everything was going great, but today, I am having some serious issues.
Can anyone give any insight into how to change the resource pool for Dataflow jobs with regard to Dataprep? I can't even get a basic column transform to push through.
Looking forward to anyone helping me with this because honestly, this issue one of those "just change this and maybe that will fix it and if not, maybe a few weeks and it'll work".
Here is the issue in screenshot: https://i.stack.imgur.com/Qi4Dg.png
UPDATE:
I believe some of my issue may deal with GCP Compute incident 18012 espcially since it's a us-central based issue for creation of instances.
The incident you mentioned was actually resolved on November 5th and was only affecting the us-central1-a zone. Seeing that your question was posted on November 10th and other users in the comments got the error in the us-central1-b zone, the error is not related to the incident you linked.
As the error message suggests, this is a resource availability issue. These scenarios are rare and are usually resolved quickly. If this ever happens in the future, using Compute Engine instances in other regions/zones will solve the issue. To do so using Dataprep, as mentioned in the comment, after the job is launched from Dataprep, you can re-run the job from Dataflow while specifying the region/zone you would like to run the job in.

Cannot Extend GPU Quota on Google Cloud

I am using Google Cloud for development and training of deep neural networks. I've reached the limits of what I can do with CPUs and now need to create and instance with one or more GPUs.
I've followed the instructions from multiple sources. As the instance was being created I received a notification that my quota for my region (us-west1) was zero and to request an increase.
I did so and received the confirmation email within minutes. However, when I then attempted to recreate the instance I was again met with the quota increase error.
I submitted another request (same region) but heard nothing.
I tried in a different region, again requesting a quota increase, but heard nothing. I did this 6 times and -- as you might have guessed -- neither received a confirmation email nor was I able to create my instance.
I tried the hack of using Chrome in Incognito mode, but no joy.
This was an issue a few months ago, at least judging from the S/O and Google forum posts. I would think that by now it would be fixed.
Any help would be much appreciated as I'm totally stuck
NB: Cross-posted to the gce-discussion forum
I think you should contact the Google Cloud Platform Support for this kind of issues.
Open a case asking why your quota increase has not been applied and I am sure they are going to solve this in some days or at least to tell you why your request was declined.
Notice that quoting from the official Documentation "Free Trial accounts do not receive GPU quota by default."
Disclaimer: I work for the Google Cloud Support.

WSO2 Throttling API

I have gone through read the various questions involving throttling on stack overflow. However, I didn't find anyone with a similar issue to what I'm seeing. I have gone through the tutorials and setup process on the WSO2 site regarding throttling.
This is what I have done:
Setup an additional tier to allow 5 calls per minute on the
following levels (Advanced Throttling, Application Throttling,
Subscription Throttling).
Edit the API and set the subscription tier level to the new custom
tier
Set the Application to the new tier level
Set the Advanced Throttling Policy to apply to the API, then I saved & published
Ran 1100 HTTP requests from an application that calls the API on an
interval every second. Every request made was successfully processed
without any throttling.
I installed version 1.9 of API manager and setup the very same rules
The requests were throttled correctly.
Any help would be greatly appreciated, I'm not really sure if it is a bug or a configuration issue on my end.
Regards
So after much digging in the WSO2 documentation. I have found that in order to use the advanced throttling techniques (which are enabled by default) you must use Traffic Manager (which is disabled by default).
There are instructions on how to use Traffic Manager in the WSO2 documentation. If advanced throttling is disabled the basic throttling works as expected.
It took some time to discover this as the documentation doesn't clearly make the distinction very clear in the documentation.
I hope this helps someone having a similar issue.

AWS Your account is not ready for posting messages yet

I just signed up to the forum for AWS using my console account. All good.
I go post for the first time and I get:
Your account is not ready for posting messages yet
I do not have an ad blocker so I have not found any other solutions to this. Any help is appreciated.
If this is a persistent problem, the solution is to open a ticket with support.
According to this document, this is to help reduce the amount of spam. New accounts accumulate the ability to post messages over time.
To limit spam posted to the AWS forums, the number of messages an account can post is limited. The number of messages an account can post steadily increases over time. Newly activated accounts might not be able to post any messages for a few hours.
Look here for more info.
I could posted my question in forum with in 1 hour.
Just wait for a while, approximately 30 mins. It's automatically solved.

Amazon Web Services: where to get help?

I'm working with Amazon's Product Advertising API and need some help on a few issues. The questions I have posted on SO and Amazon developer forums have gone unanswered. Where can I find help?
Looks like your best bet is going to be to pay amazon for support: http://aws.amazon.com/premiumsupport/
My guess is that there aren't many people using that API hence the problem getting regular programmers to help you. This is evidenced by a notice on the main AWS page (https://affiliate-program.amazon.com/gp/advertising/api/detail/main.html) about a number of discontinued API operations and responses due to low usage.
"low usage" in this scenario is usually marketing speak meaning "no one except that one guy in Minnesota".