Is anyone else having an issue with a lot of their datastore entities being "un-editable" in the Developers Console?
I always get this error when clicking on an entity ID:
We could not find an entity with namespace: "{NAMESPACE}", kind: "{KIND}", and identifier "id={ID}"
Google Issue Reported
Related
error [INTERNAL]: An internal error occurred while processing task /appengine-flex-v1/insert_flex_deployment/flex_create_resources>2020-05-22T15:14:57.416Z3210.jc.5: Deployment Manager operation thesis-lock/operation-1590160497681-5a63e1799a578-3c148be2-663d8bc4 errors: [code: "RESOURCE_ERROR"
location: "/deployments/aef-flex-20200522t171231/resources/aef-flex-20200522t171231"
message: \"ResourceType\":\"compute.beta.regionAutoscaler\",\"ResourceErrorCode\":\"403\",\"ResourceErrorMessage\":{\"code\":403,\"errors\":[{\"domain\":\"usageLimits\",\"message\":\"Exceeded limit \'QUOTA_FOR_INSTANCES\' on resource \'aef-flex-20200522t171231\'. Limit: 8.0\",\"reason\":\"limitExceeded\"}],\"message\":\"Exceeded limit \'QUOTA_FOR_INSTANCES\' on resource \'aef-flex-20200522t171231\'. Limit: 8.0\",\"statusMessage\":\"Forbidden\",\"requestPath\":\"https://compute.googleapis.com/compute/beta/projects/.../regions/asia-south1/autoscalers\",\"httpMethod\":\"POST\"}}"
I'm getting the aboveerror when trying to deploy my app to Google App Engine using gcloud app deploy.
I've been able to deploy previously without any problems or errors in exactly the same way. I haven't changed my app.yaml. I have checked my quota in the Console yet I can find no quota that have been exceeded. The documentation does not provide any insights.
Any ideas as to what I can do?
I have found some similar questions on SO, but none of them seem to point to this issue specifically and none of the proposed solutions to those questions seem to work.
Google is already aware of this, and the engineering team is working on it. There is an Issue Tracker thread that you can "star" to keep track of updates and follow-ups regarding this issue.
Current workaround: Switch from App Engine Flexible to Standard environment.
I am currently referring to google documentation for autoscaling using pubsub metric from stackdriver:
Autoscaling Deployments with External Metrics
But, I am getting some error in deploying google sample config present in above link/config link: Link to config image
Error: error validating data: ValidationError(HorizontalPodAutoscaler.spec.metrics[0]): unknown field "external" in io.k8s.api.autoscaling.v2beta1.MetricSpec; if you choose to ignore these errors, turn validation off with --validate=false
Looked around the web but was unable to find any reference to this error. I am not sure what is wrong.
Looks Like, There was a version error.
Previously i was using 1.9.7-gke.11 (Although note that this is default gke version right now )
Now with 1.10.9-gke.5 , Everything is working fine
Playing with Bookshelf tutorial and the Auth package.
The ListBooksCreatedBy query is failing with this error:
could not list books: datastoredb: could not list books: rpc error: code = FailedPrecondition desc = no matching index found. recommended index is:
- kind: Book
properties:
- name: CreatedByID
- name: Title
However, index.yaml does exist and is in the same directory as app.yaml :
index YAML content:
indexes:
# This index enables filtering by "CreatedByID" and sort by "Title".
- kind: Book
properties:
- name: CreatedByID
direction: asc
- name: Title
direction: asc
Why would the index not be imported?
Where in the Golang App Engine code is the index.yaml imported?
I searched the src and found nothing.
The index.yaml file is not intended to be imported/used in your application code, it is intended to be deployed to the Datastore service (separately/independently from your app deployments!) to configure its indexing activities. From Updating indexes:
You upload your index.yaml configuration file to Cloud Datastore
with the gcloud command. If the index.yaml file defines any indexes
that don't exist in Cloud Datastore, those new indexes are built.
It can take a while for Cloud Datastore to create all the indexes and
therefore, those indexes won't be immediately available to App Engine.
If your app is already configured to receive traffic, then exceptions
can occur for queries that require an index that is still in the
process of being built.
To avoid exceptions, you must allow time for all the indexes to build.
Only after proper deployment and, if needed, the completion of the index update operation (i.e. the index reaches the Serving state) the app's queries needing that index can work.
The index.yaml file is also used by the local development server in its datastore emulation. By default it automatically updates the file with the necessary indexes for the queries it encounters, but the file isn't automatically deployed to the Datastore. But you can disable this behaviour using the --require_indexes option. From Local Development Server Options:
--require_indexes=yes|no
Disables automatic generation of entries in the index.yaml file.
Instead, when the application makes a query that requires that its
index be defined in the file and the index definition is not found, an
exception will be raised, similar to what would happen when running on
App Engine. The default value is no.
Earlier today we started to see instances of server errors popping up on an old realtime document. This is a persistent error and the end result appears to be that the document is completely inaccessible using the gapi.drive.realtime.load endpoint. Not great.
However the same document is accessible through the gapi.client.drive.realtime.get endpoint. Which is great for data recovery, but not so great for actually using the document. It's possible I can 'fix' the document by doing a 'drive.realtime.update', but haven't tried as hopefully the doc can be used to track down the bug.
Document ID: 0B9I5WUIeAEJ1Y3NLQnpqQWVlX1U
App ID: 597847337936
500 Error Message: "Document was not successfully migrated to new UserKey format"
Anyone else seeing this issue? Can I provide any additional information?
Anybody knows how to allow non-utf8 for appengine datastore keys?
I am using appengine for go.
Below is the error i get if i put non-utf8.
API error 1 (datastore_v3: BAD_REQUEST): key path element name is not valid UTF-8
project member said it is a design decision:
https://code.google.com/p/googleappengine/issues/detail?id=12896
Thanks.