[google-appengine] Re: When/Where to create index and add documents for Search API - Java

[Akash Eldo]

I'm using Firebase Firestore, but I think it has  similar callbacks. 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0bfeec98-e60d-4e9c-8913-14a5328baf77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: When/Where to create index and add documents for Search API - Java

[Jim]

Are you using Cloud Datastore?  If so, you can use Datastore Callbacks and 
define "put" and "delete" callback functions on specific kinds.  Whenever 
an entity is put or deleted your callback functions will be called and you 
can do your index updates there.

https://cloud.google.com/appengine/docs/standard/java/datastore/callbacks





On Saturday, December 29, 2018 at 11:34:29 AM UTC-6, Akash Eldo wrote:
>
> I'm creating a Java web server on the Google App Engine to do full text 
> search on my database. Before I can search, I have to add all my database 
> entries to an index. I should only have to do this once because the index 
> is stored in persistent storage. Even if GCP creates a new instance of my 
> Java server, the index should still be there (right?).
>
>
> My question is, how do I set up my program so it will only create the 
> index once? I've tried using Warming Services, but as I understand it that 
> will be called every time a new instance is created, so there'd be 
> redundant calls to my index creation code
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/58f621c0-6b0e-4ecb-8cff-860579e38a7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Custom domains missing

[Srinivasu Kota]

almost 6 years back i have migrated my appengine app from xyz to xyz-hrd 
(for example)

as part of migration google didn't move custom domains to xyz-hrd, but they 
are still present to xyz appid

i found they are still present using gcloud command for xyz domain.

gcloud app domain-mappings list


i could not delete them as it gives this error


ERROR: (gcloud.app.domain-mappings.delete) NOT_FOUND: The AppId that you are 
looking for has been deleted


but xyz-hrd doesn't list them as well..


i need to add SSL certificate, how can i do that.


also there is another unknown custom domain is added to my account not sure who 
has added it, but i couldn't delete it even though i am owner of the app-id


please help me to fix this problem. I don't have any premium support. It looks 
like it is problem of migration script few years ago and we have not noticed it 
till now.


Thanks


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8db79d95-3064-4b4f-864b-8b37a19d2fe3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[Shiva Wu]

So I guess no update on the load balancer update speed, huh? It has been 
more than a year...

On Wednesday, 5 April 2017 16:28:11 UTC-7, Nick (Cloud Platform Support) 
wrote:
>
> Hey Stanislas,
>
> So, I can confirm that my prior investigation and intuitions were on the 
> right track. I can confirm that a majority of deployment lag comes from 
> programming the Google Cloud Load Balancers (GCLB). This is what we've seen 
> in this case. Updates have to go out across the entire infrastructure while 
> still respecting certain locks used to keep configurations consistent. 
> These Load Balancers are not visible to users in the Console and not 
> user-configurable as they're infrastructural and meant to be exactly as 
> they are, else users may try to modify or accidentally delete them, which 
> would cause a lot of issues.
>
> We're devoting a lot of energy to decreasing GCLB configuration push 
> times, so rest assured that our efforts in that direction should pay off 
> going forward.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Tuesday, March 21, 2017 at 6:41:52 PM UTC-4, Stanislas Marion wrote:
>>
>> Great, thank you so much for your help, I'll be very interested in the 
>> details you'll get from your investigation.
>>
>> On Tue, Mar 21, 2017 at 9:22 PM 'Nick (Cloud Platform Support)' via 
>> Google App Engine > wrote:
>>
>>> Hey Stanislas,
>>>
>>> The exact explanation speculated on in my last post shouldn't be taken 
>>> as any description of what's necessarily going on, however it was an 
>>> estimate of what might be happening based on the logs observed. I'm 
>>> corresponding with experts in this area to get a more clear answer at the 
>>> moment. 
>>>
>>> You could look into deploying on Container Engine 
>>> , which would mean that the 
>>> front-end management done by the App Engine Flexible Environment 
>>> infrastructure wouldn't be happening, rather it would be the responsibility 
>>> of the resources you deploy on Container Engine (a managed service based 
>>> pretty transparently on Kubernetes ). Surely 
>>> deploying new container images to your pool of instances in a cluster (or 
>>> multiple clusters) would be quite fast, since the master sitting in front 
>>> of your clusters and the nodes in the cluster are not as massively 
>>> distributed as the App Engine Flexible Environment serving infrastructure, 
>>> hence updating their routing rules would be relatively fast. This is 
>>> something to look into and experiment with if you don't want to wait on the 
>>> more detailed word from experts, but don't rush to that if you're not all 
>>> that curious.
>>>
>>> I'll get back to this thread with more details when they're forthcoming 
>>> in our investigation.
>>>
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support 
>>>
>>> On Tuesday, March 21, 2017 at 3:50:34 PM UTC-4, Stanislas Marion wrote:

 Hi Nick,
 Thanks a lot for the lengthy explanation. 
 In this light, is there anything I can do to speed things up? Like for 
 instance take care of the load-balancer myself? Indeed I don't see a 
 reason 
 why it should need to be changed. Could I do this with GAE or would I have 
 to move to G Container/Compute E?
 Cheers,

 On Tue, Mar 21, 2017 at 8:42 PM 'Nick (Cloud Platform Support)' via 
 Google App Engine > wrote:

> Hey Stanislas,
>
> My initial hunch was that the issue was the deployment of other 
> resources necessary to support the containers running. My analysis of 
> deployment-related logs appears to confirm this:
>
> I created a simple NodeJS app using your dockerfile and default.yaml. 
> I then pushed the docker image to gcr.io and ran "gcloud app deploy 
> --image-url ..."
>
> After about 1 minute of waiting, all resources associated with the 
> deployment had apparently completed, but the command had not returned yet:
>
> ```
> $ gcloud deployment-manager resources list --deployment 
> aef-default-20170321t185300
>
> NAME   TYPE   
>   STATE  ERRORS  INTENT
> aef-default-20170321t185300-00 
> compute.beta.regionInstanceGroupManager  COMPLETED  []
> aef-default-20170321t185300-00ahs  compute.v1.httpsHealthCheck 
>  COMPLETED  []
> aef-default-20170321t185300-00it   compute.v1.instanceTemplate 
>  COMPLETED  []
> aef-default-20170321t185300-bs compute.v1.backendService   
>  COMPLETED  []
> aef-default-20170321t185300-hcfw   compute.v1.firewall 
>  COMPLETED  []
> aef-default-20170321t185300-hcscompute.v1.httpsHealthCheck 
>  COMPLETED  []
> ```
>
> At around the same time that the last of the above completed, I see 
> the following in the Console logs

[google-appengine] When/Where to create index and add documents for Search API - Java

[Akash Eldo]

I'm creating a Java web server on the Google App Engine to do full text 
search on my database. Before I can search, I have to add all my database 
entries to an index. I should only have to do this once because the index 
is stored in persistent storage. Even if GCP creates a new instance of my 
Java server, the index should still be there (right?).


My question is, how do I set up my program so it will only create the index 
once? I've tried using Warming Services, but as I understand it that will 
be called every time a new instance is created, so there'd be redundant 
calls to my index creation code

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/48ba78d2-d728-42e7-ae7a-dee84c389358%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] When/Where to create index for Search API - Java

[Akash Eldo]

I'm creating a Java web server on the Google App Engine to do full text 
search on my database. Before I can search, I have to add all my database 
entries to an index. I should only have to do this once because the index 
is stored in persistent storage. Even if GCP creates a new instance of my 
Java server, the index should still be there(right?).


My question is, how do I set up my program so it will only create the index 
once? I've tried using Warming Services, but as I understand it that will 
be called every time a new instance is created, so there'd be redundant 
calls to my index creation code

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/76a3e6de-24b9-437c-9ed8-772f536a2c30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

[Shiva Wu]

So I guess no update on the GCLB deployment speed, huh? It has been more 
than a year...

On Wednesday, 5 April 2017 16:28:11 UTC-7, Nick (Cloud Platform Support) 
wrote:
>
> Hey Stanislas,
>
> So, I can confirm that my prior investigation and intuitions were on the 
> right track. I can confirm that a majority of deployment lag comes from 
> programming the Google Cloud Load Balancers (GCLB). This is what we've seen 
> in this case. Updates have to go out across the entire infrastructure while 
> still respecting certain locks used to keep configurations consistent. 
> These Load Balancers are not visible to users in the Console and not 
> user-configurable as they're infrastructural and meant to be exactly as 
> they are, else users may try to modify or accidentally delete them, which 
> would cause a lot of issues.
>
> We're devoting a lot of energy to decreasing GCLB configuration push 
> times, so rest assured that our efforts in that direction should pay off 
> going forward.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Tuesday, March 21, 2017 at 6:41:52 PM UTC-4, Stanislas Marion wrote:
>>
>> Great, thank you so much for your help, I'll be very interested in the 
>> details you'll get from your investigation.
>>
>> On Tue, Mar 21, 2017 at 9:22 PM 'Nick (Cloud Platform Support)' via 
>> Google App Engine > wrote:
>>
>>> Hey Stanislas,
>>>
>>> The exact explanation speculated on in my last post shouldn't be taken 
>>> as any description of what's necessarily going on, however it was an 
>>> estimate of what might be happening based on the logs observed. I'm 
>>> corresponding with experts in this area to get a more clear answer at the 
>>> moment. 
>>>
>>> You could look into deploying on Container Engine 
>>> , which would mean that the 
>>> front-end management done by the App Engine Flexible Environment 
>>> infrastructure wouldn't be happening, rather it would be the responsibility 
>>> of the resources you deploy on Container Engine (a managed service based 
>>> pretty transparently on Kubernetes ). Surely 
>>> deploying new container images to your pool of instances in a cluster (or 
>>> multiple clusters) would be quite fast, since the master sitting in front 
>>> of your clusters and the nodes in the cluster are not as massively 
>>> distributed as the App Engine Flexible Environment serving infrastructure, 
>>> hence updating their routing rules would be relatively fast. This is 
>>> something to look into and experiment with if you don't want to wait on the 
>>> more detailed word from experts, but don't rush to that if you're not all 
>>> that curious.
>>>
>>> I'll get back to this thread with more details when they're forthcoming 
>>> in our investigation.
>>>
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support 
>>>
>>> On Tuesday, March 21, 2017 at 3:50:34 PM UTC-4, Stanislas Marion wrote:

 Hi Nick,
 Thanks a lot for the lengthy explanation. 
 In this light, is there anything I can do to speed things up? Like for 
 instance take care of the load-balancer myself? Indeed I don't see a 
 reason 
 why it should need to be changed. Could I do this with GAE or would I have 
 to move to G Container/Compute E?
 Cheers,

 On Tue, Mar 21, 2017 at 8:42 PM 'Nick (Cloud Platform Support)' via 
 Google App Engine > wrote:

> Hey Stanislas,
>
> My initial hunch was that the issue was the deployment of other 
> resources necessary to support the containers running. My analysis of 
> deployment-related logs appears to confirm this:
>
> I created a simple NodeJS app using your dockerfile and default.yaml. 
> I then pushed the docker image to gcr.io and ran "gcloud app deploy 
> --image-url ..."
>
> After about 1 minute of waiting, all resources associated with the 
> deployment had apparently completed, but the command had not returned yet:
>
> ```
> $ gcloud deployment-manager resources list --deployment 
> aef-default-20170321t185300
>
> NAME   TYPE   
>   STATE  ERRORS  INTENT
> aef-default-20170321t185300-00 
> compute.beta.regionInstanceGroupManager  COMPLETED  []
> aef-default-20170321t185300-00ahs  compute.v1.httpsHealthCheck 
>  COMPLETED  []
> aef-default-20170321t185300-00it   compute.v1.instanceTemplate 
>  COMPLETED  []
> aef-default-20170321t185300-bs compute.v1.backendService   
>  COMPLETED  []
> aef-default-20170321t185300-hcfw   compute.v1.firewall 
>  COMPLETED  []
> aef-default-20170321t185300-hcscompute.v1.httpsHealthCheck 
>  COMPLETED  []
> ```
>
> At around the same time that the last of the above completed, I see 
> the following in the Console logs when

[google-appengine] ImportError: No module named google.oauth2

[zi yang]

I use thedev_appserver.py to start my project, but it gives me this 
error:

ImportError: No module named google.oauth2  

But I have installed those modules:

[image: 微信图片_20181228215104.png]
   

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/92b6fe96-51b5-4d64-beb7-85679ef16a74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.