charlieevett commented on issue #153: URL: https://github.com/apache/pulsar-client-python/issues/153#issuecomment-1739732109
Sure, here is most of the uwsgi.ini file we use: `[uwsgi] http = :$(PORT) # Close connections because ELB expects sockets or keep-alives otherwise # http://uwsgi-docs.readthedocs.org/en/latest/HTTP.html#can-i-use-uwsgi-s-http-capabilities-in-production add-header = Connection: close master = true processes = $(PROCESSES) die-on-term = true memory-report = true vacuum=True log-x-forwarded-for=True log-format = %(addr) - %(user) [%(ltime)] "%(method) %(uri) %(proto)" %(status) %(size) ("%(referer)" "%(uagent)" | %(msecs) listen = 128 threads = true # Worker Management max-requests = 750 ; Restart workers after this many requests max-worker-lifetime = 1800 ; Restart workers after this many seconds reload-on-rss = 256 ; Restart workers after this much resident memory worker-reload-mercy = 60 ; How long to wait before forcefully killing workers ` uwsgi is run using a very basic command in a Docker container: `uwsgi uwsgi.ini` The issue we're seeing is with the max-requests or max-worker-lifetime handling, when these limits are hit and uwsgi kills the worker process, it will often segfault during the exit. Relaunching process is fine, so the main issue is the file system filling up with core files. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
