Python threads run in parallel when in Docker container, but run sequentially when container is run on Google Cloud Run

By -

first post on SO, let me know how I can improve my question.

1. Summary

Goal: My app is a Craigslist scraper, it finds new posts and sends the feed to the user's email. It has a main thread that always listens to requests, and a worker thread, managed by the main thread, and is either working or sleeping.

Expected vs Actual Results: As mentioned in the title, the app works fine in the container locally, but when it's hosted on Cloud Run, the output and side-effects of the worker thread are deferred until the worker thread is killed.

It seems like the worker thread is only started when the main thread calls to kill it, at which point the worker thread only does one iteration of its work and then kills itself.

No errors messages.

2. What I've tried.

I've tried changing some of the Cloud Run container environment settings, like increasing amount of memory and number of vCPUs.

settings

Please let me know what additional information would help.



from Recent Questions - Stack Overflow https://ift.tt/3raZFyz
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more