-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fileDescriptorLimit could not set according to system default value #1158
Comments
Thanks for your issue 😀
I'm not aware that native-packager scripts mess with any file limit settings. |
* soft nofile 1000000
* hard nofile 1000000
addSbtPlugin("com.typesafe.sbt" % "sbt-native-packager" % "1.2.0")
enablePlugins(RpmPlugin, JavaServerAppPackaging, SystemdPlugin)
|
Thanks for the more detailed explanation 😄 At the moment we don't have conditional template replacements. This is the systemd template that renders the systemd service conf. Is there a "magic" value that says "use system default"? I haven't had any issue with file descriptor limits. What's the use case for making this limit not application specific? |
I catch this case by a bug, In our application, HttpClient jar is used to call RESTFUL API, unfortunately, after running period of time, app throws "too many files open" exception. |
Thanks for sharing 🤗 I guess then there's no need to configure this in another way, right? |
maybe |
Systemd ignores limits from places like limits.conf. |
Expected behaviour
when packaging, sbt-native-packager will use default value of fileDescriptorLimit or use user defined. If is it possible to use the ulimit value of app running machine?
for example, I package using the default value (1024), but the app running machine is 100000, when I check /proc/PID/limits, the "Max open files" is 1024, not 100000.
If I set a fixed value, the app will run on different machines, and their system "max open files" are different. Maybe it is unreasonable to use a fixed value when packaging
The text was updated successfully, but these errors were encountered: