request-timeout | Like setTimeout but using requestAnimationFrame

I know that for GCP cloud scheduler the max timeout is around 20 minutes for a HTTP request source.

Is it somehow possible, on GCP (perhaps using a different service) for me to invoke an HTTP endpoint, that takes around 65 minutes to respond, every ~6 hours?

I want a Ingress, that routes host.com/abc/xyz to service/xyz. I have the following configuration but its routing host.com/abc/xyz to service/abc/xyz.

Project Description

I'm working on a NodeJS/Express application that, on loading the home page, uses Fetch to call a route that makes an API request. The data retrieved from the API request is returned to the client into a dropdown.

Problem

The API request often takes longer than 2 minutes to return a response, which causes Fetch to timeout with a 504 Gateway Timeout. It's my understanding the default timeout for Express is 2 minutes, so I've tried numerous ways to increase this timeout but have had no luck. It may be worth noting that I only get these timeout errors when testing the deployed code. When I test by running the code locally, I get no errors, and the 2 minute timeout does not appear to exist. Enforcing a timeout using some of the attempts below would cause a timeout when running locally.

Fix Attempts

1. Using the Express connect-timeout middleware as described here. I tested as a top-level middleware, and within the route itself.

2. Setting the server timeout after the app.listen() function:

   ...

I need to Timeout the request if no response is received in 5s. I tried server.tomcat.connection-timeout, but No Luck.

I am aware of spring.mvc.async.request-timeout property using Callable, but server.tomcat.connection-timeout should work ,right?

application.properties

I tried defining request.timeout.ms property in following 2 ways :-

application.properties

I have my own webshop set up with a payment provider and to finalize the buy they send me a post to a page with some data for me to acknowledge the order.

The problem is that when they do the request it returns a 406 error for them. This is what i could find in the logs

I have Django project. It works with nginx, uwsgi and google cloud run. This project is using docker which python:3.9 image. I have got this error since 17,Aug.

2021-10-13 17:22:29.654 JSTGET504717 B899.9 sGoogleStackdriverMonitoring-UptimeChecks(https://cloud.google.com/monitoring) https://xxxx/

The request has been terminated because it has reached the maximum request timeout. To change this limit, see https://cloud.google.com/run/docs/configuring/request-timeout

and also this error occur on all my pages. However when I open my pages myself, I can see my pages. It means I can't see 504 error and I can only check that it happens from server log.

I added a line in admin.py at 17, Aug. I didn't think this line is no related with this error. Because this change is only effect in admin page. I had rollback my code before the error. Now I'm still can't fix this error.

Builded docker image is different size before after error. And Vulnerability has decreased. I think this is caused by some small change on python image. In this case, how can I solve this problem?

I changed docker image to python:3.8 and python:3.9.6-buster. I couldn't fix the error.

I have a Flask app deployed on Heroku, and I'm using Celery+Redis for async processing. The test page doesn't load when I send a request, and I receive this error:

There is a keyspace occupying 55tb of space, cluster has 66 nodes in it (dse 5.1.6, cassandra 3.11) The keyspace has 3 tables in it and there are no reads/writes on the tables since last one month.

Want to drop the keyspace/tables to reclaim space without causing any issues in the cluster?

1. When dropping tables and keyspace on this cluster - what might cause issues? the size of the unused keyspace (55tb) or the number of nodes (66) in the cluster to which the schema change (drop tables/keyspace) would would need to be propagated?
2. Other than dropping tables and then keyspace is there any other way to safely drop the keyspace? For example would dropping the sstables from nodes make drops quick and smoother? Would dropping sstables trigger repairs/compactions and cause any issues?
3. Is there any way to disable auto_snapshot at session level or from a driver level for specific tables or keyspace?
4. Any considerations before/after dropping the tables/keyspace? here are the steps I am going to follow - a. nodetool describecluster b. drop tables using cqlsh (with request-timeout=600) c. drop keyspace using cqlsh (with request-timeout=600) d. nodetool describecluster, check for any inconsistencies e. From each node delete the data directory for the keyspace (data is already backed up somewhere, there is no need of autosnapshot)