Setting the requestTimeout="00:20:00" in the web. Our Connection string "DefaultConnection": "Data Source=server_name_here,port_number_here Initial Catalog=db_name_here Integrated Security=False Persist Security Info=False User ID=user_name_here Password=password_here OptionsBuilder.UseSqlServer(connectionString, sqlServerOptions => sqlServerOptions.CommandTimeout(900)) From what I can see our NGINX ingress controller returns 504 to the client after a request takes more than 60s to process. When a request takes over 60s to respond it seems that the ingress controller will bounce. Var connectionString = configuration.GetConnectionString("DefaultConnection") NGINX ingress controller timing out request after 60s. SetBasePath(Directory.GetCurrentDirectory()) IConfigurationRoot configuration = new ConfigurationBuilder() We have tried setting the CommandTimeout to 900 seconds as below protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder) This query fetches data from many related tables using Include()įor large data we have noticed that the web service return a 504 Gateway Timeout. We have tried setting the CommandTimeout to 900 seconds as below. Important Note:- NGINX file may be located at /usr/local/nginx/conf, /etc/nginx, or /usr/local/etc/nginx depending on your installation. We make a call to the webservice via a POST request. This query fetches data from many related tables using Include () For large data we have noticed that the web service return a 504 Gateway Timeout. The Web Service communicates to an Microsoft SQL Server Express (64-bit) Database, version. This is hosted on an IIS Server on AWS Lightsail. As you may be aware, 504 Gateway Timeout error Nginx is generated often by a number of reasons on the backend connection that is serving content. if you get pods in the ingress-nginx namespace, youll likely see that your NGINX pod is restarting multiple times, or maybe even in a CrashLoopBackOff state. I have created a React Project using dotnetcore 3.1 Version. Because the liveness probe is failing, after 3 failed probes (the default-you dont have that overridden) the pod will be restarted by Kubernetes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |