Summary of solving the problem of downloading Java service by k8s

Problem description:

When we go to the Java program of ingress, we often have the function of exporting data. At this time, the download timeout will be caused by slow network and long background processing time, and the download failure will be caused by too large download files. The comprehensive solution is as follows

Edit ingress

metadata:
  annotations:
    /fastcgi-buffer-size: 128k
    /fastcgi-buffers: 4 128k
    /fastcgi-busy-buffers-size: 256k
    /fastcgi-temp-file-write-size: 256k
    /proxy-buffering: 'on'
    /proxy-connect-timeout: '600'
    /proxy-read-timeout: '600'
    /proxy-send-timeout: '600'

in
1) Change the reverse proxy timeout time

    /proxy-buffering: 'on'
    /proxy-connect-timeout: '600'
    /proxy-read-timeout: '600'
    /proxy-send-timeout: '600'

2) Change the cache size

    /fastcgi-buffer-size: 128k
    /fastcgi-buffers: 4 128k
    /fastcgi-busy-buffers-size: 256k
    /fastcgi-temp-file-write-size: 256k
    /proxy-buffering: 'on'

This is the article about k8s solving the timeout problem of java service download. For more related content on k8s java service download timeout, please search for my previous article or continue browsing the related articles below. I hope everyone will support me in the future!